From: Cameron Hutchison <lists@xdna.net>
To: buildroot@busybox.net
Subject: [Buildroot] Copying extra libs into image using external toolchain
Date: Mon, 08 Feb 2010 06:34:42 -0000 [thread overview]
Message-ID: <7ad1.4b6fb082.b951f@getafix.xdna.net> (raw)
In-Reply-To: 7931.4b6fa347.59f92@getafix.xdna.net
Cameron Hutchison <lists@xdna.net> writes:
>Alternatively, I could put all the libraries
>in /lib and just forget about /usr/lib (I prefer to on embedded systems,
>but that's probably not a commonly accepted idea).
Here's a patch that does just that and nothing else. It's much smaller
and might be more useful to others:
diff --git a/toolchain/external-toolchain/ext-tool.mk b/toolchain/external-toolchain/ext-tool.mk
index 1f5aa19..e39979f 100644
--- a/toolchain/external-toolchain/ext-tool.mk
+++ b/toolchain/external-toolchain/ext-tool.mk
@@ -45,8 +45,8 @@ copy_toolchain_lib_root = \
DST="$(strip $3)"; \
STRIP="$(strip $4)"; \
\
- LIB_DIR="$${SYSROOT_DIR}/lib" ; \
- for FILE in `find $${LIB_DIR} -maxdepth 1 -name "$${LIB}.*"`; do \
+ for FILE in `find $${SYSROOT_DIR} -name "$${LIB}.*"`; do \
+ LIB_DIR=`dirname $${FILE}`; \
LIB=`basename $${FILE}`; \
while test \! -z "$${LIB}"; do \
rm -fr $(TARGET_DIR)$${DST}/$${LIB}; \
prev parent reply other threads:[~2010-02-08 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 23:07 [Buildroot] Copying extra libs into image using external toolchain Cameron Hutchison
2010-02-03 0:04 ` Grant Edwards
2010-02-03 22:13 ` Cameron Hutchison
2010-02-04 0:01 ` Lionel Landwerlin
2010-02-06 16:02 ` Thomas Petazzoni
2010-02-08 5:38 ` Cameron Hutchison
2010-02-08 6:34 ` Cameron Hutchison [this message]
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=7ad1.4b6fb082.b951f@getafix.xdna.net \
--to=lists@xdna.net \
--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