Re: [yocto] Adjusting Extensible SDK for build setup

["Richard Purdie" <richard.purdie@linuxfoundation.org>]

On Mon, 2020-07-20 at 15:06 +0000, Monsees, Steven C (US) wrote:
>  
> I am fairly new to the Yocto SDK build process, and am looking to
> create an extensible SDK for one of our platforms.
>  
> I am currently working with Rocko 2.4.1, in conjunction with
> uninative release 1.9…
>  
> My current build system setup does not follow the standard
> configuration, I use a different environment setup script other than
> “oe-init-build-env”.
>  
> My environment setup script “setup-build-env” is also not located in
> the  ${COREBASE}, i.e. the “poky” directory, but rather at
> “${COREBASE}/../meta-bae/meta-limws”, the meta-limws level has
> multiple architecture sub levels (each an independent build), I am
> only looking to build an SDK for one of these architectures. Each
> architecture’s  bblayers.conf provides the appropriate layers…
>  
> My build directory is expected to reside here:
>   “${COREBASE}/../meta-bae/meta-limws/builds, and there are multiple
> architecture builds under this directory

I think the build directory expectation isn't going to work with the
eSDK.

The eSDK is really designed against one configuration and the build
directory becomes that specific SDK. You therefore can't require some
sub directory of the eSDK become the build directory as that isn't how
its designed to operate.

Cheers,

Richard