From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] External toolchain: crosstool-NG instead of buildroot?
Date: Fri, 18 Dec 2009 22:31:39 +0100 [thread overview]
Message-ID: <20091218223139.2118763c@surf> (raw)
In-Reply-To: <hgfudc$e2$1@ger.gmane.org>
Hello,
Le Fri, 18 Dec 2009 13:00:28 +0000 (UTC),
Grant Edwards <grant.b.edwards@gmail.com> a ?crit :
> The buildroot docs recommends using crosstool-NG to generate
> external toolchains.
>
> Is there some reason one shouldn't or can't use a toolchain
> generated buildroot?
Theorically, Buildroot should work just as fine as Crosstool-NG for
generating toolchain.
In practive, my own *personal* feeling is that the Crosstool-NG
community is spending more time to improve this toolchain generation
tool than the Buildroot community spends on the toolchain part. I have
the impression that they do a better job at following new upstream
versions, integrating necessary patches, etc. But again, I have no
objective facts to validate these feelings.
Cheers,
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-12-18 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 13:00 [Buildroot] External toolchain: crosstool-NG instead of buildroot? Grant Edwards
2009-12-18 21:31 ` Thomas Petazzoni [this message]
2009-12-18 21:36 ` Grant Edwards
2009-12-20 19:50 ` Peter Korsgaard
2009-12-20 21:37 ` Yann E. MORIN
2009-12-21 20:06 ` Peter Korsgaard
2009-12-21 22:10 ` Yann E. MORIN
2009-12-22 7:54 ` Peter Korsgaard
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=20091218223139.2118763c@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.