From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v11 1/2] package/btrfs-progs: install to staging directory
Date: Wed, 27 Jul 2016 23:38:04 +0200 [thread overview]
Message-ID: <20160727233804.241fee0e@free-electrons.com> (raw)
In-Reply-To: <1469394628-19412-1-git-send-email-christian@paral.in>
Hello,
On Sun, 24 Jul 2016 14:10:27 -0700, Christian Stewart wrote:
> Other packages when building against btrfs-progs require headers in the
> staging directory under /usr/include/btrfs. This patch enables
> installing btrfs-progs to the staging directory to enable other packages
> to build against the btrfs-progs headers.
>
> Signed-off-by: Christian Stewart <christian@paral.in>
> ---
> package/btrfs-progs/btrfs-progs.mk | 1 +
> 1 file changed, 1 insertion(+)
I've applied after fixing the BR2_STATIC_LIBS=y case, by:
1/ Adding a BTRFS_PROGS_INSTALL_STAGING_OPTS variable
2/ Adding a patch that installs the static lib and the headers during
"make install-static".
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-07-27 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 21:10 [Buildroot] [PATCH v11 1/2] package/btrfs-progs: install to staging directory Christian Stewart
2016-07-24 21:10 ` [Buildroot] [PATCH v11 2/2] docker-engine: new package Christian Stewart
2016-07-24 21:25 ` Christian Stewart
2016-07-27 21:40 ` Thomas Petazzoni
2016-07-27 22:12 ` Christian Stewart
2016-07-28 1:57 ` Khem Raj
2016-07-28 6:29 ` Thomas Petazzoni
2016-07-24 21:48 ` [Buildroot] [PATCH v11 1/2] package/btrfs-progs: install to staging directory Thomas Petazzoni
2016-07-24 23:35 ` Christian Stewart
2016-07-25 7:47 ` Thomas Petazzoni
2016-07-27 21:38 ` 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=20160727233804.241fee0e@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