From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/6] Makefile: export PATH
Date: Sun, 17 Nov 2013 08:33:40 +0100 [thread overview]
Message-ID: <87mwl3zdm3.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20131115205317.GG3337@free.fr> (Yann E. MORIN's message of "Fri, 15 Nov 2013 21:53:17 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
>> To me, this could make easier writing post-{build,image} scripts.
> Indeed, it *is* usefull for those scripts.
> The first thing I do in br.config is to exactly set PATH to include the
> host/usr/bin and host/usr/sbin directories in front of the user's PATH.
> But maybe we should just set PATH at the time we call them?
I *THINK* always adding those host directories to the path would be
safe, as long as it happens after 'which' calls in the toplevel
makefile. This would also allow us to get rid of HOST_PATH / TARGET_PATH
(which are currently not identical, but should be).
But it will need some testing.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-11-17 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 20:59 [Buildroot] [PATCH 0/6] PATH cleanup Samuel Martin
2013-11-11 20:59 ` [Buildroot] [PATCH 1/6] Makefile: introduce BR2_PATH Samuel Martin
2013-11-11 20:59 ` [Buildroot] [PATCH 2/6] Makefile: add $(HOST_DIR)/sbin to BR2_PATH Samuel Martin
2013-11-11 20:59 ` [Buildroot] [PATCH 3/6] *.mk: replace (TARGET|HOST)_PATH by BR2_PATH Samuel Martin
2013-11-11 20:59 ` [Buildroot] [PATCH 4/6] infra: remove unused {TARGET, HOST}_PATH definition Samuel Martin
2013-11-11 20:59 ` [Buildroot] [PATCH 5/6] pkg-cmake.mk, pkg-autotools.mk: add PATH in the configure command environment Samuel Martin
2013-11-11 22:30 ` Thomas Petazzoni
2013-11-11 20:59 ` [Buildroot] [PATCH 6/6] Makefile: export PATH Samuel Martin
2013-11-11 22:31 ` Thomas Petazzoni
2013-11-15 20:37 ` Samuel Martin
2013-11-15 20:53 ` Yann E. MORIN
2013-11-17 7:33 ` Peter Korsgaard [this message]
2014-01-02 19:21 ` 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=87mwl3zdm3.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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