Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] --includedir=/usr/include vs	--includedir=(STAGING_DIR)/usr/include
Date: Mon, 30 Jul 2007 21:36:08 +0200	[thread overview]
Message-ID: <20070730193608.GB27993@aon.at> (raw)
In-Reply-To: <0707302103451.17391@somehost>

On Mon, Jul 30, 2007 at 09:06:34PM +0200, Cristian Ionescu-Idbohrn wrote:
>On Mon, 30 Jul 2007, Steven J. Hill wrote:
>
>> > 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'?
>
>That's fine with me. But my question was:
>
>  --includedir=/usr/include vs --includedir=$(STAGING_DIR)/usr/include
>                                            ^^^^^^^^^^^^^^

depending on the package --prefix=$(STAGING_DIR)/usr
is enough and all other (except, perhaps specifying the location of
$(STAGING_DIR)/etc) are not needed anymore.

There are indeed quite some packages that are not yet converted. Patches
to clean those up are very welcome.

  reply	other threads:[~2007-07-30 19:36 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
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 [this message]
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=20070730193608.GB27993@aon.at \
    --to=rep.dot.nop@gmail.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