linux/poky.git/meta/classes-recipe, branch halstead/hashclient

Revert "testimage: Enable runtime 'login' screenshot tests"

2024-04-12T17:04:02+00:00

This reverts commit c631640bbdbb3d041bad7d23a612e623cab58855. Signed-off-by: Richard Purdie

testimage: Enable runtime 'login' screenshot tests

2024-04-12T17:04:02+00:00

Enable the new runtime login screenshot tests which primarily test whether sato images display a desktop correctly. (From OE-Core rev: a7785de9c3be647665e116f5eede814b318db282) Signed-off-by: Richard Purdie

classes/pypi: don't expose PYPI_ARCHIVE_NAME

2024-04-12T17:04:02+00:00

This variable is only used when constructing a SRC_URI and some recipes think that it's the correct value to assign if the PyPi package name isn't the same as the recipe name, when PYPI_PACKAGE is actually all that needs to be set. Also document the variables we expect the recipe to assign if needed, and where the PyPi URL structure is documented. (From OE-Core rev: bb21b96a7edfe5f8ae43cf843f80bb0c0a025f0d) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

autotools: update link in comment for cross compiling

2024-04-04T13:05:03+00:00

(From OE-Core rev: bc0a28203334a5925a8f3ea2b955a4cdad87c4c9) Signed-off-by: Jörg Sommer Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

image-live.bbclass: Adjust the default value for INITRD_LIVE

2024-04-04T13:05:03+00:00

The ${INITRAMFS_FSTYPES} may contains multi filesystem types, such as "cpio.gz cpio.xz". So it can't be used directly in setting of the default INITRD_LIVE. We choose the first filesystem type in ${INITRAMFS_FSTYPES} for the default INITRD_LIVE. (From OE-Core rev: aa1a55a90ea86349734e2b62288d54863e01c7b8) Signed-off-by: Kevin Hao Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

populate_sdk_ext.bbclass: only overwirte lsb string if uninative is used

2024-03-30T22:25:43+00:00

Overwriting the lsb string without inheriting from uninative causes shared state cache entries to end up in the wrong path where they are not beeing picked up by the extensible SDK environment. (From OE-Core rev: 6a4c83919f27f0f552e9b79aed11e3da6791b7e9) Signed-off-by: Timon Bergelt Signed-off-by: Richard Purdie

cml1: prompt location of updated .config after do_menuconfig()

2024-03-30T22:25:43+00:00

When modifying the kernel config by invoking '-c menuconfig' manually, a sensible next step is to persist this changed configuration somewhere. A way to do this is to copy the generated .config back to the original config location. For this purpose, emit a copy+pasteable printout of the saved .config path similar to what we have for the fragment location in the 'diffconfig' task already. Example output: | Changed configuration saved at: | /path/to/bsp/build/tmp/work/my-machine-oe-linux/linux-custom/6.6.4/build/.config | Recompile will be forced (From OE-Core rev: b104470763b081f040f4fcac564136fc5562f23b) Signed-off-by: Enrico Jörns Signed-off-by: Richard Purdie

cml1: remove needless check for write_taint attribute

2024-03-30T22:25:43+00:00

The 'FIXME' comment itself says to remove this once the minimum bitbake version has been bumped. This was in 2012. The function was introduced in bitbake commit f7b55a94 ("bitbake: bitbake: ensure -f causes dependent tasks to be re-run") and is already part of bitbake 1.15.3 which is the minimum bitbake version since 'danny'. Remove the check. (From OE-Core rev: 035fe46fbf57ca83baf6610482ee7ee83c825a06) Signed-off-by: Enrico Jörns Signed-off-by: Richard Purdie

kernel-module-split.bbclass: enhance objcopy command call for kernel compilation with llvm

2024-03-26T17:10:51+00:00

Using meta-clang for llvm kernel compilation previously defaulted to the gcc objcopy tool. To improve flexibility and compatibility, $OBJCOPY is preferred over $HOST_PREFIXobjcopy in the kernel-module-split.bbclass. With $OBJCOPY already defined in bitbake.conf, the empty condition has been removed, simplifying the invocation process. (From OE-Core rev: 45366f9162e5a7707c8a46c46b115e8501d367d0) Signed-off-by: lixiaoyong Signed-off-by: Richard Purdie

classes/qemuboot: add depends on qemu-system-native and qemu-helper-native

2024-03-25T13:01:14+00:00

Any image that inherits qemuboot must also add image dependencies on qemu-system-native and qemu-helper-native, otherwise the image won't be able to be booted. Currently this is done by conf/machine/include/qemu.inc, but not every machine that uses qemuboot includes that file. Move the EXTRA_IMAGEDEPENDS from qemu.inc into qemuboot.bbclass, so that the dependencies don't have to be duplicated. (From OE-Core rev: dd54cf058f632e985917ff227483995f368e6a7d) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie