From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5] toolchain-external: unify LIB_EXTERNAL_LIBS and USR_LIB_EXTERNAL_LIBS
Date: Sun, 27 Mar 2016 22:36:34 +0200 [thread overview]
Message-ID: <56F84452.7070009@mind.be> (raw)
In-Reply-To: <1455304826-10557-6-git-send-email-patrickdepinguin@gmail.com>
On 02/12/16 20:20, Thomas De Schampheleire wrote:
> From: Thomas De Schampheleire<thomas.de.schampheleire@gmail.com>
>
> With the alignment of toolchain library location in target and staging,
> there is no need anymore for the distinction between LIB_EXTERNAL_LIBS and
> USR_LIB_EXTERNAL_LIBS. Unify them into TOOLCHAIN_EXTERNAL_LIBS.
>
> Related, update the help text of
> BR2_TOOLCHAIN_EXTRA_TOOLCHAIN_EXTERNAL_LIBS.
>
> Signed-off-by: Thomas De Schampheleire<thomas.de.schampheleire@gmail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
> ---
> toolchain/toolchain-external/Config.in | 3 +--
> toolchain/toolchain-external/toolchain-external.mk | 22 +++++++++++-----------
> 2 files changed, 12 insertions(+), 13 deletions(-)
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-03-27 20:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 19:20 [Buildroot] [PATCH 0/5] Align library locations in target and staging Thomas De Schampheleire
2016-02-12 19:20 ` [Buildroot] [PATCH 1/5] toolchain-external: blackfin: install FDPIC libraries also to staging Thomas De Schampheleire
2016-03-22 21:48 ` Romain Naour
2016-03-27 16:20 ` Arnout Vandecappelle
2016-04-25 21:00 ` Thomas Petazzoni
2016-02-12 19:20 ` [Buildroot] [PATCH 2/5] toolchain-external: remove unused calculation of ARCH_SUBDIR Thomas De Schampheleire
2016-03-22 21:53 ` Romain Naour
2016-03-27 20:34 ` Arnout Vandecappelle
2016-03-27 23:10 ` Arnout Vandecappelle
2016-04-21 21:30 ` Thomas Petazzoni
2016-02-12 19:20 ` [Buildroot] [PATCH 3/5] toolchain-external: extract installation of gdbserver to separate define Thomas De Schampheleire
2016-03-22 22:04 ` Romain Naour
2016-03-27 16:43 ` Arnout Vandecappelle
2016-04-25 21:02 ` Thomas Petazzoni
2016-02-12 19:20 ` [Buildroot] [PATCH 4/5] toolchain-external: align library locations in target and staging dir Thomas De Schampheleire
2016-03-22 22:53 ` Romain Naour
2016-03-27 20:34 ` Arnout Vandecappelle
2016-04-25 21:15 ` Thomas Petazzoni
2016-04-26 11:32 ` Thomas De Schampheleire
2016-04-25 21:08 ` Thomas Petazzoni
2016-02-12 19:20 ` [Buildroot] [PATCH 5/5] toolchain-external: unify LIB_EXTERNAL_LIBS and USR_LIB_EXTERNAL_LIBS Thomas De Schampheleire
2016-03-22 22:58 ` Romain Naour
2016-03-27 20:36 ` Arnout Vandecappelle [this message]
2016-04-25 21:16 ` Thomas Petazzoni
2016-03-10 8:02 ` [Buildroot] [PATCH 0/5] Align library locations in target and staging Thomas De Schampheleire
2016-03-27 20:39 ` Arnout Vandecappelle
2016-03-27 20:52 ` Romain Naour
2016-03-27 23:08 ` Arnout Vandecappelle
2016-03-29 14:21 ` Thomas De Schampheleire
2016-03-29 14:33 ` Arnout Vandecappelle
2016-04-25 21:17 ` Thomas Petazzoni
2016-04-26 7:50 ` Thomas De Schampheleire
2016-04-26 8:28 ` 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=56F84452.7070009@mind.be \
--to=arnout@mind.be \
--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