From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: Chris, Larson <clarson@kergoth.com>,
bitbake-devel@lists.openembedded.org,
Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 1/1] bitbake.conf: add BB_STAMPS_DIR for constructing STAMP
Date: Wed, 15 Aug 2012 15:00:47 +0100 [thread overview]
Message-ID: <1345039247.538.23.camel@ted> (raw)
In-Reply-To: <502BA8F2.9070606@windriver.com>
On Wed, 2012-08-15 at 21:49 +0800, Robert Yang wrote:
>
> On 08/15/2012 09:42 PM, Richard Purdie wrote:
> > On Fri, 2012-08-10 at 10:02 +0800, Robert Yang wrote:
> >> Add BB_STAMPS_DIR for constructing STAMP, the defination of STAMP
> >> before:
> >>
> >> STAMP = "${TMPDIR}/stamps/${MULTIMACH_TARGET_SYS}/${PF}
> >>
> >> We can only change the TMPDIR if we want to change the STAMP's location,
> >> but the cache would be regenerated if TMPDIR changed, so add
> >> BB_STAMPS_DIR for constructing it, and add it to the BB_ENV_EXTRAWHITE,
> >> this is very usefull for the "bitbake -S", since then it can be run by:
> >>
> >> BB_STAMPS_DIR=<path> bitbake -S <recipe>
> >>
> >> which will avoid putting the stamps to ${TMPDIR}/stamps.
> >>
> >> BTW, break the too long BB_ENV_EXTRAWHITE into several lines.
> >>
> >> [YOCTO #1659]
> >>
> >> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> >> ---
> >> meta/conf/bitbake.conf | 3 ++-
> >> scripts/oe-buildenv-internal | 5 ++++-
> >> 2 files changed, 6 insertions(+), 2 deletions(-)
> >
> > BB_ is a prefix for variables bitbake specifically uses for
> > configuration. It doesn't fit in this context since its metadata defined
> > and doesn't actually influence or is used by bitbake itself.
> >
> > We therefore need to use a different name for this.
> >
>
> Thanks, how about "STAMPS_DIR" ? And can we put the bitbake-whatchanged
> to bitbake/bin or bitbake/contrib as Chris Larson worried about ?
He's right, it depends on the metadata and therefore shouldn't really be
in bitbake. It could go into scripts/ in oe-core.
Cheers,
Richard
next prev parent reply other threads:[~2012-08-15 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 2:02 [PATCH 0/1] bitbake.conf: add BB_STAMPS_DIR for constructing STAMP Robert Yang
2012-08-10 2:02 ` [PATCH 1/1] " Robert Yang
2012-08-15 13:42 ` Richard Purdie
2012-08-15 13:49 ` Robert Yang
2012-08-15 14:00 ` Richard Purdie [this message]
2012-08-15 14:13 ` Robert Yang
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=1345039247.538.23.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.com \
--cc=liezhi.yang@windriver.com \
/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