From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/lockdev: handle static/shared only build
Date: Wed, 7 Jan 2015 22:01:43 +0100 [thread overview]
Message-ID: <20150107220143.3565f3b1@free-electrons.com> (raw)
In-Reply-To: <1420585564-7921-1-git-send-email-romain.naour@openwide.fr>
Dear Romain Naour,
On Wed, 7 Jan 2015 00:06:03 +0100, Romain Naour wrote:
> Add a patch to install headers and static library separately.
>
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
> ---
> v2: Headers must always be installed in staging,
> remove static library installation from install_dev target (ThomasP)
Thanks, both patches applied. Can you submit upstream?
To be honest, I am wondering if it's really a good idea to patch all
package to make sure they only install shared libraries in a
BR2_SHARED_LIBS=y build. Ideally yes, but do we want to carry patches
in all packages that have a crazy build system, and are for many of
them essentially unmaintained? I don't know.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-07 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 23:06 [Buildroot] [PATCH v2 1/2] package/lockdev: handle static/shared only build Romain Naour
2015-01-06 23:06 ` [Buildroot] [PATCH v2 2/2] package/lockdev: use LOCKDEV_MAJOR to create symbolic links Romain Naour
2015-01-07 21:01 ` Thomas Petazzoni [this message]
2015-01-07 21:17 ` [Buildroot] [PATCH v2 1/2] package/lockdev: handle static/shared only build Yann E. MORIN
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=20150107220143.3565f3b1@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