Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	Alexander Kanavin <alex@linutronix.de>
Subject: RE: [OE-core] [PATCH 1/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists)
Date: Thu, 7 Jul 2022 14:38:31 +0000	[thread overview]
Message-ID: <9ae77d11ee2848b4992c5c104928664b@axis.com> (raw)
In-Reply-To: <CANNYZj8pEFcM1g_qOVbP1HDUE05yjQwyxsJpLM_em3NRPnM6kw@mail.gmail.com>

> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Alexander Kanavin
> Sent: den 7 juli 2022 15:56
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin
> <alex@linutronix.de>
> Subject: Re: [OE-core] [PATCH 1/2] scripts/oe-setup-builddir: copy
> site.conf.sample out of template directories (if it exists)
> 
> On Thu, 7 Jul 2022 at 15:45, Peter Kjellerstedt
> <peter.kjellerstedt@axis.com> wrote:
> 
> > > Setting up a build directory from standard poky
> > > or oe-core templates (which I presume is how you set up builds) does
> > > not hold a promise that what is being copied will not change in
> > > potentially breaking ways.
> >
> > While I may be able to fix the environment for builds that use some of
> > our layers, setting up pure poky builds will no longer work without
> > manual intervention.
> 
> Wait. How are you setting up pure poky builds right now, so that your
> magic site.conf is correctly inserted into builds?
> 
> Alex

Actually, you can forget what I said. I had a look at our wrapper for 
oe-init-build-env, which is responsible for creating our templateconf 
directory, and it will of course not be affected by your change. (It was 
six years since I wrote that code, so my memory was obviously a bit 
fuzzy.)

And in case you wonder what that wrapper actually does, it creates the 
bblayers.conf.sample file based on all layers that are found in the top 
directory. It also creates a local.conf.sample file by combining fragment 
files in the layers (i.e., local.conf.sample.XX where XX is a number 
between 00 and 99). The local.conf.sample from meta-poky is considered 
to have XX == 50. The reason for this is that we quickly realized that 
the static templateconf directory setup was unusable for us when we 
want to be able to use layers in different combinations.

//Peter


  reply	other threads:[~2022-07-07 14:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 18:23 [PATCH 1/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists) Alexander Kanavin
2022-07-06 18:23 ` [PATCH 2/2] bitbake-layers: add a command to save the active build configuration as a template into a layer Alexander Kanavin
2022-07-07 13:26 ` [OE-core] [PATCH 1/2] scripts/oe-setup-builddir: copy site.conf.sample out of template directories (if it exists) Peter Kjellerstedt
2022-07-07 13:36   ` Alexander Kanavin
2022-07-07 13:45     ` Peter Kjellerstedt
2022-07-07 13:56       ` Alexander Kanavin
2022-07-07 14:38         ` Peter Kjellerstedt [this message]
2022-07-07 14:48           ` Alexander Kanavin
2022-07-07 15:21             ` Peter Kjellerstedt
2022-07-15 14:42 ` Richard Purdie
2022-07-15 16:00   ` Alexander Kanavin
2022-07-15 21:57     ` Alexandre Belloni
2022-07-16  7:37       ` Alexander Kanavin
2022-07-15 16:15   ` Alexander Kanavin
2022-07-15 16:24     ` Richard Purdie
2022-07-15 16:35       ` Alexander Kanavin

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=9ae77d11ee2848b4992c5c104928664b@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=openembedded-core@lists.openembedded.org \
    /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