summaryrefslogtreecommitdiffstats
path: root/meta/conf/bitbake.conf
Commit message (Collapse)AuthorAgeFilesLines
* bitbake.conf: define WORKDIR in terms of BASE_WORKDIRRoss Burton2013-09-221-1/+2
| | | | | | | | | | 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>
* bitbake.conf/package: Collapse PKGDATA_DIR into a single machine specific ↵Richard Purdie2013-09-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* bitbake.conf: include machine name in DEPLOY_DIR_IMAGEPaul Eggleton2013-09-141-1/+1
| | | | | | | | | | | | | | | | | | | 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>
* bitbake.conf: Stop providing ${P} and ${PF} by defaultRichard Purdie2013-09-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* bitbake.conf: Add SDKPKGSUFFIX to hash whitelistRichard Purdie2013-09-041-1/+1
| | | | | | | | | | 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>
* Drop darwin8/darwin9 usageRichard Purdie2013-08-231-4/+0
| | | | | | | | | | | 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>
* bitbake.conf: Work around dev symlink problems on darwinRichard Purdie2013-08-231-6/+9
| | | | | | | | | | | | | | | | | | | | | | 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>
* bitbake.conf/classes/gcc: Don't hardcode -nativesdkRichard Purdie2013-08-231-1/+2
| | | | | | | | | | | | | 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>
* gettext: Improve USE_NLS handling for nativesdk/crosssdk/cross-canadianRichard Purdie2013-08-231-0/+1
| | | | | | | | | | | | | | | | 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>
* package_rpm.bbclass: NO_RECOMMENDATIONS supportMark Hatle2013-08-221-0/+1
| | | | | | | | | | | | | | | | | | 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>
* classes/rootfs_rpm: implement BAD_RECOMMENDATIONS for RPMPaul Eggleton2013-07-291-0/+2
| | | | | | | | | | | | | | | | | | | | 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>
* bitbake.conf: Add extra fakeroot parametersRichard Purdie2013-06-141-0/+2
| | | | | | | | | 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>
* bitbake.conf: define empty EXTRA_IMAGE_FEATURES before using themMartin Jansa2013-05-151-0/+2
| | | | | | | | | | | * 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>
* bitbake.conf: export STRINGSMartin Jansa2013-05-121-0/+1
| | | | | | | | | * 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>
* bitbake.conf: update way to set default ROOT_HOMEKang Kai2013-05-101-1/+1
| | | | | | | | | | | 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>
* bitbake.conf: Use casting to ensure valid comparisionRichard Purdie2013-05-091-2/+2
| | | | | | | | | 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>
* bitbake.conf: set SERIAL_CONSOLES from SERIAL_CONSOLE by defaultPaul Eggleton2013-05-021-0/+3
| | | | | | | | | | | 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>
* bitbake.conf: Don't add ${PN} to RRECOMMENDS_${PN}-dbgPhil Blundell2013-04-291-1/+0
| | | | | | | | | | | 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>
* bitbake.conf: explicitly backfill sysvinit, not DISTRO_FEATURES_INITMANRoss Burton2013-03-261-1/+1
| | | | | | | | | | 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>
* bitbake.conf: Add LICENSE_PATH to sstate whitelistKhem Raj2013-03-171-1/+1
| | | | | | | | | | | | | | | | | | | | 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>
* bitbake.conf: add STAMPS_DIR for constructing STAMPRobert Yang2013-03-071-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | 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>
* bitbake.conf: move PERSISTENT_DIR outside TMPDIRMartin Jansa2013-03-021-1/+1
| | | | | | | | | | | | * 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>
* conf: Remove unused ROOT_FLASH_SIZE variable from the configHolger Hans Peter Freyther2013-02-171-3/+0
| | | | | | | | | | 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>
* bitbake.conf: Update hashconfig after BB_ORIGENV changesRichard Purdie2013-02-061-4/+3
| | | | | | | | | | 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>
* meta: remove all mention of PCMCIA_MANAGERRoss Burton2013-01-251-1/+0
| | | | | | | | | | 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>
* prserv: change PRSERV_HOST semanticsConstantin Musca2013-01-251-6/+1
| | | | | | | | | | | | | | - 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>
* base: make feature backfilling happen earlierRichard Purdie2013-01-241-3/+0
| | | | | | | | | | | | | | | | | 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>
* bitbake.conf: unbreak all builds with custom DISTRO_FEATURESMarcin Juszkiewicz2013-01-241-1/+1
| | | | | | | | | | | | | | | | | 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>
* bitbake.conf: remove update-modules from DISTRO_FEATURESLaurentiu Palcu2013-01-181-1/+1
| | | | | | | | | | | 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>
* bitbake.conf: import var ROOT_HOMEKang Kai2012-12-261-0/+3
| | | | | | | | | | | | 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>
* bitbake.conf: add nonarch_base_lib variableConstantin Musca2012-12-191-0/+1
| | | | | | | | | | 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>
* bitbake.conf: exclude DATETIME var dependency from IMAGE_NAMEMartin Jansa2012-12-191-0/+1
| | | | | | | | | | | | | * 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>
* bitbake.conf/utils: Drop some OVERRIDES from FILESPATHRichard Purdie2012-12-111-0/+2
| | | | | | | | | | | | | 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>
* bitbake.conf: Change build output message to list BUILD_SYS, TARGET_SYS and ↵Richard Purdie2012-11-271-1/+1
| | | | | | | | | | | | | | | | | | 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>
* bitbake.conf: Drop obsolete FILESDIR settingRichard Purdie2012-11-261-1/+0
| | | | | | | | | | | | | 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>
* bitbake.conf: add TUNE_CCARGS[vardepvalue]Martin Jansa2012-11-251-0/+1
| | | | | | | | | | | | * 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>
* Revert "bitbake.conf: Drop obsolete FILESDIR setting"Richard Purdie2012-11-211-0/+1
| | | | | | | | 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>
* bitbake.conf: Drop obsolete FILESDIR settingRichard Purdie2012-11-211-1/+0
| | | | | | | | | | | 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>
* bitbake.conf/sanity: Separate versions and PN stamp components into separate ↵Richard Purdie2012-11-201-3/+3
| | | | | | | | | | | | | | | directories for WORKDIR and STAMP This means some of the hacks we have to tell where the package name ends and the version starts in the directory layout becomes obsolete, simplifying the work of some of the cleanup scripts. It also makes the layout slightly more intuitive to the user. It does force a rebuild onto the user but it will reuse sstate successfully. (From OE-Core rev: 05075cf3138d1c61f5cf4fe0e1a4587acc00c692) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add udev rules into ${PN} files by defaultKhem Raj2012-11-021-0/+1
| | | | | | | | | | | | | | As we move to systemd, udev is not provided by systemd where the arch independent files are stored in /lib and /usr/lib and not in ${base_libdir} and ${libdir} which means the files like udev rules go into /lib/udev or /usr/lib/udev. This patch adds these paths to be packaged into default ${PN} output package from a recipe (From OE-Core rev: 6cbc0c7bf3f35e18f0abd29e5a704fba55f88ab2) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Change systemd_unitdir definitionKhem Raj2012-10-271-1/+1
| | | | | | | | | | | | | | | systemd_unitdir indicates the arch independent files which are basically scripts and unit files and systemd wants then to be in /lib always even when base_libdir is /lib64, hence we have to reflect that and not use base_libdir to define it. Otherwise on architectures where base_libdir is lib64 e.g. ppc64 or multilibbed x86_64 this wont work (From OE-Core rev: 50e713d4ae35f9b5f5f2a515a95d77573610d707) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: break three very long linesRobert Yang2012-10-241-6/+14
| | | | | | | | | | | | | | | | | | Break the following 3 very long lines into 3 pieces, make a line under 80 characters, will modify BB_HASHBASE_WHITELIST and BB_HASHCONFIG_WHITELIST in the next patch: BB_HASHBASE_WHITELIST BB_HASHCONFIG_WHITELIST BB_SIGNATURE_EXCLUDE_FLAGS [YOCTO #3299] (From OE-Core rev: 1417f606982c591178dd408a7ef79f449a6e2554) 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>
* PACKAGES_DYNAMIC: use regexp not globMartin Jansa2012-10-191-1/+1
| | | | | | | | | | | * bitbake uses PACKAGES_DYNAMIC as regexp ^ could make matching faster (and it will be more clear that we're expecting regexp not glob) * made all those last '-' optional, use .* (or nothing) (From OE-Core rev: 2f3ebdfa5f42dae51063b043cc4b0fbe20b40064) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: change libexecdir to ${libdir}/${BPN}Saul Wold2012-10-181-1/+4
| | | | | | | | | | | | | | | | | | | In order to be more compliant with the Filesystem Hierarchs Standard (FHS), this change removes the /usr/libexec default in favor of ${libdir}/${BPN} (which is typically /usr/lib). http://www.pathname.com/fhs/pub/fhs-2.3.html This also address the native and STAGING variations [YOCTO #2915] (From OE-Core rev: 68c31b095a1cb20bd297df596024fc568614f5e8) (From OE-Core rev: 406bd38b4232f9f399ef5ffe0b4fac72ed605a23) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass, module.bbclass: Make update-modules optionalPhil Blundell2012-10-181-1/+1
| | | | | | | | | | | | | | | | | | The update-modules mechanism is something of a historical relic and it isn't entirely clear that it has a great deal of value nowadays. Also, it causes a problem when building a read-only rootfs since update-modules itself refuses to configure offline. Allow DISTROs to circumvent this whole thing by declaring (via DISTRO_FEATURES) that they don't wish to use update-modules. This is backfilled for existing distributions and will have to be marked as CONSIDERED by those who actually don't want it. (From OE-Core rev: 14bf8ed115453077b4d4042b4b70ed6b3bca2a9f) Signed-off-by: Phil Blundell <pb@pbcl.net> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add CCACHE_DISABLE to BS_HASHBASE_WHITELISTMike Crowe2012-10-021-1/+1
| | | | | | | | | | If CCACHE is in the whitelist then CCACHE_DISABLE probably should be too. (From OE-Core rev: c03f76160e3cc3cb4fbf3cee114665c34bff06e6) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add chrpath-native to ASSUME_PROVIDEDRichard Purdie2012-10-021-0/+2
| | | | | | | | We assume chrpath is provided natively so it should be listed in ASSUME_PROVIDED. (From OE-Core rev: 97a3ea712003e8d48dc68c282e656591f39d2d1a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: parse license configElizabeth Flanagan2012-09-281-0/+1
| | | | | | | | | | license.conf hasn't been being parsed. It probably should be. (From OE-Core rev: b393b31fee3b4d42890c2bcbba09ea231c131dea) Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add and use 'localedir' variableChristopher Larson2012-09-251-0/+1
| | | | | | | | | | | | | | This avoids the hardcoding of ${libdir}/locale which is all over the place, and will facilitate use of ${exec_prefix}/lib/locale instead of ${libdir}/locale. This doesn't actually change any output at this time. Verified this with buildhistory against the packages produced from core-image-base. (From OE-Core rev: b744f4cc2912334b8493a89525fd02af8e9b8edf) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/gcc-common.inc: Fix STAMPCLEAN expressionRichard Purdie2012-09-211-1/+1
| | | | | | | | | | | | The globs used for STAMPCLEAN were too greedy matching gcc-cross-initial stamps for gcc-cross for example. This patch resolves that problem making the assumption that PV starts with something numeric. This assumption should hold in most cases and has a better failure case that the current situation. (From OE-Core rev: d7fbc70b6c6ac629d2a23ac16ab45461f88b4b26) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-14 17:23:29 +0000