From: Richard Braun <rbraun@sceen.net>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchains and sysroot
Date: Fri, 19 Oct 2012 12:02:13 +0200 [thread overview]
Message-ID: <20121019100213.GA7355@mail.sceen.net> (raw)
In-Reply-To: <20121019095730.GA6397@mail.sceen.net>
On Fri, Oct 19, 2012 at 11:57:30AM +0200, Richard Braun wrote:
> On Fri, Oct 19, 2012 at 11:46:10AM +0200, Jean-Mickael Guerin wrote:
> > I would expect the wrapper the use -I and -L to help the lookup of
> > headers and libraries installed afterwards. Why --sysroot?
>
> -I and -L extend the default list of search directories whereas
> --sysroot replaces them. This completely avoids using native libraries
> by mistake.
I might have answered a bit fast. I suppose what you have in mind is let
the toolchain use its own sysroot, defined at compile time (when the
toolchain was built) and then extend it with -I and -L. The problem with
this is that it would force everyone to use the very same path for one
toolchain, which can be tedious for external toolchains (you might have
several with the same built-in sysroot).
--
Richard Braun
next prev parent reply other threads:[~2012-10-19 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 9:10 [Buildroot] external toolchains and sysroot Jean-Mickael Guerin
2012-10-19 9:38 ` Richard Braun
2012-10-19 9:46 ` Jean-Mickael Guerin
2012-10-19 9:57 ` Richard Braun
2012-10-19 10:02 ` Richard Braun [this message]
2012-10-19 11:06 ` Jean-Mickael Guerin
2012-10-19 11:26 ` Richard Braun
2012-10-21 9:41 ` Thomas Petazzoni
2012-10-23 6:45 ` Jean-Mickael Guerin
2012-10-23 7:28 ` Thomas Petazzoni
2012-10-23 8:46 ` Arnout Vandecappelle
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=20121019100213.GA7355@mail.sceen.net \
--to=rbraun@sceen.net \
--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