From: Steven J. Hill <sjhill@realitydiluted.com>
To: buildroot@busybox.net
Subject: [Buildroot] --includedir=/usr/include vs --includedir=$(STAGING_DIR)/usr/include
Date: Mon, 30 Jul 2007 14:02:32 -0500 [thread overview]
Message-ID: <20070730190231.GA5834@real.realitydiluted.com> (raw)
In-Reply-To: <0707302043450.17391@somehost>
> Noticed that some .mk files use different --includedir= configure options.
> Shouldn't --includedir=/usr/include be used everywhere?
>
With the recent changes that buildroot has undergone, I actually think
this is a good idea. Any objections to getting rid of 'include' in the
staging directory all together and going to 'usr/include'?
-Steve
next prev parent reply other threads:[~2007-07-30 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 18:49 [Buildroot] --includedir=/usr/include vs --includedir=$(STAGING_DIR)/usr/include Cristian Ionescu-Idbohrn
2007-07-30 19:02 ` Steven J. Hill [this message]
2007-07-30 19:06 ` [Buildroot] --includedir=/usr/include vs --includedir=(STAGING_DIR)/usr/include Cristian Ionescu-Idbohrn
2007-07-30 19:36 ` Bernhard Fischer
2007-07-30 19:52 ` Cristian Ionescu-Idbohrn
2007-07-30 20:11 ` Bernhard Fischer
2007-07-31 8:40 ` Cristian Ionescu-Idbohrn
2007-07-31 9:45 ` Bernhard Fischer
2007-07-31 6:13 ` Hans-Christian Egtvedt
2007-07-31 8:43 ` Bernhard Fischer
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=20070730190231.GA5834@real.realitydiluted.com \
--to=sjhill@realitydiluted.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