Nevermind, answered my own question. Setting CMP0043 to new at the beginning of the main file and then push/popping and setting to old where needed produced no warnings.
On Fri, Jun 13, 2014 at 9:44 AM, Nils Gladitz <[email protected]> wrote: > On 13.06.2014 18:32, Jake wrote: > >> Hello, >> >> I upgraded to 3.0 recently and tried to generate build files for a >> project (https://github.com/tpaviot/oce/). I noticed the new warning >> about CMP0043 and have been trying to fix, but setting the policy to OLD, >> even at the beginning of CMakeLists.txt doesn't seem to do anything. Is >> this a bug or what? "cmake_policy(SET CMP0043 OLD)" is what I put at the >> beginning. >> > > cmake_minimum_required() resets policies to match the version provided. > Did you set the policy before or after? > > Nils > >
-- 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://www.cmake.org/mailman/listinfo/cmake
