From 60216e158fe2f9e68d1dff6676852c45e9d1ffc2 Mon Sep 17 00:00:00 2001 From: Christoph Ruediger Date: Tue, 16 Jan 2018 15:10:26 +0100 Subject: Help: Improved MAIN_DEPENDENCY documentation of add_custom_command() --- Help/command/add_custom_command.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Help/command/add_custom_command.rst b/Help/command/add_custom_command.rst index 1b0aa14..d4f644a 100644 --- a/Help/command/add_custom_command.rst +++ b/Help/command/add_custom_command.rst @@ -146,8 +146,10 @@ The options are: Specify the primary input source file to the command. This is treated just like any value given to the ``DEPENDS`` option but also suggests to Visual Studio generators where to hang - the custom command. At most one custom command may specify a - given source file as its main dependency. + the custom command. Each source file may have at most one command + specifying it as its main dependency. A compile command (i.e. for a + library or an executable) counts as an implicit main dependency which + gets silently overwritten by a custom command specification. ``OUTPUT`` Specify the output files the command is expected to produce. -- cgit v0.12