GitLab

* Use custom_target() instead of configured shell scripts
* Do not copy all the .rst files in the build directory
* Setup dependencies between targets
* Tidy up dependencies lookup
* Remove unused files
* Upgrade Doxyfile to the latest version and cleanup used options

Makes sure links are activated before starting scanning again.

invalidation may destroy the closure and this will trigger
_wplua_closure_finalize(), which will remove the closure from the
array while the original code is also trying to do the same

if we destroy the closure after it has been removed from the
array, _wplua_closure_finalize() will not remove anything and
will continue happily

Not used and not useful with the current design.
May be reverted in the future, if necessary.

We have ended up not using them, so let's not carry them
in the ABI of 0.4

We can always revert that, but let's first decide how
these objects should be used

Sometimes the default device node might not exist when reevaluating endpoints
for the first time on startup, so the policy would link endpoints to another
device node. Then, the default device node appears and the policy moves the
endpoints to the default device node while the previous link has not finish its
activation yet. This race condition can cause endpoint links to fail when being
activated. Delaying the reevaluation of endpoint links until the first client
link is created avoids this issue.

Allows relinking client nodes to other devices if the current device has been
removed. This allows audio to keep playing in a different device if a bluetooth
device is disconnected.

Some audio nodes such as null-audio-sink nodes don't support Props or Route enum
params.

Always remove the task from the list before returning to make sure it will
always be triggered once.

Fixes possible race condition when setting adapter ports format in the callback
of a previous adapter ports format call.

This allows to run WirePlumber preferably when pipewire-media-session is
also installed.

Allows handling errors if creation fails

George Kiagiadakis authored Apr 28, 2021 and Julian Bouzas committed May 13, 2021

These are also printed by libpipewire on the DEBUG level
and they are really not that harmful, so we don't need to spam
users with "failed" messages and alarm them

George Kiagiadakis authored Apr 28, 2021 and Julian Bouzas committed May 13, 2021

Add a unit test for this. Create a link with invalid nodes and expect
the activation transition to error out.

the "long" type in spa-pod is int64_t, so we need to make sure we
pass a 64-bit number there, otherwise the va_args is going to crash
on some architectures while reading arguments off the stack