I noticed local CMake variables for CMAKE_INCLUDE_PATH and
CMAKE_LIBRARY_PATH no longer work in CMake 2.6.x.  It appears the
documentation has been changed to require these to be CACHE variables.

First of all, why the change in behavior?  Shouldn't a locally specified
CMAKE_INCLUDE_PATH variable trump any cache specified version just like in
CMake 2.4.x?
Second of all, CMAKE_PREFIX_PATH seems to work fine as a local variable.
Why the discrepency?

The use case here is to allow the user to specify a cache variable for a
package that has tons of libraries and then to use that cache variable to
manipulate CMAKE_PREFIX_PATH (or CMAKE_INCLUDE_PATH / CMAKE_LIBRARY_PATH) to
effect the detection of the libraries.

-- 
Philip Lowman
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to