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] Speeding up the Build
Date: Mon, 8 Feb 2016 21:20:39 +0100	[thread overview]
Message-ID: <20160208212039.38bed8ae@free-electrons.com> (raw)
In-Reply-To: <CAJJ6jxs8G9i=K-qCCu29LZe0ro-kEjJeVTOHiEgEmmP88O=taQ@mail.gmail.com>

Hello,

On Mon, 8 Feb 2016 12:14:35 -0800, Steve Calfee wrote:

> Sorry I don't use CMAKE. Could your solution be extended to other host
> packages? Python for instance takes a long time to build and I have
> one installed. Unless we are patching the host tool or require a
> special version, it would build faster if buildroot used the installed
> version rather than building. I mean generically it would be nice.

For Python, we:

 1/ Need a host-python whose version matches the one of the target
    python being built.

 2/ Need some special host tools that are built as part of the
    host-python build, in order to build some stuff for the target
    python.

So unfortunately, it's not straightforward to use the Python of your
distribution.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-02-08 20:20 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
2016-02-08 20:14   ` Steve Calfee
2016-02-08 20:20     ` Thomas Petazzoni [this message]
  -- 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=20160208212039.38bed8ae@free-electrons.com \
    --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