diff options
author | Brad King <brad.king@kitware.com> | 2015-07-13 19:25:50 (GMT) |
---|---|---|
committer | Brad King <brad.king@kitware.com> | 2016-02-03 14:37:17 (GMT) |
commit | cc39240a10fb040fca80bf3669245f2f2d5736c5 (patch) | |
tree | 0b26230a0dd1dde9514dbbe7d6f06a3402c6e8b3 /src/graph.cc | |
parent | f1f3f494f5f67a4cd64b0cddaad472b070f6db07 (diff) | |
download | Ninja-cc39240a10fb040fca80bf3669245f2f2d5736c5.zip Ninja-cc39240a10fb040fca80bf3669245f2f2d5736c5.tar.gz Ninja-cc39240a10fb040fca80bf3669245f2f2d5736c5.tar.bz2 |
Add support for build statement implicit outputs
Some build rules produce outputs that are not mentioned on the command
line but that should be part of the build graph. Such outputs should
not be named in the `$out` variable. Extend the build statement syntax
to support specification of implicit outputs using the syntax
`| out1 out2` after the explicit outputs and before the `:`.
For example, compilation of a Fortran source file `foo.f90` that defines
`MODULE FOO` may now be specified as:
rule fc
command = f95 -c $in -o $out
build foo.o | foo.mod: fc foo.f90
The `foo.mod` file is an implicit output generated by the compiler based
on the content of the source file and not mentioned on the command line.
Diffstat (limited to 'src/graph.cc')
-rw-r--r-- | src/graph.cc | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/graph.cc b/src/graph.cc index 9e65675..3391305 100644 --- a/src/graph.cc +++ b/src/graph.cc @@ -241,8 +241,9 @@ string EdgeEnv::LookupVariable(const string& var) { edge_->inputs_.begin() + explicit_deps_count, var == "in" ? ' ' : '\n'); } else if (var == "out") { + int explicit_outs_count = edge_->outputs_.size() - edge_->implicit_outs_; return MakePathList(edge_->outputs_.begin(), - edge_->outputs_.end(), + edge_->outputs_.begin() + explicit_outs_count, ' '); } |