linux/poky.git/meta/classes/toolchain-scripts.bbclass, branch yocto-4.0.19

toolchain-scripts: Handle spaces within user $PATH

2023-03-23T22:45:34+00:00

The environment-setup script generated by the recipe was not quoting the user existing PATH when updating it causing the export command to fail. Add necessary double quotes around $PATH. (From OE-Core rev: 64dd672193b43b1364acc73918a54abaa93645e4) Signed-off-by: Kenfe-Mickael Laventure Signed-off-by: Alexandre Belloni (cherry picked from commit 42177ff2d45ee70ad00917bb6fbabca49dae4f59) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

toolchain-scripts: compatibility with unbound variable protection

2023-01-26T23:37:05+00:00

Fixed an error when Bash's unbound variable protection is enabled (set -u) and variable "LD_LIBRARY_PATH" does not exist. (From OE-Core rev: ad2b7b4d4138ac5f6f74f69d9d6d88a592b14c6f) Signed-off-by: Jan Kircher Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 85685370b0ad93291cda59fb091a15eeecf5e0d5) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

cmake: support to create per-toolchain cmake file in SDK

2022-03-31T16:52:59+00:00

The patch creates ${MULTIMACH_TARGET_SYS}-toolchain.cmake file at ${SDK_INSTALL_DIR}/sysroots/${SDK_SYS}/usr/share/cmake/, which is per-toolchain CMake toolchain file containing arch-specific values and independent of OE environment variables. The file gets created after installing SDK toolchain installer ined by running "bitbake -c populate_sdk ". The changes are similar to meson-setup.py which is used to create arch-specific ${SDK_INSTALL_DIR}/sysroots/${SDK_SYS}/usr/share/meson/*-meson.cross [YOCTO #14644] Tested-by: Jan Dorniak (From OE-Core rev: 42e68397ec74b3cd8ae5df45355c8f6254b48cd8) Signed-off-by: Jagadeesh Krishnanjanappa Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

toolchain-scripts.bbclass: use double quotes for exported PS1

2022-02-08T14:20:18+00:00

Use double quotes("") rather than single quotes('') for PS1 in EXPORT_SDK_PS1 which will be exported in SDK environment file. Then it could set PS1 for SDK env with some variables in host env, such as the original PS1. The SDK PS1 could be some distinct words plus original PS1 rather than replace the whole original PS1. For example, it could set in local.conf with SDK_PS1 = "(oesdk) \${PS1}" then it just prepends '(oesdk) ' before original PS1 after source the SDK environment file. (From OE-Core rev: e13e657dabcabd97f50794e7375777ef5ad883c8) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

siteinfo/autotools: Ensure task checksums reflect site files

2021-09-23T12:49:11+00:00

Currently, if you change the site files, nothing rebuilds since they are not accounted for in task checksums. They could/should be through the file-checksums task flag. We need to cache all the files looked for, whether the exist or not so that if they do exist and didn't, the checksum also changes. This gets complicated by the need to clean out hardcoded build paths from the variable and that other layers can have site files. This patch adds this functionality. A new variable, SITEINFO_PATHVARS is added which controls which substitutions to make on the file-checksum values to remove the hardcoded paths. Layers adding site files will need to set this to a variable that has the layer path in it and is excluded from task hashes (COREBASE is the one the core layer uses). This patch will cause yocto-check-layer to fail for some layers where site files are added yet the layer isn't a machine specific layer. This is arguable correct since these additional site files apply to all recipes and things from a layer like core could be changed by such changes so it is right they should rebuild. There is a determinism issue potentially there if not. meta-openembedded does have some such references but looking at them they should move to core or likely just be removed as most look obsolete anyway. [YOCTO #13729] (From OE-Core rev: 29daffc2410f06f36b779d5bf1fd1ef6e900ca8f) Signed-off-by: Richard Purdie

Convert to new override syntax

2021-08-02T14:44:10+00:00

This is the result of automated script conversion: scripts/contrib/convert-overrides.py converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie

toolchain-scripts.bbclass: customize prompt string for SDKs

2021-03-11T15:24:13+00:00

Introduce a new variable SDK_PS1 to customize prompt string for SDKs when source script environment-setup-script. If variable SDK_PS1 is not set or empty, nothing changed. Otherwise new PS1 with the value of SDK_PS1 is used after source the sdk environment file. (From OE-Core rev: 81ed52f245c18c50e8df51fce1f62906cd4ddd05) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

toolchain-scripts: export READELF

2019-10-09T13:07:43+00:00

The readelf binary is prefixed, so export READELF in the SDKs so that the correct readelf binary can be used. This fixes problems with the symbol extractor in Meson with multilib SDKs where readelf can't be found correctly. (From OE-Core rev: 2795e3bfdefc9f48294802ea7301dae1910553dc) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

toolchain-scripts: run post-relocate scripts for every environment

2019-01-08T11:16:44+00:00

SDKs for multilib configurations have multiple environment scripts, so re-arrange the post-relocate hook invocation so that it runs the post-relocate hooks after sourcing each environment script. (From OE-Core rev: c4897001cb3eeda1f4f11197b28c09c950bdcf02) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

toolchain-scripts: put TARGET_ARCH and TARGET_OS into environment

2018-08-07T11:13:03+00:00

It's useful for the SDK to know exactly what TARGET_ARCH and TARGET_OS are, specifically for SDK QA. (From OE-Core rev: 0b5f1b0430efac8129bca330370d8818ea93bb39) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie