From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Adriaan Schmidt <adriaan.schmidt@siemens.com>
Subject: [PATCH 1/4] imagetypes_wic: Prepare for WIC_IMAGER_INSTALL being undefined
Date: Fri, 10 Nov 2023 18:41:24 +0100 [thread overview]
Message-ID: <f3cfccf899a6805b0b6b1c3409179fa6c7e908cb.1699638087.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1699638087.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
We will migrate WIC_IMAGER_INSTALL to IMAGER_INSTALL:wic, and that can
leave the old variable unset behind.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
meta/classes/imagetypes_wic.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/imagetypes_wic.bbclass b/meta/classes/imagetypes_wic.bbclass
index 6b50959f..e150c0e9 100644
--- a/meta/classes/imagetypes_wic.bbclass
+++ b/meta/classes/imagetypes_wic.bbclass
@@ -83,7 +83,7 @@ python () {
bb.build.addtask('do_transform_template', 'do_image_wic', None, d)
}
-IMAGER_INSTALL:wic += "${WIC_IMAGER_INSTALL}"
+IMAGER_INSTALL:wic += "${@d.getVar('WIC_IMAGER_INSTALL') or ''}"
# wic comes with reasonable defaults, and the proper interface is the wks file
ROOTFS_EXTRA ?= "0"
--
2.35.3
next prev parent reply other threads:[~2023-11-10 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 17:41 [PATCH 0/4] IMAGER_INSTALL cleanups Jan Kiszka
2023-11-10 17:41 ` Jan Kiszka [this message]
2023-11-10 17:41 ` [PATCH 2/4] Convert WIC_IMAGER_INSTALL to IMAGER_INSTALL:wic Jan Kiszka
2023-11-10 17:41 ` [PATCH 3/4] meta-isar: Limit wic-related imager dependencies to that image type Jan Kiszka
2023-11-10 17:41 ` [PATCH 4/4] imagetypes_wic: Deprecate WIC_IMAGER_INSTALL Jan Kiszka
2023-11-10 22:00 ` Florian Bezdeka
2023-11-21 7:02 ` [PATCH 0/4] IMAGER_INSTALL cleanups Uladzimir Bely
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=f3cfccf899a6805b0b6b1c3409179fa6c7e908cb.1699638087.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=isar-users@googlegroups.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