From 0ece8f79ed480152fa70ca7dea7b6625386a63e3 Mon Sep 17 00:00:00 2001 From: Brad King Date: Thu, 30 Jun 2011 08:38:00 -0400 Subject: [PATCH] Document caveat of custom commands in multiple targets (#12311) A common mistake when using custom commands is to list the output of a command in multiple targets that may build in parallel. Warn against this case in the documentation and suggest a better approach. --- Source/cmAddCustomCommandCommand.h | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Source/cmAddCustomCommandCommand.h b/Source/cmAddCustomCommandCommand.h index 47b542c81..05e7dc28e 100644 --- a/Source/cmAddCustomCommandCommand.h +++ b/Source/cmAddCustomCommandCommand.h @@ -75,6 +75,10 @@ public: "A target created in the same directory (CMakeLists.txt file) that " "specifies any output of the custom command as a source file is given " "a rule to generate the file using the command at build time. " + "Do not list the output in more than one independent target that may " + "build in parallel or the two instances of the rule may conflict " + "(instead use add_custom_target to drive the command and make the " + "other targets depend on that one). " "If an output name is a relative path it will be interpreted " "relative to the build tree directory corresponding to the current " "source directory. "