Re: [yocto] Adjusting Extensible SDK for build setup

Re: [yocto] Adjusting Extensible SDK for build setup

[Richard Purdie]

On Mon, 2020-07-20 at 15:57 +0000, Monsees, Steven C (US) wrote:
> The BUILDDIR is defined as configurable under Yocto...
>
> I set this up as per the Yocto docs based on the "MACHINE' I am
> building, I do not believe this is the issue. 
> 
> There is no issue when building the standard SDK... 
> 
> I am looking for the proper variable settings for COREBASE,
> COREBASE_FILES, and OE_INIT_ENV_SCRIPT variables required by eSDK
> when working with
> a different environment setup script not located in the COREBASE
> (i.e. poky) directory...

Looking at the code in populate_sdk_ext.bbclass:copy_buildsystem(), 
it looks in each layer for the script specified in OE_INIT_ENV_SCRIPT.

From your description its impossible to know whether meta-limws or
meta-bae is seen as individual layers and whether they're copied
individually into layers/ in the eSDK or not.

I'd guess that " meta-limws/setup-build-env" or "meta-bae/meta-
limws/setup-build-env" should work as the value for OE_INIT_ENV_SCRIPT.

If poky is being used and is unaltered, COREBASE and COREBASE_FILES
should work unaltered.

Cheers,

Richard

Re: [yocto] Adjusting Extensible SDK for build setup

[Monsees, Steven C (US)]

Yes, this is what I saw as well...

I had to add two lines to the populate_sdk_ext.bbclass to properly get it to pick up my env script.
I set :

	OE_INIT_ENV_SCRIPT = "setup-build-env"
	CORE_BASE_Files = " \
	     Scripts \
	     LICENSE \
	     .templateconf \
	"
This allowed me to build the "minimale SDK EXT.

	SDK_EXT_TYPE = "minimal"
	SDK_LOCAL_CONF_WHITELIST = "SSTATE_MIRRORS"

Was hoping I would be able to configure the variables rather than modify the script...
Do not want to introduce future support ussues if possible.

Thanks,
Steve

-----Original Message-----
From: yocto@lists.yoctoproject.org [mailto:yocto@lists.yoctoproject.org] On Behalf Of Richard Purdie
Sent: Monday, July 20, 2020 12:17 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] Adjusting Extensible SDK for build setup

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


On Mon, 2020-07-20 at 15:57 +0000, Monsees, Steven C (US) wrote:
> The BUILDDIR is defined as configurable under Yocto...
>
> I set this up as per the Yocto docs based on the "MACHINE' I am 
> building, I do not believe this is the issue.
> 
> There is no issue when building the standard SDK... 
> 
> I am looking for the proper variable settings for COREBASE, 
> COREBASE_FILES, and OE_INIT_ENV_SCRIPT variables required by eSDK when 
> working with a different environment setup script not located in the 
> COREBASE (i.e. poky) directory...

Looking at the code in populate_sdk_ext.bbclass:copy_buildsystem(),
it looks in each layer for the script specified in OE_INIT_ENV_SCRIPT.

From your description its impossible to know whether meta-limws or meta-bae is seen as individual layers and whether they're copied individually into layers/ in the eSDK or not.

I'd guess that " meta-limws/setup-build-env" or "meta-bae/meta- limws/setup-build-env" should work as the value for OE_INIT_ENV_SCRIPT.

If poky is being used and is unaltered, COREBASE and COREBASE_FILES should work unaltered.

Cheers,

Richard

Re: [yocto] Adjusting Extensible SDK for build setup

[Richard Purdie]

On Mon, 2020-07-20 at 16:28 +0000, Monsees, Steven C (US) wrote:
> Yes, this is what I saw as well...
> 
> I had to add two lines to the populate_sdk_ext.bbclass to properly
> get it to pick up my env script.
> I set :
> 
> 	OE_INIT_ENV_SCRIPT = "setup-build-env"
> 	CORE_BASE_Files = " \
> 	     Scripts \
> 	     LICENSE \
> 	     .templateconf \
> 	"
> This allowed me to build the "minimale SDK EXT.
> 
> 	SDK_EXT_TYPE = "minimal"
> 	SDK_LOCAL_CONF_WHITELIST = "SSTATE_MIRRORS"
> 
> Was hoping I would be able to configure the variables rather than
> modify the script...
> Do not want to introduce future support ussues if possible.

Both variables are assigned with weak defaults. Can't you just set
those variables in your own distro config to override the defaults?

Cheers,

Richard

Re: [yocto] Adjusting Extensible SDK for build setup

[Monsees, Steven C (US)]

No, I guess I wasn't clear, I needed to add to lines of code in the scripts to adjust things so that my env script was copied to the proper SDK build env "layers" directory and set the conf_initpath to use my env script...

The variable assignments mentioned are configured in my distro config for the overall SDK build.

Steve

-----Original Message-----
From: yocto@lists.yoctoproject.org [mailto:yocto@lists.yoctoproject.org] On Behalf Of Richard Purdie
Sent: Monday, July 20, 2020 1:03 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] Adjusting Extensible SDK for build setup

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


