From c9af21f9defcc9b3db778f8e42fa0f0a0910b750 Mon Sep 17 00:00:00 2001
From: Eike Ziller <eike.ziller@theqtcompany.com>
Date: Tue, 24 Mar 2015 08:18:46 +0100
Subject: [PATCH] Kits: Not having a CMake executable set is perfectly valid.

It is the normal situation on Windows & OS X for simple Qt development.

Change-Id: I84453ebcc62200bd6c7223a593b5953c20194069
Reviewed-by: Daniel Teske <daniel.teske@theqtcompany.com>
Reviewed-by: Tobias Hunger <tobias.hunger@theqtcompany.com>
---
 .../cmakeprojectmanager/cmakekitinformation.cpp     | 13 ++-----------
 1 file changed, 2 insertions(+), 11 deletions(-)

diff --git a/src/plugins/cmakeprojectmanager/cmakekitinformation.cpp b/src/plugins/cmakeprojectmanager/cmakekitinformation.cpp
index 0fdf1023484..b0ce2c96f58 100644
--- a/src/plugins/cmakeprojectmanager/cmakekitinformation.cpp
+++ b/src/plugins/cmakeprojectmanager/cmakekitinformation.cpp
@@ -101,17 +101,8 @@ QVariant CMakeKitInformation::defaultValue(Kit *) const
 
 QList<Task> CMakeKitInformation::validate(const Kit *k) const
 {
-    CMakeTool *tool = CMakeKitInformation::cmakeTool(k);
-    QList<Task> result;
-    if (!tool) {
-        result.append(Task(Task::Warning,
-                           tr("No CMake tool set."),
-                           Utils::FileName(),
-                           -1,
-                           Core::Id(Constants::TASK_CATEGORY_BUILDSYSTEM)));
-    }
-
-    return result;
+    Q_UNUSED(k);
+    return QList<Task>();
 }
 
 void CMakeKitInformation::setup(Kit *k)