[CMake] Changes to cmake_minimum_required() for 3.12
Johannes Zarl-Zierl
johannes.zarl-zierl at jku.at
Mon Jul 2 06:43:38 EDT 2018
Hi,
Just giving my 2 cents:
If the preferred solution is the "POLICY_NEW_UNTIL" wording, then why not make
this accepted as well? This way, you can deprecate the backwards-compatible
version in a few years and remove it some time thereafter. In the end, you'll
get a cleaner solution...
Cheers,
Johannes
On Montag, 2. Juli 2018 08:43:57 CEST Craig Scott wrote:
> On Mon, Jul 2, 2018 at 4:04 AM, Alan W. Irwin <Alan.W.Irwin1234 at gmail.com>
>
> wrote:
> > On 2018-07-01 08:12+1000 Craig Scott wrote:
> >
> > Older CMake versions
> >
> >> will see the extra dots as being version component separators and will
> >> end
> >> up effectively ignoring the max part.
> >
> > This explanation of how "..." will be interpreted by older CMake
> > versions makes sense, but it wasn't obvious to me without that
> > explanation. And I suspect other build-system developers/maintainers
> > would also benefit from the explanation. Therefore, please explicitly
> > include the above explanation in the latest documentation of both the
> > cmake_minimum_required and cmake_policy commands.
>
> I've updated the merge request to incorporate this feedback.
>
> https://gitlab.kitware.com/cmake/cmake/merge_requests/2180
--
Johannes Zarl-Zierl
Information management
JOHANNES KEPLER UNIVERSITY LINZ
Altenberger Straße 69
4040 Linz, Austria
P +43 732 2468 3898
johannes.zarl-zierl at jku.at
www.jku.at
More information about the CMake
mailing list