Hi everyone, We have a strange situation where we do have too many include paths, which makes command line for obj compilation too long on windows (more 32kb). I've tried using set(CMAKE_NINJA_FORCE_RESPONSE_FILE 1), but apparently after checking cmake upstream I've realized that it's only implemented for linking, and not compilation.
What we should do (other than fixing "the problem" with too many paths) ? Would be nice to have this feature working for makefiles and ninja. PS. Can we do something about bloated cmake ninja generator ? in our case cmake generates 1.8 Mb Makefile and 84 Mb build.ninja, though ninja is still faster than make even in this case. Best, Dmitry
-- 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-developers
