From: "'Liu, Yi' via isar-users" <isar-users@googlegroups.com>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"Wang, Qi" <wq.wang@siemens.com>
Subject: RE: [PATCH] bitbake: Move the preferred bootstrap assignment before including local.conf
Date: Fri, 31 Oct 2025 13:40:34 +0000 [thread overview]
Message-ID: <AS2PR10MB6927F921BBB3149B025AD8DCBFF8A@AS2PR10MB6927.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <582667cb348a02de684cc0866c2f9c9c83820247.camel@siemens.com>
> -----Original Message-----
> From: Moessbauer, Felix (FT RPD CED OES-DE)
> <felix.moessbauer@siemens.com>
> Sent: Friday, October 31, 2025 11:13 AM
> To: Liu, Yi (FT RPD CED INW-CN) <liuyi@siemens.com>; Kiszka, Jan (FT RPD
> CED) <jan.kiszka@siemens.com>
> Cc: isar-users@googlegroups.com
> Subject: Re: [PATCH] bitbake: Move the preferred bootstrap assignment
> before including local.conf
>
> On Fri, 2025-10-31 at 02:53 +0000, 'Liu, Yi' via isar-users wrote:
> > > -----Original Message-----
> > > From: Kiszka, Jan (FT RPD CED) <jan.kiszka@siemens.com>
> > > Sent: Thursday, October 30, 2025 7:29 PM
> > > To: Liu, Yi (FT RPD CED INW-CN) <liuyi@siemens.com>; isar-
> > > users@googlegroups.com
> > > Subject: Re: [PATCH] bitbake: Move the preferred bootstrap
> > > assignment before including local.conf
> > >
> > > On 30.10.25 04:06, 'Liu Yi' via isar-users wrote:
> > > > This change relocates the assignment for the preferred providers
> > > > of the bootstrap-host and bootstrap-target to occur before
> > > > including local.conf, ensuring that these two variables in
> > > > local.conf can be overwritten by the end users.
> > > >
> > > > Signed-off-by: Liu Yi <liuyi@siemens.com>
> > > > ---
> > > > meta/conf/bitbake.conf | 5 +++--
> > > > 1 file changed, 3 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index
> > > > 5ab8ced7..a06ef90e 100644
> > > > --- a/meta/conf/bitbake.conf
> > > > +++ b/meta/conf/bitbake.conf
> > > > @@ -210,6 +210,9 @@ TASK_USE_NETWORK = "1"
> > > > TASK_USE_SUDO = "1"
> > > > TASK_USE_NETWORK_AND_SUDO = "1"
> > > >
> > > > +PREFERRED_PROVIDER_bootstrap-host ??= "isar-mmdebstrap-host"
> > > > +PREFERRED_PROVIDER_bootstrap-target ??= "isar-mmdebstrap-target"
> > > > +
> > > > include conf/local.conf
> > > > include conf/multiconfig/${BB_CURRENT_MC}.conf
> > > > include conf/machine/${MACHINE}.conf @@ -217,5 +220,3 @@
> include
> > > > conf/distro/${DISTRO}.conf
> > > >
> > > > PATCHRESOLVE ?= "noop"
> > > >
> > > > -PREFERRED_PROVIDER_bootstrap-host ??= "isar-mmdebstrap-host"
> > > > -PREFERRED_PROVIDER_bootstrap-target ??= "isar-mmdebstrap-target"
> > >
> > > Looks good.
> > >
> > > I suppose that this comes from some out-of-tree experiments with a
> > > non- Debian, non-Raspberry and non-Ubuntu OS? ;)
> > >
> > > Jan
> > >
> > > --
> > > Siemens AG, Foundational Technologies Linux Expert Center
> >
> > You guessed it.
> >
> > This comes from the experiment of building openKylinOS via ISAR.
>
> I would be happy to see these experiments also on this list. Feel free to send as
> an RFC, similar to the raspbian support.
Thx for the suggestion. I will talk with Wang Qi to determine the next step for it.
>
> >
> > Somehow the build process got failed in the task do_bootstrap due to
> > uninstalling of libc6, if I chose the mmdebstrap as the preferred one.
> >
> > So, I tried to switch to debootstrap in local.conf or in
> > local-conf-head from kas yaml, then found it always be overwritten by the
> value from bitbake.conf.
>
> I'm a bit surprised why this did not work, as the extra-weak assignment still
> can be overwritten by a weak or strong one.
> Example:
>
> kas_trixie.yml
>
> header:
> version: 14
>
> build_system: isar
>
> machine: qemuamd64
> distro: debian-trixie
>
> target: mc:qemuamd64-trixie:isar-image-base
>
> repos:
> isar:
> layers:
> meta:
>
> local_conf_header:
> pref-prov: |
> PREFERRED_PROVIDER_bootstrap-host = "foo"
>
> kas-container shell -c "bitbake-getvar -r bootstrap-host
> PREFERRED_PROVIDER_bootstrap-host" kas_trixie.yml # output
> PREFERRED_PROVIDER_bootstrap-host="foo"
>
I think the above command output only indicates PREFERRED_PROVIDER_bootstrap-host's current value
comes from the shell environment, with this value explicitly set in the kas yaml file.
However, the value of PREFERRED_PROVIDER_bootstrap-host(target) during the build process will eventually
come from bitabke.conf. The variables defined from the local_conf_header in kas yaml are also added to local.conf,
which has been included into bitbake.conf.
So, the assignment order of these variables in the bitabake.conf determines their final value.
Liu Yi
> Felix
>
> >
> > Best Regards,
> > Liu Yi
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> "isar-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> email to isar-users+unsubscribe@googlegroups.com.
> > To view this discussion visit
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgrou
> ps.google.com%2Fd%2Fmsgid%2Fisar-
> users%2FAS2PR10MB692752E80892472B234F4B43BFF8A%2540AS2PR10
> MB6927.EURPRD10.PROD.OUTLOOK.COM&data=05%7C02%7Cliuyi%40sie
> mens.com%7C87767d19682f4b15c7c708de182b7201%7C38ae3bcd95794f
> d4addab42e1495d55a%7C1%7C0%7C638974772022009884%7CUnknown
> %7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIl
> AiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sd
> ata=tN%2BA6MZxeJnNwfnMNQw9rII0TlKLAKYZJ6UCOrVw2uo%3D&reserve
> d=0.
>
> --
> Siemens AG
> Linux Expert Center
> Friedrich-Ludwig-Bauer-Str. 3
> 85748 Garching, Germany
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/AS2PR10MB6927F921BBB3149B025AD8DCBFF8A%40AS2PR10MB6927.EURPRD10.PROD.OUTLOOK.COM.
prev parent reply other threads:[~2025-10-31 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 3:06 'Liu Yi' via isar-users
2025-10-30 11:29 ` 'Jan Kiszka' via isar-users
2025-10-31 2:53 ` 'Liu, Yi' via isar-users
2025-10-31 3:13 ` 'MOESSBAUER, Felix' via isar-users
2025-10-31 13:40 ` 'Liu, Yi' via isar-users [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=AS2PR10MB6927F921BBB3149B025AD8DCBFF8A@AS2PR10MB6927.EURPRD10.PROD.OUTLOOK.COM \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=liuyi@siemens.com \
--cc=wq.wang@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