diff options
author | Evan Martin <martine@danga.com> | 2013-04-19 21:38:23 (GMT) |
---|---|---|
committer | Evan Martin <martine@danga.com> | 2013-04-19 21:38:23 (GMT) |
commit | c57fd1a903cb342dc414307088352cdb550d3641 (patch) | |
tree | 61afaeb95b4e95febfb62721e80bac9d80cfd25d /src/state.cc | |
parent | 0275ead49797dc5b5723d89205bafcd7c313a76d (diff) | |
download | Ninja-c57fd1a903cb342dc414307088352cdb550d3641.zip Ninja-c57fd1a903cb342dc414307088352cdb550d3641.tar.gz Ninja-c57fd1a903cb342dc414307088352cdb550d3641.tar.bz2 |
adjust the wording in "multiple rules generate X" warning
Ideally we'd detect this at build time and only warn if your build
was affected, but that's hard to do. (Really we should just abort
when this scenario is detected rather than continuing, but now
users are relying on it.)
Hopefully improves issue #543.
Diffstat (limited to 'src/state.cc')
-rw-r--r-- | src/state.cc | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/state.cc b/src/state.cc index d2d5ebe..9b6160b 100644 --- a/src/state.cc +++ b/src/state.cc @@ -154,7 +154,8 @@ void State::AddOut(Edge* edge, StringPiece path) { edge->outputs_.push_back(node); if (node->in_edge()) { Warning("multiple rules generate %s. " - "build will not be correct; continuing anyway", + "builds involving this target will not be correct; " + "continuing anyway", path.AsString().c_str()); } node->set_in_edge(edge); |