On Thu, 23 Jan 2025 at 18:12, Alexander Kanavin <[email protected]> wrote: > - 'top directory' means the place under which bitbake-setup reads and > writes everything. It makes a promise to not touch anything outside of > that, unless otherwise directed to by entries in settings (currently > there is one such setting for fetcher downloads for layers and config > registries). Top directory can be selected by a command line option, > or otherwise assumed to be ~/bitbake-builds/
Of course I managed to forget something :) If BBPATH is in environment (e.g. we are in a bitbake environment), then the top directory is deduced from that and doesn't need to be specified by hand. I need to check that bitbake-setup gracefully handles the situation when BBPATH is present, but the bitbake build is a 'legacy' one that is not inside a bitbake-setup-made build tree. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2099): https://lists.openembedded.org/g/openembedded-architecture/message/2099 Mute This Topic: https://lists.openembedded.org/mt/110775384/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
