On 09/17/2018 04:01 AM, Rolf Eike Beer wrote: > I suggest that every module included from the CMake installation is > considered clean for whatever we do and automatically gets a policy > scope push/pop right from the C++ level.
That's fine with me for policies like CMP0057 that affect the CMake language features. We can't do that for every policy because some policies affect the way modules behave for the calling project. When include() or find_package() establishes the policy scope for the included module we can inject a few settings. Thanks, -Brad -- 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-developers
