The documentation for add_custom_command() contains this little nugget when discussing the COMMAND keyword:
If COMMAND specifies an executable target name ...<snip>... Additionally a > target-level dependency will be added so that the executable target will be > built before any target using this custom command. However this does NOT > add a file-level dependency that would cause the custom command to re-run > whenever the executable is recompiled. I'm struggling to come up with a scenario where that last part about file level dependencies becomes relevant. Can anyone come up with a simple use case which highlights that particular aspect of dependencies and commands? -- Craig Scott Melbourne, Australia https://crascit.com
-- 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
