default-providers.inc: Let libva-native provide libva-dev-native
PATCH 1/1 default-providers.inc: Let libva-native provide libva-dev-native
This fixes parsing errors e.g.
NOTE: Multiple providers are available for runtime libva-dev-native (libva-initial-native, libva-native) Consider defining a PREFERRED_RPROVIDER entry to match libva-dev-native
--- meta/conf/distro/include/default-providers.inc | 3 +++ 1 file changed, 3 insertions(+)
meta/conf/distro/include/default-providers.inc +3 -0
@@ -52,6 +52,9 @@ PREFERRED_PROVIDER_nativesdk-opkg ?= "nativesdk-opkg" PREFERRED_PROVIDER_console-tools ?= "kbd" PREFERRED_PROVIDER_gzip-native ?= "pigz-native" PREFERRED_PROVIDER_udev ?= "${@bb.utils.contains('DISTRO_FEATURES','systemd','systemd','eudev',d)}" +# libva-initial is a bootstrap version to break circular dependency with mesa +# Use the full libva for -dev packages +PREFERRED_RPROVIDER_libva-dev-native ?= "libva-native" # Alternative is ltp-ddt in meta-oe: meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb PREFERRED_PROVIDER_ltp ?= "ltp" PREFERRED_PROVIDER_getopt ?= "util-linux-getopt"
Quoted 8 lines · Khem Raj via lists.openembedded.org
This fixes parsing errors e.g.
NOTE: Multiple providers are available for runtime libva-dev-native (libva-initial-native, libva-native) Consider defining aPREFERRED_RPROVIDERentry to match libva-dev-nativeSigned-off-by Khem Raj <[email protected]>---
meta/conf/distro/include/default-providers.inc | 3 +++1 file changed, 3 insertions(+)
This isn't the right way to fix this. Why is libva-initial-native providing this?
Cheers,
Richard
Quoted 7 lines · Richard Purdie
Quoted 2 lines · Khem Raj via lists.openembedded.org
This fixes parsing errors e.g.
NOTE: Multiple providers are available for runtime libva-dev-native(libva-initial-native, libva-native)
Quoted 2 lines
Consider defining a
PREFERRED_RPROVIDERentry to match libva-dev-native
Quoted 8 lines
Quoted 4 lines
Signed-off-by Khem Raj <[email protected]>--- meta/conf/distro/include/default-providers.inc | 3 +++ 1 file changed, 3 insertions(+)This isn't the right way to fix this. Why is libva-initial-native providing this?
bitbake -c fetch universe --dry-run -k
revealed this. I also wondered if we could just do something like below in libva-initial recipe.
RPROVIDES:${PN}-dev:remove = "libva-dev"
Quoted 5 lines
Cheers,
Richard