On Mon, 2023-07-31 at 16:14 +0200, Alexander Kanavin wrote: > On Mon, 31 Jul 2023 at 14:42, Richard Purdie > <[email protected]> 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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#185144): https://lists.openembedded.org/g/openembedded-core/message/185144 Mute This Topic: https://lists.openembedded.org/mt/98802403/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
