From: Patrick Ohly <patrick.ohly@intel.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: OpenEmbedded Core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel.bbclass: Allow ${S} to be overridden
Date: Mon, 14 Nov 2016 08:59:53 +0100 [thread overview]
Message-ID: <1479110393.3240.3.camel@intel.com> (raw)
In-Reply-To: <20161111193902.3e34bf60@nuc.betafive.co.uk>
On Fri, 2016-11-11 at 19:39 +0000, Paul Barker wrote:
> On Wed, 9 Nov 2016 15:42:29 -0800
> Andre McCurdy <armccurdy@gmail.com> wrote:
>
> > The solution I use (learned the hard way) is to ensure that "S = ..."
> > comes after "inherit kernel" in the kernel recipe.
> >
>
> Ok, yea, this works for me.
>
> Is this expected? S is set to ${STAGING_KERNEL_DIR} at the start of
> kernel.bbclass. The base_do_unpack_append() function is defined later
> in kernel.bbclass. If S is set to ${WORKDIR}/${BP} only after
> kernel.bbclass is inherited, then that's after base_do_unpack_append()
> has been parsed.
Parsing itself does not expand variable references (*), so it is
possible to use a variable that gets changed later on and use the value
that the variable eventually ends up having.
(*) There's one exception - the := assignment expands based on the
currently defined variables at the time of parsing the assignment.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2016-11-14 7:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 18:38 [PATCH] kernel.bbclass: Allow ${S} to be overridden Paul Barker
2016-11-05 10:14 ` Paul Barker
2016-11-09 1:04 ` Burton, Ross
2016-11-09 2:23 ` Bruce Ashfield
2016-11-09 10:04 ` Burton, Ross
2016-11-09 11:34 ` Burton, Ross
2016-11-09 13:09 ` Bruce Ashfield
2016-11-09 18:08 ` Paul Barker
2016-11-09 23:42 ` Andre McCurdy
2016-11-11 19:39 ` Paul Barker
2016-11-14 7:59 ` Patrick Ohly [this message]
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=1479110393.3240.3.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox