Michael Wild wrote: > Won't that fail for compiler-installations with spaces in the path > (admittedly a bad idea, but on Windows probably not that unlikely)?
By the time the new code is reached we've already split the arguments from the compiler itself. This is done in CMakeDetermineCCompiler.cmake using the "PROGRAM/PROGRAM_ARGS" option of get_filename_component() which already accounts for spaces in the path. It uses an algorithm similar to what the Windows command prompt does. It works backwards from the end and tries using everything to the left of each space as a file name until something is found. What this could change is if a single argument to the compiler really needs a space. However this already doesn't work in the case of the standard CFLAGS, CXXFLAGS, and FFLAGS variables. -Brad _______________________________________________ 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
