On Tue, 2023-08-22 at 12:00 +0200, Alexander Kanavin wrote: > It's probably simpler to enforce that the build folder is not under > poky/ if I understand this right? How is it created, and at which > point? 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 will send a v2 with a minimalistic, static settings.json file added to git. It covers all build folder under poky. I tried several different things and this looks like the best solution to me. Regards, Adrian > Alex > > On Mon, 21 Aug 2023 at 23:46, Adrian Freihofer via > lists.openembedded.org > <adrian.freihofer=siemens....@lists.openembedded.org> wrote: > > > > On Mon, 2023-08-21 at 21:56 +0200, Luca Ceresoli wrote: > > > Hello Adrian, > > > > > > On Mon, 21 Aug 2023 18:07:05 +0200 > > > "Adrian Freihofer" <adrian.freiho...@gmail.com> wrote: > > > > > > > This is just my setup. It's not supposed to be merged into > > > > poky. > > > > > > If this not supposed to me merged, clarifying that on the subject > > > line > > > would be nice (e.g. add "**** DO NOT MERGE ****") to not > > > overlook > > > that, > > > as well as moving this patch at the end of the series IMO. > > > > > > Thank you for the hint. I will update it as soon as I get more > > feedback. > > > > But we should probably discuss this a bit more. When VSCode is used > > to > > work on a meta layer (e.g. poky), some indexer plugins start > > indexing > > the code. In the case of a meta-layer repository, the build folder > > can > > be very large and it is very important to configure VSCode to > > ignore > > it. Otherwise, the plugins will run with 100% CPU load until an OOM > > exception occurs. In practice, this makes VSCode more or less > > unusable > > for working with Yocto until a file like the one added by this > > patch is > > deployed before VSCode starts. And from the user's point of view, > > it is > > not obvious why the system runs at 100% CPU load and eventually > > crashes. In other words: If you don't have this patch, you will > > hate > > VSCode as a Yocto developer. > > > > It is even more misleading that VSCode starts the indexers > > immediately, > > but does not stop or reconfigure them when the ignore list is > > updated. > > In practice, this means that every time the ignore list is changed, > > VSCode immediately starts indexing the build folder until the OOM > > exception stops it. Depending on the system's OOM handler, the > > entire > > build machine may crash. > > > > Particularly annoying is the Python plugin that ignores the general > > ignore list and requires an extra ignore section. > > > > However, putting a static file in poky doesn't look like a good > > solution. Depending on the setup, the configuration here is not > > valid. > > A better approach would be to handle this in the bitbake plugin. > > But > > even that looks kind of wrong, because why should the bitbake > > plugin > > configure other indexer plugins? Other ideas would be to have the > > configuration file generated by the layer setup tool or simply > > cover > > this topic in the documentation. > > > > Regards, > > Adrian > > > > > > > > Luca > > > > > > > > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#186522): https://lists.openembedded.org/g/openembedded-core/message/186522 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] -=-=-=-=-=-=-=-=-=-=-=-