On Mon, 2020-07-20 at 16:28 +0000, Monsees, Steven C (US) wrote:
> Yes, this is what I saw as well...
> 
> I had to add two lines to the populate_sdk_ext.bbclass to properly get 
> it to pick up my env script.
> I set :
> 
> 	OE_INIT_ENV_SCRIPT = "setup-build-env"
> 	CORE_BASE_Files = " \
> 	     Scripts \
> 	     LICENSE \
> 	     .templateconf \
> 	"
> This allowed me to build the "minimale SDK EXT.
> 
> 	SDK_EXT_TYPE = "minimal"
> 	SDK_LOCAL_CONF_WHITELIST = "SSTATE_MIRRORS"
> 
> Was hoping I would be able to configure the variables rather than 
> modify the script...
> Do not want to introduce future support ussues if possible.

Both variables are assigned with weak defaults. Can't you just set those variables in your own distro config to override the defaults?

Cheers,

Richard

Re: [yocto] Adjusting Extensible SDK for build setup

[Richard Purdie]

On Mon, 2020-07-20 at 17:13 +0000, Monsees, Steven C (US) wrote:
> No, I guess I wasn't clear, I needed to add to lines of code in the
> scripts to adjust things so that my env script was copied to the
> proper SDK build env "layers" directory and set the conf_initpath to
> use my env script...
> 
> The variable assignments mentioned are configured in my distro config
> for the overall SDK build.

It would be helpful to understand which two lines you needed to modify
and how.

Was the setup script being copied at all without your changes? If so
where was it being copied? If not, what did you change and where was it
copied afterwards?

What value are you setting conf_initpath to?

Its very difficult to answer questions on a layer structure which isn't
clearly described :(

Cheers,

Richard

Re: [yocto] Adjusting Extensible SDK for build setup

[Monsees, Steven C (US)]

My apologies...

In populate_sdk_ext.bbclass line 815, I hardcoded the relpath for test purposes :
	relpath = 'layers/meta-bae/meta-limws/setup-build-env'

In copy_buildsystem.py after line 312 I appended my script to the list to be copied:
	Layers.append("<<full path>>/setup-build-env")

Steve

-----Original Message-----
From: yocto@lists.yoctoproject.org [mailto:yocto@lists.yoctoproject.org] On Behalf Of Richard Purdie
Sent: Monday, July 20, 2020 1:19 PM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] Adjusting Extensible SDK for build setup

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


On Mon, 2020-07-20 at 17:13 +0000, Monsees, Steven C (US) wrote:
> No, I guess I wasn't clear, I needed to add to lines of code in the 
> scripts to adjust things so that my env script was copied to the 
> proper SDK build env "layers" directory and set the conf_initpath to 
> use my env script...
> 
> The variable assignments mentioned are configured in my distro config 
> for the overall SDK build.

It would be helpful to understand which two lines you needed to modify and how.

Was the setup script being copied at all without your changes? If so where was it being copied? If not, what did you change and where was it copied afterwards?

What value are you setting conf_initpath to?

Its very difficult to answer questions on a layer structure which isn't clearly described :(

Cheers,

Richard

Adjusting Extensible SDK for build setup

[Monsees, Steven C (US)]

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


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.

In the Yocto Project Mega-Manual, Appendix B.2... it talks about setting up COREBASE and COREBASE_FILES...

The default COREBASE_FILES is setup in populate_sdk_ext.bbclass as:

COREBASE_FILES ?= " \
    oe-init-build-env \
    scripts \
    LICENSE \
    .templateconf \
"
How do I configure COREBASE, COREBASE_FILES, and OE_INIT_ENV_SCRIPT variable so that populate_sdk_ext.bbclass is able to properly run "do_populate_sdk_ext" without having to modify populate_sdk_ext.bbclass ?

Can someone tell me the proper configuration for these variables so that my "setup-build-env" script is copied/used correctly by the SDK build env ?

Thanks,
Steve




[-- Attachment #2: Type: text/html, Size: 4590 bytes --]

Re: [yocto] Adjusting Extensible SDK for build setup

[Richard Purdie]

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

Re: [yocto] Adjusting Extensible SDK for build setup

[Monsees, Steven C (US)]

The BUILDDIR is defined as configurable under Yocto...
I set this up as per the Yocto docs based on the "MACHINE' I am building, I do not believe this is the issue. 

There is no issue when building the standard SDK... 

I am looking for the proper variable settings for COREBASE, COREBASE_FILES, and OE_INIT_ENV_SCRIPT variables required by eSDK when working with
a different environment setup script not located in the COREBASE (i.e. poky) directory...

Thanks,
Steve

-----Original Message-----
From: yocto@lists.yoctoproject.org [mailto:yocto@lists.yoctoproject.org] On Behalf Of Richard Purdie
Sent: Monday, July 20, 2020 11:31 AM
To: Monsees, Steven C (US) <steven.monsees@baesystems.com>; yocto@lists.yoctoproject.org
Subject: Re: [yocto] Adjusting Extensible SDK for build setup

*** WARNING ***
EXTERNAL EMAIL -- This message originates from outside our organization.


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