On Tue, 2023-08-22 at 22:09 +0200, Alexander Kanavin wrote: > On Tue, 22 Aug 2023 at 21:11, Freihofer, Adrian > <adrian.freiho...@siemens.com> wrote: > > Do you mean something like this: > > > > cd poky > > . oe-init-build-env ../poky-build > > > > Yes, it would probably work. But moving the build folder would > > break a > > long-established standard. I'm not sure if such a change would be > > accepted by the users. > > I'm not sure there's a standard. You can do > > . /path/to/poky/oe-init-build-env
With "standard" I mean that just doing . oe-init-biuld-env is what probably most manuals suggest and what most users expect to work. But with VSCode it does not until there is a settings.json. I just sent a v2 which adds a static settings.json file to git: https://lists.openembedded.org/g/openembedded-core/message/186524 The globs in the settings.json should cover all build folders which are inside the poky folder. For a build folder outside of the poky folder it does not harm. > > from any directory, and the build directory will be made there, and > not in poky/. As long as you don't let users run oe-init-build-env > directly (such as with upcoming oe-setup-build :) we should be fine? Yes, that would be nice. But it does not cover all possible cases. Adrian > > A more radical idea is to indeed prevent build directories from being > created under poky/ directly in oe-init-build-env. I'll be everyone's > favorite blame target again for this. > > Alex > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#186538): https://lists.openembedded.org/g/openembedded-core/message/186538 Mute This Topic: https://lists.openembedded.org/mt/100876148/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
