Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Issue for the integration of Codesourcery external toolchains
Date: Tue, 12 Jan 2010 15:25:44 +0200	[thread overview]
Message-ID: <20100112132543.GC8097@jasper.tkos.co.il> (raw)
In-Reply-To: <4d28d4b51001120456o1e9a6a8fs94b88ed4c4a30b94@mail.gmail.com>

Hi Lionel,

On Tue, Jan 12, 2010 at 01:56:03PM +0100, Lionel Landwerlin wrote:
> On Tue, Jan 12, 2010 at 1:48 PM, Baruch Siach <baruch@tkos.co.il> wrote:
> > On Tue, Jan 12, 2010 at 11:54:41AM +0100, Thomas Petazzoni wrote:
> > > On Wed, 6 Jan 2010 08:59:53 +0200
> > > Baruch Siach <baruch@tkos.co.il> wrote:
> > >
> > > > >  * Build a more normal sysroot in $(STAGING_DIR) by combining the
> > > > >    contents of armv4t and the header files. But this would require
> > > > >    telling gcc that the libraries aren't in armv4t anymore. This is
> > > > >    probably possible using a custom spec file, but is quite
> > > > >    complicated.
> > > >
> > > > How about generating symlinks in the staging directory:
> > > >
> > > > armv4t/usr/include -> ../../usr/include
> > > > thumb2/usr/include -> ../../usr/include
> > > >
> > > > and then using the output of -print-sysroot for each target?
> > >
> > > Because everything in Buildroot assumes that the libraries and headers
> > > must be installed in $(STAGING_DIR)/usr/include and
> > > $(STAGING_DIR)/usr/lib, not in $(STAGING_DIR)/armv4/usr/include and
> > > $(STAGING_DIR)/armv4/usr/lib.
> >
> > I'll clarify. I suggest the following steps:
> >
> > 1. Copy the entire CodeSourcery sysroot (as reported by -print-sysroot)
> > into
> >   $(STAGING_DIR).
> >
> > 2. Create the following symlinks:
> >
> >    $(STAGING_DIR)/armv4t/usr/include -> ../../usr/include
> >    $(STAGING_DIR)/thumb2/usr/include -> ../../usr/include
> >
> 
> Or just
>        $(STAGING_DIR)/armv4t/ -> $(STAGING_DIR)
> 
> ;)

Probably not. The $(STAGING_DIR)/armv4t directory is a real one containing the 
ARMv4T version of the standard shared libraries in $(STAGING_DIR)/armv4t/lib 
and $(STAGING_DIR)/armv4t/usr/lib.

baruch

> >
> > 3. Set as necessary:
> >
> >    STAGING_DIR=$(STAGING_DIR)/armv4t
> >
> >    or
> >
> >    STAGING_DIR=$(STAGING_DIR)/thumb2
> >
> > Buildroot then sees libraries and headers in $(STAGING_DIR)/usr/lib and
> > $(STAGING_DIR)/usr/include respectively, as expected.
> >
> > baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      reply	other threads:[~2010-01-12 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04 15:24 [Buildroot] Issue for the integration of Codesourcery external toolchains Thomas Petazzoni
2010-01-04 23:23 ` Lionel Landwerlin
2010-01-12 10:52   ` Thomas Petazzoni
2010-01-12 22:09     ` Yann E. MORIN
2010-01-12 23:39       ` Thomas Petazzoni
2010-01-12 23:40     ` Lionel Landwerlin
2010-01-06  6:59 ` Baruch Siach
2010-01-12 10:54   ` Thomas Petazzoni
2010-01-12 12:48     ` Baruch Siach
2010-01-12 12:56       ` Lionel Landwerlin
2010-01-12 13:25         ` Baruch Siach [this message]

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=20100112132543.GC8097@jasper.tkos.co.il \
    --to=baruch@tkos.co.il \
    --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