public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v3 0/3] Fix cross-build from base-apt when custom DISTRO name used
Date: Fri, 25 Nov 2022 08:37:52 +0100	[thread overview]
Message-ID: <8ce8f56c-ebe6-ff91-f796-af9cbca7a10b@siemens.com> (raw)
In-Reply-To: <20221125064253.21907-1-ubely@ilbers.de>

On 25.11.22 07:42, Uladzimir Bely wrote:
> This patchset is mostly intended for downstreams that prefer
> to rename DISTRO variable (like `meat-iot2050`) and use
                                   ^^^^
Nice typo :)

> ISAR_CROSS_COMPILE = "1".
> 
> This also fixes the case with cross-build or raspberry targets
> from cached base-apt repo. While it uses separate repositories
> for host (Debian) and target (Raspbian) distros, base-apt is
> splittend onto two parts corresponding to original repos.

split

> 
> Also, testsuite repro tests were updated to cover crosss-build case

cross

> and raspberry target is now used in it.
> 
> Changes since v2:
> - Cleaned garbage in commit message for patch 2.
> 
> Changes since v1:
> - Support cached cross-build from base-apt for different base distros
> for host and target (e.g. raspberry).
> 
> 
> Uladzimir Bely (3):
>   Populate base-apt from both DISTRO and HOST_DISTRO download dirs
>   testsuite: Run signed repro test in cross mode
>   testsuite: Replace bananapi with rpi-arm-v7 in signed repro tests
> 
>  meta-isar/conf/distro/raspbian-stretch.conf   |  2 +
>  meta-isar/conf/distro/raspios-bullseye.conf   |  2 +
>  meta-isar/conf/distro/ubuntu-focal.conf       |  2 +
>  meta/conf/distro/debian-common.conf           |  2 +
>  .../isar-bootstrap/isar-bootstrap.inc         |  9 +++-
>  meta/recipes-devtools/base-apt/base-apt.bb    | 47 ++++++++++---------
>  testsuite/citest.py                           |  4 +-
>  7 files changed, 42 insertions(+), 26 deletions(-)
> 

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux


      parent reply	other threads:[~2022-11-25  7:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25  6:42 Uladzimir Bely
2022-11-25  6:42 ` [PATCH v3 1/3] Populate base-apt from both DISTRO and HOST_DISTRO download dirs Uladzimir Bely
2022-11-25  7:42   ` Jan Kiszka
2022-11-25  7:56     ` Uladzimir Bely
2022-11-25 14:11       ` Jan Kiszka
2022-11-25 14:48         ` Uladzimir Bely
2022-11-25 15:40           ` Jan Kiszka
2022-11-26  5:30             ` Uladzimir Bely
2022-11-27 19:05               ` Jan Kiszka
2022-11-28  6:05                 ` Uladzimir Bely
2022-11-28  6:32                   ` Jan Kiszka
2022-11-28  6:41                     ` Uladzimir Bely
2022-11-28  6:51                       ` Jan Kiszka
2022-11-28 11:12                         ` Uladzimir Bely
2022-11-28 11:45                           ` Jan Kiszka
2022-11-25  6:42 ` [PATCH v3 2/3] testsuite: Run signed repro test in cross mode Uladzimir Bely
2022-11-25  6:42 ` [PATCH v3 3/3] testsuite: Replace bananapi with rpi-arm-v7 in signed repro tests Uladzimir Bely
2022-11-25  7:37 ` Jan Kiszka [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=8ce8f56c-ebe6-ff91-f796-af9cbca7a10b@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=ubely@ilbers.de \
    /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