On Tue, 5 Jul 2022 at 10:51, Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > The challenge with your approach is that it is bolted directly onto > bitbake-layers, which makes it not only OE-Core API but bitbake API > too. There is a standard such changes need to reach and I'm not > convinced that is doesn't tie our hands in future as is. > > I suspect in reality, we could probably have the same functionality in > a separate script in OE-Core, maybe improving the APIs/library > functions from bitbake-layers if needed. That would lower the bar and > mean we could have something focused on eSDK needs rather than the > wider problem.
I added the layer config generator as a bitbake-layers plugin for these reasons: 1. It is layer management functionality, and so logically belongs in that tool. 2. It is more visible and discoverable when it is in there, as opposed to all those executables in poky/scripts/ which most people have no idea about. 3. It needs to get a list of active layers and their locations programmatically, which is trivial from a bitbake-layers plugin, less so from other places. 4. it can reuse code from meta/lib/oe if/when needed. There are a few things in there that I'd already like to do differently, and there's also the 'save the active build/conf in TEMPLATECONF format' piece missing, so there'll be a reworked version, arriving in bite-sized chunks for easier review/discussion. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#167645): https://lists.openembedded.org/g/openembedded-core/message/167645 Mute This Topic: https://lists.openembedded.org/mt/92117681/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
