summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/manual.asciidoc24
1 files changed, 13 insertions, 11 deletions
diff --git a/doc/manual.asciidoc b/doc/manual.asciidoc
index 8ab2195..9506f0c 100644
--- a/doc/manual.asciidoc
+++ b/doc/manual.asciidoc
@@ -134,6 +134,9 @@ but they are not part of make itself.)
Getting started
---------------
+Start by downloading the code from
+https://github.com/martine/ninja[the github repo].
+
The included `bootstrap.sh` should hopefully produce a working `ninja`
binary, by first blindly compiling all non-test files together then
re-building Ninja using itself.
@@ -265,10 +268,10 @@ The special rule name `phony` can be used to create aliases for other
targets. For example:
----------------
-build all: phony some/file/in/a/faraway/subdir
+build foo: phony some/file/in/a/faraway/subdir/foo
----------------
-This makes `ninja all` build the other files. Semantically, the
+This makes `ninja foo` build the longer path. Semantically, the
`phony` rule is equivalent to a plain rule where the `command` does
nothing, but phony rules are handled specially in that they aren't
printed when run, logged (see below), nor do they contribute to the
@@ -323,16 +326,15 @@ it will generate the appropriate syntax.
Integration with other build systems
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-*gyp* A work-in-progress patch to http://gyp.googlecode.com[gyp, the
-system used to generate build files for the Chromium browser] to
-generate ninja files for Linux is available from
-https://github.com/martine/gyp/tree/ninja[my "ninja" branch of the
-upstream gyp project]. To use it, put that branch in place of
-Chromium's gyp, set `GYP_GENERATORS=ninja` in your environment, and
-run `./build/gyp_chromium` to regenerate the build files.
+*gyp*. http://gyp.googlecode.com[gyp, the system used to generate build
+files for the Chromium browser] can generate ninja files for Linux.
+See http://code.google.com/p/chromium/wiki/NinjaBuild[the Chromium
+Ninja documentation] for details.
-*CMake*. I have heard from people who have been working on generating
-Ninja files from CMake, but I don't think it's in a working state yet.
+*CMake*. Various people have worked on generating Ninja files from
+CMake. Currently, it sounds like
+https://github.com/pcc/CMake/tree/ninja-generator[pcc's branch] is the
+one to try.
*Autotools*. In theory, you could coax Automake into producing
.ninja files as well, but I haven't tried it. It may very well be the