On Tue, 27 Sept 2022 at 23:31, Peter Kjellerstedt <[email protected]> wrote: > I am not too fond of the "writing the config directly" idea. The reason > for that is that things change upstream (as you are well aware of, that's > after all the whole reason for the discussion). This is why I prefer to > go through the templates and basically only provide the list of layers > to add. That way when things change upstream in the template files, we > automatically follow. (And if it has not been obvious before, our wrapper > uses the bblayers.conf.sample file from meta-poky and just replaces the > list of layers with our list of layers. Which of course sounds like then > we could just write the final config file directly, but we also want to > continue to rely on oe-init-build-env for determining _where_ to write > the final files.)
Wait, wait, wait. If so, you can initialize using the template from poky, then you get BBPATH or BUILDDIR placed in the environment (by oe-init-build-env) telling where the config files are. So you can write to them directly (e.g. local.conf), or use 'bitbake-layers add-layer' (or 'remove-layer') to tweak the list of layers using supported tooling - after the initialization, but before any builds. No? Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171134): https://lists.openembedded.org/g/openembedded-core/message/171134 Mute This Topic: https://lists.openembedded.org/mt/93847437/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
