Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 2/2] oe-setup-build: add a tool for discovering config templates and setting up builds
Date: Mon, 31 Jul 2023 15:23:57 +0100	[thread overview]
Message-ID: <00b2ccaee29163f2cbaafacad2ee85f3b88255ed.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj9yxqxMB4NfEpvJnb3KxBXpVTVJZ_dppMjmd5XQRapzUQ@mail.gmail.com>

On Mon, 2023-07-31 at 16:14 +0200, Alexander Kanavin wrote:
> On Mon, 31 Jul 2023 at 14:42, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > > > Yes, getting the layer name means parsing but we can likely handle that
> > > > at this point as we're in python.
> > > 
> > > You mean getting BBFILE_COLLECTIONS value out of conf/layer.conf? That
> > > should be fairly easy with standard python, yes.
> > 
> > I think we should be able to use bits of bitbake to help too?
> 
> But how? To use bitbake a build must be set up first. The script sets
> up the build. When the script executes, bitbake won't yet run.

To use bitbake itself, yes. To use tinfoil, or library code from
lib/bb, it doesn't necessarily need that. You don't want bitbake itself
anyway.

> > The conf-notes.txt has a specific purpose and I don't like the idea of
> > trying to make it to two things badly. We therefore need to put this
> > information into which is likely a new location, probably a new conf
> > file within each template directory?
> 
> So perhaps:
> conf-description.txt - a short (one line ideally) description of what
> the configuration is for, shown by oe-setup-build to help the users
> choose one configuration from several.
> conf-notes.txt - a kind of freeform 'readme' for the configuration
> explaining how to use it, and which are the key bitbake targets etc,
> shown after the selection is made, when a build is set up from a
> selected template.

I'm still thinking we should try and get away from these text files...

Cheers,

Richard


      reply	other threads:[~2023-07-31 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10  9:57 [PATCH 1/2] scripts/oe-setup-layers: write a list of layer paths into the checkout's top dir Alexander Kanavin
2023-05-10  9:57 ` [PATCH 2/2] oe-setup-build: add a tool for discovering config templates and setting up builds Alexander Kanavin
2023-07-31 10:56   ` [OE-core] " Richard Purdie
2023-07-31 11:31     ` Alexander Kanavin
2023-07-31 12:04       ` Richard Purdie
2023-07-31 12:15         ` Alexander Kanavin
2023-07-31 12:42           ` Richard Purdie
2023-07-31 14:14             ` Alexander Kanavin
2023-07-31 14:23               ` Richard Purdie [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=00b2ccaee29163f2cbaafacad2ee85f3b88255ed.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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