From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: one more curiosity about oe-buildenv-internal: what's with BBEXTRA?
Date: Wed, 21 Mar 2012 19:20:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1203211920360.16949@oneiric> (raw)
In-Reply-To: <1332371826.9740.222.camel@ted>
On Wed, 21 Mar 2012, Richard Purdie wrote:
> On Wed, 2012-03-21 at 19:02 -0400, Robert P. J. Day wrote:
> > apparently, given the following in oe-buildenv-internal:
> >
> > BITBAKEDIR="$OEROOT/bitbake$BBEXTRA/"
> >
> > you can use BBEXTRA to use a different bitbake directory than the
> > default. is this a debugging aid? are normal users meant to know
> > about this? i don't see any mention of it anywhere. in fact, from
> > the top level of oe-core:
> >
> > $ grep -r BBEXTRA *
> > scripts/oe-buildenv-internal:BITBAKEDIR="$OEROOT/bitbake$BBEXTRA/"
> > $
>
> I was responsible for this one a long time ago and it was simply a
> development aid. I was probably its main user although I haven't used it
> in a while. We don't have multiple versions of bitbake being used
> heavily anymore, thankfully.
is it worth just removing? i can send in a patch unless you'd
rather quietly keep it around.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2012-03-21 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 23:02 one more curiosity about oe-buildenv-internal: what's with BBEXTRA? Robert P. J. Day
2012-03-21 23:17 ` Richard Purdie
2012-03-21 23:20 ` Robert P. J. Day [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=alpine.DEB.2.02.1203211920360.16949@oneiric \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox