Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to rebuild following .config change?
Date: Wed, 24 Jun 2009 09:13:53 +0200	[thread overview]
Message-ID: <20090624091353.38df494a@surf> (raw)
In-Reply-To: <h1rchh$9du$1@ger.gmane.org>

Le Tue, 23 Jun 2009 20:05:06 +0000 (UTC),
Grant Edwards <grant.b.edwards@gmail.com> a ?crit :

> You can do a "distclean", but then all the sources get
> re-downloaded and toolchains re-built -- which takes a _long_
> time.

It's true that Buildroot doesn't handle partial rebuilds very well.
This is something we should improve.

In the mean time, here is how I use Buildroot :

 * Set the BUILDROOT_DL_DIR environment variable, so that downloads are
   made to a completely separate directory from the Buildroot source
   and Buildroot build directories ;

 * Use an external toolchain (such as one generated by Crosstool-NG,
   for example). This way, the toolchain generation process is
   independent from Buildroot, and you don't need to re-generate the
   toolchain everytime you want to recompile the root filesystem from
   scratch ;

 * Use out-of-tree generation in Buildroot with "make
   O=/path/to/somewhere". This way, all generated files are in a
   separate directory, which makes it easy to clean everything.

Sincerly,

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

  parent reply	other threads:[~2009-06-24  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 20:05 [Buildroot] How to rebuild following .config change? Grant Edwards
2009-06-23 20:14 ` Bernhard Reutner-Fischer
2009-06-24  7:13 ` Thomas Petazzoni [this message]
2009-06-25 19:02   ` 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=20090624091353.38df494a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox