Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] Speeding up the Build
Date: Sat, 6 Feb 2016 15:24:30 +0100	[thread overview]
Message-ID: <56B6021E.3070608@lucaceresoli.net> (raw)
In-Reply-To: <CAJJ6jxvwFavFNNVMnBuCGr4hmEgOdRzyU6XDx=_9bF9a9FUn5Q@mail.gmail.com>

Hi Steve,

Steve Calfee wrote:
> Hi,
>
> I know buy faster hardware...
>
> We have the ability to share a common download directory, so multiple
> systems builds can have faster downloads.
>
> We have the ability to install a pre-build toolchain - that really helps.
>
> We can have multiple output directories, using the single downloaded
> buildroot directory. Saves git downloading and disk storage.
>
> Is there any way to share the host built utilities? It could be done
> like using a pre-built toolchain, or some kind of special links for
> output/host. The problem is .../host is splatted right in the middle
> of the dynamic per build output directory. Do these files get changed
> much in normal buildroot use, so they should stay in output?

Not quite replying to your question (Arnout has already done, with
great detail).

But I submitted a patch [0] to skip host-cmake building entirely. It
saves 30% of the build time in my setup. If you use cmake-based
packages, you might want to give it a try and give your feedback.

[0] http://patchwork.ozlabs.org/patch/579445/

-- 
Luca

-- 
Luca

  reply	other threads:[~2016-02-06 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 17:24 [Buildroot] Speeding up the Build Steve Calfee
2016-02-06 14:24 ` Luca Ceresoli [this message]
2016-02-08 20:14   ` Steve Calfee
2016-02-08 20:20     ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2016-02-03 21:59 [Buildroot] Speeding up the build Steve Calfee
2016-02-05 21:00 ` Arnout Vandecappelle
2016-02-05 21:04 ` 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=56B6021E.3070608@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --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