Any project that isn't setting cmake_minimum_required before calling project is invoking deprecated behavior of CMake, and is ignoring Policy CMP0000 ( https://cmake.org/cmake/help/v3.4/policy/CMP0000.html#policy:CMP0000 ).
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. On Tue, Jan 3, 2017 at 2:49 PM, René J.V. Bertin <rjvber...@gmail.com> wrote: > On Tuesday January 03 2017 14:27:40 Robert Maynard wrote: > > Well, that has to be set in every project, or else we'd have to write an > initial cache file to be loaded with -C ... > > Weird, btw: I just ran into a project that apparently wasn't satisfied with > setting only CMP0025 on the commandline. It did set the minimum required > version to 2.8.x but that was well after the project() definition, and it > seems to be behind the scenes of that call that the compiler features are > tested (judging from message(STATUS "here") probes). > > Do you know what's happening there, and have any brilliant thoughts how we > can prevent this without have to scan each project? > >> Sorry I wasn't clear. I mean the cmake_minimum_required command ( >> https://cmake.org/cmake/help/v3.0/command/cmake_minimum_required.html >> ) > -- 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
