linux/poky.git/meta/conf/toolchain, branch master

toolchain: Provide abstraction for recipe specific toolchain selection

2025-06-16T21:26:38+00:00

This change implements a toolchain selection mechanism. Selection is made using a set of variables, primarily PREFERRED_TOOLCHAIN_TARGET which defaults to gcc. It uses the familiar name for toolchain e.g. "gcc" which selects GNU compiler + binutils as default C/C++ toolchain or "clang" which will use LLVM/Clang Compiler. Layers an add their own toolchain definitions too. There are also PREFERRED_TOOLCHAIN_NATIVE and PREFERRED_TOOLCHAIN_SDK which will ulitmately allow selection of the toolchain used for the native/cross and nativesdk/crosssdk compilers. This currently isn't functional but is essential to the patch to ensure things are set to the existing gcc support in those cases. Users would most commonly want to set: PREFERRED_TOOLCHAIN_TARGET ?= "clang" in local.conf or other distro specific global configuration metadata. It is also selectable at recipe scope, since not all packages are buildable with either clang or gcc, a recipe can explicitly require a given toolchain using the TOOLCAHIN variable, e.g. glibc can not be built with clang therefore glibc recipe sets: TOOLCHAIN = "gcc" The TOOLCHAIN variable is distinct from the user preference so recipes with specific requirements can be identified. This also allows different polcies to be be specified for native/SDK cases in the future. (From OE-Core rev: 45bdedd213aff8df3214b95ef2a8551c0abd93a0) Signed-off-by: Richard Purdie

toolchain/clang: Set compiler providers correctly

2025-06-09T16:43:42+00:00

The clang toolchain include file contained some incorrect settings from the initial draft of the file. Fix those to point at the correct compiler. (From OE-Core rev: 265d1993669cba1ddf60a048798fe943a903c942) Signed-off-by: Richard Purdie

meta: Add TCOVERRIDE for toolchain selection at recipe scope

2025-06-09T16:43:42+00:00

TCOVERRIDE is defined to toolchain- and its added to OVERRIDES that a recipe can see and it can use "toolchain-gcc" or "toolchain-clang" to set specific metadata based upon global distro toolchain policy. (From OE-Core rev: 6010f47124d9067609bbe5d9ff16193c8bf79acf) Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

clang.inc: Add compiler-rt to default deps when using clang compiler

2025-05-27T08:01:17+00:00

This provides needed built-ins which clang uses along with libgcc its not yet a full replacement for libgcc (From OE-Core rev: 2976122bec35165248b312e93ec111b745a91333) Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

clang.inc: Specify ldso when using usrmerge

2025-05-27T08:01:17+00:00

This matches the expectations of distro setups and clang's understanding of what the ldso should look like (From OE-Core rev: 2e95208253211872a501407a1180dc192a634195) Signed-off-by: Khem Raj Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie

toolchain/clang: Remove duplicate RANLIB setting

2025-04-29T08:55:31+00:00

Its already assigned couple of lines above (From OE-Core rev: 67a1d55cb50703a3f585521cf44693ade66cc88b) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

bitbake.conf: Start to separate out gcc related variable definitions

2025-03-05T09:31:16+00:00

To be able to switch toolchains, we need to separate out the gcc definitions into seperate include files. This patch starts that process. Whilst the include is still hardcoded for now, it allows developers to start experimenting with this locally more easily and stops people reinventing this patch. A sample clang configuruation is also included which I was using for experimentation. (From OE-Core rev: be063d58c0985a2c43c16302efb44706fbf3f1b3) Signed-off-by: Richard Purdie