mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2025-10-31 22:25:38 -04:00
readme: add section on building with make or meson
Add a short paragraph to indicate that there are two methods to build pipewire. Signed-off-by: Harry van Haaren <harryhaaren@gmail.com>
This commit is contained in:
parent
6a0ee7a298
commit
ac37d0f180
1 changed files with 19 additions and 0 deletions
19
README
19
README
|
|
@ -13,3 +13,22 @@ pipelines. This includes:
|
||||||
Nodes in the graph can be implemented as separate processes,
|
Nodes in the graph can be implemented as separate processes,
|
||||||
communicating with sockets and exchanging multimedia content using fd
|
communicating with sockets and exchanging multimedia content using fd
|
||||||
passing.
|
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
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue