linux/poky.git/meta/classes-recipe/rust-target-config.bbclass, branch langdale

meta: remove True option to getVar and getVarFlag calls (again)

2023-02-15T21:47:00+00:00

* True is default since 2016 and most layers were already updated not to pass this parameter where not necessary, e.g. oe-core was updated couple times, first in: https://git.openembedded.org/openembedded-core/commit/?id=7c552996597faaee2fbee185b250c0ee30ea3b5f Updated with the same regexp as later oe-core update: https://git.openembedded.org/openembedded-core/commit/?id=9f551d588693328e4d99d33be94f26684eafcaba with small modification to replace not only d.getVar, but also data.getVar as in e.g.: e.data.getVar('ERR_REPORT_USERNAME', True) and for getVarFlag: sed -e 's|$d\.getVarFlag \?$( \?$[^,()]*, \?[^,()]*$, \?True)|\1(\2)|g' \ -i $(git grep -E 'getVarFlag ?$ ?([^,()]*), ?([^,()]*), ?True$' \ | cut -d':' -f1 \ | sort -u) (From OE-Core rev: f12fcb8a3f3d11c981c223569f8f40ec705c837a) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie (cherry picked from commit 26c74fd10614582e177437608908eb43688ab510) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

rust: Do not use default compiler flags defined in CC crate

2023-01-26T23:39:06+00:00

Rust crates build dependecy C libraries using "CC" crate. This crate adds some default compiler parameters depending on target arch. For some targets these parameters conflict with the parameters defined by OE. Warnings/errors like this can be seen in the case: cc1: error: switch '-mcpu=cortex-a15' conflicts with switch '-march=armv7-a+fp' [-Werror] Lets use only the OE parameters by exporting CRATE_CC_NO_DEFAULTS. https://github.com/rust-lang/cc-rs#external-configuration-via-environment-variables This patch fixes https://bugzilla.yoctoproject.org/show_bug.cgi?id=14947 (From OE-Core rev: 94939f608c6984e3a92999a384a03a35c2b34ed6) Signed-off-by: Anton Antonov Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 0c07089bdf7e0d7d8f37552db0bcd75f860979d9) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

rust-target-config: match riscv target names with what rust expects

2022-11-09T17:42:14+00:00

Official rust risc-v targets are prefixed with riscv32gc- and riscv64gc-: https://doc.rust-lang.org/nightly/rustc/platform-support.html Particularly crossbeam-utils make important build time decisions for atomics based on those names, and so we need to match ours with official targets. On the other hand, the actual definitions for those targets do not use the 'gc' suffix in 'arch' and 'llvm-target' fields, and so we need to follow that too, to avoid cryptic mismatch errors from rust-llvm: https://github.com/rust-lang/rust/blob/master/compiler/rustc_target/src/spec/riscv32gc_unknown_linux_gnu.rs (From OE-Core rev: 2daa8d76369cd06e5c357e393e3145e08f3d6760) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 1cfb9c8a59d98ccc9b0510cd28fb933f72fb6b6c) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

rust-target-config: Fix qemuppc target cpu option

2022-08-31T09:40:07+00:00

We see a lot of warnings about incorrect processor types on qemuppc, drowning out anything else. Fix the option. (From OE-Core rev: 0371e429d9e127983ddfaec366ce1c38c99158e4) Signed-off-by: Richard Purdie

rust-target-config: Drop has-elf-tls option

2022-08-30T09:33:35+00:00

This option doesn't seem to exist any more and causes lots of warnings. Remove it. (From OE-Core rev: 8e1614a906086fb46c5dd7b7f2dffab91194165c) Signed-off-by: Richard Purdie Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie

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