From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] post-{build, images} hooks: export BUILD_DIR too
Date: Mon, 28 Oct 2013 06:17:08 +0100 [thread overview]
Message-ID: <20131028061708.5e69ab8e@skate> (raw)
In-Reply-To: <a4300dc9-2aa9-4d40-9b79-26ec5b317c52@email.android.com>
Dear Thomas De Schampheleire,
On Sun, 27 Oct 2013 22:12:34 +0100, Thomas De Schampheleire wrote:
> >+# This extra environment we can not export ourselves, so we have
> >+# to expicitly pass it to user-supplied external hooks (eg.
> >+# post-build, post-images)
> >+USER_HOOKS_EXTRA_ENV=\
> >+ BUILD_DIR=$(BUILD_DIR)
>
> I'd add a bit more info here: we cannot export BUILD_DIR globally because some packages, like uboot, also use this same variable for another purpose.
(Unfortunately, we've asked you to not wrapped patches you reply to,
but now, it has the consequence that you no longer wrap what you write.
Well, I guess with K9 it's hard to get both).
Regarding BUILD_DIR and other variables being exported, is it really
safe to export other variables with a relatively generic name such as
TARGET_DIR, BASE_DIR, HOST_DIR, BINARIES_DIR, etc. ? Should we instead
expose them to post-build/post-image scripts as BR2_<something> ? But
well, of course, it means breaking the existing API, which isn't nice.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-28 5:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 17:24 [Buildroot] [pull request v2] Pull request for branch yem/instrument-build Yann E. MORIN
2013-10-27 17:24 ` [Buildroot] [PATCH 1/4] post-{build, images} hooks: export BUILD_DIR too Yann E. MORIN
2013-10-27 17:24 ` [Buildroot] [PATCH 2/4] pkg-infra: introduce pre/post-step hooks Yann E. MORIN
2013-10-27 21:40 ` Thomas De Schampheleire
2013-10-28 14:22 ` Ryan Barnett
2013-10-29 18:43 ` Yann E. MORIN
2013-10-29 20:03 ` Thomas De Schampheleire
2013-10-29 20:56 ` Yann E. MORIN
2013-10-27 17:24 ` [Buildroot] [PATCH 3/4] pkg-infra: add hook to log timing of steps Yann E. MORIN
2013-10-27 17:24 ` [Buildroot] [PATCH 4/4] pkg-infra: add user-supplied step-hooks Yann E. MORIN
2013-10-27 21:12 ` [Buildroot] [PATCH 1/4] post-{build, images} hooks: export BUILD_DIR too Thomas De Schampheleire
2013-10-28 5:17 ` Thomas Petazzoni [this message]
2013-10-29 18:41 ` Yann E. MORIN
2013-10-29 20:08 ` Thomas De Schampheleire
2013-10-29 18:35 ` Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2013-11-10 23:51 [Buildroot] [pull request v3] Pull request for branch yem/instrument-build Yann E. MORIN
2013-11-10 23:51 ` [Buildroot] [PATCH 1/4] post-{build, images} hooks: export BUILD_DIR too Yann E. MORIN
2013-11-11 8:04 ` Thomas De Schampheleire
2013-11-11 15:03 [Buildroot] [pull request v4] Pull request for branch yem/instrument-build Yann E. MORIN
2013-11-11 15:03 ` [Buildroot] [PATCH 1/4] post-{build, images} hooks: export BUILD_DIR too Yann E. MORIN
2013-11-11 16:10 ` Thomas De Schampheleire
2013-11-11 21:40 ` Samuel Martin
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=20131028061708.5e69ab8e@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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