RE: [oe] [meta-multimedia][PATCHv7] pipewire: update to v0.3.56

[Peter Kjellerstedt <peter.kjellerstedt@axis.com>]

[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]

I still don't understand how you intend for a "gstreamer" distro feature to work. You use it in the pipewire recipe to decide whether to use the "gstreamer" or "ffmpeg" PACKAGECONFIG by default. However, that seems very specific to pipewire. We use both GStreamer and FFmpeg in our products, so using a distro feature to distinguish between them is not something universal.

//Peter

From: Markus Volk <f_l_k@t-online.de>
Sent: den 21 augusti 2022 16:01
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: RE: [oe] [meta-multimedia][PATCHv7] pipewire: update to v0.3.56


i tried to follow your suggestions,
Thanks

Am So, 21. Aug 2022 um 12:49:24 +0000 schrieb Peter Kjellerstedt <peter.kjellerstedt@axis.com<mailto:peter.kjellerstedt@axis.com>>:

AFAIK, there are no current examples of "gstreamer" being used a distro feature. What is it supposed to mean? When is it supposed to be used? Why is it needed?


I found an example of this, but I must confess that this was in an old third-party layer. What I want this DISTRO_FEATURE for is the ability to use it to enable/disable gstreamer support in recipes. Not just here in pipewire. The same goes for Jack. Is this already used as a DISTRO_FEATURE? If so, maybe we could use it to make the Jack server depend on it instead of always building it as it currently does?

[-- Attachment #2: Type: text/html, Size: 4520 bytes --]