Luke Kucalaba wrote:
Good catch. That seems to have fixed the example--I'll try to apply the
same fix to the real project to see if this is going to be resolved now.
Thanks for looking into this for me, I really appreciate your time and
effort.
The only reason that I wanted to use the cache is to hide certain cmake
variables from the typical end user, even if they click "Show Advanced
Values". I'm the primary CMake maintainer for our software team, and I
don't want the other developers to be monkeying around with some of
these CMake variables (like CMAKE_CXX_FLAGS_DEBUG), although others are
OK to change (like CMAKE_VERBOSE_MAKEFILE for instance). I figured
these variables were cached anyway because they show up in the cache
when you check "Show Advanced Values". What does it even mean then when
you show advanced variables like CMAKE_CXX_FLAGS_DEBUG in the cache
window (using CMakeSetup), when it is actually being used as a "local
variable"? Are there global equivalents to these CMake variables?
I suppose we'll just go with what works and have to remind everyone to
just ignore the "show advanced values" option at all costs.
You can still set them with the CACHE FORCE to hide them. Just do that
once in the project (to bogus values), then use the local variables to
actually set the values that you want.
-Bill
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
