default.
+[[ref_log]]
The Ninja log
~~~~~~~~~~~~~
-[[ref_log]]
-
For each built file, Ninja keeps a log of the command used to build
it. Using this log Ninja can know when an existing output was built
with a different command line than the build files specify (i.e., the
`.ninja_log` will be kept in that directory instead.
+[[ref_versioning]]
Version compatibility
~~~~~~~~~~~~~~~~~~~~~
-[[ref_versioning]]
-
Ninja version labels follow the standard major.minor.patch format,
where the major version is increased on backwards-incompatible
syntax/behavioral changes and the minor version is increased on new
the build correctly. See <<ref_versioning,the discussion of versioning>>.
+[[ref_rule]]
Rule variables
~~~~~~~~~~~~~~
-[[ref_rule]]
A `rule` block contains a list of `key = value` declarations that
affect the processing of the rule. Here is a full list of special
shell-quoted space-separated list of files provided to the `build`
line referencing this `rule`.
+[[ref_dependencies]]
Build dependencies
~~~~~~~~~~~~~~~~~~
-[[ref_dependencies]]
There are three types of build dependencies which are subtly different.
foo = bar
----
+[[ref_scope]]
Evaluation and scoping
~~~~~~~~~~~~~~~~~~~~~~
-[[ref_scope]]
Top-level variable declarations are scoped to the file they occur in.