sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity
generic-poky/meta/conf/distro/include/default-providers.inc

48 lines
1.9 KiB
PHP
Raw Normal View History

Add files missing from previous change Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-11 22:47:06 +00:00
#
# Default virtual providers
#
PREFERRED_PROVIDER_virtual/db ?= "db"
PREFERRED_PROVIDER_virtual/db-native ?= "db-native"
xserver-xf86(-dri)-lite: rename to xserver-xorg and xserver-xorg-lite * xserver-xorg is closer to upstream naming and that's how it's named in OE-classic and meta-oe? It would make meta-oe transition easier and better to do it now then convert meta-oe to xserver-xf86 and then rename it back later. (From OE-Core rev: 0b31c7200a368533df970f0efeb81e2e20c73593) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-10-07 14:37:10 +00:00
PREFERRED_PROVIDER_virtual/xserver ?= "xserver-xorg"
PREFERRED_PROVIDER_virtual/xserver-xf86 ?= "xserver-xorg"
qemu, default-providers: Add mesa as default virtual/egl * it's safer to select it consistently with virtual/libgl* providers (From OE-Core rev: d9321da1bf01175a9e3721607df31055e3765bc6) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-14 12:49:04 +00:00
PREFERRED_PROVIDER_virtual/egl ?= "mesa"
mesa: rename mesa-dri recipe to just mesa Rename mesa-dri recipes to just mesa. Also, replace all references to mesa-dri in all recipes/configs. The reason for this renaming (quote from bugzilla): "mesa-dri is a artefact of mesa-xlib existing, which doesn't anymore. mesa-dri should be renamed to mesa." [YOCTO #3385] (From OE-Core rev: c8bbb9983bcc7cfc5332e89c3e8148505b4ca83f) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-19 16:23:56 +00:00
PREFERRED_PROVIDER_virtual/libgl ?= "mesa"
PREFERRED_PROVIDER_virtual/libgles1 ?= "mesa"
PREFERRED_PROVIDER_virtual/libgles2 ?= "mesa"
mesa: add virtual/mesa provider As there are two alternative mesa recipes (mesa and mesa-gl), there needs to be a virtual provider that recipes that explicitly need Mesa (such as xserver-xorg) can depend on. (From OE-Core rev: 4a407568472d3c87cd2ce11baf199568249640b6) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-11 11:33:48 +00:00
PREFERRED_PROVIDER_virtual/mesa ?= "mesa"
update-alternatives: Add a build-time dependency We need to add a build time dependency on virtual/update-alternatives, however we can't just do DEPENDS +=, or we end up with various problems. To work around this, in the anonymous python space we ensure we only do the addition when the package does not provide virtual/update-alternatives and it is a target package. Also the system wide PREFERRED_PROVIDER was incorrect. It references a runtime package, and not the recipe it should have. This has been corrected. [YOCTO #3691] (From OE-Core rev: 56a59ef12936dcc6464cf1d43dda6957a5aa8c65) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Tested-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-18 23:13:38 +00:00
PREFERRED_PROVIDER_virtual/update-alternatives ?= "opkg"
Add files missing from previous change Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-11 22:47:06 +00:00
PREFERRED_PROVIDER_virtual/update-alternatives-native ?= "opkg-native"
default-providers: default to libx11, not -trim (From OE-Core rev: 8b0a1ce417feea5f58fc08f54025343c7c7ff892) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-09-11 19:18:02 +00:00
PREFERRED_PROVIDER_virtual/libx11 ?= "libx11"
Add files missing from previous change Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-11 22:47:06 +00:00
PREFERRED_PROVIDER_xf86-video-intel ?= "xf86-video-intel"
#
# Default virtual runtime providers
#
VIRTUAL-RUNTIME_update-alternatives ?= "update-alternatives-cworth"
task-base: move default definition of VIRTUAL-RUNTIME_apm This belongs in default-providers.conf (From OE-Core rev: afff4e6130e835048d81f65f703e118d5944629a) Signed-off-by: Joshua Lock <josh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-13 18:56:47 +00:00
VIRTUAL-RUNTIME_apm ?= "apm"
task-base: rename VIRTUAL-RUNTIME-alsa-state to use underscore * in http://lists.linuxtogo.org/pipermail/openembedded-core/2012-January/016226.html we talked about VIRTUAL-RUNTIME_alsa-state, but VIRTUAL-RUNTIME-alsa-state was used instead, which is inconsistent with other VIRTUAL-RUNTIME vars (From OE-Core rev: d5b892467023d77d219ae05170c875f7b423aa78) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-19 13:51:44 +00:00
VIRTUAL-RUNTIME_alsa-state ?= "alsa-state"
Add files missing from previous change Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-11 22:47:06 +00:00
#
# Default recipe providers
#
PREFERRED_PROVIDER_dbus-glib ?= "dbus-glib"
PREFERRED_PROVIDER_dbus-glib-native ?= "dbus-glib-native"
PREFERRED_PROVIDER_gdk-pixbuf ?= "gdk-pixbuf"
PREFERRED_PROVIDER_libgcc ?= "libgcc"
nativesdk: Switch to using nativesdk as a prefix, not a suffix As discussed on the mailing lists, using a suffix to package names is hard and has lead to many recipes having to do PKGSUFFIX games. Its looking extremely hard to scale nativesdk much further without hacking many recipes. By comparison, using a prefix like multilib does works much better and doesn't involve "hacking" as many recipes. This change converts nativesdk to use a prefix using the existing multilib infrastructure. (From OE-Core rev: 81813c0e322dc04ce4b069117188d8a54dfddb8c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-22 17:43:33 +00:00
PREFERRED_PROVIDER_nativesdk-libgcc ?= "nativesdk-libgcc"
Add files missing from previous change Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-11 22:47:06 +00:00
PREFERRED_PROVIDER_linux-libc-headers ?= "linux-libc-headers"
nativesdk: Switch to using nativesdk as a prefix, not a suffix As discussed on the mailing lists, using a suffix to package names is hard and has lead to many recipes having to do PKGSUFFIX games. Its looking extremely hard to scale nativesdk much further without hacking many recipes. By comparison, using a prefix like multilib does works much better and doesn't involve "hacking" as many recipes. This change converts nativesdk to use a prefix using the existing multilib infrastructure. (From OE-Core rev: 81813c0e322dc04ce4b069117188d8a54dfddb8c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-22 17:43:33 +00:00
PREFERRED_PROVIDER_nativesdk-linux-libc-headers ?= "nativesdk-linux-libc-headers"
Add files missing from previous change Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-05-11 22:47:06 +00:00
PREFERRED_PROVIDER_matchbox-panel ?= "matchbox-panel-2"
PREFERRED_PROVIDER_opkg ?= "opkg"
PREFERRED_PROVIDER_opkg-native ?= "opkg-native"
nativesdk: Switch to using nativesdk as a prefix, not a suffix As discussed on the mailing lists, using a suffix to package names is hard and has lead to many recipes having to do PKGSUFFIX games. Its looking extremely hard to scale nativesdk much further without hacking many recipes. By comparison, using a prefix like multilib does works much better and doesn't involve "hacking" as many recipes. This change converts nativesdk to use a prefix using the existing multilib infrastructure. (From OE-Core rev: 81813c0e322dc04ce4b069117188d8a54dfddb8c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-12-22 17:43:33 +00:00
PREFERRED_PROVIDER_nativesdk-opkg ?= "nativesdk-opkg"
default-providers: add kbd as PREFERRED_PROVIDER for console-tools kbd is used a primary provider for console-tools (From OE-Core rev: 9a88125c546e6bcbec683eb736e232236c38a4f9) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-01-24 17:53:52 +00:00
PREFERRED_PROVIDER_console-tools ?= "kbd"
default-providers: Set pigz-native as the default provider for gzip-native (From OE-Core rev: 56cbae8500284af309759099a75b35379a5f962c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-03-18 00:02:34 +00:00
PREFERRED_PROVIDER_gzip-native ?= "pigz-native"
default-providers: add default provider for make remake PROVIDES make, so we need a default provider. (From OE-Core rev: 9af884d433d18582b14977eb340cfdfa4801e7fe) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-16 17:16:06 +00:00
PREFERRED_PROVIDER_make ?= "make"
default-providers: change udev selection logic Change the logic so that the udev provider is the standalone udev, unless the systemd DISTRO_FEATURE is set. The previous logic was designed to fail if both sysvinit and systemd were enabled, which we're supporting now. (From OE-Core rev: f5d018a769fa297efa629cbbf6e42a49173faa8b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-02-28 15:58:53 +00:00
PREFERRED_PROVIDER_udev ?= "${@base_contains('DISTRO_FEATURES','systemd','systemd','udev',d)}"
default-providers: Set the preferred provider for bluez There is a need for a default provider for bluez now that bluez5 recipe is also present. After the introduction of bluez5 recipe, the following warnings are displayed: "NOTE: multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5) NOTE: consider defining a PREFERRED_PROVIDER entry to match libasound-module-bluez" Upon debug, bitbake shows: DEBUG: checking PREFERRED_PROVIDER_bluez4 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101-r5 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7-r0 (value None) against ['bluez4', 'bluez5'] Bitbake is faced with the question "what should provide libasound-module-bluez?" which is a runtime name. It needs to try and find a PREFERRED_PROVIDER entry which matches this but those use *build time* naming. So it converts "libasound-module-bluez" into the canonical ${PN} of bluez4 and bluez5 and then tries to look those up. What it actually should do is go one step further of mapping bluez4/bluez5 into the virtual/bluez but that does not happen. Bug opened on this issue: YB5044 https://bugzilla.yoctoproject.org/show_bug.cgi?id=5044 [YOCTO #5030] (From OE-Core rev: 6f07d066074b1e01ff3c16408812e6b6d5e531ac) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-21 13:02:03 +00:00
# There are issues with runtime packages and PREFERRED_PROVIDER, see YOCTO #5044 for details
# on this rather strange entry.
PREFERRED_PROVIDER_bluez4 ?= "bluez4"
ltp: set PREFERRED_PROVIDER and rename runtests_noltp.sh script * ltp installs 2 different runtests_noltp.sh files from different directories into /opt/ltp/testcases/bin/runtests_noltp.sh last one installed wins and causes unexpected changes in buildhistory's files-in-image.txt report, rename them to have unique name as other ltp scripts have. * also define PREFERRED_PROVIDER to resolve note shown when building with meta-oe layer: NOTE: multiple providers are available for ltp (ltp, ltp-ddt) NOTE: consider defining a PREFERRED_PROVIDER entry to match ltp * use patch generated without -M in my builds both versions worked, but Saul reported that it fails to apply with: Applying patch 0001-Rename-runtests_noltp.sh-script-so-have-unique-name.patch patch: **** Only garbage was found in the patch input. Now I've see the same issue on different builder (with Ubuntu 12.04). (From OE-Core master rev: ec3bb2c2203b2e8bafc1a631f623f858779e20b7) (From OE-Core rev: 198623d80d31f19c963e61d03cbcb12dd318dfdf) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-12-07 17:49:42 +00:00
# Alternative is ltp-ddt in meta-oe: meta-oe/recipes-devtools/ltp-ddt/ltp-ddt_0.0.4.bb
PREFERRED_PROVIDER_ltp ?= "ltp"