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] ninja/python-meson packages
Date: Thu, 10 Nov 2016 09:18:08 +0100	[thread overview]
Message-ID: <20161110091808.06ceb521@free-electrons.com> (raw)
In-Reply-To: <20161110044245.mpwgroempys43o27@tarshish>

Hello,

On Thu, 10 Nov 2016 06:42:45 +0200, Baruch Siach wrote:

> On Wed, Nov 09, 2016 at 11:01:12PM +0100, C?dric Marie wrote:
> > Roughly, add dependency on ninja, add an option in cmake configure step (-G
> > ninja) and use ninja instead of make in build and install commands.  
> 
> Does that mean that we won't be able to use the host distro installed cmake? 
> Not so good in terms of build time. I guess it offsets most of the build time 
> gain in moving to ninja, if not more.

This is one of the reasons why I want to have this as an option, at
least initially. We clearly want to keep the nice benefit of using the
system-provided CMake.

Thanks,

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

  reply	other threads:[~2016-11-10  8:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 15:26 [Buildroot] ninja/python-meson packages Cédric Marie
2016-11-09 20:28 ` Thomas Petazzoni
2016-11-09 22:01   ` Cédric Marie
2016-11-09 22:13     ` Thomas Petazzoni
2016-11-10 10:28       ` Thijs Vermeir
2016-11-10 20:49         ` Cédric Marie
2016-11-13 21:24         ` Arnout Vandecappelle
2016-11-10  4:42     ` Baruch Siach
2016-11-10  8:18       ` Thomas Petazzoni [this message]
2016-11-10 10:05         ` Cédric Marie
2017-03-22 12:53 ` Fatih Aşıcı
2017-07-03 15:17   ` Vicente Olivert Riera
2017-07-03 22:08     ` Peter Korsgaard

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=20161110091808.06ceb521@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