What are we trying to accomplish here? I have set up 3 of my machines (1 each MacOSX, FreeBSD, and Linux --- like my housekeeper, I don't do Windows) to submit nightly builds using the Ninja generator. That will test the impact of changes in the generator.
But it appears that we may also need to be testing the evolving state of ninja. For that, it would seem that we need a different dashboard and (at least as a wrapper) a CMake driven build of ninja. Am I missing something? Richard On Feb 16, 2012, at 3:46 PM, Peter Kümmel wrote: > On 16.02.2012 21:38, Bill Hoffman wrote: >> On 2/16/2012 2:57 PM, Peter Kümmel wrote: >> >>> They are not interested. >>> There is another patch in the pipeline but with >>> this the current generator doesn't work. >>> >>> Use the official ninja and drop Win atm. >>> >> Bummer. I am most interested in windows. Would love to stop using > > OK, I could update my branch with the official one, disable all > Windows specific patches on Linux. This way, testing on Linux is like > testing against the official ninja, and an Windows we have intermediate > version until ninja supports win32. > > But I don't wanna touch the generator atm because I don't like the actual > proposal for response file support. > > >> gmake... Seems like they are doing lots of stuff with .d files for >> windows. So, they seem interested in supporting the platform. Is there >> something we can change in the cmake generator to make it work with the >> way ninja is today, and will be for the foreseeable future? >> >> >> -Bill -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
