From 942a523a7336da410e74fe5f72015fbc5ae2067a Mon Sep 17 00:00:00 2001 From: Nixon Enraght-Moony Date: Fri, 29 Jan 2021 18:34:58 +0000 Subject: Clarify purpose for implicit dependencies --- doc/manual.asciidoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/manual.asciidoc b/doc/manual.asciidoc index e1ae083..8fd5d86 100644 --- a/doc/manual.asciidoc +++ b/doc/manual.asciidoc @@ -949,8 +949,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 <>. -- cgit v0.12