<br><br><div class="gmail_quote">On Tue, Jan 12, 2010 at 1:48 PM, Baruch Siach <span dir="ltr"><<a href="mailto:baruch@tkos.co.il">baruch@tkos.co.il</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Thomas,<br>
<div class="im"><br>
On Tue, Jan 12, 2010 at 11:54:41AM +0100, Thomas Petazzoni wrote:<br>
> On Wed, 6 Jan 2010 08:59:53 +0200<br>
> Baruch Siach <<a href="mailto:baruch@tkos.co.il">baruch@tkos.co.il</a>> wrote:<br>
><br>
> > > * Build a more normal sysroot in $(STAGING_DIR) by combining the<br>
> > > contents of armv4t and the header files. But this would require<br>
> > > telling gcc that the libraries aren't in armv4t anymore. This is<br>
> > > probably possible using a custom spec file, but is quite<br>
> > > complicated.<br>
> ><br>
> > How about generating symlinks in the staging directory:<br>
> ><br>
> > armv4t/usr/include -> ../../usr/include<br>
> > thumb2/usr/include -> ../../usr/include<br>
> ><br>
> > and then using the output of -print-sysroot for each target?<br>
><br>
> Because everything in Buildroot assumes that the libraries and headers<br>
> must be installed in $(STAGING_DIR)/usr/include and<br>
> $(STAGING_DIR)/usr/lib, not in $(STAGING_DIR)/armv4/usr/include and<br>
> $(STAGING_DIR)/armv4/usr/lib.<br>
<br>
</div>I'll clarify. I suggest the following steps:<br>
<br>
1. Copy the entire CodeSourcery sysroot (as reported by -print-sysroot) into<br>
$(STAGING_DIR).<br>
<br>
2. Create the following symlinks:<br>
<br>
$(STAGING_DIR)/armv4t/usr/include -> ../../usr/include<br>
$(STAGING_DIR)/thumb2/usr/include -> ../../usr/include<br></blockquote><div><br>Or just<br> $(STAGING_DIR)/armv4t/ -> $(STAGING_DIR)<br><br>;)<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
3. Set as necessary:<br>
<br>
STAGING_DIR=$(STAGING_DIR)/armv4t<br>
<br>
or<br>
<br>
STAGING_DIR=$(STAGING_DIR)/thumb2<br>
<br>
Buildroot then sees libraries and headers in $(STAGING_DIR)/usr/lib and<br>
$(STAGING_DIR)/usr/include respectively, as expected.<br>
<div class="im"><br>
baruch<br>
<br>
--<br>
~. .~ Tk Open Systems<br>
=}------------------------------------------------ooO--U--Ooo------------{=<br>
- <a href="mailto:baruch@tkos.co.il">baruch@tkos.co.il</a> - tel: +972.2.679.5364, <a href="http://www.tkos.co.il" target="_blank">http://www.tkos.co.il</a> -<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">buildroot mailing list<br>
<a href="mailto:buildroot@busybox.net">buildroot@busybox.net</a><br>
<a href="http://lists.busybox.net/mailman/listinfo/buildroot" target="_blank">http://lists.busybox.net/mailman/listinfo/buildroot</a><br>
</div></div></blockquote></div><br>