From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] why does oe-buildenv-internal check for -z "$BDIR"?
Date: Sat, 18 Apr 2020 17:30:58 +0100 [thread overview]
Message-ID: <e610ad1ecb7cd084ab61fe4bcf56b01568c5edc7.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LFD.2.21.2004181159130.1300328@localhost.localdomain>
On Sat, 2020-04-18 at 12:04 -0400, Robert P. J. Day wrote:
> perusing the OE init scripts, and noticed this in
> oe-buildenv-internal, line 42:
>
> if [ -z "$BDIR" ]; then
> if [ -z "$1" ]; then
> BDIR="build"
> else
> BDIR="$1"
> ... snip ...
>
> i'm curious ... under what circumstances would BDIR *not* be unset
> (or not be the empty string) at that point? i'm just puzzled as to a
> possible flow of control that gets to that point where BDIR has a
> non-empty value, since i've never seen any mention in the docs about
> such a possibility.
>
> doesn't hurt, of course, just not sure what that test is trying to
> accomplish.
You can do:
$ source oe-init-build-env build2
and if your shell supports it, build becomes build2?
Cheers,
Richard
next prev parent reply other threads:[~2020-04-18 16:31 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 ` Richard Purdie [this message]
2020-04-18 16:43 ` [OE-core] " 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
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=e610ad1ecb7cd084ab61fe4bcf56b01568c5edc7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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