kolan
/
CMake
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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.
This commit is contained in:
Brad King 2010-11-05 08:08:37 -04:00
parent 947de96030
commit 80edcc6a86
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Source/cmAddCustomCommandCommand.h
View File

@ -152,6 +152,9 @@ public:
"If any dependency is an OUTPUT of another custom command in the " "If any dependency is an OUTPUT of another custom command in the "
"same directory (CMakeLists.txt file) CMake automatically brings the " "same directory (CMakeLists.txt file) CMake automatically brings the "
"other custom command into the target in which this command is built. " "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) " "If DEPENDS specifies any target (created by an ADD_* command) "
"a target-level dependency is created to make sure the target is " "a target-level dependency is created to make sure the target is "
"built before any target using this custom command. Additionally, " "built before any target using this custom command. Additionally, "