From 80edcc6a86d7b5e00073c5cd2584383f971b7645 Mon Sep 17 00:00:00 2001 From: Brad King Date: Fri, 5 Nov 2010 08:08:37 -0400 Subject: Document custom command behavior without DEPENDS (#11407) The behavior of add_custom_command when no DEPENDS option is specified matches that of standard Make behavior, but it does not hurt to describe it explicitly. --- Source/cmAddCustomCommandCommand.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Source/cmAddCustomCommandCommand.h b/Source/cmAddCustomCommandCommand.h index c67caa5..6c5e1af 100644 --- a/Source/cmAddCustomCommandCommand.h +++ b/Source/cmAddCustomCommandCommand.h @@ -152,6 +152,9 @@ public: "If any dependency is an OUTPUT of another custom command in the " "same directory (CMakeLists.txt file) CMake automatically brings the " "other custom command into the target in which this command is built. " + "If DEPENDS is not specified the command will run whenever the OUTPUT " + "is missing; if the command does not actually create the OUTPUT then " + "the rule will always run. " "If DEPENDS specifies any target (created by an ADD_* command) " "a target-level dependency is created to make sure the target is " "built before any target using this custom command. Additionally, " -- cgit v0.12