On Wed, 2023-05-10 at 11:57 +0200, Alexander Kanavin wrote: > This is the last (I believe) piece of the puzzle in setting up builds from > nothing > without having to write custom scripts or use external tools. > > After layers have been fetched and placed into their respective locations by > oe-setup-layers, one would surely want to proceed to the actual build, and > here's how: > > 1. Without arguments or with 'list-config-templates', the tool reads > available layers > from .oe-layers.json file (written out by oe-setup-layers) and prints what > templates it has found, as seen below. If the following is not enough > information, > adding '-v' will also print conf-notes.txt for each of the templates: > > $ oe-setup-build > Available build configuration templates (re-run with -v to see their > descriptions): > > /srv/work/alex/poky/scripts/oe-setup-build setup-build-env -c > /srv/work/alex/poky/meta-poky/conf/templates/default > will create a build configuration in /srv/work/alex/build-meta-poky-default > > /srv/work/alex/poky/scripts/oe-setup-build setup-build-env -c > /srv/work/alex/meta-alex/conf/templates/configuration-gizmo > will create a build configuration in > /srv/work/alex/build-meta-alex-configuration-gizmo > > /srv/work/alex/poky/scripts/oe-setup-build setup-build-env -c > /srv/work/alex/meta-alex/conf/templates/configuration-gadget > will create a build configuration in > /srv/work/alex/build-meta-alex-configuration-gadget
I've just been looking at this again and I'm still not convinced this is right. In particular, the above output worries me a lot, partly as I barely understand it and I suspect if I struggle, I won't be the only one. With this kind of core tool, the "interface" to the user needs to be really clear and the problem here is that it isn't. Being more specific, from the above it is listing some commands I could run, but the user is being left to work out what the difference is for themselves. If I print a list like: a) poky default b) gizmo config c) gadget config then ask the user to select one, it is clear as the user is drawn to the key information. In the above text output, you have to know where to look in the commands to guess the pieces. The "/srv/work/alex" string is confusing the output and in many ways even filtering that out would help reduce the "superfluous" text but the issue does run deeper than that. As another example, perhaps I shouldn't need the -v to get at least some summary of what each one does? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#185134): https://lists.openembedded.org/g/openembedded-core/message/185134 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]] -=-=-=-=-=-=-=-=-=-=-=-
