Re: [OE-core] eSDK is missing native cross-compiler toolchain and compiled target libs

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Tue, 2023-08-01 at 18:50 +0000, Ross Burton wrote:
> On 24 Jul 2023, at 12:38, Sutton, Chris (FP) - IC via lists.openembedded.org <chris.sutton=l3harris.com@lists.openembedded.org> wrote:
> >  I’ve built the eSDK for poky honister. However, it DOES NOT contain the cross-compiler toolchain/compiled target libs.
> > I build the standard SDK and it DOES contain the cross-compiler toolchain/compiled target libs but of course has no built-in QEMU.
> 
> I can’t see any reason why you can’t just add nativesdk-qemu to your standard SDK.
> 
> > I am confused by this. I thought the eSDK came with a toolchain, but it seems not.
> >  I need both the cross-compiler toolchain/compiled target libs and QEMU.
> > How can I include the cross-compiler toolchain/compiled target libs in the eSDK build?
> 
> eSDKs are pretty minimal out of the box, you need to use ‘devtool sdk-install’ to install tools.  ‘devtool sdk-install gcc-cross-aarch64’ or similar should work I believe.

A lot depends which eSDK we're talking about too. I'd have expected
most images to have basic target libs so the eSDK built against them
should have it too.

Is this a minimal eSDK or an eSDK including all the sstate artefacts?
That might also make a difference...

Cheers,

Richard