ENV paths with backslashes

[Alexander Neundorf]

On Saturday 11 February 2006 17:25, Alexander Neundorf wrote:
> On Saturday 11 February 2006 16:45, Peter Kümmel wrote:
> > I've found the reason for not scanning for dependencies:
> >
> > When I get a environment variable with $ENV the backslashes
> > are not replaced:
>
> Cool that you found the reason :-)
> We can implement a workaround (not tested):
>
> macro(MACRO_GETENV_WIN_PATH var name)
>    set(${var} $ENV{${name}})
>    string( REGEX REPLACE "\\\\" "/" ${var} ${${var}} )
> endmacro(MACRO_GETENV_WIN_PATH var name)
>
> and use this. I'm not sure whether this is a bug or a feature ("well, why
> should it modify the content of a environment variable ?" vs. "why doesn't
> it automatically transform a path ?")
>
> Usage: macro_getenv_win_path(MSSDK_INCLUDE_DIR MSSDK)

Will this then have to be used for all paths which come from an windows 
environment variable ?

Alex
-- 
Work: alexander.neundorf AT jenoptik.com - http://www.jenoptik-los.de
Home: neundorf AT kde.org                - http://www.kde.org
      alex AT neundorf.net               - http://www.neundorf.net