On Tuesday January 03 2017 11:41:29 Robert Maynard wrote: > It is the responsibility of the project to understand what components > of CMake they require, and correctly specify a cmake_minimum required > that satisfies all those requirements. In this case to use compile > features you need a minimum of 3.0 which also automatically enables > policy 25.
I agree with you in a way, but in reality it would be up to end users and packagers to feed back that information to an unknown number of projects and convince them why it's necessary to comply with the request. That's just not doable. It would be a lot easier if the policy could be set at a central location, in this case in the Qt module invoking the test that fails. And it's CMake's responsibility to generate useful error messages, and where possible provide a hint for the fix. > You can explicitly do both of those things currently see: > https://cmake.org/cmake/help/v3.0/manual/cmake-policies.7.html Ah, thanks. I take it one can also change a line in cmPolicies.h: SELECT(POLICY, CMP0025, "Compiler id for Apple Clang is now AppleClang.", \ 3, 0, 0, cmPolicies::NEW) \ ? 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
