From: Ross Burton <Ross.Burton@arm.com>
To: "chris.sutton@l3harris.com" <chris.sutton@l3harris.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] eSDK is missing native cross-compiler toolchain and compiled target libs
Date: Tue, 1 Aug 2023 18:50:15 +0000 [thread overview]
Message-ID: <0D714194-137D-47CB-9401-C7B2DAB33FA7@arm.com> (raw)
In-Reply-To: <KF92.1690198680497382322.XSbE@lists.openembedded.org>
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.
Ross
next prev parent reply other threads:[~2023-08-01 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 11:38 eSDK is missing native cross-compiler toolchain and compiled target libs Sutton, Chris (FP) - IC
2023-08-01 18:50 ` Ross Burton [this message]
2023-08-01 21:44 ` [OE-core] " Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0D714194-137D-47CB-9401-C7B2DAB33FA7@arm.com \
--to=ross.burton@arm.com \
--cc=chris.sutton@l3harris.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox