summaryrefslogtreecommitdiffstats
path: root/meta/conf/bitbake.conf
Commit message (Collapse)AuthorAgeFilesLines
* buildhistory: Fix package output files for SDKsAndres Beltran2021-10-141-0/+1
| | | | | | | | | | | | | | | | | Currently, installed packages are listed for images in image-info.txt, but not for SDKs in sdk-info.txt. Add TOOLCHAIN_HOST_TASK and TOOLCHAIN_TARGET_TASK to the output variables in sdk-info.txt. Moreover, package output files for the SDK host are empty because PKGDATA_DIR defaults to the target directory. Fix this bug and create a new variable called PKGDATA_DIR_SDK which stores the correct path for the SDK host package data. (From OE-Core rev: 82e6172c1df378dff4e503aa878501c08937b5bb) Signed-off-by: Andres Beltran <abeltran@linux.microsoft.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_rpm: use zstd instead of xzAlexander Kanavin2021-10-111-0/+4
| | | | | | | | | | | | | | | | | zstd has similar time and space performance in compression but is vastly faster in decompression, which benefits rootfs creation (especially when installing very large packages) and on-target package installation. Also, ensure ZSTD_THREADS doesn't change sstate checksums. The detailed explanation is in the commit making similar change for XZ_THREADS. (From OE-Core rev: e72c0b94554a9bc293844ec2bddb0c04ea19791d) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Set vardepvalue for PARALLEL_MAKEINSTRichard Purdie2021-10-041-0/+1
| | | | | | | | | | | | | | | If you leave PARALLEL_MAKEINST at its default from PARALLEL_MAKE, sstate checksums are fine and don't change as the number of cores do. If you override it to a specific value, this does the cause the sstate checksums to change. We don't want the checksums to change if the value of this variable differs. Therefore set a vardepvalue so a specific value is used for checksum purposes. (From OE-Core rev: 0a20d7f462b42800a8420dbb57e6ac8b84770b39) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Ensure XZ_THREADS doesn't change sstate checksumsRichard Purdie2021-09-111-0/+1
| | | | | | | | | | | | | rpm output packages currently depend on the value of XZ_THREADS which is ok if left to the default value but problematic if system limits are set such as on the autobuilder. Force the value to a specific one in the hashes for better sstate reuse and consistent rpm task checksums. (From OE-Core rev: 0296dc71c01d1b7953d74ef37d56429e2f4fcfab) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Use the new variable override syntax in a commentPeter Kjellerstedt2021-08-261-5/+5
| | | | | | | | | | It is probably a good idea if the comment that describes how variable overrides work use the new override syntax... (From OE-Core rev: 1fd8882db9011a6fe18da7611fba3426fd5cb00d) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add lz4c, pzstd and zstdJoshua Watt2021-08-181-3/+3
| | | | | | | | | | Adds the command line compression tools which are needed by bitbake (From OE-Core rev: 58f5389e3c6b0e5b29df8850c2056b5fc41b618f) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: use new override syntax in commentsChen Qi2021-08-121-2/+2
| | | | | | | (From OE-Core rev: 572e7db6e8831227911ff3e52bde3a4aa6df1c91) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add DEBUG_PREFIX_MAP to TARGET_LDFLAGSTony Battersby2021-08-121-1/+1
| | | | | | | | | | | | | | | -f*-prefix-map flags are required when linking with LTO enabled to make the output binary reproducible. See discussion here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101473 [YOCTO #14481] (From OE-Core rev: fddaecc88979967d0e00e2fafdbaaabec030da9f) Signed-off-by: Tony Battersby <tonyb@cybernetics.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sdk: Decouple default install path from built in pathRichard Purdie2021-08-021-1/+3
| | | | | | | | | | | | | | Add SDKPATHINSTALL which is used as the default install location of the SDK instead of SDKPATH. This means the default install path isn't encoded into every SDK binary, meaning if a date is used there the entire SDK doesn't have to rebuild. Most distros can switch to only customise SDKPATHINSTALL meaning more sstate reuse too. [YOCTO #14100] (From OE-Core rev: bc4ee5453560dcefc4a4ecc5657df5cc1666e153) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Convert to new override syntaxRichard Purdie2021-08-021-45/+45
| | | | | | | | | | | | This is the result of automated script conversion: scripts/contrib/convert-overrides.py <oe-core directory> converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: change GNOME_MIRROR to new oneOleksandr Kravchuk2021-07-241-1/+1
| | | | | | | | | | URI has been permanently moved and returns HTTP 301. (From OE-Core rev: a3a85d54af38a30f6de5f6d23e432afa26859888) Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: enable debuginfod in native/nativesdkAlexander Kanavin2021-06-171-2/+2
| | | | | | | | | This was an oversight when the distro feature was introduced. (From OE-Core rev: 4a985ff0dd13c455dadf85f4ad35a0a42f4bd9f1) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: alphabetize contents of ASSUME_PROVIDEDRobert P. J. Day2021-05-181-8/+8
| | | | | | | | | Alphabetical order is always good. (From OE-Core rev: 338834153ec2042fbe256b598753ffe492221cc4) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: sort MIRROR list, add missing SAMBA_MIRRORRobert P. J. Day2021-05-061-3/+5
| | | | | | | | | | | As is the pattern with all lists, put the list of MIRRORs in alphabetical order, and add an entry for SAMBA_MIRROR as it appears in the samba recipe from the meta-networking layer. (From OE-Core rev: 3301536f821dce86cd3683d9c50abea2d39c6c20) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Use gcc-nm as default NMKhem Raj2021-04-271-1/+1
| | | | | | | | | This ensures linker LTO plugin is loaded correctly (From OE-Core rev: d6ffd683bf635548e0bfb3fd6458ed03e26ec2bf) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Limit the number of OpenMP threadsJoshua Watt2021-04-051-1/+6
| | | | | | | | | | | | Limits the number of OpenMP threads to match BB_NUMBER_THREADS. This prevents OpenMP (libgomp in particular) from falling back to using all the available CPUs, which behaves poorly when attempting to limit build usage, especially when attempting to build in a container. (From OE-Core rev: fd2b8986aef11609123da917aaf6bcbe41f63112) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: ensure BUILD_* tools match target toolsRoss Burton2021-03-281-0/+3
| | | | | | | | | Add a few more tools to the BUILD_* list, to match the target tool list. (From OE-Core rev: 633393830aea0120c4a2a165917040223630c49d) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: correct description of HOSTTOOLS_DIRRobert P. J. Day2021-03-281-1/+1
| | | | | | | | | HOSTTOOLS_DIR contains symlinks to host tools, not copies (From OE-Core rev: fb7692da7faa49b370680decbbaceaeb85b6889d) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Split PSEUDO_IGNORE_PATHS to be more readableRichard Purdie2021-02-271-1/+4
| | | | | | | | | We've had a lot of concern about the readability of diffs of this path setting, refactor to avoid long line length. (From OE-Core rev: f3930cba16ccbc4b76ed14187d5586d6479bc59e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Introduce FAKEROOTLOGS variable used by bitbake to print ↵Tomasz Dziendzielski2021-02-241-0/+1
| | | | | | | | | | | | pseudo.log Bitbake depends on this variable while looking for pseudo.log file in case of fakeroot task failure. (From OE-Core rev: e8e9e5f62b144828387e20eec2e66fcd61edd0d3) Signed-off-by: Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Do not use lib64 for baselib on musl/ppc64Khem Raj2021-02-231-2/+2
| | | | | | | | | | musl is configured to use /lib and /usr/lib for ppc64 unlike glibc where it is expected to have libs in /lib64 and /usr/lib64 (From OE-Core rev: 998d15a86282d9cf57fbd0a4eb76a56b9938a348) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Set as default task umask of 022Richard Purdie2021-02-161-0/+3
| | | | | | | | | | | | | Rather than trying to set the umask of every task to the correct value for determinism, set one value globally. This uses a new bitbake variable so bump the minimum version to match. This fixes strange determinism issues in at least quilt-ptest, valgrind-ptest and kernel-devsrc. (From OE-Core rev: b07b7deeae3d519d9998d583592f3e4f8f2802b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/python: Drop setting RDEPENDS/RPROVIDES defaultRichard Purdie2021-01-291-2/+0
| | | | | | | | | | | | We never recommend setting RDEPENDS or RPROVIDES without a package name against them. The default in bitbake.conf is legacy only, drop it. The python recipe was trying to add to the empty variable in the native case fix that too. (From OE-Core rev: b8bbc1bbe282cce2ea4d0ff293f931f6caf6153b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "ccache.bbclass: use ccache from host distribution"Robert Yang2021-01-201-1/+1
| | | | | | | | | | | This reverts commit f5b29367af4d8e5daea5771264774aa49519f9a8. Will use ccache-native which is more reliable. (From OE-Core rev: 1b659623430e1a6e6dd266e65bab7ca8155a7138) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add /run/ to PSEUDO_IGNORE_PATHSRichard Purdie2021-01-081-1/+1
| | | | | | | | | | | | Builds were failing on WSL2 which turns out to be due to accesses to /run/ on those systems. Add this to PSEUDO_IGNORE_PATHS to fix builds on WSL2. [YOCTO #14175] (From OE-Core rev: 1d1bf51217e8b4d54af28739d3271484ee5a7974) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add mkfifo to HOSTTOOLSRichard Purdie2021-01-051-1/+1
| | | | | | | | | This is about to be needed by the psplash recipe and is a standard part of coreutils so usually present on hosts. (From OE-Core rev: 99206612a58e6b69718910e0806d9d36997b2fba) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ccache.bbclass: use ccache from host distributionAlexander Kanavin2020-12-311-1/+1
| | | | | | | | | | | | | | | ccache 4.x has hard dependencies on cmake-native (used as build system) and zstd, which means inserting ccache-native as DEPENDS into everything creates circular dependencies which are impossible to break. ccache 3.x did not have this problem as it used plain makefiles and an in-tree copy of zlib. (From OE-Core rev: f5b29367af4d8e5daea5771264774aa49519f9a8) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: default SDKMACHINE to the build host architectureRoss Burton2020-12-241-1/+1
| | | | | | | | | | | | | | | | Currently there's a limitation that Extensible SDKs can only be build on a machine with the same architecture as the SDK. However, SDKMACHINE defaults to x86-64, which means eSDKs cannot be built out of the box on arm64 systems. By defaulting SDKMACHINE to ${BUILD_ARCH} we generate SDKs for the build host, so they'll always work out of the box. (From OE-Core rev: 539cd4a5fbb9e4507d90bfb1165fcb06907b46d8) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Prevent pyc file generation in pseudo contextPaul Barker2020-12-201-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | This also effectively reverts commit b6d30c21b0: bitbake.conf: Extend PSEUDO_IGNORE_PATHS to ${COREBASE}/meta The contents of ${COREBASE}/meta were ignored as pyc files could be generated for the contents of the lib subdirectory if python modules were imported within a pseudo context. However this doesn't protect us from pyc files being generated in the lib directories for other layers. It's far better to tell python not to produce pyc files when running under pseudo (by setting the PYTHONDONTWRITEBYTECODE variable) as this will cover any location where pyc files could possibly be created. This variable is set in FAKEROOTBASEENV so that it applies to the bitbake-worker instance for fakeroot tasks, preventing pyc files from being generated for imports in python tasks themselves. Also add a test case to ensure that pyc files are not created in tasks which are executed under pseudo. (From OE-Core rev: 73d538f20743017a44cea4c20dbe09a0327cfc71) Signed-off-by: Paul Barker <pbarker@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Canonicalize paths in PSEUDO_IGNORE_PATHSPeter Kjellerstedt2020-12-201-2/+2
| | | | | | | | | | | Use oe.path.canonicalize() to canonicalize the paths in PSEUDO_IGNORE_PATHS before passing them to pseudo. This is needed since pseudo will compare them to paths that are canonicalized. (From OE-Core rev: 1f2a497daa09cf3459e27ad6e0e8513938b52c79) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "bitbake.conf: Add all layers (from BBLAYERS) to PSEUDO_IGNORE_PATHS"Richard Purdie2020-12-091-1/+1
| | | | | | | | | | | | | This reverts commit cc30537bb4d0815c4d69f0b1a1a8a200085902d5. There are issues with this change where the build directory may be included within the paths included in BBLAYERS, which is particularly problematic where people are using kas. An alternative to this to handle the pyc file issue is being worked on but revert this for now whilst that fix is developed. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add all layers (from BBLAYERS) to PSEUDO_IGNORE_PATHSPeter Kjellerstedt2020-12-031-1/+1
| | | | | | | | | | | Instead of ignoring ${COREBASE}/meta in PSEUDO_IGNORE_PATHS (which may or may not ignore all layers depending on how they are named and placed under ${COREBASE}), ignore all layers. (From OE-Core rev: cc30537bb4d0815c4d69f0b1a1a8a200085902d5) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Exclude ${CCACHE_DIR} from pseudo databaseMingli Yu2020-10-301-1/+1
| | | | | | | | | | | | | | | | | | | | | When ccache enabled as below: INHERIT += "ccache" CCACHE_DIR = "/path/build/ccache" There comes do_install failure for some recipes randomly, take linux-libc-headerswhen as example. $ cat /path/build/tmp/work/corei7-64-wrs-linux/linux-libc-headers/5.8-r0/pseudo/pseudo.log [snip] path mismatch [1 link]: ino 243004209 db '/path/build/ccache/6/stats' req '/path/build/ccache/7/stats.lock'. [snip] Exclude ${CCACHE_DIR} from pseudo database to fix the potential do_install failure. (From OE-Core rev: b65e5280bf9e7f1f9c8e6acabab79bcf209e5342) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Extend PSEUDO_IGNORE_PATHS to ${COREBASE}/metaRichard Purdie2020-10-081-1/+1
| | | | | | | | | Unfortunately, .pyc files can be generated in meta/lib/oe which corrupt the pseudo database so we need to extend the ignore list to cover this as well. (From OE-Core rev: e0cb6dd689a362d8433caa14cc5a9fdd5eb44923) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* base/bitbake.conf: Enable pseudo path filteringRichard Purdie2020-10-071-5/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a pretty big change to the way pseudo operates when used in OpenEmbedded. Normally, pseudo monitors and logs (adds to its database) any file created or modified whilst in a fakeroot environment. There are large numbers of files we simply don't care about the permissions of whilst in that fakeroot context, for example ${S}, ${B}, ${T}, ${SSTATE_DIR}, the central sstate control directories, This change uses new functionality in pseudo to ignore these directory trees, resulting in a cleaner database with less chance of "stray" mismatches if files are modified outside pseudo context. It also should reduce some overhead from pseudo as the interprocess round trip to the server is avoided. There is a possible complication where some existing recipe may break, for example, we found a recipe which was writing to "${B}/install" for "make install" in do_install and since we listed ${B} as not to be tracked, there were errors trying to chown root for files in this location. This patch fixes a few corner cases in OE-Core when used with this new ignore list: * The archiver directory matched a "${WORKDIR}/deploy*" pattern so was renamed to something else since that directory does need its root permissions * The ${S} and ${B} ignoring is conditional on them being different to ${WORKDIR} * package_write_* task output (the debs/rpms/ipks) are now owned by the build user so we don't want the file ownership information in the hashequiv outhash calculation even if they are built under pseudo. * The fontcache postinstall intercept is run under qemu outside of pseudo context so delete files it may delete up front where pseudo can see this. * SSTATE_DIR is in PSEUDO_PATHS_IGNORE, which is in FAKEROOTENV which is cached by bitbake. We therefore need to trigger reparsing if this changes, which means SSTATE_DIR can be in BB_HASHBASE_WHITELIST but not BB_HASHCONFIG_WHITELIST. Rework the variables to handle this. This otherwise breaks some of our sstate tests in oe-selftest. * Ignore the temp directory wic uses for rebuilding rootfs. (From OE-Core rev: ad8f5532ffaead9a5ad13e1034fe9e5e1b7979f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: add name of multiconfig to BUILDCFG_HEADER when multiconfig is ↵Chris Laplante2020-09-301-1/+1
| | | | | | | | | active (From OE-Core rev: 96694d3bc16acfb88206e2d1b9e884ab5887c44d) Signed-off-by: Chris Laplante <chris.laplante@agilent.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: use ${TCMODE}-${TCLIBC} directory for CACHEMartin Jansa2020-09-171-1/+4
| | | | | | | | | | | | | | | | | | | | | | | * move TCMODE and TCLIBC from defaultsetup.conf to bitbake.conf * set CACHE as it was in defaultsetup.conf and drop it from defaultsetup.conf * most if not all DISTROs are now including defaultsetup.conf and TCLIBC is pretty much expected to be always set correctly, e.g.: meta/recipes-core/systemd/systemd_243.2.bb: if d.getVar('TCLIBC') == "musl": meta/recipes-devtools/gcc/gcc-runtime.inc: if [ "${TCLIBC}" != "glibc" ]; then meta/recipes-devtools/gcc/libgcc.inc: if [ "${TCLIBC}" != "glibc" ]; then meta/recipes-devtools/icecc-toolchain/nativesdk-icecc-toolchain_0.1.bb:ENV_NAME="${DISTRO}-${TCLIBC}-${SDK_ARCH}-@TARGET_PREFIX@${DISTRO_VERSION}.tar.gz" meta/recipes-devtools/valgrind/valgrind_3.15.0.bb:RRECOMMENDS_${PN} += "${TCLIBC}-dbg" meta/recipes-kernel/linux/kernel-devsrc.bb:RDEPENDS_${PN} = "bc python3 flex bison ${TCLIBC}-utils" meta/classes/buildhistory.bbclass:BUILDHISTORY_DIR_IMAGE = "${BUILDHISTORY_DIR}/images/${MACHINE_ARCH}/${TCLIBC}/${IMAGE_BASENAME}" meta/classes/cross-canadian.bbclass: if d.getVar("TCLIBC") in [ 'baremetal', 'newlib' ]: meta/classes/kernel.bbclass: tclibc = d.getVar('TCLIBC') meta/classes/toaster.bbclass: BUILDHISTORY_DIR_IMAGE_BASE = e.data.expand("%s/images/${MACHINE_ARCH}/${TCLIBC}/"% BUILDHISTORY_DIR) (From OE-Core rev: 57aa60ef6422568b425b6ccc4451567efc578469) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image-artifact-names: introduce new bbclass and move some variables into itMartin Jansa2020-09-171-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * similar to kernel-artifact-names for other recipes/bbclasses which need to use some deployed artifacts * bitbake.conf: move IMAGE_BASENAME, IMAGE_VERSION_SUFFIX, IMAGE_NAME, IMAGE_LINK_NAME variables * image_types.bbclass: move IMAGE_NAME_SUFFIX variable * currently IMAGE_NAME_SUFFIX is used only by image.bbclass, image_types.bbclass and meta/recipes-core/images/build-appliance-image_15.0.0.bb but if it's needed by some recipe which isn't itself an image, then it's useful in bitbake.conf, e.g. we have a recipe for creating VirtualBox appliances which combines .wic.vmdk with .ovf file to create .zip with appliance, but for that we need the filename of .wic.vmdk which now contains IMAGE_NAME_SUFFIX https://github.com/webOS-ports/meta-webos-ports/blob/4980ce52a43ac6897657602810313af359f0b839/meta-luneos/recipes-core/images/luneos-emulator-appliance.inc#L24 * we were hardcoding .rootfs suffix where needed, but for quite long time it's configurable with IMAGE_NAME_SUFFIX since: commit 380ee36811939d947024bf78de907e3c071b834f Author: Patrick Ohly <patrick.ohly@intel.com> Date: Mon Mar 7 18:07:52 2016 +0100 image creation: allow overriding .rootfs suffix and might not match with hardcoded .rootfs, so make it easier to use IMAGE_NAME_SUFFIX where needed even without inheritting whole image_types.bbclass [YOCTO #12937] (From OE-Core rev: 456b700d51a5052a285a8477304f902c335223be) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: hash equivalency and pr serviceMark Hatle2020-09-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the PR service is enabled a number of small changes may happen to variables. In the do_package step a call to package_get_auto_pr will end up setting PRAUTO and modifying PKGV (if AUTOINC is there). PRAUTO is then used by EXTENDPRAUTO, which is then used to generate PKGR. Since this behavior typically happens BEFORE the BB_UNIHASH is calculated for do_package, we need a way to defer the expansion until after we have the unihash value. Writing out the pkgdata files w/o AUTOPR and PKGV (AUTOINC) expanded to placeholder values is the easiest way to deal with this. All other variables are expanded as expected. In the next task, typically do_packagedata, we will then use the UNIHASH from the do_package to get the PR (AUTOPR) as well as generate the AUTOINC replacement value (now PRSERV_PV_AUTOINC). The do_packagedata then translates the placeholders to the final values when copying the data from pkgdata to pkgdata-pdata-input. Also update the prservice test case. With unihash, just changing the do_package (via a _append) will not change the PR. So write the date to a specific file that is incorporated into the unihash to ensure it is always different for the test. Various assert messages were also updated to make it easier to figure out where/why a problem occured. (From OE-Core rev: 2e32f37b0e4abc438c8f60e673cd18a5cc110768) Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: fix whitespace issuesKonrad Weihmann2020-07-081-2/+2
| | | | | | | (From OE-Core rev: a58672fdf7e3b26b57ec31b9ba4f1eaaa7f5a53c) Signed-off-by: Konrad Weihmann <kweihmann@outlook.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Remove TERM from default BB_HASHBASE_WHITELISTJacob Kroon2020-06-171-1/+1
| | | | | | | | | | | Since BitBake commit 0d5cdd0c0d65f2f81c3af0f3767fee86c4142c3a TERM is no longer preserved in the environment by BitBake, so there should be no need to whitelist it by default. (From OE-Core rev: 72c4222b095a49d5ba8252abbae5025196519cd5) Signed-off-by: Jacob Kroon <jacob.kroon@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "bitbake.conf: Remove unused DEPLOY_DIR_TOOLS variable"Richard Purdie2020-06-121-0/+1
| | | | | | | | | | | This reverts commit b1f15f651461d07a8cfbd3bdcfea0e89f195212d. The variable is used by multiple other layers and users are requesting it be added back. (From OE-Core rev: 49d0f822618890b61d2498b07dda6418f885321e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Remove unused DEPLOY_DIR_TOOLS variableRobert P. J. Day2020-05-301-1/+0
| | | | | | | | | | | | | | | | | Variable DEPLOY_DIR_TOOLS was introduced in 2007: commit f751a20152c651a33f08ceda0502fa1d4f11c005 Author: Richard Purdie <richard@openedhand.com> Date: Wed Aug 8 21:02:39 2007 +0000 bitbake.conf: Sync with OE.dev apparently never used so get rid of it. (From OE-Core rev: b1f15f651461d07a8cfbd3bdcfea0e89f195212d) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: propagate 'opengl' DISTRO_FEATURE to native/nativesdk from targetAlexander Kanavin2020-05-271-2/+2
| | | | | | | | | | | | | | | | This will allow better control over native virgl/qemu configurations. Adjust gtk+3/cairo native configurations to actually ignore opengl when building for -native: we do not need it, and it would cause build failures as only a limited subset of mesa-native is currently built. Drop native/nativesdk overrides from virglrenderer/libepoxy recipes as opengl feature is now correctly set for those variants. (From OE-Core rev: 0e1f8fa0535dab63742f575b52ec9fa891368ca2) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Prevent git from detecting parent repo in recipeJoshua Watt2020-05-091-1/+5
| | | | | | | | | | | | | Prevents git commands run in a recipe from moving up past ${WORKDIR} when searching for a .git directory, and thus prevents them from detecting the parent OE-core .git directory. Fixes several reproducibility issues where recipes would use the OE-core version as the recipe version due to git walking up the tree. (From OE-Core rev: e496605ea197414b58025293e73dec099a8976c6) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: omit XZ threads and RAM from sstate signaturesAndré Draszik2020-03-061-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The number of threads used, and the amount of memory allowed to be used, should not affect sstate signatures, as they don't affect the outcome of the compression if xz operates in multi-threaded mode [1]. Otherwise, it becomes impossible to re-use sstate from automated builders on developer's machines (as the former might execute bitbake with certain constraints different compared to developer's machines). This is in particular a problem with the opkg package writing backend, as the OPKGBUILDCMD depends on XZ_DEFAULTS. Without the vardepexclude, there is no re-use possible of the package_write_ipk sstate. Whitelist the maximum number of threads and the memory limit given assumptions outlined in [2] below. (From OE-Core rev: 7927d5f6eaab48578b23db9a4c38e2f87f011353) Signed-off-by: André Draszik <git@andred.net> [1] When starting out in multi-threaded mode, the output is always deterministic, as even if xz scales down to single-threaded later, the archives are still split into blocks and size information is still added, thus keeping them compatible with multi-threaded mode. Also, when starting out in multi-threaded mode, xz never scales down the compression level to accomodate memory usage restrictions, it just scales down the number of threads and errors out if it can not accomodate the memory limit. [2] Assumptions * We only support multi-threaded mode (threads >= 2), builds should not try to use xz in single-threaded mode * The thread limit should be set via XZ_THREADS, not via modifying XZ_DEFAULTS or XZ_OPTS, or any other way * The thread limit should not be set to xz's magic value zero (0), as that will lead to single-threaded mode on single-core systems. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: more deterministic xz compression (threads)André Draszik2020-03-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | xz archives can be non-deterministic / non-reproducible: a) archives are created differently in single- vs multi-threaded modes b) xz will scale down the compression level so as to be try to work within any memory limit given to it when operating in single-threaded mode This means that due to bitbake's default of using as many threads as there are cores in the system, files compressed with xz will be different if built on a multi-core system compared to single-core systems. They will also potentially be different if built on single-core systems with different amounts of physical memory, due to bitbake's default of limiting xz's memory consumption. Force multi-threaded operation by default, even on single-core systems, so as to ensure archives are created in the same way in all cases. (From OE-Core rev: d96aa8594c8d7531da34645cadbac4f7549d8ae6) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* hosttools: add utilities for all supported checksumsBartosz Golaszewski2020-02-281-1/+2
| | | | | | | | | | | Only md5sum and sha256sum are currently provided by HOSTTOOLS. Trying to use any other checksum conversion will result in a build failure. Fix it by adding other supported checksum utilities to HOSTTOOLS. (From OE-Core rev: 78155e5fcff9362049b576d20e31c3519c48485b) Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package.bbclass: Support stripping and debug copy of static librariesMark Hatle2020-02-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | By default, we won't copy and strip static libraries. However, this functionality can be useful in some cases where people are doing development on the target, and don't generally want the larger debug capable static libraries. To enable the new functionality set: PACKAGE_DEBUG_STATIC_SPLIT = '1' Add a new function splitstaticdebuginfo. Thus function will copy the unmodified static library into the specific debug directory location. By keeping an unmodified version, it is possible for a user trying to debug something to use -L /usr/lib/.debug-static and their existing build commands to switch from stripped to full debug versions. The PACKAGE_DEBUG_SPLIT_STYLE will select between two different approaches, /usr/lib/debug-static or <path>/.debug-static. Additionally you can now choose to strip static libraries to conserve space. If either 'PACKAGE_DEBUG_STATIC_SPLIT' or 'PACKAGE_STRIP_STATIC' is set to 1, the static library will be stripped. (This is not on by default, as it could make diagnosing static library usage difficult in some cases.) Add to insane.bbclass a skip to the staticdev warning for the specific -dbg package versions. (From OE-Core rev: 17fa66c8199d73f0b59b2b3e609075933bf1e74b) Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/sanity: Drop makeinfo as being required on buildhostRichard Purdie2020-02-031-1/+1
| | | | | | | | | | | | | | | | | This is a long standing 'odd' dependency which we've meant to resolve. We shouldn't need it and it introduces reproducability issues. We already have texinfo-dummy-native and texinfo-native which can provide it but the work to remove the hosttool was never completed. After cleaning up texinfo.bbclass, this can now be removed with minimal impact on build time. [YOCTO #13753] (From OE-Core rev: 0c58c479af151969dfb84d8763696da657f7248d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-15 16:12:38 +0000