Please take a look at the CMake dashboard:<div><br></div><div> <a href="http://open.cdash.org/index.php?project=CMake">http://open.cdash.org/index.php?project=CMake</a><br><br></div><div>I will allow the ninja generator to be enabled by default after interested parties fix all the failing tests in the "Nightly Expected" section related to the ninja generator submissions.</div>
<div><br></div><div>Honestly, I was opposed to the ninja generator being merged to 'master' and enabled at all because of the failing tests on our dashboard. Luckily for all you ninja fans out there, I do not have dictator powers. ;-)</div>
<div><br></div><div><br></div><div>David</div><div><br></div><div><br></div><div><div class="gmail_quote">On Mon, May 21, 2012 at 4:27 PM, Andreas Mohr <span dir="ltr"><<a href="mailto:andi@lisas.de" target="_blank">andi@lisas.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
On Mon, May 21, 2012 at 10:40:03AM -0400, <a href="mailto:cmake-request@cmake.org">cmake-request@cmake.org</a> wrote:<br>
> From: David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>><br>
<div class="im">> I agree with Bill here -- we cannot turn it on by default until it works<br>
> sufficiently for typical use cases.<br>
<br>
</div>So, what would be needed to turn CMake on by default?<br>
'cause it does not "work sufficiently for typical use cases" :-><br>
</asbestos_suit><br>
<br>
<br>
While there might be backwards compatibility reasons for only actually<br>
having Ninja truly enabled once it truly works (after all after some years<br>
certain user code may resort to merely checking whether the feature<br>
is provided or not, rather than doing sufficiently precise checks<br>
"well, in this CMake pre-beta it actually was still broken,<br>
and 3 days later they fixed it"),<br>
I cannot help but wonder whether this configuration (build-time disabling<br>
rather than a slightly special way of runtime disabling)<br>
is hindering progress a bit due to artificially limiting developer uptake.<br>
OTOH people who tend to like playing with certain bleeding edge things (like me)<br>
are actually able to enable it manually - it's just somewhat more<br>
effort:<br>
<div class="HOEnZb"><div class="h5"><br>
> For specialized use cases, if you know you want to turn it on, you can<br>
> easily re-build a CMake of your own that has it enabled. Simply turn on the<br>
> advanced cache option CMAKE_ENABLE_NINJA when configuring CMake.<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">Andreas Mohr<br>
</font></span></blockquote></div><br></div>