On Wed, 18 May 2022 at 09:50, Pascal Bach <[email protected]> wrote:
> The advantages of this approach is: > 1. The bitbake environment and the "sdkenv" are the same. The only > difference is how you use it (devtool or bitbake) and how much you > reley on the sstate cache. > 2. Developers always have the full power of bitbake available. So it's > easy to update dependencies, crate new sdk and even do completely new > builds. > 3. There is no need to crate a new eSDK installer as you can always > test it directly from within bitbake by calling devtool sdkenv <recipe> > 4. Updates are simple as it just means updating the recipes and > providing an sstate-mirror. > > What do you think? Is this feasible or even desired? Yes, it's feasible and I have a working proof of concept now: https://lists.openembedded.org/g/openembedded-core/message/167226 Please take a look, try it out and let me know! Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1562): https://lists.openembedded.org/g/openembedded-architecture/message/1562 Mute This Topic: https://lists.openembedded.org/mt/90990557/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
