From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/8 RFC] core: install foo-config scripts early in the PATH (branch yem/foo-config-in-PATH)
Date: Mon, 21 Dec 2015 23:34:58 +0100 [thread overview]
Message-ID: <20151221233458.32befcc2@free-electrons.com> (raw)
In-Reply-To: <20151221223030.GG3454@free.fr>
Yann,
On Mon, 21 Dec 2015 23:30:30 +0100, Yann E. MORIN wrote:
> And how do we handle them today? If we don't do anything about it, then
> this series would indeed not solve those, but it would not break it
> either, since it would already be broken today.
>
> Unless we do have code to manually install them in $(HOST_DIR)/usr/bin ?
What? No, we are just installing them in $(STAGING_DIR), like all
libraries. You can look at package/rtai/rtai.mk for an example.
> > Also, this solution doesn't solve the (admittedly unlikely) case of a
> > package calling /usr/bin/<foo>-config directly.
>
> Indeed. But it is already broken today, and the series does not break it
> any more.
It is not broken today. Such special *-config scripts get naturally
installed in $(STAGING_DIR), they might be fixed up by a patch or some
custom hook. And then on the consumer side, we pass some environment
variable or other trick to get the consumer build system to use this
specific -config script rather than the one in the PATH. Nothing
special.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-21 22:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 15:56 [Buildroot] [PATCH 0/8 RFC] core: install foo-config scripts early in the PATH (branch yem/foo-config-in-PATH) Yann E. MORIN
2015-12-21 15:56 ` [Buildroot] [PATCH 1/8 RFC] core: split long line of directories Yann E. MORIN
2015-12-21 15:56 ` [Buildroot] [PATCH 2/8 RFC] core/pkg-generic: use a $(foreach) loop to fix foo-config scripts Yann E. MORIN
2015-12-21 15:56 ` [Buildroot] [PATCH 3/8 RFC] core/pkg-generic: install foo-config scripts in their own dir Yann E. MORIN
2015-12-21 18:51 ` Baruch Siach
2015-12-21 20:50 ` Yann E. MORIN
2015-12-21 15:56 ` [Buildroot] [PATCH 4/8 RFC] core: re-instate different target and host PATHs Yann E. MORIN
2015-12-21 15:56 ` [Buildroot] [PATCH 5/8 RFC] fs: use HOST_PATH Yann E. MORIN
2015-12-21 15:56 ` [Buildroot] [PATCH 6/8 RFC] packages: " Yann E. MORIN
2015-12-21 15:56 ` [Buildroot] [PATCH 7/8 RFC] packages: use TARGET_PATH Yann E. MORIN
2015-12-21 18:44 ` Baruch Siach
2015-12-21 20:46 ` Yann E. MORIN
2015-12-21 15:56 ` [Buildroot] [PATCH 8/8 RFC] package/libhid: no need for custom PATH Yann E. MORIN
2015-12-21 22:20 ` [Buildroot] [PATCH 0/8 RFC] core: install foo-config scripts early in the PATH (branch yem/foo-config-in-PATH) Thomas Petazzoni
2015-12-21 22:30 ` Yann E. MORIN
2015-12-21 22:34 ` Thomas Petazzoni [this message]
2015-12-21 22:55 ` Yann E. MORIN
2015-12-22 10:53 ` Thomas Petazzoni
2015-12-22 11:06 ` Yann E. MORIN
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=20151221233458.32befcc2@free-electrons.com \
--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