summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJan Niklas Hasse <jhasse@bixense.com>2021-03-05 22:51:32 +0100
committerGitHub <noreply@github.com>2021-03-05 22:51:32 +0100
commitac0fe07d9e924661c6c443f4a9503d4f4308fb20 (patch)
tree359f46d7dfbf36ca372bc62c84f9eb4af7fa63c9
parent0c11d6e4dc3adcf010a86b03ca9ce9e855eedf42 (diff)
parent942a523a7336da410e74fe5f72015fbc5ae2067a (diff)
downloadninja-ac0fe07d9e924661c6c443f4a9503d4f4308fb20.tar.gz
Merge pull request #1907 from aDotInTheVoid/patch-1
Clarify purpose for implicit dependencies
-rw-r--r--doc/manual.asciidoc5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/manual.asciidoc b/doc/manual.asciidoc
index 54403ac..a5012b4 100644
--- a/doc/manual.asciidoc
+++ b/doc/manual.asciidoc
@@ -980,8 +980,9 @@ source file of a compile command.
+
This is for expressing dependencies that don't show up on the
command line of the command; for example, for a rule that runs a
-script, the script itself should be an implicit dependency, as
-changes to the script should cause the output to rebuild.
+script that reads a hardcoded file, the hardcoded file should
+be an implicit dependency, as changes to the file should cause
+the output to rebuild, even though it doesn't show up in the arguments.
+
Note that dependencies as loaded through depfiles have slightly different
semantics, as described in the <<ref_rule,rule reference>>.