* [meta-multimedia][PATCH] pipewire: Add glib-2.0-native dep for bluez5
@ 2024-11-24 16:54 AmateurECE
2024-11-29 23:28 ` [oe] " Khem Raj
0 siblings, 1 reply; 4+ messages in thread
From: AmateurECE @ 2024-11-24 16:54 UTC (permalink / raw)
To: openembedded-devel; +Cc: Ethan D. Twardy
The SPA plugins for bluez depend on D-Bus bindings generated using
gdbus-codegen at build time. Some PACKAGECONFIG combinations appear to
pull this in accidentally. Add an explicit dependency to ensure that
it's in the sysroot when PACKAGECONFIG contains bluez5.
Signed-off-by: Ethan D. Twardy <ethan.twardy@gmail.com>
diff --git a/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.0.5.bb b/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.0.5.bb
index c8ac04d59..1c51fcc15 100644
--- a/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.0.5.bb
+++ b/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.0.5.bb
@@ -96,7 +96,7 @@ PACKAGECONFIG:class-target ??= " \
# as being in conflict.
PACKAGECONFIG[alsa] = "-Dalsa=enabled,-Dalsa=disabled,alsa-lib udev,,pipewire-alsa pipewire-alsa-card-profile"
PACKAGECONFIG[avahi] = "-Davahi=enabled,-Davahi=disabled,avahi"
-PACKAGECONFIG[bluez] = "-Dbluez5=enabled,-Dbluez5=disabled,bluez5 sbc"
+PACKAGECONFIG[bluez] = "-Dbluez5=enabled,-Dbluez5=disabled,bluez5 sbc glib-2.0-native"
PACKAGECONFIG[bluez-aac] = "-Dbluez5-codec-aac=enabled,-Dbluez5-codec-aac=disabled,fdk-aac"
PACKAGECONFIG[bluez-opus] = "-Dbluez5-codec-opus=enabled,-Dbluez5-codec-opus=disabled,libopus"
PACKAGECONFIG[bluez-lc3] = "-Dbluez5-codec-lc3=enabled,-Dbluez5-codec-lc3=disabled,liblc3"
--
2.45.2
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [oe] [meta-multimedia][PATCH] pipewire: Add glib-2.0-native dep for bluez5
2024-11-24 16:54 [meta-multimedia][PATCH] pipewire: Add glib-2.0-native dep for bluez5 AmateurECE
@ 2024-11-29 23:28 ` Khem Raj
2024-12-03 15:03 ` AmateurECE
0 siblings, 1 reply; 4+ messages in thread
From: Khem Raj @ 2024-11-29 23:28 UTC (permalink / raw)
To: ethan.twardy; +Cc: openembedded-devel
Thanks for the patch, it is not done on top of master it seems. Please
rebase it on master and resend if patch is needed for master
otherwise mark the release branch in subject prefix. This will help
route it correctly.
On Fri, Nov 29, 2024 at 11:57 AM AmateurECE via lists.openembedded.org
<ethan.twardy=gmail.com@lists.openembedded.org> wrote:
>
> The SPA plugins for bluez depend on D-Bus bindings generated using
> gdbus-codegen at build time. Some PACKAGECONFIG combinations appear to
> pull this in accidentally. Add an explicit dependency to ensure that
> it's in the sysroot when PACKAGECONFIG contains bluez5.
>
> Signed-off-by: Ethan D. Twardy <ethan.twardy@gmail.com>
>
> diff --git a/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.0.5.bb b/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.0.5.bb
> index c8ac04d59..1c51fcc15 100644
> --- a/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.0.5.bb
> +++ b/meta-multimedia/recipes-multimedia/pipewire/pipewire_1.0.5.bb
> @@ -96,7 +96,7 @@ PACKAGECONFIG:class-target ??= " \
> # as being in conflict.
> PACKAGECONFIG[alsa] = "-Dalsa=enabled,-Dalsa=disabled,alsa-lib udev,,pipewire-alsa pipewire-alsa-card-profile"
> PACKAGECONFIG[avahi] = "-Davahi=enabled,-Davahi=disabled,avahi"
> -PACKAGECONFIG[bluez] = "-Dbluez5=enabled,-Dbluez5=disabled,bluez5 sbc"
> +PACKAGECONFIG[bluez] = "-Dbluez5=enabled,-Dbluez5=disabled,bluez5 sbc glib-2.0-native"
> PACKAGECONFIG[bluez-aac] = "-Dbluez5-codec-aac=enabled,-Dbluez5-codec-aac=disabled,fdk-aac"
> PACKAGECONFIG[bluez-opus] = "-Dbluez5-codec-opus=enabled,-Dbluez5-codec-opus=disabled,libopus"
> PACKAGECONFIG[bluez-lc3] = "-Dbluez5-codec-lc3=enabled,-Dbluez5-codec-lc3=disabled,liblc3"
> --
> 2.45.2
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#114119): https://lists.openembedded.org/g/openembedded-devel/message/114119
> Mute This Topic: https://lists.openembedded.org/mt/109839311/1997914
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [oe] [meta-multimedia][PATCH] pipewire: Add glib-2.0-native dep for bluez5
2024-11-29 23:28 ` [oe] " Khem Raj
@ 2024-12-03 15:03 ` AmateurECE
2024-12-03 16:16 ` Khem Raj
0 siblings, 1 reply; 4+ messages in thread
From: AmateurECE @ 2024-12-03 15:03 UTC (permalink / raw)
To: Khem Raj; +Cc: openembedded-devel
On Fri Nov 29, 2024 at 5:28 PM CST, Khem Raj wrote:
> Thanks for the patch, it is not done on top of master it seems. Please
> rebase it on master and resend if patch is needed for master
> otherwise mark the release branch in subject prefix. This will help
> route it correctly.
Thanks for getting back to me, Khem! I will rebase onto master and
resend the patch shortly. Please forgive my question, I'm unfamiliar
with the OpenEmbedded development process: I'd like this change to be
applied to both master and the scarthgap branch, since I'm currently
basing my work on scarthgap. In that case, should I submit two patches,
one to be applied to master, and one to be applied to scarthgap (with
[scarthgap] in the subject line)?
Ethan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [oe] [meta-multimedia][PATCH] pipewire: Add glib-2.0-native dep for bluez5
2024-12-03 15:03 ` AmateurECE
@ 2024-12-03 16:16 ` Khem Raj
0 siblings, 0 replies; 4+ messages in thread
From: Khem Raj @ 2024-12-03 16:16 UTC (permalink / raw)
To: Ethan D. Twardy; +Cc: openembedded-devel
On Tue, Dec 3, 2024 at 7:03 AM Ethan D. Twardy <ethan.twardy@gmail.com> wrote:
>
> On Fri Nov 29, 2024 at 5:28 PM CST, Khem Raj wrote:
> > Thanks for the patch, it is not done on top of master it seems. Please
> > rebase it on master and resend if patch is needed for master
> > otherwise mark the release branch in subject prefix. This will help
> > route it correctly.
>
> Thanks for getting back to me, Khem! I will rebase onto master and
> resend the patch shortly. Please forgive my question, I'm unfamiliar
> with the OpenEmbedded development process: I'd like this change to be
> applied to both master and the scarthgap branch, since I'm currently
> basing my work on scarthgap. In that case, should I submit two patches,
> one to be applied to master, and one to be applied to scarthgap (with
> [scarthgap] in the subject line)?
yes
>
> Ethan
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2024-12-03 16:16 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-11-24 16:54 [meta-multimedia][PATCH] pipewire: Add glib-2.0-native dep for bluez5 AmateurECE
2024-11-29 23:28 ` [oe] " Khem Raj
2024-12-03 15:03 ` AmateurECE
2024-12-03 16:16 ` Khem Raj
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.