Would anyone be opposed to having cmMakefile::AddCustomCommandToTarget()
throw an error in case the target does not exist?
Currently this just silently fails without any diagnostics.
I assume this wouldn't need a policy since there is no useful behavior
here to preserve?
Nils
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
