meta-openembedded/meta-multimedia
Khem Raj f8a25ccf54 pipewire: Do not split modules using PACKAGES_DYNAMIC for native case
One of the module has -native in its name which causes it to be provided
by both pipewire and pipewire-native and we need to set preferred
provider just for that. The fine tailored packages is not needed for
native case anyway so disable it

Fixes
NOTE: Multiple providers are available for runtime pipewire-modules-protocol-native (pipewire, pipewire-native)
Consider defining a PREFERRED_RPROVIDER entry to match pipewire-modules-protocol-native

Signed-off-by: Khem Raj <raj.khem@gmail.com>
2023-02-02 10:25:33 -08:00
..
classes Convert to new override syntax 2021-08-03 10:21:25 -07:00
conf layer.conf: update LAYERSERIES_COMPAT for mickledore 2023-01-04 14:34:04 -08:00
licenses Alliance for Open Media: new library 2020-10-06 08:45:24 -07:00
recipes-connectivity gssdp: check opengl is enabled or not 2022-11-10 10:41:35 -08:00
recipes-dvb Make tvheadend recipe compatible with the latest tvheadend version 2023-01-12 09:02:10 -08:00
recipes-mkv recipes: Update LICENSE variable to use SPDX license identifiers 2022-03-04 17:41:45 -08:00
recipes-multimedia pipewire: Do not split modules using PACKAGES_DYNAMIC for native case 2023-02-02 10:25:33 -08:00
recipes-support crossguid: Fix build with gcc13 2023-01-26 10:24:25 -08:00
COPYING.MIT meta-multimedia: initial add 2012-02-24 13:53:17 +01:00
README README: update to main repo 2021-09-27 11:34:55 -07:00

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: master

URI: git://git.openembedded.org/meta-openembedded
layers: meta-oe
branch: master

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia]' in the subject

When sending single patches, please use something like:
git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix='meta-multimedia][PATCH'

You are encouraged to fork the mirror on github https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like GitLab, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Layer maintainer: Andreas Müller <schnitzeltony@gmail.com>