From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2 v2] pkg-infra: munging .la files is not limited to autotools packages
Date: Sun, 19 Jul 2015 11:53:52 +0200 [thread overview]
Message-ID: <20150719115352.7d513f34@free-electrons.com> (raw)
In-Reply-To: <2498f2352f5b65d77d91f6405d39e6349de640dc.1430687963.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sun, 3 May 2015 23:30:39 +0200, Yann E. MORIN wrote:
> Currently, we're only fixing libtool's .la files for autotools packages,
> and even more so, only for those that do not define their own
> _INSTALL_STAGING_CMDS.
>
> However, .la files might also be installed by non-autotools packages,
> like the NVidia GPU binary blob (libGL.la).
>
> So, move that code into the global build rule, so all packages get their
> .la files fixed, whether they be autotools packages or not, and whether
> they define their own _INSTALL_STAGING_CMDS or not.
>
> Also print a message.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> ---
> package/pkg-autotools.mk | 27 ---------------------------
> package/pkg-generic.mk | 30 ++++++++++++++++++++++++++++++
> 2 files changed, 30 insertions(+), 27 deletions(-)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-19 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 21:30 [Buildroot] [PATCH 0/2 v2] pkg-infra: better fix libtool files wrt. /usr (branch yem/libtool) Yann E. MORIN
2015-05-03 21:30 ` [Buildroot] [PATCH 1/2 v2] autotools-package: also handle pre-installed external toolchain in .la fixup Yann E. MORIN
2015-05-04 13:35 ` Peter Korsgaard
2015-05-03 21:30 ` [Buildroot] [PATCH 2/2 v2] pkg-infra: munging .la files is not limited to autotools packages Yann E. MORIN
2015-07-19 9:53 ` Thomas Petazzoni [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=20150719115352.7d513f34@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