Re: [OE-core] multiple toolchains in SDK?

[Adrian Freihofer <adrian.freihofer@gmail.com>]

On Wed, 2025-02-05 at 18:16 +0000, Joakim Tjernlund via
lists.openembedded.org wrote:
> 
> On Fri, 2024-12-06 at 17:08 +0100, Christian Eggers wrote:
> > On Friday, 6 December 2024, 15:12:03 CET, Joakim Tjernlund via
> > lists.openembedded.org wrote:
> > > Trying to figure out how to build in SDK:
> > > gcc-arm32-musl
> > > and
> > > gcc-arm64-musl(or possibly gcc-arm64-newlib)
> > 
> > +1
> > 
> > We currently use ARMv7 (32 bit) with musl for our products and it
> > is possible
> > that we'll have to switch to ARMv8 for some derivatives in future.
> > As we
> > develop multiple products in parallel, having a SDK with both
> > compilers / library sets
> > would be great.
> 
> Any luck?
> 
>   Jocke
> 
> > 
> > > 
> > > without using multilib(as musl do not support multilib gcc-
> > > style), also
> > > the arm64 toolchain only needs to contains static libc.a
> > > 
> > > I cannot find how to express this in Yocto/Poky. Any pointers
> > > please?
> > > 
> > > Jocke
> > > 
> > 

Hi

Since you are writing very specifically about tool chains, you probably
need the environment script that is traditionally available with the
SDK or the eSDK installer. However, an SDK installer is limited in many
ways. Supporting only one architecture is one of them.

For some releases, the same environment script has also been available
in the Bitbake environment. You can use for example
  devtool ide-sdk --mode=shared
to bootstrap the SDK out of a bitbake environment as documented here:
https://docs.yoctoproject.org/dev/singleindex.html#devtool-ide-sdk-configures-ides-and-bootstraps-sdks

I would argue that such an environment has many advantages over an
environment set up by an eSDK installer. But the bootstrapping of such
an SDK requires to replicate a bitbake environment, basically: the
layers, the sstate-cache and a build configuration. There are multiple
ways how this can be done:

- Here is probably the official future:
https://lists.openembedded.org/g/openembedded-core/message/210948
- layers and build configurations are in git, the sstate is shared
- And there several other tools doing this.

Therefore, it is probably more promising to make the replication of the
Bitbake environment as simple as running an SDK installer is at time,
instead of further improving the installer-based approach.

Regards,
Adrian



> > 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#210874):
> https://lists.openembedded.org/g/openembedded-core/message/210874
> Mute This Topic: https://lists.openembedded.org/mt/109957875/4454582
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe:
> https://lists.openembedded.org/g/openembedded-core/unsub [
> adrian.freihofer@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>