On 04 Mar 2015, at 19:40, Nils Gladitz <[email protected]<mailto:[email protected]>> wrote:
cmake_minimum_required() resets all policies according to the given version. CMP0005 was introduced in 2.6.0 so requiring 2.8.8 sets it to NEW. CMP0054 was introduced in 3.1 so requiring 2.8.8 clears the policy (since it did not exist in 2.8.8). Thanks very much for the explanation. Nevertheless I do not understand the logic. Running with 3.1 with the exactly the same code generates warnings that were not there in 2.8.8. In order to switch them off I need to set the policy to NEW, which gets cleared by requiring somehow a less restrictive condition. Cheers, Pere ------------------------------------------------------------- Pere Mato CERN, PH Department, CH 1211 Geneva 23, Switzerland e-mail: [email protected]<mailto:[email protected]> tel: +41 22 76 78696 fax: +41 22 76 68792 gsm: +41 76 48 70855
-- 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
