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] howto incorporate buildroot into an autobuild
Date: Tue, 13 Nov 2012 09:45:26 +0100	[thread overview]
Message-ID: <20121113094526.6392ab30@skate> (raw)
In-Reply-To: <1352767649.18724.34.camel@genx>

Hello John,

On Mon, 12 Nov 2012 16:47:29 -0800, John Stile wrote:
> I am using buildroot for an embedded Arm project.
> 
> I was wondering how people using buildroot implement continuous
> integration builds?
> 
> Do you start from a clean checkout, build the whole tool chain (which
> takes a long time), and then build the project specific stuff?
> 
> I worry about not starting from a clean checkout, since some options may
> change, and the tools won't be rebuilt.
> 
> But I also worry people will complain how long the build takes.
> 
> Is there a good strategy to balance these concerns?

If you do continuous integration builds, do you really care that much
about the build time? Even if the build takes an hour, it is still very
reasonable for an continuous integration build system.

Tips to reduce the build time:

 * Get a fast machine. Many people complaining about build time are
   building inside a virtual machine on a slow laptop. This simply
   cannot work. Get a 4 or 8 cores machine, with 16+ GB of RAM, and
   some good I/Os.

 * Use an external toolchain.

Best regards,

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

  parent reply	other threads:[~2012-11-13  8:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  0:47 [Buildroot] howto incorporate buildroot into an autobuild John Stile
2012-11-13  5:02 ` Avery Pennarun
2012-11-13 21:04   ` Arnout Vandecappelle
2012-11-13  8:45 ` Thomas Petazzoni [this message]
2012-11-13 20:43   ` Arnout Vandecappelle

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=20121113094526.6392ab30@skate \
    --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