On Tuesday January 03 2017 15:23:45 Robert Maynard wrote: > Basically my recommendation is if a project isn't setting > cmake_minimum_required before the first project call than nothing you > can do will fix that, as it is an error.
The issue here is not that the minimum version was NOT being set. Apparently that isn't an issue if I set CMP0025 from the commandline. The issue was a project that requested an earlier CMake version (2.8.something) further down. Apparently that undoes the explicit CMP0025 setting, but not if I execute a cmake_minimum_required(3.0) first. Either way, I'm getting signals from others using the build system this is about (MacPorts) to please not force a minimum required CMake version, and calling `cmake_minimum_required` in an initial cache file does not have the expected effect. R. -- 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://public.kitware.com/mailman/listinfo/cmake-developers
