On Wed, Mar 07, 2012 at 07:14:52AM +0100, Nicolas Desprès wrote: > On Tue, Mar 6, 2012 at 8:58 PM, Clifford Yapp <[email protected]> wrote: > >> >>>>> We *could*, if popular demand is high enough, merge it in anyway and > >> >>>>> call it "experimental" to start with, or we could get it right all > >> >>>>> the > >> >>>>> way before we merge to 'master' and put it out in an official CMake > >> >>>>> release. > > > > > > What would be involved with fixing the remaining OSX issues? Do we need > > CMake changes, ninja changes, both...? > > > > Obviously full support would be preferable, unless it won't be happening for > > quite some time - I would agree that if non-GUI apps won't work on OSX it > > would be better to limit an activation of Ninja to those platforms where it > > will Work As Expected. > > > > So contrary to what I have said at the beginning of this thread. It > seems that merging it master will generate more bug report than > patches to fix the issue. If it is the case, I prefer to disable it. I > will try to fix them ASAP anyway.
It seems that public opinion is against me. Well, I guess we can disable the Ninja generator by default on Mac. Anyone who wants to turn it back on should be able to use an internal CMake variable when building CMake. Thanks, -- Peter -- 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
