James Bigler wrote:
I filed a documentation bug: http://public.kitware.com/Bug/view.php?id=8815
I've committed documentation and updated the bug entry.
BTW, is there a particular reason why custom commands are only registered in the directory where they appear? They seem kind of like the little brother of a target, and targets are global.
It was developed that way historically. At the time they were created they literally mapped to OUTPUT: DEPENDS COMMAND rules in makefiles, and CMake used directory-level recursive make so the rules could only work in the same directory. Since then the design of generated makefiles has totally changed but the behavior was preserved. There are arguments for and against global scoping of custom commands. I'd rather not get into a lengthy discussion about it unless someone volunteers to implement any changes, maintain them, and deal with all the compatibility issues. -Brad _______________________________________________ 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://www.cmake.org/mailman/listinfo/cmake
