On Thu, May 1, 2014 at 2:16 PM, Matthew Woehlke <[email protected]> wrote: > On 2014-05-01 13:35, John Drescher wrote: >>> >>> I thought they probably were. My question was really if the behaviour >>> that >>> results from that was desirable. I can't see any reason why they should >>> be >>> cached as they aren't user configurable variables. Would it break >>> anything >>> badly if they were not stored in the cache ? It would result in more >>> consistent behaviour IMHO. >>> >> >> Executing >> >> cmake . >> >> would fail in the bin folder if it had no way to know where the source >> folder is. > > > 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? >
I see now. Sorry for the noise.. John -- 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
