[OE-core] [PATCH 0/2] Extensible SDK improvements

[Richard Purdie]

On Sat, 2020-03-07 at 12:54 +0100, Adrian Freihofer wrote:
> Hi Richard,
> 
> We have found two already supported ways to copy variables from the
> bitbake environment local.conf to the eSDK local.conf
> 
> If a variable is defined in the local.conf bitbake environment,
> SDK_LOCAL_CONF_WHITELIST and SDK_LOCAL_CONF_BLACKLIST can be used to
> add it to the local.conf eSDK file.
> 
> If a variable should be statically defined for the eSDK but not for
> the
> bitbake environment, sdk-extra.conf is useful.
> 
> Now we would like to add a third way to add variables which are
> dynamically calculated by bitbake but need to be statically added to
> the eSDK local.conf. For example we would like to support something
> like that:
> 
> def get_version_from_git(d):
>     version = d.getVar("GIT_VERSION", True)
>     if version:
>         return version                    # runs in eSDK
>     else:
>         return bb.process.run("git...     # runs in bitbake
> 
> GIT_VERSION := "${@get_version_from_git(d)}"
> 
> SDK_LOCAL_CONF_EXTRALIST_append = " GIT_VERSION"

This worries me a bit since it means the eSDK and the "real" build can
behave differently. I appreciate that can happen even with the other
variables and means of setting them but this takes it to a new level.

Ultimately I think we're aiming to have normal builds convert into an
eSDK and vice versa more easily. This seems to pull us further away
from that :/.

What is the reasoning for having them behaving differently?

Cheers,

Richard