On Wed, 14 Sept 2022 at 10:17, ChenQi <[email protected]> wrote: > The codes are in: https://github.com/WindRiver-Labs/wrlinux-x > > e.g. > > ./wrlinux-x/setup.sh --all-layers (this pulls down all supported layers) > > ./wrlinux-x/setup.sh --all-layers --dl-layers (this pulls down all > supported layers, together with their needed tarballs/git repos) > > ./wrlinux-x/setup.sh (this pulls down the default list of layers) > > ./wrlinux-x/setup.sh --layers meta-xxx (this pulls down the default list > of layers + meta-xxx and its dependencies) > > And the final list of layers are in > <project_dir>/config/bblayers.conf.sample, which will be updated if > needed when re-running the setup.sh script.
May I suggest that the tool skips the bblayers.conf.sample step altogether, and simply writes the desired layers directly into bblayers.conf? It can do this with 'bitbake-layers add-layer'. Is there a need for doing the intermediate step of generating the template? Just to be clear where I am coming from: anything in TEMPLATECONF must not be auto-generated during build setup, and must be under version control. We are trying to standardize layer setup and configuration handling, and this would be a necessary step towards that. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#170643): https://lists.openembedded.org/g/openembedded-core/message/170643 Mute This Topic: https://lists.openembedded.org/mt/93368468/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
