summaryrefslogtreecommitdiffstats
path: root/meta/conf/bitbake.conf
AgeCommit message (Collapse)Author
2018-11-07oe-init-buildenv/base: Relax python version checks in favour of HOSTTOOLS ↵Richard Purdie
manipulation Several distros are now shipping "python" as python v3 contra to the original python guidelines. This causes users confusion/pain in trying to use our tools. We can just force "python" to "python2" within HOSTTOOLS to avoid this issue and hide the complexity from the user. (From OE-Core rev: b06a6cde5c5503f456f260c773cf126085e18c8d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-09-13bitbake.conf: Make BUILD_OPTIMIZATION respect to DEBUG_BUILDRobert Yang
We may also need debug native tools, so make BUILD_OPTIMIZATION respect to DEBUG_BUILD, otherwise, we need set CFLAGS in the recipe which isn't convenient. (From OE-Core rev: 5db09f7ad007d1def009a60d7d9bf9c13c0faa4e) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-09-13oe/utils.py: Add vartrue()Robert Yang
It can be used to simplify code like: "${@['iffalse', 'iftrue'][var]}" (From OE-Core rev: fc5a5af7bc3619f575988a75efc0c4fe15478b2d) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-09-04recipes: Update git.gnome.org addresses after upstream changesRichard Purdie
git.gnome.org is no more. It has ceased to be. It's an ex-git. Please see here: https://about.gitlab.com/2018/05/31/welcome-gnome-to-gitlab/ Note that gitlab does not support git://, only https:// (and ssh). [Commit message from Alexander Kanavin] (From OE-Core rev: 8382cdc0888ca645a44aacaac1155afb8dcde979) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-08-21bitbake.conf, kernel-artifact-names.bbclass: introduce IMAGE_VERSION_SUFFIX ↵Martin Jansa
instead of using DATETIME directly * this makes it easier to use different version string than DATETIME, e.g. set from jenkins job while keeping the suffix consistent across all artifacts stored in DEPLOYDIR (From OE-Core rev: 1245935b9bf32e0321d8ff12492983ba8506190a) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-08-01multiconfig: Enable multiconfig dependencies on oe-coreAlejandro Enedino Hernandez Samaniego
This patch enables multiconfig dependencies (mcdepends) to be used on recipes using the following format: task[mcdepends] = "multiconfig:FROM-MC:TO-MC:PN:task-to-depend-on" For the sake of simplicity consider the following example: Assuming we have set up multiconfig builds, one for qemux86 and one for qemuarm, named x86 and arm respectively. Adding the following line to an image recipe (core-image-sato): do_image[mcdepends] = "multiconfig:x86:arm:core-image-minimal:do_rootfs" Would state that core-image-sato:do_image from x86 will depend on core-image-minimal:do_rootfs from arm so it can be executed. This patch makes modifications to bitbake.conf to enable mcdepends, and to sstatesig and staging.bbclass to avoid conflicts between packages from different multiconfigs. [YOCTO #10681] (From OE-Core rev: f71bfe833c657244d2fd07b3b71e86081d7d1c04) Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-07-24sstate/bitbake.conf: Use pigz if availableRichard Purdie
Currently the compression of sstate objects is single threaded. In the case of ltp, this takes around 33s. If we add pigz into the list of non-fatal HOSTTOOLS and then use if it available when building the sstate object, this time drops to around 6s. Since pigz is now widely available this is an optimisation we should utilise. (From OE-Core rev: 2de56aa0792ec93445130d801936a8ea643fad27) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-06-28bitbake.conf: Allow BBINCLUDED to be unsetRichard Purdie
For some reason the layer index is expanding HOSTTOOLS before BBINCLUDED is set so recent changes break it. This adds in a simple workaround to stop it b reaking allowing the index to function correctly again. (From OE-Core rev: 40a904bf8bc1279c3da0893c003f740f1d2066c2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-06-28bitbake.conf: handle cmake -dev files packaging with default rulesAndre McCurdy
Move packaging rules for cmake -dev files from cmake.bbclass into bitbake.conf to handle recipes (e.g. harfbuzz 1.8.1) which build with autotools but also install cmake -dev files. (From OE-Core rev: 543e39ad5e2baa0f1ece013a89483783e6b15dd9) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-06-21bitbake.conf/testimage: Add in compatiblity hacksRichard Purdie
The testimage changes break the autobuilder. The plan is to revert these hacks but due to various changes happening with the autobuilder, we need these for now to keep things working until we can move to the new autobuilder codebase. (From OE-Core rev: 309a02931779f32d1139cc1169a039cbe4638706) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-06-21image/testimage: Rework auto image test executionRichard Purdie
The TEST_IMAGE interface has never particularly worked and image testing currently gets configured manually. This reworks the interface to better serve the needs of its users, replacing it with TESTIMAGE_AUTO. This does away with the need for the separate class due to better bitbake APIs for changing tasks. TESTIMAGE_AUTO will automatically boot under qemu any image that is built. It also adds in dependencies so that any SDK for which testing is requested will automatically be built first. The code in bitbake.conf was error prone (e.g. testsdk wasn't considered), this improves it to standardise on IMAGE_CLASSES as the standard configuration mechanism. (From OE-Core rev: b34d44f3dfea8254826a46701a4fe3769a900434) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-06-04bitbake.conf: drop redundant -nv from FETCHCMD_wgetAndre McCurdy
Since the addition of progress reporting, the wget fetcher will over-ride -nv by unconditionally appending "--progress=dot -v" to the final wget command line. http://git.openembedded.org/bitbake/commit/?id=4027649f422ee64b1c4e1ad8d48ac295050afbff (From OE-Core rev: 69f4f4aa56291e1e507a62d45834df65d699ec51) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-06-04bitbake.conf: fix HOSTTOOLS setting related to image testingChen Qi
A list of tools are added to HOSTTOOLS depending on if we inherit testimage or not. Unfortunately, if we use TEST_IMAGE variable to automate the test, these tools are not added to HOSTTOOLS. Modify the condition to also check TEST_IMAGE to fix the above problem. Also, change to use if...else... instead of list index for such setting. (From OE-Core rev: 263f8ad612674b0b47cd980212556332c17cb370) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-06-04bitbake.conf: fix minor typo in commentsAndre McCurdy
(From OE-Core rev: afcf5a6a8eb43c2832928e825566f951705e5529) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-06-04bitbake.conf: include ASNEEDED in TARGET_LDFLAGS directlyAndre McCurdy
Previously, ASNEEDED was appended to TARGET_LDFLAGS from as-needed.inc via tcmode-default.inc and so may not have been enabled for external toolchain builds or other configurations which over-ride TCMODE (ie builds which do not include tcmode-default.inc). Include ASNEEDED in TARGET_LDFLAGS directly from bitbake.conf to ensure that the optimisation is applied to all builds (and for consistency with the way that TARGET_LINK_HASH_STYLE is handled). (From OE-Core rev: 996bcb143cb8755cadb986e084b5f24e3ffdb03b) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-06-04bitbake.conf: drop obsolete commented out value for TARGET_LDFLAGSAndre McCurdy
The commented out value for TARGET_LDFLAGS dates back to the switch to sysroot enabled toolchains in 2007 and is now obsolete. http://git.openembedded.org/openembedded-core/commit/?id=ba2e1f4d933c37b372d6749d64614f2510ee9d7b (From OE-Core rev: d47245b038d27aa5228052af71d973b9ac1c3a46) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-05-22bitbake.conf: drop obsolete comment referring to the fail-fast over-rideAndre McCurdy
The comment appears to have been accidentally left behind when the fail-fast over-ride was removed by: http://git.openembedded.org/openembedded-core/commit/?id=83ce96f44516c8a4a44c8c0140949256f8422014 Also update comments to refer to bitbake variables as just variables, rather than environment variables. (From OE-Core rev: 819935bba9047ad8af63bd5d1c199fecf96572b2) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-05-22bitbake.conf: drop _build-${BUILD_OS} over-rideAndre McCurdy
Building on a host OS other than a recent version of Linux is not recommended or supported. Drop the historical _build-${BUILD_OS} over-ride to avoid giving the impression that other host OS's might be supported. (From OE-Core rev: 428fc39356cb77830de9e0d3f1dbd00f5868290a) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-05-22bitbake.conf: make libc over-ride lower priority than _forcevariableAndre McCurdy
Fix long standing quirk, _forcevariable is documented as being the highest priority over-ride. (From OE-Core rev: b3598b8f1ed1cdc7849e1e4f30d618e87e1bf582) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-23bitbake.conf: re-order DEBUG_PREFIX_MAPJuro Bystricky
When specifying several -fdebug-prefix-map command line options to gcc, they are evaluated right to left (last one first). Normally, the order is irrelevant. However, when we try to map both: recipe-sysroot-native recipe-sysroot the order matters. With the original order most of our debug packages contain incorrect debug symbols. Take for example /usr/bin/.debug/setfacl from acl-dbg: $ strings setfacl | grep native ... -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include -native/usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include Reordering the fdebug-prefix-map arguments will give us the correct paths: /usr/lib/x86_64-poky-linux/gcc/x86_64-poky-linux/7.3.0/include Note there may be additional an incorrect paths, such as: /usr/src/debug/glibc/2.27-r0/recipe-sysroot-native/usr/lib/x86_64-poky-linux.gcc-cross-initial-x86_64/gcc/x86_64-poky-linux/7.3.0/include But that one needs to be fixed in the recipe for glibc. (From OE-Core rev: 593ffffc3baf064b982891d61dacebd08aed3e96) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-20bitbake.conf: add scp to HOSTTOOLS_NONFATALJef Driesen
The scp tool is used by the ssh fetcher. (From OE-Core rev: 96f6cc7f6a3f7fa4e5cf2b00f0f163eceb904c60) Signed-off-by: Jef Driesen <jef.driesen@niko.eu> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-18bitbake.conf: Set and export TZ envvar to UTCRichard Purdie
We just ran into an issue where tar failed to build on one server setup but built everywhere else just fine. It was running makeinfo to regenerate some docs files and makeinfo was too old for the host it was running on. There was no dependency on makeinfo-native as it was not meant to be regenerating the docs. It was being regenerated as a date from a timestamp used in the docs was different in Asian timezones than in the other timezones our builds were being tested in. I added an entry to https://wiki.yoctoproject.org/wiki/TipsAndTricks/ about how this was debugged. As such, lets default to setting and exporting TZ to 'UTC' as was already pioneered by the reproducibile builds work. This makes the builds deterministic. [YOCTO #12665] (From OE-Core rev: 2a90ae7a3286724ff9e3615c4dbf56038f703810) (From OE-Core rev: e31f31f81efe4b60938b724bece2a03c7c74a68d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-04-07nativesdk-glibc: Split glibc and libcrypt to use libxcrypt insteadRichard Purdie
Fedora28[1] has decided to go ahead and use libxcrypt to replace libcrypt from glibc despite the change not having merged into glibc upstream yet. This breaks the use of uninative in OE on fedora28 since binaries there are now using new symbols only found in libxcrypt. libxcrypt is meant to be backwards compatible with libcrypt but not the reverse. Since this will impact OE in the next release cycle, this changes nativesdk only to use this new model and adds libxcrypt to work in that case. This allows us to build a uninative which is compatible with fedora28 and previous other OSes. In order to work, recipes will now need to depend on virtual/crypt where they use libcrypt since its now a separate library and we can't depend on it from glibc to preseve backwards compatibility since glibc needs to build first. For now, only the problematic nativesdk recipes have been fixed up. For target use, the default provider remains glibc for now. Assuming this change is merged into upstream glibc, we will need to roll this change out for the target but we will do this in the next release cycle when we can better deal with the resulting bugs. [1] https://fedoraproject.org/wiki/Changes/Replace_glibc_libcrypt_with_libxcrypt Original patch from Charles-Antoine Couret <charles-antoine.couret@essensium.com>, tweaked by RP to add virtual provides, SkipRecipe for libxcrypt and other minor tweaks. (From OE-Core rev: c1573cb7faeb296fe7077a60d02443d5ed5bded0) Signed-off-by: Charles-Antoine Couret <charles-antoine.couret@essensium.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-03-15risc-v: Pin oldest kernel to 4.15 for the new kidKhem Raj
(From OE-Core rev: fd3d98fd5690dab391c27a71e26f74e0f9a25f3a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-02-06bitbake.conf: Add xattr to DISTRO_FEATURES_NATIVENiko Mauno
Commit db1f1adace58763c35774e3fdfeaac5c3ca646fd disabled 'xattr' from DISTRO_FEATURES when native packages are built, whereas for target packages it was retained. This changed eg. mtd-utils-native to build without extended attributes (capabilities) support from there on. Thus even setcap was called succesfully for a binary during pkg_postinst on build host, the capabilities did not exist on target rootfs due to now xattr-less host-side mkfs utility. Adding xattr to DISTRO_FEATURES_NATIVE restores previous behaviour, fixing the discontinuity in capability propagation to target device rootfs. (From OE-Core rev: 2ad3b8ae1c56a46bf14fc6bc4c34e4b3a568d741) Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30bitbake.conf: Add comm to HOSTTOOLSNiko Mauno
This mitigates following issues during u-boot do_compile() step -- otherwise, if comm is not available, they are quietly ignored: .../scripts/check-config.sh: line 33: comm: command not found .../scripts/check-config.sh: line 39: comm: command not found Since 'comm' is provided by coreutils package, adding it to HOSTTOOLS was considered a lower impact fix compared to adding coreutils-native buildtime dependency to u-boot recipe. (From OE-Core rev: 6dc33687de9edd4269cbaf85e30945771f61f313) Signed-off-by: Niko Mauno <niko.mauno@vaisala.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-30meta: don't use deprecated functions from utils.bbclassRoss Burton
These functions were moved to meta/lib/oe in 2010 and the base_* functions in utils.bbclass were intended to be a short-term compatibility layer. They're still used in a few places, so update the callers to use the new functions. (From OE-Core rev: c97acbd034532895ce57c6717ed1b3ccc7900b0d) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-29bitbake.conf: add STAMPS_DIR to BB_HASHBASE_WHITELISTMing Liu
This allows scripts/bitbake-whatchanged to calculate the dependency changes correctly since it needs to set different STAMPS_DIR during the comparation. (From OE-Core rev: 8547f1e29104b75299f1056524da4a058a029940) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-06bitbake.conf: Set AUTOREV to have a vardepvalueRichard Purdie
If you have a recipe which does not include SRCPV in PV but does set SRCREV = "${AUTOREV}" and you run do_fetch, then change the repo to a new commit then run do_unpack, do_unpack will fail since the new commit doesn't exist in the repo that was fetched. The problem is the revision chosen is not represented in the do_fetch task hash. It if were, the fetch would rerun first and the commit would be present. It works when PV includes SRCPV since that does contain the chosen commit from the AUTOREV. The solution is to include the SRCPV value into the representation of AUTOREV used for checksum calculation purposes. Add a selftest for this issue. (From OE-Core rev: 7b8ee9285a197784d51e339f1603240f49435846) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-10bitbake.conf: set more conservative default for IMAGE_FSTYPES_DEBUGFSAndre McCurdy
Setting IMAGE_FSTYPES_DEBUGFS to the same value as IMAGE_FSTYPES can lead to creating a large number of DEBUGFS filesystem images, many of which may not make much sense (or may not even be buildable). (From OE-Core rev: a41f7cdf0cbc56a283d5c845c36d88a0208bf386) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-10-16bitbake.conf: Adds ipv6 to DISTRO_FEATURES_NATIVEAlejandro Hernandez
Before we introduced DISTRO_FEATURES_NATIVE on commit: db1f1adace58763c35774e3fdfeaac5c3ca646fd ipv6 was enabled by default on DISTRO_FEATURES via DISTRO_FEATURES_LIBC hence for example python-native was built with ipv6 support. After this, ipv6 was automatically disabled on DISTRO_FEATURES. On some packages (python) this may cause errors when they try to download something on their do_compile stage. This patch adds ipv6 to DISTRO_FEATURES_NATIVE leaving it as it was before, to avoid errors like the one mentioned above [YOCTO #11978] (From OE-Core rev: a09184bf47323b63d9548d17cc1e4e694cb605a9) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-10-16bitbake.conf: add ssh to HOSTTOOLS_NONFATALChen Qi
We changed to make tools required by testimage to be included conditionally. This resulted in users who use ssh for git fetching having failures. Add ssh to HOSTTOOLS_NONFATAL to make things work for the above situation. [YOCTO #12227] (From OE-Core rev: 50e7619aebae5351e9a41fe1b909a31b9e383f0a) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-10-09bitbake.conf: add tools required by testimage to HOSTTOOLS conditionallyChen Qi
Add tools required by testimage to HOSTTOOLS only when testimage is inherited. These tools, as described in the comment, are only required by the testimage task. So this change should not have negtive effect. This would also solve build error on hosts which miss some tool such as scp. (From OE-Core rev: 8ca61a5464743ff85b6d26886112750d6ddd13e0) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-10-07bitbake.conf: Add 'id' to HOSTTOOLSOtavio Salvador
The 'id' utility is used in 'rootfs_check_host_user_contaminated' rootfs-postcommand so it must be available. (From OE-Core rev: 6c054925d5f80790aea4cce6f8f83edc7da623b9) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-09-26meta: drop True option to getVar callsMing Liu
Search made with the following regex: getVar ?\((.*), True\). (From OE-Core rev: dbc0eaf478feb3f752ae22fd184984494fc85d0a) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-09-18gawk: Enable native buildingNathan Rossi
Also update the ASSUME_PROVIDED in bitbake.conf to contain gawk-native as the dependency is passed in via HOSTTOOLS for native builds. This allows for recipes to depend on gawk-native, and have the dependency met if not already provided by the host tools. (From OE-Core rev: cbc396dd10488990c98bb6fd94c7d10a736d57c1) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-09-18bitbake.conf: Add default FILESYSTEM_PERMS_TABLESMark Hatle
If FILESYSTEM_PERMS_TABLES was not defined, the default was selected by the packages.bbclass. This made it difficult for a recipe or layer to 'append' to the default. Copy the default into the bitbake.conf, allowing future _append and += style actions. Default was remove from package.bbclass. If a value is not set, only the built-in perms fixes will be used. (From OE-Core rev: b65736e1b7161619a0c5972376d3e713ccf53850) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-09-12bitbake.conf: add bzr to HOSTTOOLS_NONFATALMartin Jansa
* it's used by bzr fetcher: meta/conf/bitbake.conf:FETCHCMD_bzr = "/usr/bin/env bzr" and when it isn't available in PATH do_fetch tasks fail with: /usr/bin/env: ‘bzr’: No such file or directory * it was also added in: https://patchwork.openembedded.org/patch/140107/ but this change wasn't merged (nor rejected AFAIS) (From OE-Core rev: c7ba7e9e7a7ca2caf453106112dc5a3c855b21d3) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-31bitbake.conf: add definition for BUILDSDK_CXXFLAGSChang Rebecca Swee Fun
${BUILDSDK_CXXFLAGS} was introduced since commit 55c83cb239df5faf5e2143fffca47f2f16931cb3 cross.bbclass: override TARGET_* flags bitbake.conf has definitions for both ${BUILDSDK_CPPFLAGS} and ${BUILDSDK_CFLAGS} but there is none for ${BUILDSDK_CXXFLAGS}. This was a regression as in the past, CXXFLAGS is the same as CFLAGS in SDK environment. Adding definition for ${BUILDSDK_CXXFLAGS} will resolve CXXFLAGS being set wrongly in SDK environment. [YOCTO #11769] (From OE-Core rev: 073ca1cbd1b70d5b36618584a8c88cbba391a259) Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-27bitbake.conf: Drop usage of build/BUILD_SYS and target/TARGET_SYS conf filesRichard Purdie
Its been highlighted that TARGET_SYS can be changed by MACHINE and DISTRO files so this doesn't work at all today. build/ configuration files also don't see to be used. Drop these forms of include files for those reasons and simplfy the code slightly. (From OE-Core rev: df61351b625fcd2e86aac7630944cc0403455de6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-18bitbake.conf: add VOLATILE_LOG_DIR variableChen Qi
The default value is "yes" which results in the /var/log being a link pointing to /var/volatile/log which is on tmpfs. Setting valid boolean false value ('no', 'n', 'false', 'f', '0') would make /var/log to be a directory on persistent storage. [YOCTO #6132] (From OE-Core rev: 016bafce52f74462dc8f21a1c1b43ba2e6e59442) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-08-09bitbake.conf: whitelist BB_SERVER_TIMEOUT from config hashPaul Eggleton
We don't need to reparse recipes just because BB_SERVER_TIMEOUT changed, so exclude it from the config hash. (From OE-Core rev: a686fcabacd49fdb814e646305c1f33fee1d5abf) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-17bitbake.conf: add CCACHE_NOHASHDIR to hash whitelistRoss Burton
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-17ccache: don't export CCACHE_DISABLE globallyRoss Burton
CCACHE_DISABLE was added to bitbake.conf in oe-core dd2bab (June 2012) because autogen-native exports HOME=/dev/null during the build, which is then used by a host ccache to construct the path to it's cache (/dev/null/.ccache) and this fails. However we now always export CCACHE_DIR to solve the same problem in a more efficient way so CCACHE_DISABLE can be deleted. (From OE-Core rev: ef33a3138384667f819688141086102e6e83ec44) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-07-06bitbake.conf: support for merged usr with DISTRO_FEATURE usrmergeAmarnath Valluri
A new configuration variable ${root_prefix} added, which shall be used by all base_{lib,bin,sbin}dir variables. When usrmerge DISTRO_FEATURE is enabled ${root_prefix} points to ${exec_prefix} otherwise to ${base_prefix} (From OE-Core rev: 700848c6ebd03bf3105d09a41d758883ab875618) Signed-off-by: Amarnath Valluri <amarnath.valluri@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-27Revert "bitbake.conf: Add sdl-config to HOSTTOOLS if using host SDL"Richard Purdie
This clearly wasn't tested as the correct variable is ASSUME_PROVIDED. This reverts commit 91cee064332969207334cd1ee5c31d02610281fc. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-14Revert "bitbake.conf: DISTRO_FEATURES as overrides"Patrick Ohly
This reverts commit 3b3ae91a22d6f685e804df4f32cdeebe1bd6bd88. It turned out that the code which expands DISTRO_FEATURES early during base config parsing can fail because some entries in DISTRO_FEATURES might call Python functions like base_conditional() from base.bbclass which aren't defined yet. A different solution will be needed. (From OE-Core rev: 0c6e4a14ba8d9d9701ec16ffe46d618f41633571) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-14bitbake.conf: Don't exclude MACHINE/MACHINEOVERRIDES from hashesRichard Purdie
A long time ago (6 years), this seemed like a good idea. The reality is that OVERRIDES should not be being added to hashes and if it is, it likely needs excluding in its own right. This was a nice workaround but we need to fix the real underlying issues now. In some cases this means excluding OVERRIDES from the variables dependency using the vardepsexclude flag however caution is needed to ensure this is safe. Variable values used to construct hashes are unexpanded but the values used are computed after the application of OVERRIDES. The important detail is if the end resulting unexpanded value changes, not the value of the OVERRIDES used in the construction of that unexpanded value. This is why dependencies on OVERRIDES itself shouldn't be in the hashes in general. The recent DISTRO_FEATURES changes adding in override mappings for them highlighted this issue. We have some good sstate tests which are effective at highlighting where potential issues arrive with OVERRIDES contamination (oe-selftest -r sstatetests.SStateTests). (From OE-Core rev: b227781f9c59a7dfe30f3f1c0dcff87e29a1689b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-12bitbake.conf: DISTRO_FEATURES as overridesPatrick Ohly
As discussed in "[Openembedded-architecture] Yocto Compatible 2.0 + signature changes", changes in .bbappend must depend on some explicit configuration change, typically selecting a distro feature. For _append and _remove, adding an override that is set only when the corresponding entry is in DISTRO_FEATURES achieves that: In local.conf: DISTRO_FEATURES_append = " my-distro-feature" In layer.conf: DISTRO_FEATURES_OVERRIDES += "my-distro-feature" In a .bbappend: do_install_append_df-my-distro-feature () { ... } The subset of DISTRO_FEATURES that are made available as overrides must be configured explicitly because using them this way should be a conscious decision. (From OE-Core rev: 3b3ae91a22d6f685e804df4f32cdeebe1bd6bd88) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-06-12bitbake.conf: add BB_CMDLINE to BB_HASHCONFIG_WHITELISTPaul Eggleton
We really don't want the just-introduced BB_CMDLINE influencing the config hash. Part of the fix for [YOCTO #11634]. (From OE-Core rev: 861159318a99a314d2f8bdb0fa772a6b4bd7a97e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-14 07:32:21 +0000