summaryrefslogtreecommitdiffstats
path: root/HACKING.md
diff options
context:
space:
mode:
authorKulak <sergei.gnezdov@gmail.com>2017-09-28 22:02:14 (GMT)
committerGitHub <noreply@github.com>2017-09-28 22:02:14 (GMT)
commitaa44a55f67f79cfb52cb590e956d5067f343276c (patch)
tree2d8cadc66e84c8b6a9c1de99246ee495b6baa935 /HACKING.md
parentb26168be150bd1cbdd6daca59f53755a56fe7939 (diff)
downloadNinja-aa44a55f67f79cfb52cb590e956d5067f343276c.zip
Ninja-aa44a55f67f79cfb52cb590e956d5067f343276c.tar.gz
Ninja-aa44a55f67f79cfb52cb590e956d5067f343276c.tar.bz2
correction of location of binary
original said "source root", but actual location is project root. Perhaps it is mean to be "src" parent, but that's a bit confusing.
Diffstat (limited to 'HACKING.md')
-rw-r--r--HACKING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/HACKING.md b/HACKING.md
index e7c91ef..9198bdf 100644
--- a/HACKING.md
+++ b/HACKING.md
@@ -13,7 +13,7 @@ run `ninja_test` when developing.
Ninja is built using itself. To bootstrap the first binary, run the
configure script as `./configure.py --bootstrap`. This first compiles
all non-test source files together, then re-builds Ninja using itself.
-You should end up with a `ninja` binary (or `ninja.exe`) in the source root.
+You should end up with a `ninja` binary (or `ninja.exe`) in the project root.
#### Windows