From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Creating an external toolchain [was: Re: Antw:Re: Antw: Antw:Re: libgcc build fails on Fedora15]
Date: Wed, 28 Sep 2011 08:05:20 +0200 [thread overview]
Message-ID: <201109280805.21263.arnout@mind.be> (raw)
In-Reply-To: <7290fd86f3ac9.4e80ae6d@home.nl>
On Monday 26 September 2011 16:55:09, MARCEL JANSSEN wrote:
> I just have one question which probably belongs in the faq (I may have
> missed something as well). I can't yet figure out how to build the output
> for different devices without recompiling the whole toolchain. I have
> several different images which are just a little different in the sense
> that they all have the same kernel but some different packages. It would
> be great if I could just switch between configs and don't have to
> recompile the whole toolchain again or even shared packages between those
> configs.
Buildroot supports an external toolchain, but it isn't easy to create one.
The easiest is to use a crosstool-NG toolchain: build it, install it in some
central place, and use it as an external toolchain from buildroot.
It would be nice if buildroot also supported creation of an external
toolchain (based on an internal toolchain config). The toolchain is currently
built in output/host/usr/... and is not relocatable, so it's difficult to
share it between different buildroot builds.
Regards,
ARnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 31BB CF53 8660 6F88 345D 54CC A836 5879 20D7 CF43
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110928/7a66a3c7/attachment-0001.html>
next prev parent reply other threads:[~2011-09-28 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 14:55 [Buildroot] Antw:Re: Antw: Antw:Re: libgcc build fails on Fedora15 MARCEL JANSSEN
2011-09-27 21:44 ` Thomas Petazzoni
2011-09-28 6:05 ` Arnout Vandecappelle [this message]
2011-09-28 10:19 ` [Buildroot] Creating an external toolchain [was: Re: Antw:Re: Antw: Antw:Re: libgcc build fails on Fedora15] Thomas De Schampheleire
2011-09-28 18:30 ` Steve Calfee
2011-09-28 18:43 ` Thomas De Schampheleire
2011-09-28 21:02 ` Michael S. Zick
2011-09-28 21:21 ` Bryan Hundven
2011-09-28 18:48 ` Grant Edwards
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=201109280805.21263.arnout@mind.be \
--to=arnout@mind.be \
--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