PACKAGECONFIG definition for a feature such as qt5/6 support doesn't have to be in an external .bbappend, as in itself it doesn't change how a recipe is being built, it only defines a recipe option, component command line switches to enable it, and dependencies that need to be fulfilled.
If there are other missing recipe options, then just add them to the gstreamer recipe. Where and how these options should be enabled is another question: default set in oe-core is made such that no external layers are required. I tend to think that vendor layers such as meta-qt6 shouldn't mess with other recipes (through bbappends) behind integrators' backs, unless those changes are strictly required for building qt itself. Alex On Fri, 21 Apr 2023 at 16:33, Bartosz Golaszewski <b...@bgdev.pl> wrote: > > I noticed that there are some recipes in OE-core that depend on > recipes living in third-party layers which are not in LAYERDEPENDS. > > For instance: gstreamer1.0-plugins-good has a PACKAGECONFIG switch for > qt5 which pulls in a bunch of packages from meta-qt5 but the core > layer (obviously) doesn't depend on meta-qt5. > > It would seem to me the right way to do it, would be to add a > .bbappend to meta-qt5 that would extend the gstreamer recipe with qt5 > support. > > Is this done on purpose or is it just some leftover from earlier development? > > I'm asking because I want to add support for qt6qml gstreamer module > but I'm not sure anymore where this should go - oe-core or meta-qt6. > > Bart > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#102145): https://lists.openembedded.org/g/openembedded-devel/message/102145 Mute This Topic: https://lists.openembedded.org/mt/98411872/21656 Group Owner: openembedded-devel+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
