John Biddiscombe wrote:
IMO this whole thing is upside down. SET should override unless
explicitely forbidden (for example by adding a READONLY qualifier, or
so), not the other way around.
Quite right. The original implementation was strange, but we're stuck
with it. I would however like to vote in favour of changing set with
NOTFOUND since NOTFOUND is a special value and it should be overwritten.
No, no,no no.....
If set did an override with cache variables, then the GUI would be
absolutely useless. If you want that behavior then just use INTERNAL
variables. Those variables are never presented to the user and are
stored in the cache. If you want a variable that a user can change in
the cache, then you never never want to change, but only initialize it
from a cmakelist file.
-Bill
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
