mirror of
https://gitlab.freedesktop.org/pipewire/pipewire
synced 2024-09-20 00:11:31 +00:00
fca3e1d85d
Do not use dynamic types anymore. The reason is that it's difficult: - to maintain a shared type database over a network. - the extra overhead when translating between processes and for maintaining the translation tables. - race conditions in translating in RT-threads, this is a problem because we want to make event streams. We now have simple enums with types and extension points for all types. This is also nicer to use in general. We don't need the mapper anymore or pass strings around as types. There is a parallel type info system to get more info about ids and enums and their hierarchy. It can also be used for debugging. |
||
---|---|---|
doc | ||
man | ||
pkgconfig | ||
po | ||
spa | ||
src | ||
.gitignore | ||
_config.yml | ||
autogen.sh | ||
config.h.meson | ||
git-version-gen | ||
GPL | ||
LGPL | ||
LICENSE | ||
Makefile.in | ||
meson.build | ||
meson_options.txt | ||
NEWS | ||
PROTOCOL | ||
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