mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-10-31 22:25:38 -04:00
Multimedia processing graphs
We can initialize the transport as soon as we get async notify from the client when setup completes. Node initialization happens after that and then finaly the node is initialized and we can send the transport and fds. Small cleanups |
||
|---|---|---|
| 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