Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/2] cmake: use Ninja by default
Date: Thu, 18 Jan 2018 12:38:04 +0000	[thread overview]
Message-ID: <20180118123804.2465-2-ross.burton@intel.com> (raw)
In-Reply-To: <20180118123804.2465-1-ross.burton@intel.com>

This changes the cmake class to use Ninja instead of Make by default.

If a recipe is broken with Ninja then the recipe can set OECMAKE_GENERATOR="Unix
Makefiles" to change back to Make.

Signed-off-by: Ross Burton <ross.burton@intel.com>
---
 meta/classes/cmake.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
index 74a952142ff..d60dad8d66b 100644
--- a/meta/classes/cmake.bbclass
+++ b/meta/classes/cmake.bbclass
@@ -9,7 +9,7 @@ CCACHE = ""
 
 # What CMake generator to use.
 # The supported options are "Unix Makefiles" or "Ninja".
-OECMAKE_GENERATOR ?= "Unix Makefiles"
+OECMAKE_GENERATOR ?= "Ninja"
 
 python() {
     generator = d.getVar("OECMAKE_GENERATOR")
-- 
2.11.0



  reply	other threads:[~2018-01-18 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 12:38 [PATCH 1/2] cmake: allow the generator to be changed Ross Burton
2018-01-18 12:38 ` Ross Burton [this message]
2018-01-18 13:04   ` [PATCH 2/2] cmake: use Ninja by default Otavio Salvador
2018-01-18 15:02   ` Böszörményi Zoltán
2018-01-18 16:02     ` Burton, Ross
2018-01-19 23:33   ` Alejandro Enedino Hernandez Samaniego
2018-01-18 13:02 ` ✗ patchtest: failure for "cmake: allow the generator to ..." and 1 more Patchwork
2018-01-18 13:04 ` [PATCH 1/2] cmake: allow the generator to be changed Otavio Salvador

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=20180118123804.2465-2-ross.burton@intel.com \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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