Re: [OE-core] [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build

2022-10-13 Thread Alexander Kanavin
Cheers - try the new layer setup and config management tools too :-) Alex On Thu, 13 Oct 2022 at 10:44, Leon Woestenberg wrote: > > Hello Alexander, > > On Wed, Jun 22, 2022 at 12:33 PM Alexander Kanavin > wrote: > > > > There's been a recent discussion about how we can make the Yocto SDK > > e

Re: [OE-core] [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build

2022-10-13 Thread Leon Woestenberg
Hello Alexander, On Wed, Jun 22, 2022 at 12:33 PM 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 a

Re: [OE-core] [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build

2022-10-10 Thread Alexander Kanavin
On Mon, 10 Oct 2022 at 10:23, Paul Eggleton wrote: > > 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"? "

Re: [OE-core] [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build

2022-10-10 Thread Paul Eggleton
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 e

[OE-core] [RFC PATCH 0/6] (e)SDK workflow directly in a Yocto build

2022-06-22 Thread Alexander Kanavin
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 Yo