mirror of
https://gitlab.freedesktop.org/pipewire/pipewire
synced 2024-09-20 00:11:31 +00:00
1d1f035e78
Pass a factory_name in the object_info of monitor and device. Restructure the factory name to mean something functionaly. With the factory to library mapping this then means that the implementation of certain factories can be configured in the config file. |
||
---|---|---|
doc | ||
man | ||
pipewire-alsa@d81bbae7ea | ||
pipewire-jack@8646c49760 | ||
pipewire-pulseaudio@531185845a | ||
po | ||
spa | ||
src | ||
.editorconfig | ||
.gitignore | ||
.gitmodules | ||
.travis.yml | ||
_config.yml | ||
autogen.sh | ||
check_missing_headers.sh | ||
config.h.meson | ||
COPYING | ||
LICENSE | ||
Makefile.in | ||
meson.build | ||
meson_options.txt | ||
NEWS | ||
PROTOCOL | ||
pw-uninstalled.sh | ||
README |
PipeWire -------- PipeWire is a server and user space API to deal with multimedia pipelines. This includes: - Making available sources of video (such as from a capture devices or application provided streams) and multiplexing this with clients. - Accessing sources of video for consumption. - Generating graphs for audio and video processing. Nodes in the graph can be implemented as separate processes, communicating with sockets and exchanging multimedia content using fd passing. Building -------- Pipewire uses the Meson and Ninja build system to compile. If you're not familiar with these tools, the included "autogen.sh" script will automatically run the correct meson/ninja commands, and output a Makefile. It follows that there are two methods to build Pipewire, however both rely on Meson and Ninja to actually perform the compilation: $ ./autogen.sh $ make or the Meson/Ninja native method: $ meson build $ cd build $ ninja You can see the available meson options in meson_options.txt file.