multiple toolchains in SDK?

multiple toolchains in SDK?

[Joakim Tjernlund]

Trying to figure out how to build in SDK:
 gcc-arm32-musl
and
 gcc-arm64-musl(or possibly gcc-arm64-newlib)

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

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

[Christian Eggers]

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]

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.

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





_______________________________________________________
Christian 
Eggers
Software Engineer
​
ARRI
Arnold & Richter Cine Technik GmbH & Co. Betriebs KG 
Arriweg 17, 
83071 
Stephanskirchen
www.arri.com 

+49 8036 3009-3118
CEggers@arri.de

​

Arnold & Richter Cine Technik GmbH & Co. Betriebs KG
Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: HRA 57918
Persönlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH
Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: HRB 54477
Geschäftsführer: Stefan Mairiedl; Walter Trauninger

​

[-- Attachment #2.1: Type: text/html, Size: 10665 bytes --]

[-- Attachment #2.2: image895117.png --]
[-- Type: image/png, Size: 528 bytes --]

[-- Attachment #2.3: image874737.png --]
[-- Type: image/png, Size: 824 bytes --]

[-- Attachment #2.4: image408484.jpg --]
[-- Type: image/jpeg, Size: 56831 bytes --]

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

[Joakim Tjernlund]

[-- Attachment #1.1: Type: text/plain, Size: 1830 bytes --]

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
>





_______________________________________________________​​​​

Christian



Eggers

Software Engineer

​

ARRI

Arnold & Richter Cine Technik GmbH & Co. Betriebs KG

Arriweg 17

,

83071



Stephanskirchen

www.arri.com

<http://www.arri.com/>

[cid:image895117.png@6B12B797.13EF4F6E]

+49 8036 3009-3118<tel:+49%208036%203009-3118>

[cid:image874737.png@FFF4299A.EDE3391B]

CEggers@arri.de<mailto:CEggers@arri.de>

​

[ALEXA 265]<https://www.arrirental.com/en/cameras/digital-65-mm-cameras/alexa-265?utm_source=ARRI&utm_medium=email&utm_campaign=alexa-265-launch&utm_content=trafficAll>


Arnold & Richter Cine Technik GmbH & Co. Betriebs KG
Sitz: München ‑ Registergericht: Amtsgericht München ‑ Handelsregisternummer: HRA 57918
Persönlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH
Sitz: München ‑ Registergericht: Amtsgericht München ‑ Handelsregisternummer: HRB 54477
Geschäftsführer: Stefan Mairiedl; Walter Trauninger

​


[-- Attachment #1.2: Type: text/html, Size: 12469 bytes --]

[-- Attachment #2: image895117.png --]
[-- Type: image/png, Size: 528 bytes --]

[-- Attachment #3: image874737.png --]
[-- Type: image/png, Size: 824 bytes --]

[-- Attachment #4: image408484.jpg --]
[-- Type: image/jpeg, Size: 56831 bytes --]

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

[Christian Eggers]

[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]

Hi Jocke,

On Wednesday, 5 February 2025, 19:16:20 CET, Joakim Tjernlund 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

as we haven't switched to a new hardware yet, I didn't investigate further into this.

regards,
Christian

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




_______________________________________________________
Christian 
Eggers
Software Engineer
​
ARRI
Arnold & Richter Cine Technik GmbH & Co. Betriebs KG 
Arriweg 17, 
83071 
Stephanskirchen
www.arri.com 

+49 8036 3009-3118
CEggers@arri.de

​

Arnold & Richter Cine Technik GmbH & Co. Betriebs KG
Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: HRA 57918
Persönlich haftender Gesellschafter: Arnold & Richter Cine Technik GmbH
Sitz: München - Registergericht: Amtsgericht München - Handelsregisternummer: HRB 54477
Geschäftsführer: Walter Trauninger

​

[-- Attachment #2.1: Type: text/html, Size: 11092 bytes --]

[-- Attachment #2.2: image352163.png --]
[-- Type: image/png, Size: 528 bytes --]

[-- Attachment #2.3: image821587.png --]
[-- Type: image/png, Size: 824 bytes --]

[-- Attachment #2.4: image392705.jpg --]
[-- Type: image/jpeg, Size: 119899 bytes --]

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

[Adrian Freihofer]

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]
> -=-=-=-=-=-=-=-=-=-=-=-
>