This new policy breaks a long standing feature of FindCUDA. Basically I could add the MAIN_DEPENDENCY to all CUDA files built. If the same CUDA file was used in multiple custom commands it would attach the build rule to the first command, and leave the remaining ones as "phantom" .rule files in the project.
I don't want to turn off the MAIN_DEPENDENCY feature, so should I push/pop the policy in FindCUDA.cmake? James
-- 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
