From: Jan Kiszka <jan.kiszka@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>,
Felix Moessbauer <felix.moessbauer@siemens.com>,
<isar-users@googlegroups.com>
Subject: Re: [PATCH] install crossbuild-essential into base schroot
Date: Thu, 4 Aug 2022 09:40:26 +0200 [thread overview]
Message-ID: <b874aee7-7c04-cfca-bce2-104826b51999@siemens.com> (raw)
In-Reply-To: <2606516.vuYhMxLoTh@home>
On 04.08.22 08:22, Uladzimir Bely wrote:
> In the email from Thursday, 4 August 2022 09:07:08 +03 user Jan Kiszka wrote:
>> On 03.08.22 18:44, Felix Moessbauer wrote:
>>> This patch always installs the crossbuild-essential-<distro>
>>
>> <distro-arch>
>>
>>> package into the lower dir of the host sbuild schroot.
>>>
>>> This avoids having to install this package in the upper-dir
>>> when cross-compiling, and is identical to build-essential when natively
>>> compiling.
>>> By that, the parallel cross-build of packages is significantly faster.
>>
>> I was wondering if that should be made dependent on ISAR_CROSS_COMPILE,
>> even though users could turn it off globally and only enable it for
>> individual packages?
>>
>> Jan
>>
>
> This might be even more conditional.
>
> Depending on compat arch option state, we might actually need crossbuild-
> essential-${COMPAT_DISTRO_ARCH} instead. Even in "native" builds, even for
> sbuild-chroot-target...
>
Indeed, good point. Though all that remains optimization, and we would
simply continue to install those deps on a package-by-package case.
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2022-08-04 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 16:44 Felix Moessbauer
2022-08-04 6:07 ` Jan Kiszka
2022-08-04 6:22 ` Uladzimir Bely
2022-08-04 7:17 ` Moessbauer, Felix
2022-08-04 7:40 ` Jan Kiszka [this message]
2022-08-04 7:35 ` Anton Mikanovich
2022-08-04 7:56 ` Moessbauer, Felix
2022-08-04 8:09 ` Uladzimir Bely
2022-08-10 14:45 ` 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=b874aee7-7c04-cfca-bce2-104826b51999@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=felix.moessbauer@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