summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* oe-pkgdata-util: add --long option to list-pkg-files to show sizesRoss Burton2018-02-161-6/+12
| | | | | | | (From OE-Core rev: 1f3a5acb825a9f707c1ab780131e009f9ce21451) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pigz: use maintainer-built tarballsRoss Burton2018-02-161-4/+4
| | | | | | | (From OE-Core rev: dcce8c82fa971010f4706350534a966896534ec2) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pigz: pigz is not gzipRoss Burton2018-02-162-21/+1
| | | | | | | | | | | | | Whilst pigz is effectively a parallel gzip, the command line arguments are not the same so pigz isn't a drop-in replacement for gzip. [ YOCTO #12139 ] [ YOCTO #12410 ] (From OE-Core rev: 1624b7bfea7ac31c344a6cfcc7865a038e943814) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* expat: remove old workaround for expat tarballRoss Burton2018-02-161-5/+0
| | | | | | | | | | | | | | | | Back in 2010 the expat 2.0.1 tarball wouldn't unpack correctly with old gzip releases (prior to 1.4). The fix was to explicitly depend on gzip-native to use our binary instead of the host[1]. We don't ship expat 2.0.1 anymore, and even Centos 7 ships gzip 1.5, so this workaround can be removed. [1] oe-core 0ff62b0462f3f64672bd4704de9a192eb1a730d1 (From OE-Core rev: adc3da99a50c3eb1a1625990e563b7d37f29e3ba) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* expat: merge bb and incRoss Burton2018-02-162-26/+27
| | | | | | | (From OE-Core rev: 0bc7c11060d82d5658c79e5ff048c5ef141d0b43) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* elfutils: Use fallthrough attributeJoshua Watt2018-02-163-38/+793
| | | | | | | | | | | | Patches elfutils to use the fallthrough attribute instead of comments to satisfy the -Wimplicit-fallthrough warning. Using comments is insufficient when compiling remotely with Icecream because the file gets pre-processed locally, removing the comments (From OE-Core rev: cd44cee91b5b17ddf617950d84513d481ab34f58) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-toolchain: Disable caret workaroundJoshua Watt2018-02-161-1/+13
| | | | | | | | | | | | | | | | | | Icecream has a behavior that causes it to recompile files locally if gcc generates any warnings or errors. The reason for this is that GCC tries to re-read the input file in order to display the offending line with a caret below it, which doesn't work in the remote chroot. Default to disabling this this workaround and add -fno-diagnostics-show-caret to the GCC flags so that errors and warnings generated by GCC do not show erroneous results. Users can override this default in the SDK by defining ICECC_CARET_WORKAROUND="1" either before or after sourcing the SDK environment. (From OE-Core rev: 8933c2b5cfa59f2289c574e196f945556790c7c1) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc.bbclass: Disable caret workaround by defaultJoshua Watt2018-02-161-1/+19
| | | | | | | | | | | | | | | | Icecream has a behavior that causes it to recompile files locally if gcc generates any warnings or errors. The reason for this is that GCC tries to re-read the input file in order to display the offending line with a caret below it, which doesn't work in the remote chroot. Default to disabling this this workaround and add -fno-diagnostics-show-caret to the GCC flags so that errors and warnings generated by GCC do not show erroneous results. (From OE-Core rev: a1488291c5733a113c28475352eded61bf52bfe8) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc.bbclass: Add Icecream support to SDKJoshua Watt2018-02-161-0/+7
| | | | | | | | | | If icecc is inherited, generated SDKs will automatically have optional support for compiling using the Icecream distributed compiler (From OE-Core rev: dea45ac88251b22b0b74dc4b3ba6ca13fe0b86d6) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-toolchain: Add SDK icecream setupJoshua Watt2018-02-163-0/+118
| | | | | | | | | | | | Icecream can now be optionally included in the generated SDK by including nativesdk-icecc-toolchain to TOOLCHAIN_HOST_TASK. When the SDK is installed a post-relocation script will check if icecc exists and if so will generate the toolchain environment. (From OE-Core rev: 7e524096879e821256812633ce37cda4b85b3073) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-shar-extract: Add post-relocate scriptsJoshua Watt2018-02-163-0/+25
| | | | | | | | | | Recipes can now install post-relocation scripts which will be run when the SDK is installed. (From OE-Core rev: 93ec145f421a45077b40ae99ee6a96bc11f91f18) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-create-env: Allow multiple tool aliasesJoshua Watt2018-02-151-56/+54
| | | | | | | | | | | | When files are added to the environment, multiple aliases can be given for the file (by calling add_path multiple times with a second argument). All of these names will end up with a symlink to the original file. (From OE-Core rev: 0a5bbad5810b69fa09dbd8d886e4f368310a5db9) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-create-env: Add support for nativesdkJoshua Watt2018-02-151-2/+2
| | | | | | | | | | icecc-create-env can now be built as a nativesdk recipe, allowing the script to be included as part of an SDK (From OE-Core rev: fa7929ed70ed39a202bd2dc935d460dd57e38ffd) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-create-env: Fix executable rpathsJoshua Watt2018-02-151-3/+37
| | | | | | | | | | | | | | | | | | | | | Executables in the toolchain archive occasionally contain runtime library search paths (RPATH) that use the $ORIGIN placeholder. However, in order for that placeholder to work, /proc must be mounted. When iceccd executes the toolchain in the chroot environment, it doesn't mount /proc, so it is unable to resolve $ORIGIN resulting in a failure to find dynamic libraries. The fix is to replace $ORIGIN in executable RPATH entries with the known chroot executable path. In order for this to work, the actual real path to the executable must be resolved to remove any symlinks, otherwise the calculate $ORIGIN replacement will be wrong. This is done by using "readlink -f", which is an acceptable dependency because Yocto already requires it. (From OE-Core rev: cfe98765b40c28a132b5a4bce39f71f06b4eb0bc) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-create-env: Archive directoryJoshua Watt2018-02-151-1/+5
| | | | | | | | | | | | | | | | | Taring up the toolchain is now done by adding the entire working directory, instead of listing all the files individually. This is done because the list of files may contain ".." entries, which tar does not like and strips out, resulting in bad archives. This should result in an identical archive to what was previously generated. In addition, symbolic links are no longer dereferenced when creating the archive, as they are purposely included to provide alternate names for files (From OE-Core rev: 122d6a5bdcbc494bba0fa2b213d730500f6f7dbc) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-create-env: Symlink alternate namesJoshua Watt2018-02-151-7/+57
| | | | | | | | | | | Instead of renaming files to a new path in the toolchain archive, keep the files with their original paths and create a relative symbolic link from the new path to the original file. (From OE-Core rev: 256f8f6cc5b520b59cfdc44aa076f71990e18e2c) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-create-env: Use program interpreter for depsJoshua Watt2018-02-151-3/+17
| | | | | | | | | | | | | ldd cannot always be used to determine a program's dependencies correctly, particularly when the program specifies an alternate program interpreter (dynamic loader). This commonly happens when using a uninative tarball. Instead, determine the program's requested interpreter, and ask it to list the dependencies. (From OE-Core rev: 96d5831ef0e535d3f91acd3e979316355fbde04e) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-create-env: Add /bin/true to environmentJoshua Watt2018-02-151-0/+10
| | | | | | | | | | | icecream daemons execute /bin/true from the environment as a check to determine if the environment is valid at all, so it needs to be included. (From OE-Core rev: c86aa6edab842c579177fe5c1f8647290b58fe61) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc-create-env: ReformatJoshua Watt2018-02-151-104/+104
| | | | | | | | | | | | The environment script used an annoying mix of tabs and spaces and no mapping of tabs to spaces would produce pleasant indentation. Reformat to eliminate tab characters and settle on 4 spaces for indentation (which matches the upstream icecream script from which this is derived) (From OE-Core rev: 884c2436a6dbcb6bff99409a80276b9ef5690875) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc.bbclass: Skip canadian-cross compilesJoshua Watt2018-02-151-0/+6
| | | | | | | | | | | | | | icecc.bbclass will no longer attempt to distribute cross-canadian compiles. While it is technically possible to generate a toolchain that runs on the build system and generates executables for the host system, this is not the normal way that icecc operates. There are so few of these recipes that it is probably not worth maintaining a distinct code path for them. (From OE-Core rev: b8a39cf5884d4ab85e82c4437b81b5fbba06137e) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc.bbclass: Fix STAGING_BINDIR_TOOLCHAIN usageJoshua Watt2018-02-151-9/+8
| | | | | | | | | | | STAGING_BINDIR_TOOLCHAIN is actually a path list, not a single path. Fix icecc.bbclass to try all the paths in the variable instead of treating it as a single path. (From OE-Core rev: 8db0d3c14c166265b740030c208e0e19a0b2a1c6) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icecc.bbclass: Move to shared work directoryJoshua Watt2018-02-151-2/+5
| | | | | | | | | | | | | | | Generate the icecc toolchains in a shared work directory. This class was already setup to correctly synchronize creating the toolchains in a shared location before the RSS changes, so return to that behavior instead of generated the toolchains in each recipe's sysroot. Additionally, it makes no sense for each recipe to generate a toolchain, only to find it was already generated and uploaded to the compile server by another recipe. (From OE-Core rev: 20a53ac7818f268d4a4c86c8f35ca982baf96acf) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: delete bbappends for removed kernelsBruce Ashfield2018-02-153-81/+0
| | | | | | | | | | | | | | 4.4/4.9/4.10 are gone from oe-core master, so we can drop our bbappends. 4.12 will be removed in the future and 4.14/4.15 added, but all default versions should be 4.12+ now. (From meta-yocto rev: fd333864ce66ca32828b3d290ea8aae4f489de9b) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-tiny: bump to v4.14Bruce Ashfield2018-02-151-1/+1
| | | | | | | | | | Updating poky-tiny to the latest LTS kernel as the default version. (From meta-yocto rev: 2623111ae35218e596eac44509b1d12291840d44) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky: update default kernel to v4.15Bruce Ashfield2018-02-151-1/+1
| | | | | | | | | | | | Updating the default kernel for qemu* to be v4.15. This allows easy integration of the latest fixes/features for new BSPs. 4.14 is also available as a LTS kernel option. (From meta-yocto rev: cdd79c0f879e5e4c480773c4507f921533e17914) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-lsb: update default kernel to v4.14Bruce Ashfield2018-02-151-1/+1
| | | | | | | | | | | 4.14 is a LTS/LTSI kernel and we are dropping anything older than 4.12 in master. As such, we make 4.14 the default for poky-lsb. (From meta-yocto rev: ba6d172fd405dcc28c13f73aec1d1034a10bfc1d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@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 Hao2018-02-153-18/+18
| | | | | | | | | Bump to the latest stable kernel for 4.4, 4.9 and 4.12. (From meta-yocto rev: 4e71a79346351f8026a65cfbd68ed0bc8f5eed5c) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: Improve package strippingRichard Purdie2018-02-151-4/+2
| | | | | | | | | | Just exclude the specific tests which have an issue with being stripped rather than the whole package. This reduces the disk footprint by around 400MB. (From OE-Core rev: 460ccb6e2c5e858614cb61f21923062b55ff325e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package: Add INHIBIT_PACKAGE_STRIP_FILES to allow files to remain unstrippedRichard Purdie2018-02-151-0/+4
| | | | | | | | | | | | | | There are cases where its useful to allow only a select few files to be excluded from the package stripping mechanism. Currently this isn't possible so add a variable to allow this. This is to be used sparingly as in general the core code should be doing the right thing. This is better than the alternative of leaving the whole package unstripped. (From OE-Core rev: 92845c65f8801de7dfa34c87b22ca2e66f18557a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eudev: bump up to version 3.2.5Chang Rebecca Swee Fun2018-02-151-2/+2
| | | | | | | | | | | | | This upgraded version of eudev includes: - Headers to build under glibc-2.25 and above - Bug fix on ata_id - Misc: rules and hardware database update (From OE-Core rev: 99e9b805d2cffcca5e6fc1750e52026a6e4c78a0) Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-selftest: meta_ide: add tests for meta-ide-supportYeoh Ee Peng2018-02-151-0/+49
| | | | | | | | | | | | | | QA team were testing meta-ide-support manually. Add automated tests to test that bibtake meta-ide-support will create the toolchain and environment setup script. Also test that after using environment setup script, one can compile c program and build cpio project. (From OE-Core rev: db40eba68f51d02677526dfa4bc21343d9c27958) Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers.inc: update recipe ownershipChang Rebecca Swee Fun2018-02-151-2/+1
| | | | | | | | | | | Remove recipe for sato-icon-theme that was obsolete since YP 2.2 release and change ownership for eudev recipe. (From OE-Core rev: 06b32fd41d911dad7acf31ec1cdeff29585fac08) Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-fitimage.bbclass: Fix 64 bit ENTRYPOINTVineeth Chowdary Karumanchi2018-02-151-1/+1
| | | | | | | | | | | | | 64 bit entry point should be passed in 2 literals ( "0x1 0x00008000" ).ENTRYPOINT is assigned with first half only and erroring out as 'command not found' for the second half. Adding quotes while assignment fixes the issue. (From OE-Core rev: e886c9c5e1a8ab28388a2e8bbb936ad5eea78615) Signed-off-by: Vineeth Chowdary Karumanchi <vineethchowz.chowdary@xilinx.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* machines: bump default linux-yocto to v4.15Bruce Ashfield2018-02-152-2/+2
| | | | | | | | | | | Ensure that the qemu* machines are building the latest available kernel in master. (From OE-Core rev: 3980f21a74ad201d8cb8f5ef6fb732fdfacd641f) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/4.9: drop recipeBruce Ashfield2018-02-153-107/+0
| | | | | | | | | | | | | | | As was previously announced, anything older than 4.14 is being dropped in the master/release branches to better support newer processors and to ensure that safe/secure kernels are the defaults for all builds. The time required to update the older kernels with constant updates (more than just CVEs) is not justified in new releases. (From OE-Core rev: fcac38960af535f3b165f862dd5f4dbca43976a7) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/4.4: drop recipeBruce Ashfield2018-02-153-101/+0
| | | | | | | | | | | | | | | As was previously announced, anything older than 4.14 is being dropped in the master/release branches to better support newer processors and to ensure that safe/secure kernels are the defaults for all builds. The time required to update the older kernels with constant updates (more than just CVEs) is not justified in new releases. (From OE-Core rev: 79d679b2f4a1c540f6c8b8fd3f268aa5c2634d57) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/4.10: drop recipeBruce Ashfield2018-02-153-107/+0
| | | | | | | | | | | | | | | As was previously announced, anything older than 4.14 is being dropped in the master/release branches to better support newer processors and to ensure that safe/secure kernels are the defaults for all builds. The time required to update the older kernels with constant updates (more than just CVEs) is not justified in new releases. (From OE-Core rev: 3a5e61548746e7dcb39d7e6c69467ddb86c25f08) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: update to v2.10.5 for kernel 4.15Bruce Ashfield2018-02-151-2/+2
| | | | | | | | (From OE-Core rev: 7f00a5161889a422d83dc113521d9241fdd89abf) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/4.12: pinctrl backportsBruce Ashfield2018-02-153-13/+13
| | | | | | | | | | | | | | | | Backporting the following pinctrl commits to enable controllers on Intel Cannon Lake: 4b7a5c1b4ec5 pinctrl: intel: Add Intel Cannon Lake PCH-H pin controller support 044631ce1937 pinctrl: intel: Add Intel Cannon Lake PCH pin controller support 2054b0ea59a7 pinctrl: intel: Make it possible to specify mode per pin in a group 55b9053b5a5a pinctrl: intel: Add support for variable size pad groups (From OE-Core rev: 4c05eb243c2cf10304383f6265721b695750cb9b) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to v4.15Bruce Ashfield2018-02-154-48/+23
| | | | | | | | (From OE-Core rev: ef96628d850f1154c7e59bca418ef3a7c9a2bcc1) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: introduce 4.15 recipesBruce Ashfield2018-02-154-0/+157
| | | | | | | | | | | | | | | | | This commit makes the 4.15 kernel available for use with the Yocto configuration fragments and qemu* BSPs. It has been tested for x86,arm,mips and powerpc against the lsb, core* and glibc/mulsc test matrix. This will serve as the "latest" kernel in master, with others being removed in subsequent commits. (From OE-Core rev: 2bb69c16b4e43b74c60d4269174dbfcdb6ab54fe) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: introduce 4.14 recipesBruce Ashfield2018-02-153-0/+107
| | | | | | | | | | | | | | | | | This commit makes the 4.14 kernel available for use with the Yocto configuration fragments and qemu* BSPs. It has been tested for x86,arm,mips and powerpc against the lsb, core* and glibc/mulsc test matrix. This will serve as the LTS kernel in master, with others being removed in subsequent commits. (From OE-Core rev: 04254d4cc9e6399afd027727864e237cb8006d6d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-xcbgen: improve reproducibilityHongxu Jia2018-02-151-1/+1
| | | | | | | | | | | Use relative path to generate .pyc files could remove build host references which leads to non-reproducible builds. (From OE-Core rev: 230890227304e27acd074a3c748812d7a603d511) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* utility-tasks: Drop fetchall and checkuriall tasksRichard Purdie2018-02-151-13/+0
| | | | | | | | | | | | | | | The same thing can now be done with "bitbake <target> --runall=fetch" or "bitbake <target> --runall=checkuri". Dropping the tasks takes "bitbake core-image-sato -g" from 22s to 8s since it no longer has to resolve the recursive dependencies (it doesn't know if any given target will touch them or not until it computes them). That is a significant enough win that its worth any impact this may have on the small number of users using the tasks. (From OE-Core rev: 8bbb43e948af45d0fa5ab31b456147f691fa2ec3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-user-manual: Added google-repo fetcher and REPODIR var.Nicolas Cornu2018-02-142-3/+47
| | | | | | | | | | | | | | Added a new repo Fetcher section in the same spirit as the existing sections for other supported fetchers. Changes included the new section, removal of the bulleted item that mentioned this fetcher as an "additional" fetcher, and the creation of a new variable in the glossary named REPODIR. (Bitbake rev: 1cf084cee506574b7bb6ed03344597b3b2f2fe08) Signed-off-by: Nicolas Cornu <nicolac76@yahoo.fr> Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: toaster: don't use git fetch --allRobert Yang2018-02-141-1/+1
| | | | | | | | | | | The '--all'' fetches all remotes, including the ones in $HOME/.gitconfig, which causes the fetching very slow, so don't use "--all", git fetch should be enough. (Bitbake rev: 038a5f4b767df7944e73b2e859ac3af2d3a08bf1) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: Handle missing donestamp file when content is validNathan Rossi2018-02-142-11/+114
| | | | | | | | | | | | | | | | | | | | | | | | In order to allow users to manually populate the download directory with valid content change the assumption that missing the donestamp file means unfetched content. This allows users to populate the download dir without needing to create dummy .done files such that a user does not need a PREMIRROR when using BB_NO_NETWORK to provide valid content files in the download directory. To ensure the correct result this change also fails first if the localpath does not exist. This prevents further parts of the function attempting to calculating the checksum on non-existent files. This also fixes some edge conditions around where if the donestamp exists but the localpath does not it returns, and did not remove the donestamp. Also added test cases to cover this use case and additional use cases where for example the fetcher does not support checksums. (Bitbake rev: a335dbbb65d5b56e71d98cf3e4fa9bfbec1dcde6) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/npm.py: Fix inverted condition to prevent infinite loopBöszörményi Zoltán2018-02-141-3/+5
| | | | | | | | | | | | | | | At least the cli-color node module has dependencies that have cyclic dependency among themselves. npm.py is prepared to deal with such a case but the condition is handled only for downloading or not a dependency again, but then it goes checking the its dependency which causes an infinite loop in _getdependencies(). Make this function simply return when a dependency is already downloaded and only download and check its dependencies when not. (Bitbake rev: 545540420112992e53f4a83104af10452df168d0) Signed-off-by: Zoltán Böszörményi <zboszor@pr.hu> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: contrib/dump_cache.py: make it can dump everythingRobert Yang2018-02-141-34/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Have a simple tool to dump bb_cache.dat is useful for investigating and studying bitbake cache. The old contrib/dump_cache.py can dump pn, pv and packages for it, now enhance it dump everything. Here is the usage: $ /path/to/dump_cache.py --help usage: dump_cache.py [-h] [-r RECIPE] [-m MEMBERS] [-s] cachefile bb_cache.dat's dumper positional arguments: cachefile specify bb_cache.dat optional arguments: -h, --help show this help message and exit -r RECIPE, --recipe RECIPE specify the recipe, default: all recipes -m MEMBERS, --members MEMBERS specify the member, use comma as separator for multiple ones, default: all members -s, --skip skip skipped recipes Use dump_cache.py --help to get help (Bitbake rev: 104572438dfedf6025fbfd125aef1d56134012e7) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: parse: fixes for resolve_file()Robert Yang2018-02-143-7/+2
| | | | | | | | | | The resolve_file() calls mark_dependency(), so the one which calls resolve_file() doesn't need call mark_dependency() again. (Bitbake rev: 4682571107323a39b42cd9ec8ee67419e7f15acc) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-09-28 02:47:00 +0000