From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/6] PATH cleanup
Date: Sat, 18 Jan 2014 20:41:39 +0100 [thread overview]
Message-ID: <1390074102-15686-1-git-send-email-s.martin49@gmail.com> (raw)
All,
Here is the 2nd round of the PATH cleanup series.
Not that much to say about this new round (the changes are mostly due to
the rebasing onto master).
Note that I've re-posted the following patches because they are unchanged
and still apply properly on master:
* patch 1/6: http://patchwork.ozlabs.org/patch/290493/
* patch 2/6: http://patchwork.ozlabs.org/patch/290494/
* patch 4/6: http://patchwork.ozlabs.org/patch/290495/
Yours,
Samuel
Samuel Martin (6):
Makefile: introduce BR2_PATH
Makefile: add $(HOST_DIR)/sbin to BR2_PATH
*.mk: replace (TARGET|HOST)_PATH by BR2_PATH
infra: remove unused {TARGET,HOST}_PATH definition
pkg-cmake.mk: add PATH in the configure command environment
Makefile: export PATH
Makefile | 4 ++++
fs/ext2/ext2.mk | 2 +-
package/Makefile.in | 12 ++++--------
package/bustle/bustle.mk | 2 +-
package/libhid/libhid.mk | 2 +-
package/pkg-cmake.mk | 2 ++
package/pkg-python.mk | 8 ++++----
package/sdl/sdl.mk | 2 +-
8 files changed, 18 insertions(+), 16 deletions(-)
--
1.8.5.3
next reply other threads:[~2014-01-18 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 19:41 Samuel Martin [this message]
2014-01-18 19:41 ` [Buildroot] [PATCH v2 3/6] *.mk: replace (TARGET|HOST)_PATH by BR2_PATH Samuel Martin
2014-01-27 20:35 ` Thomas Petazzoni
2014-01-18 19:41 ` [Buildroot] [PATCH v2 5/6] pkg-cmake.mk: add PATH in the configure command environment Samuel Martin
2014-01-18 19:41 ` [Buildroot] [PATCH v2 6/6] Makefile: export PATH Samuel Martin
2014-01-27 20:34 ` [Buildroot] [PATCH v2 0/6] PATH cleanup Thomas Petazzoni
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=1390074102-15686-1-git-send-email-s.martin49@gmail.com \
--to=s.martin49@gmail.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