On 2018-06-29 14:46-0400 Robert Maynard wrote: [...]
* The "cmake_minimum_required()" and "cmake_policy(VERSION)" commands now accept a version range using the form "<min>[...<max>]". The "<min>" version is required but policies are set based on the "<max>" version. This allows projects to specify a range of versions for which they have been updated and avoid explicit policy settings.
[...]
I suggest the following change to the above description: but policies are set based on the "<max>" version. ==> but policies are set based on the minimum of the running CMake and "<max>" versions. I prefer the latter because it immediately answers the question implied by the former, i.e., what happens if the running version is less than max? Alan __________________________ Alan W. Irwin Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ -- 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: https://cmake.org/mailman/listinfo/cmake
