From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] [PATCH 0/5] Buildroot cleanup
Date: Wed, 9 Sep 2009 08:26:20 +0200 [thread overview]
Message-ID: <20090909082620.12a60a18@surf> (raw)
In-Reply-To: <4AA77AA40200007000017857@gwia.alliedtelesyn.co.nz>
Le Wed, 09 Sep 2009 09:51:32 +1200,
"angus salkeld" <angus.salkeld@alliedtelesis.co.nz> a ?crit :
> Well you could treat crosstool-ng as just another package that is
> available to build.
> So if you select crosstool-ng, buildroot automatically sets up the
> correct external toolchain options.
That's my long term plan. Introduce a new toolchain type in Buildroot:
Crosstool-NG toolchain. Just like for uClibc today, Buildroot would
produce/tune the Crosstool-NG configuration before running the
Crosstool-NG compilation process. We could have this in parallel to the
internal building system for toolchains for a while, and then when
we're satisfied, switch to Crosstool-NG completely by removing the old
mechanism.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-09-09 6:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AA775760200006C0000A21D@gwia.alliedtelesyn.co.nz>
2009-09-08 21:51 ` [Buildroot] [RFC] [PATCH 0/5] Buildroot cleanup angus salkeld
2009-09-09 6:26 ` Thomas Petazzoni [this message]
2009-09-09 7:03 ` Peter Korsgaard
[not found] <4AA62DD20200000D00128C56@gwia.alliedtelesyn.co.nz>
2009-09-08 19:54 ` angus salkeld
2009-09-08 20:15 ` Sven Neumann
2009-09-08 21:27 ` Peter Korsgaard
2009-09-09 6:24 ` Thomas Petazzoni
2009-09-09 7:06 ` Peter Korsgaard
2009-09-09 6:32 ` Thomas Petazzoni
2009-09-07 22:09 Thomas Petazzoni
2009-09-08 17:03 ` Will Newton
2009-09-08 19:13 ` Jonathan dumaresq
2009-09-08 21:20 ` Peter Korsgaard
2009-09-09 9:36 ` Will Newton
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=20090909082620.12a60a18@surf \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.