[CMake] [ANNOUNCE] CMake 3.12.0-rc2 is ready for testing

Hendrik Sattler post at hendrik-sattler.de
Sat Jun 30 01:13:52 EDT 2018


It would actually make even more sense to rename cmake_minimum_required() to cmake_version_required() with the new syntax or something similar. Users of the old function cannot use the new syntax in older cmake versions and the old name does not actually fit the new functionality.


Am 30. Juni 2018 00:05:25 MESZ schrieb "Alan W. Irwin" <irwin at beluga.phys.uvic.ca>:
>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
>__________________________


More information about the CMake mailing list