Remove phony edges for nodes created by a dependency loader.

This patch simplifies Ninja internals without modifying
its behavior. It removes the creation (and removal) of phony
edges as producers for nodes loaded by dependency loaders, i.e.
coming from depfiles, dyndep files or the deps log.

These edges were only used to ensure the build did not
abort when these files are missing, unlike regular source
inputs. This can be easily checked by adding a new flag to
the Node class instead. This makes it easier to reason about
how Ninja works internally.

More specifically:

- Move the generated_by_dep_loader_ flag from the Edge class
  to the Node class. The flag is true by default to minimize
  changes to the source code, since node instances can be
  first created by reading the deps or build logs before
  the manifest itself.

- Modify Plan::AddSubTarget() to avoid aborting the build
  when a generated-by-deploader node is missing. Instead
  the function exits immediately, which corresponds to
  what happened before.

- State::AddOut(), State::AddIn(), State::AddValidation():
  Ensure that nodes added by these methods, which are
  only called from the manifest parser and unit-tests
  set the |generated_by_dep_loader_| flag to false, to
  indicate that these are regular input / output nodes.

- ManifestParser::ParseEdge(): Add an assertion verifying
  that the dyndep file is marked as a regular input.

- DyndepLoader::UpdateEdge(): Remove code path that
  looked for phony in-edges and ignored them.

- DepLoader::CreatePhonyInEdge() is removed as no
  longer necessary.

+ Update a few places in unit-tests that were checking
  for the creation of the phony edges.

Fuchsia-Topic: persistent-mode
Change-Id: I98998238002351ef9c7a103040eb8a26d4183969
8 files changed
tree: 24b3aee9fc9d25ac92539459242a82d895fd7c15
  1. .github/
  2. doc/
  3. misc/
  4. src/
  5. windows/
  6. .clang-format
  7. .clang-tidy
  8. .editorconfig
  9. .gitignore
  10. appveyor.yml
  11. CMakeLists.txt
  12. configure.py
  13. CONTRIBUTING.md
  14. COPYING
  15. README.md
  16. RELEASING.md
README.md

Ninja

Ninja is a small build system with a focus on speed. https://ninja-build.org/

See the manual or doc/manual.asciidoc included in the distribution for background and more details.

Binaries for Linux, Mac and Windows are available on GitHub. Run ./ninja -h for Ninja help.

Installation is not necessary because the only required file is the resulting ninja binary. However, to enable features like Bash completion and Emacs and Vim editing modes, some files in misc/ must be copied to appropriate locations.

If you're interested in making changes to Ninja, read CONTRIBUTING.md first.

Building Ninja itself

You can either build Ninja via the custom generator script written in Python or via CMake. For more details see the wiki.

Python

./configure.py --bootstrap

This will generate the ninja binary and a build.ninja file you can now use to build Ninja with itself.

CMake

cmake -Bbuild-cmake
cmake --build build-cmake

The ninja binary will now be inside the build-cmake directory (you can choose any other name you like).

To run the unit tests:

./build-cmake/ninja_test