I've been using cygwin buildbot for some time, doing pure windows builds. The trick is to have the cygwin buildslave unset a few environment variables (like cygwin's PATH and TEMP and temp), then run a windows batch file to do everything involving compilers, e.g. running windows cmake. There is a tiny bit of magic involved in cleansing the environment enough for the windows tools to be happy, but not much.
But I agree: for cmake and things like ninja that run compilers, use pure windows versions, even if you kick them off originally from a cygwin shell script. - Dan -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
