All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Adjusting Extensible SDK for build setup
Date: Mon, 20 Jul 2020 16:28:18 +0000	[thread overview]
Message-ID: <MADEUP.162382CDAD44D3F3.1350@lists.yoctoproject.org> (raw)
In-Reply-To: <bd561a5bfcde2e37f297d52ad3094831cd3d4229.camel@linuxfoundation.org>


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


  reply	other threads:[~2020-07-20 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5f15beeb.1c69fb81.4c8f7.9ea5SMTPIN_ADDED_MISSING@mx.google.com>
2020-07-20 16:16 ` [yocto] Adjusting Extensible SDK for build setup Richard Purdie
2020-07-20 16:28   ` Monsees, Steven C (US) [this message]
     [not found] <5f15c655.1c69fb81.b5042.e2fdSMTPIN_ADDED_MISSING@mx.google.com>
2020-07-20 17:02 ` Richard Purdie
2020-07-20 17:13   ` Monsees, Steven C (US)
2020-07-20 17:18     ` Richard Purdie
2020-07-20 17:50       ` Monsees, Steven C (US)
2020-07-20 15:06 Monsees, Steven C (US)
2020-07-20 15:30 ` [yocto] " Richard Purdie
2020-07-20 15:57   ` Monsees, Steven C (US)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MADEUP.162382CDAD44D3F3.1350@lists.yoctoproject.org \
    --to=steven.monsees@baesystems.com \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.