Find a file
George Kiagiadakis a63f2bb99b lib/wp: merge both WpRemote & WpRemotePipewire in WpCore
In practice we always create a remote and connect to pipewire.
Any other scenario is invalid, therefore, it is not justified
to be confused with so many classes for such small functionality.
This simplifies a lot the modules code.

Also, this commit exposes the pw_core and pw_remote objects
out of WpCore. This is in practice useful when dealing with low-level
pw and spa factories, which are used in the monitors. Let's not
add API wrappers for everything... Bindings will never use this
functionality anyway, since it depends on low level pipewire C API.
2019-09-07 17:55:46 +03:00
lib lib/wp: merge both WpRemote & WpRemotePipewire in WpCore 2019-09-07 17:55:46 +03:00
modules lib/wp: merge both WpRemote & WpRemotePipewire in WpCore 2019-09-07 17:55:46 +03:00
src lib/wp: merge both WpRemote & WpRemotePipewire in WpCore 2019-09-07 17:55:46 +03:00
tests lib/wp: merge both WpRemote & WpRemotePipewire in WpCore 2019-09-07 17:55:46 +03:00
.editorconfig Add a sample config file and a Makefile to make running (for testing) easier 2019-05-17 13:34:33 +03:00
LICENSE Relicense to MIT 2019-05-31 12:13:12 +03:00
Makefile tests: add unit test skeleton and a test for WpProperties 2019-08-24 16:19:12 +03:00
meson.build modules: port to new WpProxy API 2019-08-29 21:21:33 +03:00
meson_options.txt meson: add option to disable gobject introspection 2019-06-20 15:48:29 +03:00
README.md add README.md 2019-04-12 12:50:37 +03:00

WirePlumber

WirePlumber is a session / policy manager implementation for PipeWire.