PersistentService::Server simplification.

*Considerably* simplify the server implementation by
leveraging the IpcService class and its AcceptPeer()
method.

Using IpcService also fixes the server code for Win32,
as before this CL, waiting for the second client
connection in the server loop would always fail.

This removes the only AsyncHandle::StartAccept() call
from the source code, and AsyncHandle::StartConnect()
is never used outside of unit-tests. A future patch
will remove these two methods.

This also removes the last use of IpcServiceHandle, a
future patch will remove this class entirely.

Fuchsia-Topic: persistent-mode
Change-Id: I5aa72a6433f9259ed33ed23af35c59b4e1f40a98
Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/github.com/ninja-build/ninja/+/1008196
Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
Fuchsia-Auto-Submit: David Turner <digit@google.com>
Reviewed-by: David Fang <fangism@google.com>
5 files changed
tree: 03bcdbdf7a6dd815fa9994efcbc63b1414d3bbd3
  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.fuchsia
  16. README.md
  17. 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