From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC 1/2] toolchain: copy_toolchain_lib_root: rename LIBSPATH to LIBPATHS
Date: Wed, 3 Feb 2016 23:46:11 +0100 [thread overview]
Message-ID: <20160203234611.5108bfcd@free-electrons.com> (raw)
In-Reply-To: <1454535929-25379-2-git-send-email-patrickdepinguin@gmail.com>
Dear Thomas De Schampheleire,
On Wed, 3 Feb 2016 22:45:28 +0100, Thomas De Schampheleire wrote:
> From: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
>
> LIBSPATH is populated based on a find with a pattern that can look like:
> libfoo*.so
> and thus the output of the find will contain all file paths that match this
> pattern.
>
> Unfortunately, the name LIBSPATH suggests that only one entry is returned,
> rather than possibly multiple.
>
> As this code is quite complex, use the more accurate name LIBPATHS iso
> LIBSPATH.
>
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
> ---
> toolchain/helpers.mk | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-03 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 21:45 [Buildroot] [PATCH RFC 0/2] unify library locations in target/staging Thomas De Schampheleire
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 [this message]
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=20160203234611.5108bfcd@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