linux/poky.git/meta/classes-recipe, branch walnascar-5.2

cargo.bbclass: show PACKAGECONFIG_CONFARGS in bbnote

2025-03-25T21:20:41+00:00

* PACKAGECONFIG_CONFARGS was added in: https://git.openembedded.org/openembedded-core/commit/?id=16745b20452de60ae2474433cc1a2fb1ed9f6a64 but it wasn't added in bbnote above which might lead to confusing errors like I got now: NOTE: cargo build -v --frozen --target aarch64-webos-linux-gnu --release --manifest-path=.../git//Cargo.toml error: unexpected argument '--cfg' found Usage: cargo build --verbose... --frozen --target [] --release --manifest-path and was wondering where --cfg came from. * it was from recipe where we already use: RUSTFLAGS:append = " ${PACKAGECONFIG_CONFARGS}" it will be difficult to use PACKAGECONFIG for RUSTFLAGS and prevent them to be used here for cargo as well, what about the recipes which need them to explicitly append them to CARGO_BUILD_FLAGS ? (From OE-Core rev: 38d953b2ffd4e0cee9e77f97988e44be105023c6) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

cargo: pass PACKAGECONFIG_CONFARGS to cargo build

2025-03-20T11:29:04+00:00

In order to allow rust packages to define PACKAGECONFIG options, append the contents of PACKAGECONFIG_CONFARGS to the build command. This patch was already submitted by Bartosz Golaszewski on older version but was never merged. It will be really usefull for Rust recipes. (From OE-Core rev: 16745b20452de60ae2474433cc1a2fb1ed9f6a64) Signed-off-by: Jean-Pierre Geslin Signed-off-by: Richard Purdie

autotools: require that a configure script exists

2025-03-18T11:25:36+00:00

There's no point inheriting autotools if you're not actually going to run a configure script, so make a missing configure script fatal. (From OE-Core rev: 6d327a39befae44a88a812bdf4acde800dcee57b) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

native: Drop export statements that aren't needed

2025-03-18T10:27:31+00:00

These are already exported by bitbake.conf, no need to export them again. (From OE-Core rev: 92e52f5afac4877366c1ee2e6c6f0d1f5df84410) Signed-off-by: Richard Purdie

native: follow BUILD_* definitions for OBJCOPY, OBJDUMP and READELF

2025-03-18T10:27:31+00:00

Set the host OBJCOPY, OBJDUMP, and READELF variables to be derived from their corresponding BUILD_* definitions. This makes the native class match the build-gcc.inc file 1 to 1, as these were the only missing. Currently these variables get their definitions from gcc.inc, which uses HOST_PREFIX, and that works because the native class sets HOST_PREFIX to BUILD_PREFIX, but this doesn't seem correct. (From OE-Core rev: 87a6ffe21b706e6aeeeb77891565cbd7730ca163) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie

uboot, kernel: use hex address for UBOOT_ENTRYPOINT

2025-03-11T11:20:34+00:00

Compiling a FIT image with this default values and dump it with dumpimage shows decimal converted values. For example the default value 20008000 looks like this: Image 0 (kernel-1) ... Load Address: 0x01314c40 Entry Point: 0x01314c40 With this change the expected value is printed by dumpimage. (From OE-Core rev: e6f2ca9135ef7da8f8b5925957532734c06e55cc) Signed-off-by: Adrian Freihofer Signed-off-by: Richard Purdie

linux-fitimage: sign setup sections

2025-03-11T11:20:34+00:00

If FIT_SIGN_INDIVIDUAL is set to “1”, a signature section is added to all screen sections, but not to the setup section. To match the setup section with all other sections, the signature is also added. This also helps to implement the associated tests generically. This change is intended to make the code more consistent. However, it is not intended to make the FIT_SIGN_INDIVIDUAL function more popular. Technically, it would be better to remove the signature from all other image sections and discard the FIT_SIGN_INDIVIDUAL function, the use of which is no longer recommended anyway. (From OE-Core rev: 8bf6a9c07cdde8fc8bbd4bb61a4886ccc02a570f) Signed-off-by: Adrian Freihofer Signed-off-by: Richard Purdie

classes-recipe: Consolidate machine-id handling

2025-03-09T20:10:06+00:00

Whenever Systemd is used as an init manager, it requires a machine-id file to be present / initialized / or have the RW rootfs. This change does not introduce a new functionality, but rather merges everything we do with machine-id in one place. (From OE-Core rev: 890b81cdfadc427189eff4bbd2c24e32eb286126) Signed-off-by: Vyacheslav Yurkov Signed-off-by: Richard Purdie

cmake.bbclass: remove whitespace

2025-03-08T18:08:04+00:00

(From OE-Core rev: 219c7c4954c649a1a0c284bb5f35eee533db41c3) Signed-off-by: Victor J. Hansen Signed-off-by: Richard Purdie

kernel-arch: add macro-prefix-map in KERNEL_CC

2025-03-08T18:08:04+00:00

When building external modules, macros can include absolute names of kernel headers. The macro-prefix-map for the STAGING_KERNEL_DIR is currently missing. Add it in the same way as its done in bitbake.conf. This fixes reproducible builds and following build error: ERROR: cryptodev-module-1.14-r0 do_package_qa: QA Issue: File <..> cryptodev.ko <..> contains reference to TMPDIR [buildpaths] (From OE-Core rev: a741e11751bfb8f52be58cf51abeddca4559e5e9) Signed-off-by: Stefan Müller-Klieser Signed-off-by: Richard Purdie