Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Christopher Larson <kergoth@gmail.com>,
	 Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	 "chris.laplante@agilent.com" <chris.laplante@agilent.com>,
	 OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] why does oe-buildenv-internal check for -z "$BDIR"?
Date: Sun, 19 Apr 2020 09:11:55 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.21.2004190910470.1292842@localhost.localdomain> (raw)
In-Reply-To: <d2f052416cef21416444e08512f84dd8c4f1aeca.camel@linuxfoundation.org>

On Sun, 19 Apr 2020, Richard Purdie wrote:

> On Sat, 2020-04-18 at 18:17 -0400, Robert P. J. Day wrote:
> >   that actually matches with what i concluded -- BDIR is dead and
> > gone, but i realized that BITBAKEDIR could still be useful, even
> > if it's currently undocumented. so i'll submit a patch to ditch
> > BDIR, and leave all else as is. for now.
>
> BDIR allows the build directory to be set explicitly from a script
> without worrying about which shell is in use.

  i believe you, and i actually went specifically *looking* for
something that did that, but didn't find it.

> I'd note it is used by scripts/build-perf-test-wrapper in yocto-
> autobuilder-helper, probably for exactly this reason (I've not
> checked the history).

  and that's the snippet of info i was after ... that *something*
takes advantage of that feature.  ok, i'm happy now. :-)

rday

  reply	other threads:[~2020-04-19 13:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-18 16:04 why does oe-buildenv-internal check for -z "$BDIR"? Robert P. J. Day
2020-04-18 16:30 ` [OE-core] " Richard Purdie
2020-04-18 16:43   ` Robert P. J. Day
2020-04-18 17:08     ` Chris Laplante
2020-04-18 17:23       ` Robert P. J. Day
2020-04-18 18:45         ` Peter Kjellerstedt
2020-04-18 18:55           ` Robert P. J. Day
2020-04-18 20:10           ` Robert P. J. Day
2020-04-18 22:13             ` Christopher Larson
2020-04-18 22:17               ` Robert P. J. Day
2020-04-18 23:39                 ` Richard Purdie
2020-04-19 13:11                   ` Robert P. J. Day [this message]
2020-04-18 22:19               ` Robert P. J. Day

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.LFD.2.21.2004190910470.1292842@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=chris.laplante@agilent.com \
    --cc=kergoth@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    --cc=richard.purdie@linuxfoundation.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