Hi Alex, On Fri, 26 Aug 2022 17:25:07 +0200 "Luca Ceresoli via lists.openembedded.org" <luca.ceresoli=bootlin....@lists.openembedded.org> wrote:
> Hi Alex, > > On Thu, 25 Aug 2022 22:34:47 +0200 > "Alexander Kanavin" <alex.kana...@gmail.com> wrote: > > > This is the reverse of setting up a build by pointing TEMPLATECONF to a > > directory > > with a template and running '. oe-init-build-env': this takes the config > > files from build/conf, > > replaces site-specific paths in bblayers.conf with ##OECORE##-relative > > paths, and copies > > the config files into a specified layer under a specified template name. > > > > In many or perhaps most cases such static prefabricated configurations > > (that require no > > further editing) are just enough, and I believe they should be offered by > > the > > official configuration management. On the other hand, generating build > > configurations with a > > sufficiently versatile tool is a far more complex problem, and one we > > should try to tackle > > once we see where and how static configs fall short. > > > > Tooling to discover and select these templates when setting up a build will > > be provided later on. > > > > How to use: > > > > alex@Zen2:/srv/work/alex/poky/build-layersetup$ bitbake-layers > > save-build-conf ../../meta-alex/ test-1 > > NOTE: Starting bitbake server... > > NOTE: Configuration template placed into > > /srv/work/alex/meta-alex/conf/templates/test-1 > > Please review the files in there, and particularly provide a configuration > > description in /srv/work/alex/meta-alex/conf/templates/test-1/conf-notes.txt > > You can try out the configuration with > > TEMPLATECONF=/srv/work/alex/meta-alex/conf/templates/test-1 . > > /srv/work/alex/poky/oe-init-build-env build-try-test-1 > > alex@Zen2:/srv/work/alex/poky/build-layersetup$ > > > > Signed-off-by: Alexander Kanavin <a...@linutronix.de> > > Testing with this series produced some failures: > > error: pathspec 'yocto-4.0' did not match any file(s) known to git > > Looks like is is adding the poky-contrib remote but not poky itself. > > https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/3996/steps/14/logs/stdio > https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/4010/steps/14/logs/stdio > https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/4064/steps/14/logs/stdio > https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/4052/steps/15/logs/stdio > https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/26/steps/14/logs/stdio > This series appears to have generated other errors on several qemu builds: ERROR: core-image-sato-1.0-r0 do_testsdkext: Couldn't install the extensible SDK: To me the correlation with your code was not immediately obvious, but as Ross suggested I removed your patches and the failure disappeared. Some logs: https://autobuilder.yoctoproject.org/typhoon/#/builders/97/builds/5114/steps/16/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/60/builds/5737/steps/15/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/5724/steps/16/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5721/steps/16/logs/stdio -- Luca Ceresoli, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#169971): https://lists.openembedded.org/g/openembedded-core/message/169971 Mute This Topic: https://lists.openembedded.org/mt/93257020/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-