Re: [PATCH RFC 1/4] bootconfig: add recipe

["Freihofer, Adrian" <adrian.freihofer@siemens.com>]

Hi Franceso

Thank you for the patches.

On Thu, 2026-03-19 at 00:30 +0100, Francesco Valla wrote:
> Add a new recipe for the bootconfig tool, with source coming directly
> from the kernel shared workdir.
> 
> Signed-off-by: Francesco Valla <francesco@valla.it>
> ---
>  meta/recipes-kernel/bootconfig/bootconfig.bb | 44
> ++++++++++++++++++++++++++++
>  1 file changed, 44 insertions(+)
> 
> diff --git a/meta/recipes-kernel/bootconfig/bootconfig.bb
> b/meta/recipes-kernel/bootconfig/bootconfig.bb
> new file mode 100644
> index
> 0000000000000000000000000000000000000000..77ee70dd1839ef90a292cf829f4
> f3a4353f85c28
> --- /dev/null
> +++ b/meta/recipes-kernel/bootconfig/bootconfig.bb
> @@ -0,0 +1,44 @@
> +SUMMARY = "Apply, delete or show boot config"
> +DESCRIPTION = "bootconfig is a tool that can be used to add a boot
> config block \
> +at the end of a kernel initramfs, as well as remove it or show its
> content."
> +LICENSE = "GPL-2.0-only"
> +
> +inherit kernelsrc kernel-arch
> +
> +do_populate_lic[depends] += "virtual/kernel:do_shared_workdir"
> +do_configure[depends] += "virtual/kernel:do_shared_workdir"
> +
> +EXTRA_OEMAKE = "\
> +    -C ${S}/tools/bootconfig \
> +    O=${B} \
> +    CROSS=${TARGET_PREFIX} \
> +    CC="${CC} ${DEBUG_PREFIX_MAP} -ffile-prefix-
> map=${STAGING_KERNEL_DIR}=${KERNEL_SRC_PATH} ${CFLAGS}" \
> +    HOSTCC="${BUILD_CC} ${BUILD_CFLAGS}" \
> +    LD="${LD}" \
> +    AR=${AR} \
> +    ARCH=${ARCH} \
> +    V=1 \
> +    'DESTDIR=${D}' \
> +    'prefix=${prefix}' \
> +    'bindir=${bindir}' \
> +"
> +
> +do_compile() {
> +	oe_runmake ${B}/bootconfig
> +}
> +
> +do_install() {
> +	install -d ${D}${bindir}
> +	oe_runmake install
> +}
> +
> +
> +PACKAGE_ARCH = "${MACHINE_ARCH}"

This is not understandable to me. From the description I would assume 
this tool runs on the host machine.

> +
> +python do_package:prepend() {
> +    d.setVar('PKGV', d.getVar("KERNEL_VERSION").split("-")[0])
> +}
> +
> +B = "${WORKDIR}/${BPN}-${PV}"
> +
> +BBCLASSEXTEND = "native nativesdk"

If the tool runs on the host machine, should this not be a pure -native
recipe without this line e.g. named bootconfig-native.bb

Is bootconfig a good name for a recipe? Or should it be e.g. linux-
bootconfig-native.bb?


Side note: We need to be careful not to create a dependency of the
initramfs on the kernel build directory. Such a dependency would
essentially invalidate the sstate-cache for the kernel, which we want
to avoid.

Regards,
Adrian