Hi people,
Consider the following:
# Forcibly set the value of a cache variable
set( VAR "Hello" CACHE STRING "bla bla" FORCE )
# Show in-memory value
message( STATUS "VAR=${VAR}" )
# Load cached value just in case the above SET
# overwrote only the in-memory value
set( VAR )
# Now show the
On 2007-04-16 09:30-0700 Alan W. Irwin wrote:
My opinion is that the FORCE option to SET should _always_ force the
specified cache value (as is currently documented and as seems intuitive to
users). When you get situations like above where it doesn't always force
the value, it can be quite conf
On 2007-04-13 12:30-0700 Alan W. Irwin wrote:
Here is a complete test CMakeLists.txt file which illustrates what I believe
is a bug in 2.4.6 for the SET command:
message(STATUS TEST=${TEST})
set(TEST OFF CACHE BOOL "test variable" FORCE)
message(STATUS TEST=${TEST})
set(TEST OFF CACHE BOOL "tes
Here is a complete test CMakeLists.txt file which illustrates what I believe
is a bug in 2.4.6 for the SET command:
message(STATUS TEST=${TEST})
set(TEST OFF CACHE BOOL "test variable" FORCE)
message(STATUS TEST=${TEST})
set(TEST OFF CACHE BOOL "test variable" FORCE)
message(STATUS TEST=${TEST})
