public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: isar-users@googlegroups.com, jan.kiszka@siemens.com,
	adriaan.schmidt@siemens.com, amikan@ilbers.de, ibr@ilbers.de
Subject: Re: [PATCH v3 1/1] run imager in buildchroot-host on cross
Date: Wed, 14 Sep 2022 10:49:49 +0200	[thread overview]
Message-ID: <20220914104949.7d140c93@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20220913133839.3280660-2-felix.moessbauer@siemens.com>

I want a testcase for this where a whole wic gz/xz chain runs in CI with
a CROSS=1.

Henning

Am Tue, 13 Sep 2022 15:38:39 +0200
schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:

> When globally enabling ISAR_CROSS_COMPILE, the imager and compression
> tasks run in the host buildchroot as well (instead of the target
> buildchroot).
> 
> Similar to the cross support for DPKG recipes, this can be toggled
> on a per-image basis by setting ISAR_CROSS_COMPILE in the image
> recipe.
> 
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>  doc/user_manual.md                         | 11 +++++++++++
>  meta/classes/image-tools-extension.bbclass |  3 ---
>  2 files changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/doc/user_manual.md b/doc/user_manual.md
> index 5b2387d8..f38a133e 100644
> --- a/doc/user_manual.md
> +++ b/doc/user_manual.md
> @@ -986,6 +986,17 @@ built for the compat arch need to be tagged
> individually by setting `PACKAGE_ARCH = "${COMPAT_DISTRO_ARCH}"` in
> the package recipe. Non-tagged packages will continue to be built for
> the primary target architecture. 
> +### Cross Support for Imagers
> +
> +If `ISAR_CROSS_COMPILE = "1"`, the imager and optional compression
> tasks +run in the host buildchroot instead of the target buildchroot.
> +This gives a significant speedup when compressing the generated
> image, +as the compression is not emulated.
> +
> +In case your setup does not support cross-imaging, you can disable
> this +just for the particular image by adding `ISAR_CROSS_COMPILE =
> "0"` to your +image recipe.
> +
>  
>  ## Examining and debugging package generation inside their
> buildchroot 
> diff --git a/meta/classes/image-tools-extension.bbclass
> b/meta/classes/image-tools-extension.bbclass index b9968139..e13d4a3f
> 100644 --- a/meta/classes/image-tools-extension.bbclass
> +++ b/meta/classes/image-tools-extension.bbclass
> @@ -5,9 +5,6 @@
>  #
>  # This file extends the image.bbclass to supply tools for futher
> imager functions 
> -# Imager are expected to run natively, thus will use the target
> buildchroot. -ISAR_CROSS_COMPILE = "0"
> -
>  inherit buildchroot
>  
>  IMAGER_INSTALL ??= ""


  reply	other threads:[~2022-09-14  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-13 13:38 [PATCH v3 0/1] use xz and gzip on host (outside chroot) Felix Moessbauer
2022-09-13 13:38 ` [PATCH v3 1/1] run imager in buildchroot-host on cross Felix Moessbauer
2022-09-14  8:49   ` Henning Schild [this message]
2022-09-14 13:46     ` Moessbauer, Felix
2022-09-14 13:52       ` Henning Schild

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=20220914104949.7d140c93@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=felix.moessbauer@siemens.com \
    --cc=ibr@ilbers.de \
    --cc=isar-users@googlegroups.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