All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] On internal vs. external toolchains
Date: Wed, 29 Sep 2010 13:12:21 +0200	[thread overview]
Message-ID: <20100929131221.0a5e9c1b@surf> (raw)
In-Reply-To: <AANLkTikZEe+tS3WtxULNLNq80QrVRy0U5XWzneRcHRnw@mail.gmail.com>

On Wed, 29 Sep 2010 14:01:23 +0300
Paulius Zaleckas <paulius.zaleckas@gmail.com> wrote:

> > Are you using internal toolchain or external toolchain ?
> 
> internal

Then you could probably save ~20-30% of your build time by using an
external toolchain (generated either by Buildroot itself, Crosstool-NG
or using a ready-to-use CodeSourcery toolchain).

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-09-29 11:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 20:36 [Buildroot] Libtool work: a tentative summary Thomas Petazzoni
2010-09-28 23:26 ` Lionel Landwerlin
2010-09-29  8:32 ` Paulius Zaleckas
2010-09-29  8:51   ` Thomas Petazzoni
2010-09-29 11:01     ` Paulius Zaleckas
2010-09-29 11:12       ` Thomas Petazzoni [this message]
2010-09-29 19:59       ` Martin Banky
2010-10-03 13:22 ` Lionel Landwerlin
2010-10-03 14:22   ` Thomas Petazzoni
2010-10-03 22:36     ` Martin Banky
2010-10-03 23:47       ` Lionel Landwerlin
2010-10-04  1:19         ` Martin Banky
2010-10-04  8:09           ` Lionel Landwerlin
2010-10-05  0:04             ` Lionel Landwerlin
2010-10-07 14:57 ` [Buildroot] Tentative conclusion on the libtool work Thomas Petazzoni
2010-10-07 16:34   ` Lionel Landwerlin

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=20100929131221.0a5e9c1b@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.