environment-setup.d usage in SDKs and eSDK

environment-setup.d usage in SDKs and eSDK

[Richard Purdie]

I've just spent far too long staring at this so I'm going to write down
what I found out. I may as well share it publicly.

An eSDK can be used like a normal SDK with an environment file that can
be sourced. The challenge is that an eSDK contains native binaries
rather than the nativesdk variants in the SDK.

This means that where an SDK has nativesdk environment.d files, an eSDK
ends up using "native" environment.d files which are not used in any
other context.

Some recipes like cmake implement both. Some others like icecc or
openssl only have nativesdk variants. This probably needs cleaning up
to be consistent.

It gets worse when you find that buildtools is included in eSDK and its
environment file is sourced. This means you get a mix of nativesdk and
native. If you set OECORE_NATIVE_SYSROOT in buildtools, it corrupts the
eSDK's variable of the same name. This why buildtools has a hardcoded
list of variables it puts in the enrivonment rather than using
environment.d.

It would be better if the two sets of environment files (native and
nativesdk) referenced different variables as currently the two can't
coexist. This also really needs to be fixed.

Cheers,

Richard

Re: environment-setup.d usage in SDKs and eSDK

[Jens Rehsack]

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



> Am 07.08.2020 um 17:17 schrieb Richard Purdie <richard.purdie@linuxfoundation.org>:
> 
> I've just spent far too long staring at this so I'm going to write down
> what I found out. I may as well share it publicly.
> 
> An eSDK can be used like a normal SDK with an environment file that can
> be sourced. The challenge is that an eSDK contains native binaries
> rather than the nativesdk variants in the SDK.
> 
> This means that where an SDK has nativesdk environment.d files, an eSDK
> ends up using "native" environment.d files which are not used in any
> other context.
> 
> Some recipes like cmake implement both. Some others like icecc or
> openssl only have nativesdk variants. This probably needs cleaning up
> to be consistent.
> 
> It gets worse when you find that buildtools is included in eSDK and its
> environment file is sourced. This means you get a mix of nativesdk and
> native. If you set OECORE_NATIVE_SYSROOT in buildtools, it corrupts the
> eSDK's variable of the same name. This why buildtools has a hardcoded
> list of variables it puts in the enrivonment rather than using
> environment.d.
> 
> It would be better if the two sets of environment files (native and
> nativesdk) referenced different variables as currently the two can't
> coexist. This also really needs to be fixed.
> 
> Cheers,
> 
> Richard

Thank you very much for your patience and time digging deeper into this.
Maybe I'm getting the chance to help something - I forwarded this information
to the team and look if we can use both, SDK and eSDK so we would need
those fixups (and thus do them then ^^).

Cheers
--
Jens Rehsack - rehsack@gmail.com


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 849 bytes --]