summaryrefslogtreecommitdiffstats
path: root/meta/conf/bitbake.conf
AgeCommit message (Collapse)Author
2014-02-17bitbake.conf: add BBINCLUDED and BB_INVALIDCONF to config hash whitelistPaul Eggleton
These variables should not influence the config hash, i.e. changing them shouldn't trigger a reparse of the metadata, so whitelist them. (From OE-Core rev: 8feb51267647d0760f5bec3a8b6f95f4481d9b0d) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-02-11conf/bitbake.conf: default HOMEPAGE to blank instead of unknownPaul Eggleton
The default value for HOMEPAGE of "unknown" has been in place since the early OE-Classic days, but it doesn't really make sense - "unknown" is not a valid URL and it just means we have to explicitly check for this hardcoded string if we're displaying the value in some form of UI, such as Toaster. This has required some changes to the packaging classes as they previously did not expect the value to be blank. (From OE-Core rev: 244e1d73ef58e92d73c098044c66bd784644b933) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-02bitbake.conf: add full stop to default DESCRIPTIONPaul Eggleton
SUMMARY should not end with a full stop; however if DESCRIPTION is not set in a recipe and thus defaulted from SUMMARY, the additional DESCRIPTION values for other standard packages e.g. ${PN}-dev look a bit odd without a full stop separating the SUMMARY value and the rest of the text. Add a full stop to avoid this. (From OE-Core rev: 4b022399815f32166c402d458a40afa6470fc776) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-01-02bitbake.conf: set a default for MACHINE_FEATURESPaul Eggleton
Ensure that if MACHINE_FEATURES is not set by the machine config that we don't end up with expansion errors during parsing. Technically since the introduction of MACHINE_FEATURES_BACKFILL = "rtc" this is unlikely to be a problem unless "rtc" is also added to MACHINE_FEATURES_BACKFILL_CONSIDERED, however we should be consistent with DISTRO_FEATURES which is defaulted in bitbake.conf. (From OE-Core rev: bf2c8946d96524aaa91ab43762c963ea38ccc342) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-12-20bitbake.conf: Exclude WORKDIR changes from sstate checksumsRichard Purdie
The layout of stamp files ensures that changes to WORKDIR mean recipes get rebuilt correctly. Since WORKDIR usually contains MULTIMACH_TARGET_SYS and that depends on tune variables, including WORKDIR in sstate checksums adds a lot of noise to the system for what amounts to no gain. On the other hand, removing it reduces noise, reduces the size of the siginfo files and reduces the amount of processing bitbake has to do. It therefore seems like dropping it from the checksums is an all around win. (From OE-Core rev: 453353e05d027c6a505d1e13a7982718a13bca8b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-12-05bitbake.conf/native.bbclass: Use FC instead of F77 for fortranRichard Purdie
gcc tooling appears to be standardising around the FC variable naming. This patch changes the F77 namespace to FC instead and use the default gfortran compiler. If anyone needs the F77 variables or tools, those can still be made on a case by case basis. Also updates local.conf.sample.extended accordingly. (From OE-Core rev: ae8c17be2845eff2be8394a5d9a45e6aa321c33d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-20bitbake.conf: Remove obsolete/unused MIRROR cruftPhil Blundell
ADOBE_MIRROR, HANDHELDS_CVS and E_SVN were broken links and not used by any recipe in oe-core. FREEDESKTOP_CVS is no longer useful because all the source code that matters is in git; no recipe in oe-core still uses the CVS repository. E_MIRROR, FREEBSD_MIRROR, FREESMARTPHONE_GIT still point to valid-seeming locations but there are no recipes in oe-core that use them. Any layers which need these variables can define them for themselves. GPE_SVN, GPE_EXTRA_SVN, GPEPHONE_MIRROR and GPEPHONE_SVN are not used by any recipe in oe-core and the corresponding projects seem to be mostly dead upstream. Again, any layers which still wish to use these variables can define them locally. All the above are just wasting space in bitbake's datastore and would be better deleted. (From OE-Core rev: 3b333896c71689c664475d53daed52404bf6b21b) Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-14bitbake.conf: remove CPU_FEATURES defaultsPaul Eggleton
This variable has been unused since the tune file overhaul two years ago. (From OE-Core rev: a1d9f2374ede768057fd364da6c0e1eeeb10499f) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-14bitbake.conf: remove BOOTSTRAP_EXTRA_* variable defaultsPaul Eggleton
These were for task-bootstrap in OE-Classic and have never been used in OE-Core. (From OE-Core rev: f4692afb518f07e17fbd35a2023877b7041abef9) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-11-12bitbake.conf: Default DISTRO to nodistroRichard Purdie
An empty distro value leads to OVERRIDES and FILESOVERRIDES containing "::" entries which causes odd issues such as files being included when they shouldn't be. We could put in anonymous python to guard against empty entries but its messy and setting a default value for DISTRO to something harmless is much easier. This patch adds a weak default and ensures the sanity test doesn't complain about it. DISTRO_VERSION and SDK_VERSION are also updated to match. (From OE-Core rev: b7279f99639774674da806d37d252f388f33055f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-10-16bitbake.conf: add WARN_QA and ERROR_QA to the hash whitelistRoss Burton
I discovered bitbake rebuilding packages because WARN_QA had changed. These variables don't influence the output, so add them to the whitelist. (From OE-Core rev: 96204ae6e1b19783d6a3f8c590890714eaa9e2d9) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-10-14bitbake.conf: Remove double slash from PATH_prepend and PKG_CONFIG_DIRMartin Jansa
* we correctly have ${STAGING_DIR_NATIVE}${base_sbindir_native} and then double slash in ${STAGING_DIR_NATIVE}/${base_bindir_native} * similar in PKG_CONFIG_DIR where libdir also starts with slash ${STAGING_DIR_HOST}/${libdir}/pkgconfig * also fix double slash in insane.bbclass and staging.bbclass * I was a bit nervous about staging change (in case the / was important in some weird use-case, but the extra slash is there since following commit where other extra slashes were removed only the one before libdir was kept: commit 6ea78d648951e5bbe9669412c0863daaf7f49ca5 Author: Richard Purdie <rpurdie@linux.intel.com> Date: Mon Nov 2 17:10:51 2009 +0000 autotools.bbclass: Separate out useful staging functions into base.bbclass and call from autotools classes * this isn't fixing any real-world issue AFAIK, I was just trying to debug one weird case where debugedit fails with canonicalization unexpectedly shrank by one character and it's easier to grep for '//' without many harmless instances already in run* scripts etc (From OE-Core rev: 0ddaf52e9e344986ae2b016cc068d9eee71b4347) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-22bitbake.conf: define WORKDIR in terms of BASE_WORKDIRRoss Burton
To make it easier to move WORKDIR, define it using the new variable BASE_WORKDIR, which is the root of the work directory. (From OE-Core rev: 1eee097f2e29b9d6934711c0b1d32e59e9542f53) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-14bitbake.conf/package: Collapse PKGDATA_DIR into a single machine specific ↵Richard Purdie
directory Currently we have a hierarchy of pkgdata directories and the code has to put together a search path and look through each in turn until it finds the data it needs. This has lead to a number of hardcoded paths and file globing which is unpredictable and undesirable. Worse, certain tricks that should be easy like a GL specific package architecture become problematic with the curretn search paths. With the modern sstate code, we can do better and construct a single pkgdata directory for each machine in just the same way as we do for the sysroot. This is already tried and well tested. With such a single directory, all the code that iterated through multiple pkgdata directories and simply be removed and give a significant simplification of the code. Even existing build directories adapt to the change well since the package contents doesn't change, just the location they're installed to and the stamp for them. The only complication is the we need a different shlibs directory for each multilib. These are only used by package.bbclass and the simple fix is to add MLPREFIX to the shlib directory name. This means the multilib packages will repackage and the sstate checksum will change but an existing build directory will adapt to the changes safely. It is close to release however I believe the benefits this patch give us are worth consideration for inclusion and give us more options for dealing with problems like the GL one. It also sets the ground work well for shlibs improvements in 1.6. (From OE-Core rev: 1b8e4abd2d9c0901d38d89d0f944fe1ffd019379) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-14bitbake.conf: include machine name in DEPLOY_DIR_IMAGEPaul Eggleton
This allows a clean seperation between image outputs from different machines, and makes it possible to have convenience symlinks to make the output ready to deploy. This did require some surgery in runqemu; if explicit paths to the image and kernel are not supplied then DEPLOY_DIR_IMAGE needs to be determined from bitbake or set in the environment. However the script does try to avoid requiring it unless it really is needed. Corresponding changes were made in the automated testing code as well. Based on an RFC patch by Koen Kooi <koen@dominion.thruhere.net> (From OE-Core rev: 7e90261aec61f79680b5eaeaf5b18c7b795412a4) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-14bitbake.conf: Stop providing ${P} and ${PF} by defaultRichard Purdie
For a long time we've provided PN-PV and PN-PV-PR by tweaking PROVIDES. This looks nice at first glance however it turns out to be a bit problematic. Taking make as an example where there are two versions, 3.81 and 3.82, what should "bitbake make-3.81" do? Currently it builds make-3.81 and make-3.82 and breaks in interesting ways. Is that a bitbake bug? Well, it certainly shouldn't try and run the build. Why is it building 3.82 though? Its due to finding a dependency on "make-dev" and then trying to figure out what provides it? The answer is "make" and the default version of "make" is 3.82. So arguably, finding "make-3.81" should infer PREFERRED_VERSION_make = "3.81". Doing so resolved the above problem since now "make" resolves to "make-3.81". So what about if we have Recipe A: DEPENDS = "make-3.81" and Recipe B: DEPENDS = "make-3.82" That is clearly an error, easy. So finally what about if we have Recipe A: DEPENDS = "make-3.81" and Recipe B: DEPENDS = "make" The first recipe infers the PREFERRED_VERSION_make = "3.81" and then forces that version on everything else. Is that desired? Probably not in most cases, at least not silently. As mitigation, we could print a WARNING about this happening. The final part of the problem is that we can ony figure this out within bitbake itself. That means we'd have to teach bitbake about the PN-PV format of PROVIDES which is breaking the separation between bitbake and the metadata. We can't win :(. Nobody that I know of is using or relying on this functionality so perhaps we should just remove it instead which is what this patch does. Opinions? (From OE-Core rev: a87c205bb6cefd5e1a41b8e7ef02b5bfa380e3b6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-09-04bitbake.conf: Add SDKPKGSUFFIX to hash whitelistRichard Purdie
The gcc recipes reference this however we account for it in the work directory paths and we don't want recipes depending on the value changing. This avoids unecessary rebuilds when switching SDKs. (From OE-Core rev: 6cdcc543ce8f532a4f66246114241b43821a111e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-23Drop darwin8/darwin9 usageRichard Purdie
There were darwin8/darwin9 overrides spinkled in the code from times gone by. Lets settle on the darwin override and remove the others since its pointless duplication. We always inject darwin into OVERRIDES if needed in the darwin8/9 cases. (From OE-Core rev: 8d5e6eed7802a6056f9eaa50a85e3eee00fe2742) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-23bitbake.conf: Work around dev symlink problems on darwinRichard Purdie
On darwin, we have: libxxx.dylib -> libxxx.Y.dylib compared to Linux which has: libxxx.so -> libxxx.so.Y Our ordering of PACKAGES with -dev first and then ${PN} makes it impossible to match the files correctly using simple globbing. This makes darwin targets completely broken since both the libs and the dev symlinks end up in ${PN}-dev. Whilst this commit is a hack, it at least puts the files into ${PN} and allows the builds to be used. Symlinks don't take up much space so this isn't the end of the world. I'm open to better solutions to this. (From OE-Core rev: 51c3dbe2df45096bbd7866adabb08e114952ff13) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-23bitbake.conf/classes/gcc: Don't hardcode -nativesdkRichard Purdie
Hardcoding -nativesdk as the sdk package architecture is inflexible. We may have multiple different target OS and we need a way to be able to separate them. Turning this into a configurable value allows the flexibility we need to build different SDKMACHINEs with different OS targets. The commit should have no behaviour change, just makes things more configurable. (From OE-Core rev: a2110e86b98d646e136de9ec6b8e668079b0d4f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-23gettext: Improve USE_NLS handling for nativesdk/crosssdk/cross-canadianRichard Purdie
The gettext handling of USE_NLS has become a bit tricky to understand, or alter from the SDK context. This patch introduces a SDKUSE_NLS which can be set to configure a given SDK/ADT to use NLS or not. This is independent of the target system NLS usage. The code in gettext.bbclass is therefore simplified and the classes themselves now set USE_NLS to appropriate values. No NLS is used for native, cross and crosssdk since it is never used there and would just increase build time. (From OE-Core rev: fe634d47449899f7424adb77ff5bc7ddf8a07a47) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-22package_rpm.bbclass: NO_RECOMMENDATIONS supportMark Hatle
Add NO_RECOMMENDATIONS support. A way to disable all recommended packages from being installed. This will help shrink the size of the resulting filesystem. Add documentation on NO_RECOMMENDATIONS and BAD_RECOMMENDATIONS. Note, using NO_RECOMMENDATIONS has side effects such that kernel-modules may not have been installed. A user will need to manually add to their image any kernel-modules required to be on the image for functionality. (From OE-Core rev: 0341bfa886ea851f5a394051545b4e624d8003dd) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-07-29classes/rootfs_rpm: implement BAD_RECOMMENDATIONS for RPMPaul Eggleton
Add support for the BAD_RECOMMENDATIONS variable that can be used to prevent specific packages from being installed via an RRECOMMENDS relationship when using the RPM backend. (Previously this functionality was only available when using ipk packaging.) In the process this moves the defaulting of BAD_RECOMMENDATIONS (as empty) to bitbake.conf since it is no longer specific to the ipk backend, as well as unifying some of the code that creates the configuration for smart for use on the host and target. Fixes [YOCTO #3916]. (From OE-Core rev: 4e85129a7d47baf3e32b815cbc277bff84e085a0) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-14bitbake.conf: Add extra fakeroot parametersRichard Purdie
In order to correctly handle fakeroot at the bitbake level we need some extra information which we provide with these new variables. (From OE-Core rev: 003ea0fd1017dde50ced710179d0dc2e835d5185) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-15bitbake.conf: define empty EXTRA_IMAGE_FEATURES before using themMartin Jansa
* fixes build without EXTRA_IMAGE_FEATURES defined: ERROR: '${EXTRA_IMAGE_FEATURES}' in IMAGE_FEATURES is not a valid image feature. Valid features: dbg-pkgs .... (From OE-Core rev: b2cc92595b30d96a79f33ea7a7217834c8b6bff7) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-12bitbake.conf: export STRINGSMartin Jansa
* remove STRINGS export from systemd (From OE-Core rev: 68d7300e2cc55a5b873345874243da589e04bba0) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-10bitbake.conf: update way to set default ROOT_HOMEKang Kai
Use "??=" to set default ROOT_HOME. It can be overwrote by developer with "?=" in any layer and at same time it also can be overwrote in local.conf. (From OE-Core rev: 902d3fa57d4659ee12aac80246dcaca5c45f9d8c) Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-09bitbake.conf: Use casting to ensure valid comparisionRichard Purdie
python3 is stricter about type comparisions so add an explicit cast to int() to ensure this code is portable. (From OE-Core rev: b9a1b9ad55c0f9fec082ffa37e576d8fd664becd) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-02bitbake.conf: set SERIAL_CONSOLES from SERIAL_CONSOLE by defaultPaul Eggleton
This is the first step in deprecating SERIAL_CONSOLE without affecting machine configurations that still use it. (From OE-Core rev: 3f0d665384e6d1b7aa2854a9cc4f13e0961bacb7) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-04-29bitbake.conf: Don't add ${PN} to RRECOMMENDS_${PN}-dbgPhil Blundell
This recommendation is of no obvious value and causes unexpected behaviour when using IMAGE_FEATURES += "dbg-pkgs". (From OE-Core rev: b64f2ef2be5dca1eb13a305147a2b99d57985010) Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-26bitbake.conf: explicitly backfill sysvinit, not DISTRO_FEATURES_INITMANRoss Burton
Reflect reality by backfilling sysvinit support, instead of whatever value was in DISTRO_FEATURES_INITMAN. (From OE-Core rev: 0b6559cd93a64498646d18a121746c6816382407) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-17bitbake.conf: Add LICENSE_PATH to sstate whitelistKhem Raj
some layers e.g. meta-intel are defining LICENSE_PATH in layer.conf like LICENSE_PATH += "${LAYERDIR}/common/custom-licenses" This causes the target packages to invalidate the siginfo and casues rebuild for all packages. Thanks bitbake-diffsigs, it shows basehash changed from c27b55ea6980262fab370e539ba8bcd7 to 37962b22ebd6194e9537bc4f85819323 Variable LICENSE_PATH value changed from ' /builds2/poky/meta-intel/common/custom-licenses' to ' /b/kraj/jlinux-next/poky/meta-intel/common/custom-licenses' (From OE-Core rev: 1dab754cb1ec942f86a7cf9758e6b5169e50bff3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-07bitbake.conf: add STAMPS_DIR for constructing STAMPRobert Yang
Add STAMPS_DIR for constructing STAMP, the defination of STAMP is: STAMP = "${TMPDIR}/stamps/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}" We can only change the TMPDIR if we want to change the STAMP's location, but the bb_cache.dat would be regenerated if TMPDIR changes, so add STAMPS_DIR for constructing it, and add it to the BB_ENV_EXTRAWHITE, this is very usefull for the "bitbake -S", since then it can be run by: STAMPS_DIR=<path> bitbake -S <recipe> which will avoid putting the stamps to ${TMPDIR}/stamps. BTW, break the too long BB_ENV_EXTRAWHITE into several lines. [YOCTO #1659] (From OE-Core rev: ce732c04b3ac06633e20efa8799c4189abfd41b3) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-03-02bitbake.conf: move PERSISTENT_DIR outside TMPDIRMartin Jansa
* PR service cache needs to be persistent between rebuilds having it in directory starting with tmp* does not help people to understand that it needs to be persistent, so move it to TOPDIR (From OE-Core rev: 5d43f752429707b74dbf46ecb81ac76bad7bb715) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-02-17conf: Remove unused ROOT_FLASH_SIZE variable from the configHolger Hans Peter Freyther
This variable is set but never used in OE-core and meta-oe. It was historically used for the Opie collection but seems to be unused now. (From OE-Core rev: 323ef78e377525e2214f4700c30305c493137853) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-02-06bitbake.conf: Update hashconfig after BB_ORIGENV changesRichard Purdie
We should ignore BB_ORIGENV from the hash for the config data. There are also a number of variables which no longer make it into the data store so we can drop these from the hash whitelist. (From OE-Core rev: cb21af00f9321ea48e533089dbffbb1a9665cb92) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-25meta: remove all mention of PCMCIA_MANAGERRoss Burton
Nothing appears to use this anymore, and it's been a very long time since there was anyone expressing an interest in the alternatives. (From OE-Core rev: f6f289c13b9da9c2793d1fd30456216db8afad64) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-25prserv: change PRSERV_HOST semanticsConstantin Musca
- remove PRSERV_PORT variable - use 'hostname:port' as PRSERV_HOST format - remove USE_PR_SERV variable - one can activate PRS by setting PRSERV_HOST [YOCTO #3744] (From OE-Core rev: e00f49de8b1f79c3e07b887d257bd75a46052fa0) Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-24base: make feature backfilling happen earlierRichard Purdie
Backfilling DISTRO_FEATURES and MACHINE_FEATURES with _append statements happens too late to use those variables with conditional inherits, like this: inherit ${@base_contains('DISTRO_FEATURES','sysvinit','update-rc.d_real','',d)} Instead, do the backfilling at ConfigParse time so that it happens earlier in the parse, which results in that inherit behaving as expected when sysvinit was backfilled. (From OE-Core rev: 22429cdf79ed952072707a929643c7386fa7e056) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-24bitbake.conf: unbreak all builds with custom DISTRO_FEATURESMarcin Juszkiewicz
Commit 9e7c64ca9afbf27edd0d35a1830ce55ee6d778ab broke all builds where custom DISTRO_FEATURES were used. Resulting images ended in non-bootable state due to lack of initscripts (unless someone had sysvinit or systemd in D_E already). https://bugs.launchpad.net/linaro-oe/+bug/1102910 https://bugs.launchpad.net/linaro-oe/+bug/1099405/comments/12 (From OE-Core rev: 211e473432230765a48d7af9c66c8737a08cdec7) Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-01-18bitbake.conf: remove update-modules from DISTRO_FEATURESLaurentiu Palcu
Since update-modules is obsolete, remove it from DISTRO_FEATURES. [YOCTO #3598] (From OE-Core rev: 5a404ba472c51cec8e13d79e073a1d104a747c44) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-26bitbake.conf: import var ROOT_HOMEKang Kai
Import var ROOT_HOME to configure root home directory dynamically. [Yocto 2683] (From OE-Core rev: a78cd0b3a69b829327cea035321051ab11cba70f) Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-19bitbake.conf: add nonarch_base_lib variableConstantin Musca
Adapt stagging.bbclass to this change (From OE-Core rev: 0730a8cbb42cd8b6667f2d1daefa0f6fcec06af2) Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-12-19bitbake.conf: exclude DATETIME var dependency from IMAGE_NAMEMartin Jansa
* resolves ERROR shown when bitbake -S is used for image: ERROR: Bitbake's cached basehash does not match the one we just generated (/OE/oe-core/openembedded-core/meta/recipes-core/images/core-image-minimal.bb.do_rootfs)! ERROR: The mismatched hashes were 8c35cdf8a5d09c03941f081dd9f6d8dc and b5d6e2e5952770557c48c5779ddb73fc (From OE-Core rev: 084d16cd00365ac3db9010a2e0e08ec49b50a144) 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>
2012-12-11bitbake.conf/utils: Drop some OVERRIDES from FILESPATHRichard Purdie
There are several overrides that don't make sense as part of FILESPATH. This introduces FILESOVERRIDES and allows us to drop some of the pointless ones, simplifying the files search path further and improving the user experience. If needed by specific recipes, other overrides can be added back in for specific cases. (From OE-Core rev: b8b1b39961332c99d62ee466f7859bd62a0f806f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-27bitbake.conf: Change build output message to list BUILD_SYS, TARGET_SYS and ↵Richard Purdie
NATIVELSBSTRING The build summary is meant to reflect key configuration variables. Information about the build system we're running on is important but currently missing from the information displayed. Printing TARGET_SYS removes the need to print TARGET_OS and TARGET_ARCH and we add BUILD_SYS and NATIVELSBSTRING to show information about the build system. [YOCTO #3456] (From OE-Core rev: 764cc1eb3043c84121f597d2271108b91052095e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-26bitbake.conf: Drop obsolete FILESDIR settingRichard Purdie
FILESPATH is the preferred way of finding files now. Having a value for FILESDIR which defaults to paths which will have already been searched is pointless at best. This is the final step in letting us drop FILESDIR support entirely from bitbake at some future date. (From OE-Core rev: d6e5ceafcaef06b8a3f9acc2aa826a40a016f913) (From OE-Core rev: 3bb5c6bd51c91ada7fc17451627b8954dbe9c09c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-25bitbake.conf: add TUNE_CCARGS[vardepvalue]Martin Jansa
* we don't care about expression but value * e.g. tune-xscale and tune-arm926ejs have different expression in TUNE_CCARGS but with the same DEFAULTTUNE the result is the same http://lists.linuxtogo.org/pipermail/openembedded-core/2012-September/030032.html (From OE-Core rev: 03f1e34ea3ce80931e9c3cd2ab22824f28a7233b) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-21Revert "bitbake.conf: Drop obsolete FILESDIR setting"Richard Purdie
This reverts commit d6e5ceafcaef06b8a3f9acc2aa826a40a016f913 since the value is clearly still being used in local file urls that are only hit at do_unpack time. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-11-21bitbake.conf: Drop obsolete FILESDIR settingRichard Purdie
FILESPATH is the preferred way of finding files now. Having a value for FILESDIR which defaults to paths which will have already been searched is pointless at best. This is the final step in letting us drop FILESDIR support entirely from bitbake at some future date. (From OE-Core rev: d6e5ceafcaef06b8a3f9acc2aa826a40a016f913) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-28 15:05:06 +0000