From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Monsees, Steven C (US)" <steven.monsees@baesystems.com>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Adjusting Extensible SDK for build setup
Date: Mon, 20 Jul 2020 18:18:54 +0100 [thread overview]
Message-ID: <1be512a8c6122e1305c4290514a4603f8e4ebfaa.camel@linuxfoundation.org> (raw)
In-Reply-To: <MADEUP.1623853FAF59D08E.10418@lists.yoctoproject.org>
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
next prev parent reply other threads:[~2020-07-20 17:18 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)
2020-07-20 17:18 ` Richard Purdie [this message]
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=1be512a8c6122e1305c4290514a4603f8e4ebfaa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=steven.monsees@baesystems.com \
--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.