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

classes: Update classes to match new bitbake class scope functionality

2022-08-12T14:27:17+00:00

Move classes to classes-global or classes-recipe as appropriate to take advantage of new bitbake functionality to check class scope/usage. (From OE-Core rev: f5c128008365e141082c129417eb72d2751e8045) Signed-off-by: Richard Purdie

classes: Add SPDX license identifiers

2022-08-12T10:58:01+00:00

As stated in our top level license files, the license is MIT unless otherwise stated. Add SPDX identifers accordingly. Replace older license statementa with the standardised syntax. Also drop "All Rights Reserved" expression as it isn't used now, doesn't mean anything and is confusing. (From OE-Core rev: 081a391fe09a21265881e39a2a496e4e10b4f80b) Signed-off-by: Richard Purdie

classes: Add copyright statements to files without one

2022-08-12T10:58:01+00:00

Where there isn't a copyright statement, add one to make it explicit. Also drop editor config lines where they were present. (From OE-Core rev: 880c1ea3edc8edef974e65b2d424fc36809ea034) Signed-off-by: Richard Purdie

toolchain-scripts.bbclass: adjust toolchain_create_tree_env_script to better replicate (e)SDK

2022-07-28T10:50:17+00:00

Specifically: 1. Place the environment setup file into $B and not into $TMPDIR, so that the recipe using the class can itself better decide what to do with the file. 2. Use global, unified sysroots (provided through build-sysroots recipe) and not recipe-specific ones, as this allows flexible on-the-fly management of what libraries are available to build applications, without having to modify any recipes, similar to eSDK 'extensible' part. This also requires adjustment of the sstate sametune_samegsigs test, as meta-ide-support becomes dependent on $MACHINE (unified sysroots have it in their paths) and needs to be excluded from the test. 3. Add a few missing settings that have been added to SDK environment files. 4. Add a snippet to the environment setup file that also runs the relocation scripts. In regular SDKs this is executed by the SDK installer, in direct SDK we can do it when setting up the environment. (From OE-Core rev: db5dfd78ae441201778b1175f4fb9a3eba994899) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni 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