[CMake] problem on windows with $ENV{something}

William A. Hoffman billlist at nycap.rr.com
Sun Feb 12 10:23:07 EST 2006


At 09:57 AM 2/12/2006, Cesar Rabak wrote:
>Since the cmake is ported to the Windows platform/environment, I think it is reasonable expectation of the user to have the env vars written in the native (Windows) style.
>
>As such, cmake must be able to parse and process vars with spaces and correctly interpreting the backslashes.
>
>As matter of fact, this should be transparent for cmake, after of all the programs that make use of the information stored in these variables that have to take care of the semantics of the slashes.
>
>my .01999...

Sounds good, but is there a case when you would have a \ in an environment variable that
you did not want converted?   What if it was not a PATH at all?   We could check
to see if it is a PATH, but what if the file or path does not exist?  

-Bill



More information about the CMake mailing list