diff options
Diffstat (limited to 'ninja/doc')
| -rw-r--r-- | ninja/doc/manual.asciidoc | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/ninja/doc/manual.asciidoc b/ninja/doc/manual.asciidoc index aa5644d6451..a7352571c84 100644 --- a/ninja/doc/manual.asciidoc +++ b/ninja/doc/manual.asciidoc @@ -54,7 +54,7 @@ Here are the design goals of Ninja: higher-level build systems have different opinions about how code should be built; for example, should built objects live alongside the sources or should all build output go into a separate directory? - Is there an "package" rule that builds a distributable package of + Is there a "package" rule that builds a distributable package of the project? Sidestep these decisions by trying to allow either to be implemented, rather than choosing, even if that results in more verbosity. @@ -588,6 +588,7 @@ rule cc command = cl /showIncludes -c $in /Fo$out ---- +[[ref_pool]] Pools ~~~~~ @@ -668,6 +669,9 @@ A file is a series of declarations. A declaration can be one of: +include _path_+. The difference between these is explained below <<ref_scope,in the discussion about scoping>>. +6. A pool declaration, which looks like +pool _poolname_+. Pools are explained + <<ref_pool, in the section on pools>>. + Lexical syntax ~~~~~~~~~~~~~~ |