Hi Alex On Wednesday, 22 June 2022 22:33:06 NZDT Alexander Kanavin wrote: > There's been a recent discussion about how we can make the Yocto SDK > experience better [1]. One of the ideas was to eliminate the SDK > as a separate artefact altogether and simply provide everything > that the SDK and eSDKs do directly in a yocto build. This does not > mean that people have to 'learn Yocto', but rather that the integrators > should provide a well-functioning sstate cache infrastructure (same as > with minimal eSDK, really), and a few wrapper scripts for setting up the > build and the SDK environment that run layer setup and bitbake behind the > scenes.
FWIW I think this is quite clever - well done :) One question though: > 2. Run: > $ bitbake meta-ide-support > $ bitbake -c populate_sysroot gtk+3 > (or any other target or native item that the application developer would > need) > $ bitbake populate-sysroots Should this have been "build-sysroots"? "populate-sysroots" doesn't seem to be a valid target. It looks like this is in the SDK manual as well. Cheers Paul
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#171557): https://lists.openembedded.org/g/openembedded-core/message/171557 Mute This Topic: https://lists.openembedded.org/mt/91918831/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
