INSTALL.md: Add WIREPLUMBER_DEBUG env variable
Without this, new developers, unfamiliar with pipewire/wireplumber architecture, can easily be confused about why their debug messages are not showing up.
This commit is contained in:
parent
8aaba4fec3
commit
4ef891b047
|
@ -71,12 +71,12 @@ This will use the default config file to configure and start the daemon.
|
||||||
The default config will also start `pipewire-media-session`, a default
|
The default config will also start `pipewire-media-session`, a default
|
||||||
example media session and `pipewire-pulse`, a PulseAudio compatible server.
|
example media session and `pipewire-pulse`, a PulseAudio compatible server.
|
||||||
|
|
||||||
You can also enable more debugging with the `PIPEWIRE_DEBUG` environment
|
You can also enable more debugging with the `PIPEWIRE_DEBUG` and
|
||||||
variable like so:
|
`WIREPLUMBER_DEBUG` environment variables like so:
|
||||||
|
|
||||||
```
|
```
|
||||||
cd builddir/
|
cd builddir/
|
||||||
PIPEWIRE_DEBUG="D" make run
|
PIPEWIRE_DEBUG="D" WIREPLUMBER_DEBUG="D" make run
|
||||||
```
|
```
|
||||||
|
|
||||||
You might have to stop the pipewire service/socket that might have been
|
You might have to stop the pipewire service/socket that might have been
|
||||||
|
|
Loading…
Reference in New Issue