From: Henning Schild <henning.schild@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2 1/3] doc: Add imager dependencies section
Date: Thu, 28 Oct 2021 22:17:41 +0200 [thread overview]
Message-ID: <20211028221741.02ca5baa@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20211028171727.246342-2-amikan@ilbers.de>
Am Thu, 28 Oct 2021 20:17:25 +0300
schrieb Anton Mikanovich <amikan@ilbers.de>:
> Include into user_manual.md explanation of imager dependencies should
> be added if using wic image type with bootloader-related plugins.
>
> Inspired by issue #69
>
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
> doc/user_manual.md | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/doc/user_manual.md b/doc/user_manual.md
> index 01fe701..1b00a47 100644
> --- a/doc/user_manual.md
> +++ b/doc/user_manual.md
> @@ -586,6 +586,22 @@ Isar contains additional image type classes that
> can be used as reference:
> - `ubi-img`
> - `wic-img`
>
> +### Imager dependencies and bootloaders
> +
> +External tools used for final image prepare inside image type
> classes should be declared as `IMAGER_INSTALL`. +It will make Isar to
> install following packages into buildchroot before proceeding. +
> +If using `wic-img` image type correct bootloader dependecy should be
> added to target machine config based on selected wic plugin. +
I would make that more generic and explain what IMAGER_INSTALL is in
general. Maybe even refer to "native" from OE.
The tools are not "external", they are build tools (coming from
upstream or maybe a layer) that are not part of the image but needed to
construct it. In fact we use that variable in many of our imager
classes, not just wic.
> +When using legacy BIOS bootloader (amd64/i386 only) dependency on
> syslinux should be used: +```
> +IMAGER_INSTALL += "${SYSLINUX_BOOTLOADER_INSTALL}"
> +```
> +When using EFI bootloader dependency on GRUB should be added:
> +```
> +IMAGER_INSTALL += "${GRUB_BOOTLOADER_INSTALL}"
wic makes a good example to explain the concept. Note that EFI does not
mean grub and having to set IMAGER_INSTALL. It can also mean
systemd-boot and no IMAGER_INSTALL.
Henning
> +```
> +
> ---
>
> ## Customize and configure image
next prev parent reply other threads:[~2021-10-28 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 17:17 [PATCH v2 0/3] Update Isar documentation Anton Mikanovich
2021-10-28 17:17 ` [PATCH v2 1/3] doc: Add imager dependencies section Anton Mikanovich
2021-10-28 20:17 ` Henning Schild [this message]
2021-10-28 17:17 ` [PATCH v2 2/3] doc: Update tasks description Anton Mikanovich
2021-10-28 17:17 ` [PATCH v2 3/3] doc: Update available image types Anton Mikanovich
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=20211028221741.02ca5baa@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