From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Christopher Larson <kergoth@gmail.com>
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
"chris.laplante@agilent.com" <chris.laplante@agilent.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
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 18:19:38 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.2004181818270.571354@localhost.localdomain> (raw)
In-Reply-To: <d1b1bb06-3222-4073-831d-7f25e2566ed5@Spark>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
On Sat, 18 Apr 2020, Christopher Larson wrote:
> I don’t think this is out of date. It’s allowing the user to specify
> the path to bitbake (which I’ve done in unusual layouts or just to
> be explicit), falling back to either under OEROOT (poky-style) or in
> its parent (more typical).
>
> It’s also worth noting that oe-init-build-env and
> oe-buildenv-internal are not just used directly, but many other
> setup scripts build on top of them, so this particular flexibility
> is useful. BDIR still seems like it can be dropped regardless of the
> BITBAKEDIR logic.
so if BBEXTRA is still valid, should it be documented, perhaps in
the variable glossary?
rday
prev parent reply other threads:[~2020-04-18 22:19 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
2020-04-18 22:19 ` 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.LFD.2.21.2004181818270.571354@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