From: "Théo Lebrun via buildroot" <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: "James Hilliard" <james.hilliard1@gmail.com>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>
Subject: [Buildroot] [PATCH 3/3] package/pipewire: add optional roc
Date: Thu, 10 Mar 2022 16:20:48 +0100 [thread overview]
Message-ID: <20220310152048.633340-3-theo.lebrun@bootlin.com> (raw)
In-Reply-To: <20220310152048.633340-1-theo.lebrun@bootlin.com>
Roc is a toolkit for real-time audio streaming over the network, that
can be used as a PipeWire module.
Successful if libpipewire-module-roc-{sink,source}.so get built.
Signed-off-by: Théo Lebrun <theo.lebrun@bootlin.com>
---
package/pipewire/pipewire.mk | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/package/pipewire/pipewire.mk b/package/pipewire/pipewire.mk
index fc521c86ac..de27bce10c 100644
--- a/package/pipewire/pipewire.mk
+++ b/package/pipewire/pipewire.mk
@@ -189,6 +189,13 @@ else
PIPEWIRE_CONF_OPTS += -Draop=disabled
endif
+ifeq ($(BR2_PACKAGE_ROC),y)
+PIPEWIRE_CONF_OPTS += -Droc=enabled
+PIPEWIRE_DEPENDENCIES += roc
+else
+PIPEWIRE_CONF_OPTS += -Droc=disabled
+endif
+
define PIPEWIRE_USERS
pipewire -1 pipewire -1 * - - audio,video PipeWire System Daemon
endef
--
2.35.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-03-10 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 15:20 [Buildroot] [PATCH 1/3] package/ragel: new package Théo Lebrun via buildroot
2022-03-10 15:20 ` [Buildroot] [PATCH 2/3] package/roc: " Théo Lebrun via buildroot
2022-04-20 21:28 ` Yann E. MORIN
2022-03-10 15:20 ` Théo Lebrun via buildroot [this message]
2022-04-20 20:57 ` [Buildroot] [PATCH 1/3] package/ragel: " Yann E. MORIN
2022-04-20 21:07 ` Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220310152048.633340-3-theo.lebrun@bootlin.com \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.