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.
This commit is contained in:
Brad King 2011-06-30 08:38:00 -04:00
parent e1237478f1
commit 0ece8f79ed

View File

@ -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. "