From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 3 v2] qt5: support buildroot being located in /usr
Date: Sat, 21 Jun 2014 18:59:09 +0200 [thread overview]
Message-ID: <20140621185909.22016e05@free-electrons.com> (raw)
In-Reply-To: <53A4C052.1050105@mind.be>
Dear Arnout Vandecappelle,
On Sat, 21 Jun 2014 01:14:26 +0200, Arnout Vandecappelle wrote:
> Now that I see the two patches next to each other: why is this hook needed?
> It's already done by the generic staging-install target, no? ThomasP carries the
> blame for this, so putting him in Cc...
I don't think I should be blamed for this actually :-)
The generic staging-install fixup of .la files is only part of
the autotools-package infrastructure, because it's related to libtool,
which is normally used in combination with the rest of the autotools.
However, qt5* packages are all generic-packages, so the "generic"
staging-install fixup of .la files doesn't apply for these packages.
That being said, we could certainly make the .la fixup logic a common
macro, which could be used by both the autotools-package
infrastructure, and some other packages as well.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-06-21 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 19:11 [Buildroot] [PATCH 0 of 3 v2] Support buildroot being located in /usr Thomas De Schampheleire
2014-06-20 19:11 ` [Buildroot] [PATCH 1 of 3 v2] infra: support " Thomas De Schampheleire
2014-06-20 23:09 ` Arnout Vandecappelle
2014-06-21 9:04 ` Thomas De Schampheleire
2014-06-20 19:11 ` [Buildroot] [PATCH 2 of 3 v2] qt5: " Thomas De Schampheleire
2014-06-20 23:14 ` Arnout Vandecappelle
2014-06-21 16:59 ` Thomas Petazzoni [this message]
2014-06-20 19:11 ` [Buildroot] [PATCH 3 of 3 v2] pkgconf: don't double prefix lib/include paths with sysroot Thomas De Schampheleire
2014-06-20 23:16 ` Arnout Vandecappelle
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=20140621185909.22016e05@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.