[CMake] Why is Ninja generator disabled by default?

[Claus Klein]

it works on my macbook:

"/usr/local/CMake 2.8-8.app/Contents/bin/cmake" --version
cmake version 2.8.8.20120520-g4742e

claus-kleins-macbook-pro:CompileCommandOutput clausklein$ "/usr/local/ 
CMake 2.8-8.app/Contents/bin/cmake" -G Ninja -DMAKE_SUPPORTS_SPACES=1
-- The CXX compiler identification is GNU 4.7.0
-- Checking whether CXX compiler has -isysroot
-- Checking whether CXX compiler has -isysroot - yes
-- Checking whether CXX compiler supports OSX deployment target flag
-- Checking whether CXX compiler supports OSX deployment target flag -  
yes
-- Check for working CXX compiler using: Ninja
-- Check for working CXX compiler using: Ninja -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/clausklein/Downloads/cmake/ 
Tests/CompileCommandOutput

claus-kleins-macbook-pro:CompileCommandOutput clausklein$ ninja -d  
explain
ninja explain: output CMakeFiles/test1.dir/file_with_spaces.cxx.o  
doesn't exist
ninja explain: CMakeFiles/test1.dir/file_with_spaces.cxx.o is dirty
ninja explain: output CMakeFiles/test2.dir/relative.cxx.o doesn't exist
ninja explain: CMakeFiles/test2.dir/relative.cxx.o is dirty
ninja explain: output CMakeFiles/CompileCommandOutput.dir/ 
compile_command_output.cxx.o doesn't exist
ninja explain: CMakeFiles/CompileCommandOutput.dir/ 
compile_command_output.cxx.o is dirty
ninja explain: libtest1.a is dirty
ninja explain: libtest2.dylib is dirty
ninja explain: CompileCommandOutput is dirty
ninja explain: libtest1.a is dirty
ninja explain: libtest2.dylib is dirty
[6/6] Linking CXX executable CompileCommandOutput
claus-kleins-macbook-pro:CompileCommandOutput clausklein$

claus-kleins-macbook-pro:CompileCommandOutput clausklein$ touch file\  
with\ spaces.cxx
claus-kleins-macbook-pro:CompileCommandOutput clausklein$ ninja -d  
explain
ninja explain: output CMakeFiles/test1.dir/file_with_spaces.cxx.o  
older than most recent input file with spaces.cxx (13377238240000000  
vs 13377239270000000)
ninja explain: CMakeFiles/test1.dir/file_with_spaces.cxx.o is dirty
ninja explain: libtest1.a is dirty
ninja explain: CompileCommandOutput is dirty
ninja explain: libtest1.a is dirty
[3/3] Linking CXX executable CompileCommandOutput
claus-kleins-macbook-pro:CompileCommandOutput clausklein$


On 22.05.2012, at 13:35, Richard Wackerbarth wrote:

> One of the differences that shows up in the dashboard is that there  
> is a compile test which passes with normal Unix file paths, but  
> fails when there is a space in one of the directory names. Perhaps  
> we need to add an explicit test for everyone, ninja or otherwise, to  
> test that compiles work with spaces in the path. I have a feeling  
> that we may find additional failures.
>
> On May 22, 2012, at 6:02 AM, David Cole wrote:
>
>> Please take a look at the CMake dashboard:
>>
>>   http://open.cdash.org/index.php?project=CMake
>>
>> 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.
>>
>> 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. ;-)
>>
>>
>> David
>
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20120523/7d446b68/attachment.htm>