From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 2/2] meta-isar: enable systemd-boot for qemuarm-bookworm
Date: Fri, 8 Jul 2022 10:48:17 +0200 [thread overview]
Message-ID: <20220708104817.0b9475fa@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220707141803.22408-3-amikan@ilbers.de>
Am Thu, 7 Jul 2022 17:18:03 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> Add WIC imagetype with wks which use systemd-boot bootloader for
> SYSTEMD_BOOTLOADER_INSTALL testing.
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> meta-isar/conf/multiconfig/qemuarm-bookworm.conf | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/meta-isar/conf/multiconfig/qemuarm-bookworm.conf
> b/meta-isar/conf/multiconfig/qemuarm-bookworm.conf index
> 0819236..b515e40 100644 ---
> a/meta-isar/conf/multiconfig/qemuarm-bookworm.conf +++
> b/meta-isar/conf/multiconfig/qemuarm-bookworm.conf @@ -2,3 +2,8 @@
>
> MACHINE ?= "qemuarm"
> DISTRO ?= "debian-bookworm"
> +
> +IMAGE_FSTYPES_append = " wic"
> +WKS_FILE ?= "sdimage-efi-sd"
> +
> +IMAGE_PREINSTALL += "${SYSTEMD_BOOTLOADER_INSTALL}"
Unlike the other bootloaders this one comes from inside the target
rootfs, it is a PREINSTALL for the image, not an IMAGER_INSTALL ...
which kind of is a PREINSTALL for the build chroot.
So i suggest to somehow cover that subtle difference i.e. by naming the
variable SYSTEMD_BOOTLOADER_PREINSTALL
Henning
next prev parent reply other threads:[~2022-07-08 8:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 14:18 [PATCH 0/2] Fix and cover systemd-boot usage in bookworm Anton Mikanovich
2022-07-07 14:18 ` [PATCH 1/2] meta: introduce systemd-boot dependency variable Anton Mikanovich
2022-07-08 8:31 ` Anton Mikanovich
2022-07-08 8:32 ` Anton Mikanovich
2022-07-07 14:18 ` [PATCH 2/2] meta-isar: enable systemd-boot for qemuarm-bookworm Anton Mikanovich
2022-07-08 8:48 ` Henning Schild [this message]
2022-07-08 11:04 ` Jan Kiszka
2022-07-12 13:08 ` Anton Mikanovich
2022-07-07 15:50 ` [PATCH 0/2] Fix and cover systemd-boot usage in bookworm Henning Schild
2022-07-08 7:57 ` Bezdeka, Florian
2022-07-08 8:07 ` Anton Mikanovich
2022-07-08 8:11 ` Bezdeka, Florian
2022-07-08 8:23 ` Bezdeka, Florian
2022-07-08 8:28 ` Anton Mikanovich
2022-07-08 8:49 ` Henning Schild
2022-07-08 8:44 ` Henning Schild
2022-07-08 9:01 ` Baurzhan Ismagulov
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=20220708104817.0b9475fa@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=amikan@ilbers.de \
--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