On 2014-05-01 14:26, Nils Gladitz wrote:
On 01.05.2014 20:16, Matthew Woehlke wrote:
If CMAKE_BINARY_DIR were not cached, yes. But I don't think not
caching that is being suggested. It's not clear to me why the
*per-project* flavors need to be cached?
If they were regular instead of cache variables they would have scopes.
I guess this would break any project that currently referred to their
sub- or sibling projects with those variables.
Hmm... that's a good point. I suspect project() could work around the
scope at least by arranging to set them in the root scope, but there
might be other, related issues that could arise.
Nuts :-).
--
Matthew
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
