On Wed, 24 Aug 2022 at 16:43, Peter Kjellerstedt <peter.kjellerst...@axis.com> wrote: > We create the sample files in a small wrapper for oe-init-build-env > so that to the users, everything works just as described in the Yocto > documentation. And since the OE scripts expect TEMPLATECONF to be set > and contain sample files, that is what we create.
Actually they don't expect that. You can simply create the configs directly into the target build directory in your wrapper, and drop TEMPLATECONF altogether. Then the OE scripts will detect that the configs are already there and will skip the step of copying the templates. > Sure, that is fine. But the expectation I have is that TEMPLATECONF > refers to the directory that has the sample files needed to set up > the build environment. And that is it. As long as the sample files > exist where it says they should be, why do you need the scripts to > fail because the environment around the directory does not look > like what you happen to expect? It is only the contents of the > directory that matters. Or am I missing something? We are trying to move towards standardizing build configuration management. One step towards that goal is that config templates must live in meta-some-layer/conf/templates, and aren't scattered around, or generated on the fly. This rule only makes sense if there is some way to enforce it, which is what this change does. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#169822): https://lists.openembedded.org/g/openembedded-core/message/169822 Mute This Topic: https://lists.openembedded.org/mt/93225500/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
