summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* poky.conf: prune SANITY_TESTED_DISTROSJoshua Lock2017-02-151-8/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove several old/untested distros from the list: * poky-1.8 and poky-2.0 are no longer supported releases * ubuntu-14.04 is an LTS but we plan to remove it from the project's autobuilder cluster as the kernel is old and it doesn't use systemd -- therefore this will no longer be tested. * ubuntu-14.10 and ubuntu-15.10 are no longer supported * fedora-22 and fedora-23 are EOL * opensuse-13.2 is discontinued Add opensuse-42.2, it's the openSUSE version we run on the Yocto Project autobuilder cluster. The distro support plan is documented on the Yocto Project wiki: https://wiki.yoctoproject.org/wiki/Distro_Testing_Plan they are easily summarised as: - Fedora: most recent 2 releases - Ubuntu: most recent LTS and latest release, unless they are the same in which case the most recent 2 releases - CentOS: latest release - openSUSE: latest release (From meta-yocto rev: ba5ad19cbe9066823fe3a3b432a893f4cf67be47) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.9Alejandro Hernandez2017-02-151-2/+2
| | | | | | | | | Updates to Linux 4.9.6 (From meta-yocto rev: cdca106b64195d0035ef47d9ba7f9781b3f93904) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.8Alejandro Hernandez2017-02-151-4/+4
| | | | | | | | | Updates to Linux 4.8.17 (From meta-yocto rev: 8e09f9b4e0b9f148e9271fe1b0258cbf056cb664) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.4Alejandro Hernandez2017-02-151-4/+4
| | | | | | | | | Updates to Linux 4.4.41 (From meta-yocto rev: 4a6483c8c2e11cde1e88aede710d896bb8896586) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: Update genericx86* SRCREVs for linux-yocto 4.1Alejandro Hernandez2017-02-151-4/+4
| | | | | | | | | Updates to Linux 4.1.37 (From meta-yocto rev: d873f9eec9d7d2639c52ebd04f964295091b9764) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-yocto-bsp: bump to the latest linux stable kernel for the non-x86 BSPsKevin Hao2017-02-157-27/+27
| | | | | | | | | | Bump to the latest stable kernel for 4.1, 4.4, 4,8 and 4.9. Also set the default kernel to 4.9. (From meta-yocto rev: 5db023bddd808b01dd7d02c20b3188657c959168) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testimage.bbclass: Add check for empty test suiteMariano Lopez2017-02-151-0/+4
| | | | | | | | | | | | | | | If for some reason (most likely incorrect TEST_SUITES var) you end with an empty test suite, testimage will start the target (qemu by default) and will run an empty suite, so better have a check before starting the target. [YOCTO #10979] (From OE-Core rev: 8345f834a080737f03bee3f0c615dd9654401d93) Signed-off-by: Mariano Lopez <mariano.lopez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: Use 'populate_sdk_base' for non-linux targetsNathan Rossi2017-02-151-2/+2
| | | | | | | | | | | | | | | | | | | | | When 'populate_sdk_ext' was first introduced in commit bf81d6bb7f6 it replaced the inheriting of 'populate_sdk_base'. For non-linux targets building the extensible SDK caused build errors, and the image class was changed to inherit 'populate_sdk' when targeting a non-linux SDK_OS (in commmit e471ce3464d). However inheriting 'populate_sdk' instead of 'populate_sdk_base' causes the SDK to always be built, this is not expected for the image class. This change makes the image class inherit 'populate_sdk_base' in the non-linux SDK_OS case so that it behaves the same as it is expected to behave where 'bitbake <image> -c populate_sdk' must be executed to generate the SDK deployables. (From OE-Core rev: b7d6bb07fd37c55d07903a1e8921f17e39afde0a) 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>
* sanity.bbclass: Add which to SANITY_REQUIRED_UTILITIES.Philip Balister2017-02-151-1/+1
| | | | | | | | | | | | | | Using docker with the Fedora 23 container exposed an issue with the rpm-native configure step. If which is not present the configure script fork bombs. After much pain, I tracked this to which not being present in the default container. Add a check for which so others do not have to have this experience. (From OE-Core rev: 096c07900250db157bb0c38785b9d8efc6301cab) Signed-off-by: Philip Balister <philip@balister.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uboot-extlinux-config.bbclass: add support for timeout & defaultDalon Westergreen2017-02-151-0/+18
| | | | | | | | | | | | When multible targets are defined it is useful to allow for a default target along with a timeout. After timeout, the default target will be selected. (From OE-Core rev: 1e01c2e32c168805a9b71c1dba4b487916955813) Signed-off-by: Dalon Westergreen <dwesterg@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/copyleft_filter: include AGPL in default included listPaul Eggleton2017-02-151-1/+1
| | | | | | | | | | | | | | | | If we're including all GPL licenses then we should include AGPL in the default COPYLEFT_LICENSE_INCLUDE since it has similar terms (and currently we do have one AGPL-licensed recipe in OE-Core, namely db). (Note that the default list isn't meant to be a guaranteed complete safe list - seek legal advice based on what you're distributing if unsure.) (From OE-Core rev: a16fbf6970056a79cac8b70ce54e55e61ef63a8d) 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>
* kernel.bbclass: Make symbol to vmlinuz.bin in boot directoryAndrea Adami2017-02-151-0/+3
| | | | | | | | | | | | | The changes committed with 6e58f54be103814b6b8a85b236510633c49e6832 did only consider the vmlinuz ELF kernel but some devices do reqire a raw vmlinuz.bin (as for example gcw0 in meta-handheld booted by ubiboot). Expand the above mentioned patch to consider this case. (From OE-Core rev: 413a5faf99280f4e083358e4134aebbcfa47bb4c) Signed-off-by: Andrea Adami <andrea.adami@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check-tool: Use CA cert bundle in correct sysrootJussi Kukkonen2017-02-152-1/+218
| | | | | | | | | | | | | | Native libcurl looks for CA certs in the wrong place by default. * Add patch that allows overriding the default CA certificate location. Patch is originally from meta-security-isafw. * Use the new --cacert to set the correct CA bundle path (From OE-Core rev: 73bd11d5190a072064128cc13b4537154d07b129) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check-tool: Fixes for recipe sysrootsJussi Kukkonen2017-02-151-1/+2
| | | | | | | | | | | | | | * Use --enable-relative-plugins so cve-check-tool looks for loadable modules relative to binary location instead of hard-coding a wrong sysroot location * do_populate_cve_db() assumes that the binary cve-check-update is in the sysroot. Ensure that this is true by adding a task dependency (From OE-Core rev: 2da6b01893d0afe8750bd0b12a8d55aafa82f58c) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cve-check.bbclass: Fix dependenciesJussi Kukkonen2017-02-151-1/+1
| | | | | | | | | | | | | | With recipe-specific sysroots the cve_check task must depend on cve-check-tool-native:do_populate_sysroot to get the cve-check-tool binary into the recipe sysroot. A normal DEPENDS isn't used to avoid cyclic dependencies. (From OE-Core rev: bd60b1018bc0304bc928701e6d1090c8b1223616) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testimage: Implement custom target loadingJuro Bystricky2017-02-152-4/+72
| | | | | | | | | | | | | | This patch implements custom target loading for testimage, currently missing due to major changes to the test framework. Custom targets can be defined in various meta-layers, so we need an extra path information in order to find them. Any other additional info is retrieved as usual via the variables TEST_TARGET and TEST_SUITES (From OE-Core rev: 1dc8010afd71fe46fb28bb86fb7c07a5fbd3d7cf) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/loader.py: Avoid error in TypeError exceptionJuro Bystricky2017-02-151-1/+1
| | | | | | | | | Without this an exception would occur (From OE-Core rev: d1bda068d4bc0ad3ff81ab1f104dc12cedd20b3f) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu.py: add 'elf' as supported fstypeJuro Bystricky2017-02-151-1/+1
| | | | | | | | | Add 'elf' as also supported by OEQemuTarget. (From OE-Core rev: c1ec42ee9beb1603012db5cf990cdbf1596b2a3d) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libva: Update to new 01.org github locationSaul Wold2017-02-151-5/+6
| | | | | | | | | | | Upstream has moved to use 01.org and github, Update the various URIs that track info. S needs to be changed to WORKDIR/git as we are now a git repo. (From OE-Core rev: 9f80b36a74d4eb407f9fc4d3afc056c41241cbc6) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/core/runner.py: OEStreamLogger fix loggingAníbal Limón2017-02-151-1/+1
| | | | | | | | | | Change conditional to avoid losing stack traces when log into the logger. The logic only needs to don't log empty lines. (From OE-Core rev: 545dd180cc27a69732f2332565038bd06d01c014) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes: Drop now unneeded update_data callsRichard Purdie2017-02-1528-53/+0
| | | | | | | | | | Now that the datastore works dynamically we don't need the update_data calls so we can just remove them. They're not actually done anything at all for a while. (From OE-Core rev: 8de0c5d3bd01919e2bf0394f9c485936d6098cec) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nss: Fix nss-native so the checksum doesn't change with BUILD_ARCHRichard Purdie2017-02-091-0/+2
| | | | | | | | | | | | | | | Switching between 32 and 64 bit BUILD_ARCH shows: $ bitbake-diffsigs tmp-sstatesamehash*/stamps/*/nss-native/3.27.1-r0.do_compile.sigdata.* basehash changed from 944cc4554a823ba966aeda0ac3d33b79 to 2475db3659c248d81d0e4dadb3c1b4cd Variable SITEINFO_BITS value changed from '32' to '64' We shouldn't have this dependency and it would fail oe-selftest test_sstate_32_64_same_hash if nss-native were included, therefore exclude it. (From OE-Core rev: d1109378d730c5cf50240c4d1a468e3aef5208ea) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Make absolute symlinks an errorRichard Purdie2017-02-091-30/+12
| | | | | | | | | | | | The current relocation code is broken, at least in the native case. Fixing it would mean trying pass in new data on sstate tasks about the relative positioning of symlinks compared to the sstate relocation paths. Whilst we could do this, right now I'm favouring making this an error and fixing the small number of problematic recipes we have in OE-Core (3). (From OE-Core rev: cf94de4ddee3e5072da8608c9151301fcec02cd0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl/fontconfig/bzip2: Use relative symlinks instead of absolute ones ↵Richard Purdie2017-02-094-3/+8
| | | | | | | | | | | | | | | | | | | | | (using a new class) Absolute path symlinks are a bit of a pain for sstate and the native versions of these recipes currently contain broken symlinks as a result. There are only a small number of problematic recipes, at least in OE-Core, namely the three here. Rather than trying to make sstate handle this magically, which turns out to be a harder problem than you'd first realise, simply make the symlinks relative early in the process and avoid all the problems. The alternative is adding new complexity to sstate which we could really do without as without the complexity, you can't always tell where the absolute symlink is relative to (due to prefixes used for native sstate). (From OE-Core rev: e478550c8cd889f12e336e268e9e3b30827bf840) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oe/path: Add replace_absolute_symlinks functionRichard Purdie2017-02-091-0/+21
| | | | | | | | | | | We need a function to walk a directory and replace absolute symlinks with relative ones. Add such a function to the path module of lib/oe. It does this relative to the directory being walked for files. (From OE-Core rev: 15376e5ff35367c1b40941d10e7b19302058a53e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-initial: Remove unneeded temporary sysrootRichard Purdie2017-02-091-12/+1
| | | | | | | | | | We used to need to build gcc-cross-initial against a bare sysroot to avoid contamination. With RSS, we no longer need to do this since the recipe sysroot is already bare. We can therefore simply point at that and drop this code. (From OE-Core rev: f70603887f823c14030bb738c4951d7aa3f022db) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-native: Remove tests to save copying uneeded files aroundRichard Purdie2017-02-091-0/+3
| | | | | | | | | Removing these nearly halves the python3-native disk footprint meaning more optimal sysroot operations. We don't need these tests for anything. (From OE-Core rev: 5c8dda390cacef69bc7996eb26099d55e2b8427b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc-package: Avoid race sstate races with do_stash_localeRichard Purdie2017-02-091-6/+11
| | | | | | | | | | | | | | | | The change to make do_stash_locale an sstate task between do_install and do_package has some unforeseen problems since the function deletes part of ${D} but may or may not run depending on whether the task is installed from sstate. This cleans up the current "pre packaging" function to be more deterministic and result in the same set of files, whichever code path we end up reaching that point by. Its not an ideal sitation but it should avoid the race failures we've seen on some builds. (From OE-Core rev: 2a60bba00da9c4e2b1a1ce30e509dba82cc6c94a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest/pkgdata: use m4 instead of bashRoss Burton2017-02-071-4/+4
| | | | | | | | | | | | | The pkgdata test broke due to oe-core cf0fd8b which added alternatives support to bash, so the binary is now /bin/bash.bash. Instead of fixing the test case for this new name, use the m4 recipe instead as it has less build dependencies. (From OE-Core rev: 68da6c98841f4450736ae170e443aa744c8b77eb) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dosfstools: upgrade to 4.1Dengke Du2017-02-071-2/+2
| | | | | | | | | upgrade dosfstools from 4.0 to 4.1 (From OE-Core rev: 38c9e4531bcac71b873dd3bc0b264954c9d90150) Signed-off-by: Dengke Du <dengke.du@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image_types.bbclass: fix image dependency chain collectionAndre McCurdy2017-02-071-1/+1
| | | | | | | | | | | If image type "foo" depends on image type "bar.xz", then dependencies should be collected from the base image type (ie "IMAGE_DEPENDS_bar") not from "IMAGE_DEPENDS_bar.xz". (From OE-Core rev: 8a9f249a9166347cc0468191ce130003e3d306e1) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-module-split: Allow custom suffix for package namesAndreas Oberritter2017-02-071-1/+3
| | | | | | | | | | This makes it possible to restore the behaviour changed by commit 78cde87 "kernel-module-split: Append KERNEL_VERSION string to kernel module name". (From OE-Core rev: 4aabdddf67859cd8518e5cb672fb391c859817e0) Signed-off-by: Andreas Oberritter <obi@opendreambox.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* iproute2: Inherit pkgconfigKhem Raj2017-02-071-1/+1
| | | | | | | | | | | | Fixes ERROR: iproute2-4.9.0-r0 do_package: QA Issue: iproute2: Files/directories were installed but not shipped in any package: /usr/lib /usr/lib/tc (From OE-Core rev: eac08770b1ea3ca6640941dc8fd03fc3fa5ff869) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pcmciautils: Inherit pkgconfigKhem Raj2017-02-071-0/+2
| | | | | | | | | | | | | | | | | Fixes ERROR: pcmciautils-018-r1 do_package: QA Issue: pcmciautils: Files/directories were installed but not shipped in any package: /pcmcia-socket-startup /pcmcia-check-broken-cis /rules.d /rules.d/60-pcmcia.rules Since we do not have pkg-config in native sysroot it is not computing paths correctly and causes above error (From OE-Core rev: 748b14caed95e7c0d45f1196398689a22975dcc9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Add missing 'inherit pkgconfig'Jussi Kukkonen2017-02-071-1/+1
| | | | | | | | | The monster configure file does call pkg-config somewhere in there. (From OE-Core rev: 8f7eb210257318dfa630bbc39b3eb9be936fddcc) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* latencytop: Add missing 'inherit pkgconfig'Jussi Kukkonen2017-02-071-0/+2
| | | | | | | | | The Makefile uses pkg-config. (From OE-Core rev: 4d61f95e49e2c0953c513e6a78ca626e8fbd5684) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pong-clock: Add missing 'inherit pkgconfig'Jussi Kukkonen2017-02-071-1/+1
| | | | | | | | | The usage of pkg-config is sneakily hidden in do_compile() (From OE-Core rev: b55186f93163e120c73bacb7400b94c21cfaa675) Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: improve parse failure handlingPaul Eggleton2017-02-072-2/+16
| | | | | | | | | | | | | With the move to tinfoil2, the behaviour when parsing failed has changed a bit - exceptions are now raised, so handle these appropriately. Specifically when if parsing the recipe created when running devtool add fails, rename it to .bb.parsefailed so that the user can run bitbake afterwards without parsing being interrupted. (From OE-Core rev: b9592bd3c1ab2155b9f62d18ce593b9c88eff279) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipetool: create: do not treat numbers in SCM URLs as versionsPaul Eggleton2017-02-071-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Numbers within SCM (e.g. git) URLs are extremely unlikely to be valid version numbers - more likely they are just part of the name, thus don't try to extract them and use them as the version - doing so causes pretty bad behaviour within devtool: --------- snip --------- $ devtool add https://github.com/inhedron/libtr50 NOTE: Fetching git://github.com/inhedron/libtr50;protocol=https... ... NOTE: Using default source tree path .../build/workspace/sources/libtr ... RecursionError: maximum recursion depth exceeded while calling a Python object --------- snip --------- (This was because ${PV} was being substituted into the URL, but PV's value was being set to include ${SRCPV}, so there was a circular reference.) (From OE-Core rev: 3427508b6ce865654f8bf01a6fc04b83c70315d3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipetool: create: properly handle npm optional dependenciesPaul Eggleton2017-02-071-7/+49
| | | | | | | | | | | | | npm's package.json supports two types of dependencies - optionalDependencies and dependencies; in the code for creating a recipe from a non-npm source (e.g. a git repository) we were not handling optionalDependencies and thus when pointed at a node.js application outside of npm we weren't taking care of all dependencies. (From OE-Core rev: 2b66cb9982d10ce1744d430858eaef3e5a72c8c0) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/npm: set HOME during do_installPaul Eggleton2017-02-071-0/+3
| | | | | | | | | | | In do_compile we set HOME so that ~/.npm* only get created in the work directory; we need to do the same in do_install as well or they'll go into the user's home directory which we do not want. (From OE-Core rev: a667cb9ed2dceb804b85d1a024e2619bc34d2681) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: account for custom image tasksPaul Eggleton2017-02-071-2/+6
| | | | | | | | | | | Any custom tasks that were added on the image between do_image_complete and do_build were not being taken into account. Use the newly added bb.build.tasksbetween() function to take care of that. (From OE-Core rev: c966dee6208d3b7a9fa3c1b8aa1266058dcb65ff) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/patch: switch to new bb.build.tasksbetween() functionPaul Eggleton2017-02-071-19/+1
| | | | | | | | | | | A generic version of the code to work out the tasks between two tasks (based on the code here) has been added to bb.build, so use that instead. (From OE-Core rev: 1226e2eb2678407c315befd5700e653602e616a0) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/populate_sdk_ext: remove unnecessary dependencies breaking SDK_TARGETSPaul Eggleton2017-02-071-2/+0
| | | | | | | | | | | | | | | | | | Up until recently it was possible to set SDK_TARGETS to include a native recipe you wanted installed into the sysroot when installing the eSDK. I'm not sure what happened but now when you try to add a native recipe to SDK_TARGETS you get a missing task error because this recipe has no do_package_write_* task. Of course such a task dependency is erroneous and is apparently caused by setting SDK_RDEPENDS. I've checked and it turns out that we no longer need to set SDK_RDEPENDS anyway (probably because we explicitly set up task dependencies further down in the class, which I don't think we were fully doing in early versions of the eSDK). Thus, drop setting this variable to restore the functionality. (From OE-Core rev: fe8268ede33a8c76492b85da0f41062f47a5279c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.conf: Update minimum version requirement for devtoolRichard Purdie2017-02-071-1/+1
| | | | | | | | | A recent devtool change needs bitbake changes so bump the minmium bitbake version requirement to match. (From OE-Core rev: e7b624c268cb917c00e88e8e9a6a87585eb98eac) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Add missing parameter to debug messageRichard Purdie2017-02-071-1/+1
| | | | | | (From OE-Core rev: 77ac40f8d4a4718b05f3692222a0dc91d90f0ab8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Improve file creation resilianceRichard Purdie2017-02-071-39/+49
| | | | | | | | | | | | | If you abort a build mid execution of the staging extend_sysroot function there are currently races and cleanup of that function may fail. This change splits the code into separate phases so that the manifests are manipulated before files are installed, meaning we should be able to reverse actions if builds fail, crash or are interrupted. (From OE-Core rev: fc504b6b8538453d2f058d7cc69be098f52f8091) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Add shared manifest supportRichard Purdie2017-02-071-0/+23
| | | | | | (From OE-Core rev: 51834006476786f847b3ca60d5ed83a952fc64cb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perl-native: Remove .packlist fileRichard Purdie2017-02-071-0/+4
| | | | | | | | | | This is large and needs fixups to relocate it in each case. We can drop it, save the work and the ~150MB disk space its various copies take up. Its not needed for anything that I can see. (From OE-Core rev: 9792ba51c5caf56d182f1290df41f2a89b85f744) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* staging: Don't put ptest files into the sysrootRichard Purdie2017-02-071-0/+1
| | | | | | | | | This wastes space/time as the ptest files aren't going to be used in the sysroot so add them to the blacklist. (From OE-Core rev: 61591fe2eea588ff92ff7f81f2ed8844617f5307) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-05-11 13:35:35 +0000