Skip to contentSkip to conversation

eSDK is missing native cross-compiler toolchain and compiled target libs

DISCUSSION Sutton, Chris (FP) - IC 3 participants 3 messages Jul 24, 2023 – Aug 1, 2023

lore
Share & tools
lore
#0 lore raw

Hi

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 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?

#1 lore raw
Quoted 2 lines · Chris (FP) - IC via lists.openembedded.org

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.

Quoted 3 lines

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.

Ross

#2 lore raw
Quoted 11 lines · Ross Burton
Quoted 2 lines · Chris (FP) - IC via lists.openembedded.org

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.

Quoted 3 lines

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