> Since the policy may or may not be active (depending on the user's project) > they might be using FindCUDA.cmake with CMP0054 set to NEW or OLD. To get > identical (and warning free) behavior irregardless of the current policy > setting Adam added the proposed ugliness.
Putting my 2ยข, we can either/or: (1) put everywhere these super ugly changes, which will make code (even more) obscure (2) put cmake_policy(SET CMP0053 NEW) at the every internal .cmake file that has been reviewed for this policy and use normal (not ugly syntax) Since include/find_package does implicit policy PUSH & POP for file scope this is IMHO much cleaner solution. Of course we would need to rollback couple of existing fixes committed by Brad. WDYT? --Adam -- 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
