From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] slang.mk (was: something (slang?) creates buildroot/build_i486/staging_dir/include)
Date: Sun, 29 Jul 2007 19:09:43 +0200 [thread overview]
Message-ID: <00f501c7d26c$00029a60$dcc4af0a@atmel.com> (raw)
In-Reply-To: 0707291107480.8510@somehost
>
> I do not know much about the buildroot backyard, but I read some
> discussions about the include-dir being $(STAGING_DIR)/usr/include/
> and not $(STAGING_DIR)/include/. Wouldn't it be a good idea to make that a
> variable somewhere in the top makefiles, something like:
>
> STAGING_INCLUDE_DIR = $(STAGING_DIR)/usr/include/
>
Some stuff is normally installed in $(STAGING_DIR)/usr/include/ and
others in $(STAGING_DIR)/include/, so I do not think it will work
> and change all .mk files to use that instead? That should give one point
> of control on where the header files are installed and avoid errors and
> confusion.
>
Best Regards
Ulf Samuelsson ulf at atmel.com
Atmel Nordic AB
Mail: Box 2033, 174 02 Sundbyberg, Sweden
Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
GSM +46 (706) 22 44 57
Technical support when I am not available:
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
AVR32 Applications Group mailto:avr32 at atmel.com
http://www.avrfreaks.net/; http://avr32linux.org/
http://www.at91.com/ ; ftp://at91dist:distrib at 81.80.104.162/
next prev parent reply other threads:[~2007-07-29 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 23:08 [Buildroot] something (slang?) creates buildroot/build_i486/staging_dir/include Cristian Ionescu-Idbohrn
2007-07-28 23:25 ` Cristian Ionescu-Idbohrn
2007-07-29 9:38 ` [Buildroot] [patch] slang.mk (was: something (slang?) creates buildroot/build_i486/staging_dir/include) Cristian Ionescu-Idbohrn
2007-07-29 17:09 ` Ulf Samuelsson [this message]
2007-07-30 10:02 ` 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='00f501c7d26c$00029a60$dcc4af0a@atmel.com' \
--to=ulf@atmel.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