On 15. Mar, 2010, at 14:07 , Brad King wrote:
> Anyway, this patch should fix it.  Please test.
> 
> Thanks,
> -Brad
> 
> 
> Modules/CMakeDetermineCompilerId.cmake |    1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/Modules/CMakeDetermineCompilerId.cmake 
> b/Modules/CMakeDetermineCompilerId.cmake
> index bddd6a1..4a800a8 100644
> --- a/Modules/CMakeDetermineCompilerId.cmake
> +++ b/Modules/CMakeDetermineCompilerId.cmake
> @@ -19,6 +19,7 @@
> FUNCTION(CMAKE_DETERMINE_COMPILER_ID lang flagvar src)
>   # Make sure the compiler arguments are clean.
>   STRING(STRIP "${CMAKE_${lang}_COMPILER_ARG1}" 
> CMAKE_${lang}_COMPILER_ID_ARG1)
> +  STRING(REGEX REPLACE " +" ";" CMAKE_${lang}_COMPILER_ID_ARG1 
> "${CMAKE_${lang}_COMPILER_ID_ARG1}")
> 
>   # Make sure user-specified compiler flags are used.
>   IF(CMAKE_${lang}_FLAGS)
> -- 
> 1.6.6.1

Won't that fail for compiler-installations with spaces in the path (admittedly 
a bad idea, but on Windows probably not that unlikely)?

Michael
_______________________________________________
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

Reply via email to