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 17:13:15 +0000	[thread overview]
Message-ID: <MADEUP.1623853FAF59D08E.10418@lists.yoctoproject.org> (raw)
In-Reply-To: <224f8a27bc8a2c8074f78e32dcac025686ed420c.camel@linuxfoundation.org>


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






  reply	other threads:[~2020-07-20 17:13 UTC|newest]

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