From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC 0/2] unify library locations in target/staging
Date: Wed, 3 Feb 2016 22:45:27 +0100 [thread overview]
Message-ID: <1454535929-25379-1-git-send-email-patrickdepinguin@gmail.com> (raw)
From: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
See second patch for full details, first patch is just a minor correction
in variable naming.
This is code has been tested for various toolchains, BUT is not yet correct
for Blackfin toolchains when FDPIC_SHARED is selected (hence: DO NOT APPLY)
For this family there is some specific code that needs to be fixed.
Another improvement is the simplification of the copy_toolchain_lib_root
arguments: only the LIB argument is used now.
Finally, a follow-up patch is expected to unify the variables LIB_EXTERNAL_LIBS
and USR_LIB_EXTERNAL_LIBS, as there is no need for the distinction anymore.
/Thomas
Thomas De Schampheleire (2):
toolchain: copy_toolchain_lib_root: rename LIBSPATH to LIBPATHS
toolchain-external: unify library locations in target and staging dir
toolchain/helpers.mk | 18 ++++--------------
toolchain/toolchain-external/toolchain-external.mk | 14 ++++----------
2 files changed, 8 insertions(+), 24 deletions(-)
--
2.4.10
next reply other threads:[~2016-02-03 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 21:45 Thomas De Schampheleire [this message]
2016-02-03 21:45 ` [Buildroot] [PATCH RFC 1/2] toolchain: copy_toolchain_lib_root: rename LIBSPATH to LIBPATHS Thomas De Schampheleire
2016-02-03 22:46 ` Thomas Petazzoni
2016-02-03 21:45 ` [Buildroot] [PATCH RFC 2/2] toolchain-external: unify library locations in target and staging dir Thomas De Schampheleire
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=1454535929-25379-1-git-send-email-patrickdepinguin@gmail.com \
--to=patrickdepinguin@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