[Cmake] Set command

[William A. Hoffman]

After the bug fix, (thanks Geoff) your files should still work.  I will 
update the
document line.   The SetCommand is still inherited so you can still set things
at the top.   So, it was not changed intentionally....


-Bill


At 05:00 PM 5/24/2001 -0400, Miller, James V (CRD) wrote:
>To clarify,
>
>A variable created with SET in only used to generate the makefile in the 
>current working directory if
>it is not put in the cache?
>
>This is a change in behavior.  Why was this changed?
>
>This broke my testing configurations.  The variables I had set in my 
>toplevel CMakeLists.txt file
>didn't need to be in the cache if CMake was keeping them active during the 
>makefile generation
>process.
>
>-----Original Message-----
>From: Bill Hoffman [mailto:bill.hoffman at kitware.com]
>Sent: Thursday, May 24, 2001 12:55 PM
>To: cmake at public.kitware.com
>Subject: [Cmake] Set command
>
>
>
>I have just change the syntax of the SET comand:
>
>   SET(VAR [VALUE] [CACHE TYPE DOCSTRING])
>        "Within CMAKE sets VAR to the value VALUE. VALUE is expanded before
>VAR "
>        "is set to it. If CACHE is present, then the VAR is put in the cache."
>        " TYPE and DOCSTRING are required.  If TYPE is INTERNAL, then the "
>        " VALUE is Always written into the cache, replacing any values "
>        "existing in the cache.  If it is not a CACHE VAR, then this always "
>        "writes into the current makefile.";
>
>I have updated all of Insight, CMake and vtknew.
>
>-Bill
>
>
>_______________________________________________
>Cmake mailing list
>Cmake at public.kitware.com
>http://public.kitware.com/mailman/listinfo/cmake
>
>_______________________________________________
>Cmake mailing list
>Cmake at public.kitware.com
>http://public.kitware.com/mailman/listinfo/cmake