From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] skeleton: create include/ directory
Date: Mon, 14 May 2018 08:03:15 +0200 [thread overview]
Message-ID: <20180514080315.049085b2@windsurf.home> (raw)
In-Reply-To: <9873d2e0023b87545478d0615eb5d97bcbd82c2c.1526268236.git.baruch@tkos.co.il>
Hello,
On Mon, 14 May 2018 06:23:56 +0300, Baruch Siach wrote:
> Don't rely on a random host package to create the include/ directory for
> us. Some packages do the wrong thing since they implicitly assume that
> this directory exists already. Commit a557aedad2 (zstd: fix host headers
> installation) shows an example of that.
>
> Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> Cc: Yann E. MORIN <yann.morin.1998@free.fr>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> package/skeleton/skeleton.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/skeleton/skeleton.mk b/package/skeleton/skeleton.mk
> index efcf420d7243..9d97f02f08bf 100644
> --- a/package/skeleton/skeleton.mk
> +++ b/package/skeleton/skeleton.mk
> @@ -16,6 +16,7 @@ SKELETON_ADD_SKELETON_DEPENDENCY = NO
> define HOST_SKELETON_INSTALL_CMDS
> $(Q)ln -snf . $(HOST_DIR)/usr
> $(Q)mkdir -p $(HOST_DIR)/lib
> + $(Q)mkdir -p $(HOST_DIR)/include
Following the zstd patch, I was discussing this with Yann on IRC, and
my thinking is that we normally shouldn't have to do something like
this. Packages that install stuff in ${prefix}/include should create
this folder as needed.
Now, it is true that we already create $(STAGING_DIR)/include, and it
doesn't cost much to create such a directory ahead of time.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-14 6:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 3:23 [Buildroot] [PATCH] skeleton: create include/ directory Baruch Siach
2018-05-14 6:03 ` Thomas Petazzoni [this message]
2018-05-15 21:39 ` Arnout Vandecappelle
2018-05-19 20:43 ` Thomas Petazzoni
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=20180514080315.049085b2@windsurf.home \
--to=thomas.petazzoni@bootlin.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