AW: [CMake] Change in variable resolution?

2006-11-17 Thread wedekind
Hello Bill,

This seems to be a bug fix:

http://www.cmake.org/Bug/bug.php?op=showbugid=2722
There was some discussion here:

http://public.kitware.com/pipermail/cmake/2006-January/007942.html

There seems to be an error in this bug-fix. As I understand it, the intent
was to still allow resolution of @-variables in CONFIGURE_FILE. But that
does not work anymore.

However, I am concerned about backwards compatibility.   It was never
meant to be used in
cmake list files, but it has been inadvertently  supported in them since
the beginning.

-Bill

Ok, good to know. Fortunately it was not a big problem for me to switch from
@-variables to ${}-variables.

Cheers

Marco


___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake


Re: AW: [CMake] Change in variable resolution?

2006-11-17 Thread Bill Hoffman

wedekind wrote:

Hello Bill,

  

This seems to be a bug fix:

http://www.cmake.org/Bug/bug.php?op=showbugid=2722
There was some discussion here:

http://public.kitware.com/pipermail/cmake/2006-January/007942.html



There seems to be an error in this bug-fix. As I understand it, the intent
was to still allow resolution of @-variables in CONFIGURE_FILE. But that
does not work anymore.

  

However, I am concerned about backwards compatibility.   It was never
meant to be used in
cmake list files, but it has been inadvertently  supported in them since
the beginning.

-Bill



Ok, good to know. Fortunately it was not a big problem for me to switch from
@-variables to ${}-variables.
  
@VAR@ still worked in configure_file.  I just tested.  However, I have 
removed this bug fix in cvs,

and it will not be in 2.4.4.   It breaks backwards compatibility too much.

-Bill


___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake