From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Benedikt Niedermayr <benedikt.niedermayr@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH] sdk: force set IMAGE_FSTYPES to SDK_FORMATS
Date: Mon, 23 Mar 2026 10:39:45 +0100 [thread overview]
Message-ID: <f148a635-72a5-4c95-8ae6-6de025ddab6f@siemens.com> (raw)
In-Reply-To: <20260323091023.3231135-1-benedikt.niedermayr@siemens.com>
On 23.03.26 10:10, 'Benedikt Niedermayr' via isar-users wrote:
> The image formats for the SDK should be set with SDK_FORMATS rather than
> configuring the IMAGE_FSTYPES.
> There are even cases were unwanted image types make it into the sdk
> image format because of using append syntax which is stronger than:
>
> ```
> IMAGE_FSTYPES:class-sdk = "${SDK_FORMATS}"
> ```
>
> Setting IMAGE_FSTYPES to SDK_FORMATS during recipe pre finalize time
> force overrides the value and thus ignores every append syntax override
> assignment before.
>
> Signed-off-by: Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
> ---
> meta/classes-recipe/sdk.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes-recipe/sdk.bbclass b/meta/classes-recipe/sdk.bbclass
> index 17b56bcf7371..dc5863465958 100644
> --- a/meta/classes-recipe/sdk.bbclass
> +++ b/meta/classes-recipe/sdk.bbclass
> @@ -18,6 +18,7 @@ python sdk_virtclass_handler() {
> # sdkchroot deploy only for sdk image
> bb.build.addtask('deploy_sdkchroot', 'do_build', 'do_rootfs', d)
> bb.build.deltask('copy_boot_files', d)
> + e.data.setVar('IMAGE_FSTYPES', e.data.getVar('SDK_FORMATS'))
> else:
> # add do_populate_sdk only to the non-sdk variant
> # it only exists to preserve the interface...
> @@ -52,7 +53,6 @@ ROOTFS_FEATURES:append:class-sdk = " clean-package-cache generate-manifest expor
> ROOTFS_MANIFEST_DEPLOY_DIR:class-sdk = "${DEPLOY_DIR_SDKCHROOT}"
> ROOTFS_DPKGSTATUS_DEPLOY_DIR:class-sdk = "${DEPLOY_DIR_SDKCHROOT}"
>
> -IMAGE_FSTYPES:class-sdk = "${SDK_FORMATS}"
> TAR_TRANSFORM:class-sdk = " --transform='s|rootfs|${IMAGE_FULLNAME}|'"
>
> # bitbake dependencies
You may want to mention that the effect of building undesired
IMAGE_FSTYPES along the SDK can be observed via isar-cip-core's update
images.
Patch looks good to me.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/f148a635-72a5-4c95-8ae6-6de025ddab6f%40siemens.com.
prev parent reply other threads:[~2026-03-23 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 9:10 'Benedikt Niedermayr' via isar-users
2026-03-23 9:39 ` 'Jan Kiszka' via isar-users [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f148a635-72a5-4c95-8ae6-6de025ddab6f@siemens.com \
--to=isar-users@googlegroups.com \
--cc=benedikt.niedermayr@siemens.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox