summaryrefslogtreecommitdiffstats
path: root/meta/classes/staging.bbclass
Commit message (Collapse)AuthorAgeFilesLines
...
* staging: Handle overlapping files for build-sysrootRichard Purdie2017-01-261-2/+7
| | | | | | | | | | | | | | | The use of bb.fatal means build-sysroots fails as soon as multiple gdb's are built with overlapping files, or multiple recipes with overlapping headers exist. Change the fatal call into an exception which we can then trap. Also avoid trying to call readlink on something with isn't a symlink. This allows build-sysroots to work better under various scenarios. (From OE-Core rev: e20343a90e401bc92167867729076d321081d120) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging/allarch: Remove hardcoded PACKAGE_ARCHS from the classRichard Purdie2017-01-261-6/+10
| | | | | | | | | | | | | | | | | The code was making an assumption that the only PACKAGE_ARCH in use was TUNE_PKGARCH. This is incorrect so iterate over the list from PACKAGE_EXTRA_ARCH instead. We also need to change allarch to preserve this variable, else the staging code doesn't function. We do this in a way which clears the variable history so that the task hashes remain unaffected. [Thanks to Andrew Goodbody <andrew.goodbody@cambrionix.com> for testing/fixing] (From OE-Core rev: b1bab7a6eff6b195824be7d754de58c6e9ee2bfb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/oeqa: Replace subprocess.check_call() with check_output()Richard Purdie2017-01-231-3/+3
| | | | | | | | | | If you use subprocess.check_output() the traceback will contain the output when the command fails which is very useful for debugging. There is no good reason not to use this everywhere. (From OE-Core rev: ad750dd1cc9d789abe723daddd098ce41d8547f5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Switch to Recipe Specific SysrootsRichard Purdie2017-01-231-2/+347
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch is comparatively large and invasive. It does only do one thing, switching the system to build using recipe specific sysroots and where changes could be isolated from it, that has been done. With the current single sysroot approach, its possible for software to find things which aren't in their dependencies. This leads to a determinism problem and is a growing issue in several of the market segments where OE makes sense. The way to solve this problem for OE is to have seperate sysroots for each recipe and these will only contain the dependencies for that recipe. Its worth noting that this is not task specific sysroots and that OE's dependencies do vary enormously by task. This did result in some implementation challenges. There is nothing stopping the implementation of task specific sysroots at some later point based on this work but that as deemed a bridge too far right now. Implementation details: * Rather than installing the sysroot artefacts into a combined sysroots, they are now placed in TMPDIR/sysroot-components/PACKAGE_ARCH/PN. * WORKDIR/recipe-sysroot and WORKDIR/recipe-sysroot-native are built by hardlinking in files from the sysroot-component trees. These new directories are known as RECIPE_SYSROOT and RECIPE_SYSROOT_NATIVE. * This construction is primarily done by a new do_prepare_recipe_sysroot task which runs before do_configure and consists of a call to the extend_recipe_sysroot function. * Other tasks need things in the sysroot before/after this, e.g. do_patch needs quilt-native and do_package_write_deb needs dpkg-native. The code therefore inspects the dependencies for each task and adds extend_recipe_sysroot as a prefunc if it has populate_sysroot dependencies. * We have to do a search/replace 'fixme' operation on the files installed into the sysroot to change hardcoded paths into the correct ones. We create a fixmepath file in the component directory which lists the files which need this operation. * Some files have "postinstall" commands which need to run against them, e.g. gdk-pixbuf each time a new loader is added. These are handled by adding files in bindir with the name prefixed by "postinst-" and are run in each sysroot as its created if they're present. This did mean most sstate postinstalls have to be rewritten but there shouldn't be many of them. * Since a recipe can have multiple tasks and these tasks can run against each other at the same time we have to have a lock when we perform write operations against the sysroot. We also have to maintain manifests of what we install against a task checksum of the dependency. If the checksum changes, we remove its files and then add the new ones. * The autotools logic for filtering the view of m4 files is no longer needed (and was the model for the way extend_recipe_sysroot works). * For autotools, we used to build a combined m4 macros directory which had both the native and target m4 files. We can no longer do this so we use the target sysroot as the default and add the native sysroot as an extra backup include path. If we don't do this, we'd have to build target pkg-config before we could built anything using pkg-config for example (ditto gettext). Such dependencies would be painful so we haven't required that. * PKDDATA_DIR was moved out the sysroot and works as before using sstate to build a hybrid copy for each machine. The paths therefore changed, the behaviour did not. * The ccache class had to be reworked to function with rss. * The TCBOOTSTRAP sysroot for compiler bootstrap is no longer needed but the -initial data does have to be filtered out from the main recipe sysroots. Putting "-initial" in a normal recipe name therefore remains a bad idea. * The logic in insane needed tweaks to deal with the new path layout, as did the debug source file extraction code in package.bbclass. * The logic in sstate.bbclass had to be rewritten since it previously only performed search and replace on extracted sstate and we now need this to happen even if the compiled path was "correct". This in theory could cause a mild performance issue but since the sysroot data was the main data that needed this and we'd have to do it there regardless with rss, I've opted just to change the way the class for everything. The built output used to build the sstate output is now retained and installed rather than deleted. * The search and replace logic used in sstate objects also seemed weak/incorrect and didn't hold up against testing. This has been rewritten too. There are some assumptions made about paths, we save the 'proper' search and replace operations to fixmepath.cmd but then ignore this. What is here works but is a little hardcoded and an area for future improvement. * In order to work with eSDK we need a way to build something that looks like the old style sysroot. "bitbake build-sysroots" will construct such a sysroot based on everything in the components directory that matches the current MACHINE. It will allow transition of external tools and can built target or native variants or both. It also supports a clean task. I'd suggest not relying on this for anything other than transitional purposes though. To see XXX in that sysroot, you'd have to have built that in a previous bitbake invocation. * pseudo is run out of its components directory. This is fine as its statically linked. * The hacks for wayland to see allarch dependencies in the multilib case are no longer needed and can be dropped. * wic needed more extensive changes to work with rss and the fixes are in a separate commit series * Various oe-selftest tweaks were needed since tests did assume the location to binaries and the combined sysroot in several cases. * Most missing dependencies this work found have been sent out as separate patches as they were found but a few tweaks are still included here. * A late addition is that extend_recipe_sysroot became multilib aware and able to populate multilib sysroots. I had hoped not to have to add that complexity but the meta-environment recipe forced my hand. That implementation can probably be neater but this is on the list of things to cleanup later at this point. In summary, the impact people will likely see after this change: * Recipes may fail with missing dependencies, particularly native tools like gettext-native, glib-2.0-native and libxml2.0-native. Some hosts have these installed and will mask these errors * Any recipe/class using SSTATEPOSTINSTFUNCS will need that code rewriting into a postinst * There was a separate patch series dealing with roots postinst native dependency issues. Any postinst which expects native tools at rootfs time will need to mark that dependency with PACKAGE_WRITE_DEPS. There could well be other issues. This has been tested repeatedly against our autobuilders and oe-selftest and issues found have been fixed. We believe at least OE-Core is in good shape but that doesn't mean we've found all the issues. Also, the logging is a bit chatty at the moment. It does help if something goes wrong and goes to the task logfiles, not the console so I've intentionally left this like that for now. We can turn it down easily enough in due course. (From OE-Core rev: 809746f56df4b91af014bf6a3f28997d6698ac78) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Add dependency on virtual/binutils for strip binaryRichard Purdie2017-01-201-0/+4
| | | | | | | | | | The staging code strips binaries and we need virtual/binutils for that. Add a specific dependency since the one from do_configure and others may not be enough to ensure the binaries are in our own sysroot. (From OE-Core rev: 9a799f70574ee8e0b1267497edfb4ac63166ef8f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: remove True option to getVar callsJoshua Lock2016-12-161-11/+11
| | | | | | | | | | | | | getVar() now defaults to expanding by default, thus remove the True option from getVar() calls with a regex search and replace. Search made with the following regex: getVar ?\(( ?[^,()]*), True\) (From OE-Core rev: 7c552996597faaee2fbee185b250c0ee30ea3b5f) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Drop unused SYSROOT_LOCKRichard Purdie2016-12-081-1/+0
| | | | | | | | | This hasn't been used in years and isn't referenced anywhere, drop the definition. (From OE-Core rev: 68258f856f08f35813964e58ef761471e29373ad) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Add BB_SETSCENE_VERIFY_FUNCTION2 for bitbake runqueue changesRichard Purdie2016-06-151-0/+13
| | | | | | | | | | | | | We're about to rewrite the data structures in taskdata/runqueue in bitbake and we 'leaked' knowledge about those structures to this single function. Add a 'v2' function definition for use with the newer bitbake, the older one can remain for compatibility for a while, then be removed. The function is comparatively simple and rarely changes. (From OE-Core rev: 2a6f88d51414993d18096f7f0dc27c0b862240bc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/lib: Update xrange -> range for python3Richard Purdie2016-06-021-1/+1
| | | | | | | | xrange() no longer exists in python 3, use range() (From OE-Core rev: d022b4335100612d6596cc4c4956cb98ed5873cc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: Make it easier to define which dirs to stagePeter Kjellerstedt2016-05-131-33/+42
| | | | | | | | | | | | | | | The directories that should be staged in the sysroot are now specified in the SYSROOT_DIRS variable. Extra directories that should be staged for native are specified in SYSROOT_DIRS_NATIVE. Finally, directories that should not be staged are specified in SYSROOT_DIRS_BLACKLIST. This also removes the sysroot_stage_libdir() function as it is no longer used (it was just a wrapper for sysroot_stage_dir()). (From OE-Core rev: 80e7e7f78d957b8159bede2a5cd5614d8d73039c) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: remove trail slash from SYSROOT_DESTDIRRobert Yang2016-02-211-1/+1
| | | | | | | | | | | | Fixed path: QA Issue: <foo> sysroot-destdir//usr/lib/ <foo> Note the 2 slashes "//". (From OE-Core rev: 227247dfebe6cdff67ba2c0976b59e3f9d34f7ea) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: make already-stripped can be skippedJackie Huang2015-12-221-1/+4
| | | | | | | | | | | Add a check like what we does in package.bbclass so that the already-stripped QA test can be skipped. (From OE-Core rev: 2262fdb256954b22dadb2f7c6922e6046c269742) Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Strip files in sysrootRichard Purdie2015-06-231-0/+96
| | | | | | | | | | Add functionality to strip binaries/libraries going into the sysroot. Whilst this does fractionally slow down the build, it also significantly reduces the size of the sstate cache files. (From OE-Core rev: 30f3774f4cd5bbb8c1e6884aeff5af91ab053fc1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Exclude MULTI_PROVIDER_WHISTLIST from do_populate_sysrootRichard Purdie2014-09-301-0/+1
| | | | | | | | | | | If you switch between multilib and non-multilib builds, pretty much everything rebuilds due to the use of MULTI_PROVIDER_WHITELIST in do_populate_sysroot. It doesn't need to do this so exclude that variable for checksum purposes. (From OE-Core rev: 7f3a44ff30d07083ee8c4e2b7ac91dc6a9c8857b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/staging: ensure do_populate_sysroot re-execs on changes to sysroot ↵Paul Eggleton2014-03-251-0/+2
| | | | | | | | | | | | | | | preprocessing funcs Without this dependency, changes to functions added to SYSROOT_PREPROCESS_FUNCS do not change do_populate_sysroot's signature and thus don't cause it to re-execute. Fixes [YOCTO #5852]. (From OE-Core rev: 9950a88906bd701d0892b3ed222717ff78a93921) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Save out provider information into the sysrootRichard Purdie2014-03-251-0/+10
| | | | | | | | | | | | | | This patch saves out provider information into the sysroot for all providers except those in MULTI_PROVIDER_WHITELIST. This means that we will start seeing warnings when two providers for the same thing are installed into the sysroot. In the future those warnings can be turned into errors. Partially addresses [YOCTO #4102] (From OE-Core rev: 9e696b9d32e33ba37dc09ff312328e540fc25de2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Get rid of crazy name mappingRichard Purdie2013-12-181-1/+0
| | | | | | | | | | | | | | | When originally developed, it was thought a task may have more than one associated sstate archive. The way the code has grown that idea is now not possible or needed. We can therefore assume one sstate archive per task and drop the crazy name mapping code. Simpler is better in this case. The downside is that various sstate archives will change name so this forces a cache rebuild. Given the other sstate changes going in at this time, this isn't really a bad thing as things would rebuild anyway. (From OE-Core rev: 5afe86a6854b21692fd97c5fc7fab50dbc068acb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Use hardlinking for sysroot_stage_dirRichard Purdie2013-11-141-7/+4
| | | | | | | | | | | | This saves about 2GB on a core-image-sato build so is worth doing and is consistent with our efforts to try and decrease our build footprint. Build time in my local test seemed unaffected but on more IO bound machines it should help. (From OE-Core rev: 7136cbc64e5efb09f3fae3e2e35a181ca3d66dd4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Remove double slash from PATH_prepend and PKG_CONFIG_DIRMartin Jansa2013-10-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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>
* classes: tar 1.27 fixesRichard Purdie2013-10-141-1/+1
| | | | | | | | | | | | | tar version 1.27 returns: tar: --same-order option cannot be used with -c with the commandlines we have been using. We can remove the -s option (which is --same-order) to remove the error. (From OE-Core rev: 3d5a6d0a480a0fa98260a3b3ffc71b8d9e3e58af) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: Drop unused/legacy functionRichard Purdie2013-02-061-4/+0
| | | | | | (From OE-Core rev: 9120c88085236e1be9854376e43a7b14f937ba03) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging/insane.bbclass: Move legacy do_stage check iinto insane.bbclassRichard Purdie2013-02-061-5/+0
| | | | | | | | We might as well put all the sanity checks in one place. (From OE-Core rev: 05be11c7508984cc4aa757becb7a8f47c5b7e919) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Drop obsolete commentsRichard Purdie2013-01-251-9/+0
| | | | | | (From OE-Core rev: 44a2374dcfd68c8e158e0c901d75dbd7327652a5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add nonarch_base_lib variableConstantin Musca2012-12-191-0/+4
| | | | | | | | | | 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>
* staging.bbclass: Might as well drop the applications, fonts and pixmap ↵Richard Purdie2012-08-291-0/+1
| | | | | | | | | | | | directories from ${datadir} These cause various file conflicts and aren't useful within the sysroot anyway. We might as well remove them. Whitelisting the contents of ${datadir} that *is* useful might be a better option in future. (From OE-Core rev: c9fdd2fd108fa557d8f60339405447b4ea4d6f64) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/classes: Various python whitespace fixesRichard Purdie2012-08-211-2/+2
| | | | | | | | | | | It was pointed out we have a number of weird indentations in the python functions. This patch cleans up 3, 7 and other weird indentations for the core bbclass files. It also fixes some wierd (odd) shell function indentation which my searches picked up. (From OE-Core rev: 8385d6d74624000d68814f4e3266d47bc8885942) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: Add support for invalidtasks parameter (see bitbake change)Richard Purdie2012-07-261-2/+4
| | | | | | (From OE-Core rev: d3ae2fc896fd866aac9f064dccbff971c324f43c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: Also don't bother staging locale files, its pointlessRichard Purdie2012-07-191-2/+2
| | | | | | (From OE-Core rev: 782ce542a8250133cf1b1bc32927c17cd09cfca3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: Ensure the task starts from a clean directoryRichard Purdie2012-07-191-0/+1
| | | | | | | | | | | I found that some files were not getting removed from the sysroot, despite them clearly being removed by the recipe. I found SYSROOT_DESTDIR is only ever copied into, not cleaned. This patch ensures its empty when the task starts so that stale files are removed and not persisted. (From OE-Core rev: 8a313f6d32ae0bdac0393887712b09f1b685aaa5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: Don't stage doc/manpage/info filesRichard Purdie2012-07-191-0/+2
| | | | | | | | | | | | There is no point in having doc, manpage or info files in the staging directory. They just bloat the sstate package size and waste time as they're copied around. We never used to stage these but it crept in when we started staging $datadir. This patch corrects that so they're removed and stop making it into the sysroot. (From OE-Core rev: ec4fea852bde2294ad7a7a703ccf11eb9a109c31) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Convert tab indentation in python functions into four-spaceRichard Purdie2012-07-191-1/+1
| | | | | | (From OE-Core rev: 604d46c686d06d62d5a07b9c7f4fa170f99307d8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Quoting fixesRichard Purdie2012-02-261-1/+1
| | | | | | | | | We have various variables which are either not quoted at all or are half quoted. This patch fixes the bad exmaples so everything is consistent. (From OE-Core rev: 30253358f5e76fb7b25be27198b4c125e0dbdf2c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes: replace 'Poky' with 'OE-core'Koen Kooi2012-02-011-1/+1
| | | | | | | (From OE-Core rev: 1fdcd32520a05465b0d54c062f28bac9cdf74a20) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Remove debug accidently left inRichard Purdie2011-11-221-1/+0
| | | | | | (From OE-Core rev: 5d757b8bee10a79843e6ab726784393cbef67f73) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: Add BB_SETSCENE_VERIFY_FUNCTION functionRichard Purdie2011-11-221-0/+15
| | | | | | | | | | Since we clean out do_populate_sysroot if do_configure runs, don't allow do_populate_sysroot_setscene functions if we're going to run do_configure. (From OE-Core rev: 5f1dc1991f97037692193572298eb7f7a5640760) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Convert to use direct access to the data store (instead of bb.data.*Var*())Richard Purdie2011-11-101-3/+3
| | | | | | | | | | | | | | | | | This is the result of running the following over the metadata: sed \ -e 's:bb.data.\(setVar([^,()]*,[^,()]*\), *\([^ )]*\) *):\2.\1):g' \ -e 's:bb.data.\(setVarFlag([^,()]*,[^,()]*,[^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^(), ]*\) *,\([^)]*\)):\2.\1,\3):g' \ -e 's:bb.data.\(getVarFlag([^,()]*,[^,()]*\), *\([^() ]*\) *):\2.\1):g' \ -e 's:bb.data.\(getVar([^,()]*\), *\([^) ]*\) *):\2.\1):g' \ -i `grep -ril bb.data *` (From OE-Core rev: b22831fd63164c4db9c0b72934d7d734a6585251) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add umask task controlMark Hatle2011-06-301-0/+1
| | | | | | | | | | | | | | | | | | | | | | Bitbake now allows the umask to be specified per task. The following tasks will have a umask of 022 set by default: do_configure do_compile do_install do_package do_populate_sysroot do_rootfs do_configure and do_compile need a umask of 022 set because -many- recipes directly copy generated files out of recipe's build directory. Instead of fixing each existing and future recipe, it was shown to be much easier to just set the umask. (From OE-Core rev: 0cfa7ebcf661aa0645c6d4d858b04946ebacb7e4) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Misc hard link fixesMark Hatle2011-02-091-1/+1
| | | | | | | | | I searched the various classes and looked for copies that should attempt to preserve hardlinks. This fixes the majority of this copies by switching to using tar as the copy method. It also has the side effect of preserving sparse files. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
* staging.bbclass: Only clean out the sysroot if we rerun configure, not at ↵Richard Purdie2011-01-281-1/+6
| | | | | | setscene time Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging.bbclass: No need to create these directories any more, also remove ↵Richard Purdie2011-01-261-9/+2
| | | | | | invalid comment Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: machine specific sysroots implementationDongxiao Xu2011-01-251-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit changes the sysroots path to be machine specific. Changes includes: 1) STAGING_DIR_TARGET and STRAGING_DIR_HOST points to machine specific paths. 2) task stamp files. Adding ${MACHINE} info into stamp files for do_populate_sysroots and do_package tasks. Add a BB_STAMPTASK_BLACKLIST to keep native, nativesdk, crosssdk, and cross-canadian stamp unchanged. 3) siteconfig path. Separate the site config path for different machines to avoid one machine adopting the cache file of another machine. 4) sstate. Add machine name to sstate manifest file. Change relocation code for sstate paths since sysroot is machine. Keep native, nativesdk, crosssdk, and cross-canadian unchanged. 5) toolchain scripts. Change the environment path to point to machine specific sysroots in toolchain scripts bbclass. 6) Relocate la files when populating to a different machine of the same architecture. 7) Exclude STAGING_DIR_TARGET and STAGING_DIR_HOST parameter from sstate siginfo since they contain ${MACHINE} information. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
* staging: Use relative path in sysroot-destdir for target recipesDongxiao Xu2011-01-211-13/+13
| | | | | | | | | | Original we used absolute path in sysroot-destdir for both native and target recipes. This commit changes target recipes to use relative path which is same as the image directory. [sgw: merged with libtool sysroot work] Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
* staging.bbclass, utils.bbclass: remove la mangling codeScott Garman2011-01-211-14/+0
| | | | | | | | | libtool v2.4 --with-libtool-sysroot eliminates the need for la mangling. Based on Khem Raj's OE commits. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
* staging: relocate *.la paths in destination dirsDongxiao Xu2011-01-171-3/+4
| | | | | | | Keep the la files in source directories unchanged, and do relocation in destination directories (sysroot-destdir). Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
* Drop variables that do nothingRichard Purdie2010-12-101-1/+0
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* Revert "classes: Disable setscene tasks for initial testing"Richard Purdie2010-10-051-1/+1
| | | | This reverts commit 084ec86402bba92418898a4c47667a0574a3b3ee.
* classes: Disable setscene tasks for initial testingRichard Purdie2010-08-191-1/+1
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* staging.bbclass: Convert to packaged-stagingRichard Purdie2010-08-191-5/+10
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* staging.bbclass: mangle *.la for ${base_libdir} tooKevin Tian2010-08-131-0/+1
| | | | | | | | | currently staging.bbclass mangle *.la to ensure sysroot prefix attached to dependency_libs if other *.la is referenced, however it only happens on ${libdir}. libpam is special with its libraries under ${base_libdir}. So this extends mangle to ${base_libdir} too Signed-off-by: Kevin Tian <kevin.tian@intel.com>
* staging: Remove now unused legacy staging codeRichard Purdie2010-07-301-22/+3
| | | | Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-06-26 19:52:00 +0000