On Thu, 18 Aug 2022 at 11:27, Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > The intent is the user could add something like: > > require conf/yocto-autobuilder/x32.inc > > or > > require conf/yocto-autobuilder/multilib-mipsn32.inc > > and similar to their local.conf and more easily replicate > configurations.
This could be a subset of a broader feature, one that allows adding and removing pre-canned 'config fragments' to local.conf. The proposal is to have such fragments live in meta-somelayer/conf/fragments/path/to/some/fragment (I think allowing multiple levels is beneficial here), and each fragment would start with a comment explaining what it does followed by the actual settings. Then adding fragments can be done by appending them to local.conf, and removing by looking for markers in local.conf and editing it out, which probably could use a helper tool/subcommand. Layers could also declare 'non-optional' fragments which get included automatically by the fact of including the layer into the build, which means layer.conf can go back to being short and sweet and to the point. Thoughts? > I would like to see if we can switch the eSDK to use the json format > btw. I suspect that may be one of your next steps? :) I don't think I understand this, can you explain? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#170224): https://lists.openembedded.org/g/openembedded-core/message/170224 Mute This Topic: https://lists.openembedded.org/mt/93398200/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
