diff options
| author | Ehsan Akhgari <ehsan@mozilla.com> | 2016-05-15 21:51:07 -0400 |
|---|---|---|
| committer | Jeremiah Senkpiel <fishrock123@rocketmail.com> | 2016-05-27 18:13:41 -0400 |
| commit | de5020292ee31e67346b9083033f363e98e592d9 (patch) | |
| tree | 59aa0cf8422d1e9ad40cc3c7a9efc15859fcff1a /doc | |
| parent | 8af25a39d32d2383be219fd3a56dc773fe9277b0 (diff) | |
| download | android-node-v8-de5020292ee31e67346b9083033f363e98e592d9.tar.gz android-node-v8-de5020292ee31e67346b9083033f363e98e592d9.tar.bz2 android-node-v8-de5020292ee31e67346b9083033f363e98e592d9.zip | |
build: re-add --ninja option to configure
Ninja is a build backend supported by gyp which is much faster than
Make and is able to parallelize builds across all of the available
cores very well. On my machine, this reduces the average build time
from 5:14 minutes to 4:33 minutes.
Refs: https://github.com/nodejs/node/pull/467
Refs: de224d6e6c9381e71ffee965dbda928802cc438e
PR-URL: https://github.com/nodejs/node/pull/6780
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/guides/building-node-with-ninja.md | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/doc/guides/building-node-with-ninja.md b/doc/guides/building-node-with-ninja.md index 550effa976..eb5791af54 100644 --- a/doc/guides/building-node-with-ninja.md +++ b/doc/guides/building-node-with-ninja.md @@ -2,12 +2,11 @@ The purpose of this guide is to show how to build Node.js using [Ninja][], as doing so can be significantly quicker than using `make`. Please see [Ninja's site][Ninja] for installation instructions (unix only). -To build Node with ninja, there are 4 steps that must be taken: +To build Node with ninja, there are 3 steps that must be taken: -1. Configure the project's OS-based build rules via `./configure` as usual. -2. Use `tools/gyp_node.py -f ninja` to produce Ninja-buildable `gyp` output. -3. Run `ninja -C out/Release` to produce a compiled release binary. -4. Lastly, make symlink to `./node` using `ln -fs out/Release/node node`. +1. Configure the project's OS-based build rules via `./configure --ninja`. +2. Run `ninja -C out/Release` to produce a compiled release binary. +3. Lastly, make symlink to `./node` using `ln -fs out/Release/node node`. When running `ninja -C out/Release` you will see output similar to the following if the build has succeeded: ``` @@ -28,12 +27,12 @@ As such, if you wish to run the tests, it can be helpful to invoke the test runn ## Alias -`alias nnode='./configure && tools/gyp_node.py -f ninja && ninja -C out/Release && ln -fs out/Release/node node'` +`alias nnode='./configure --ninja && ninja -C out/Release && ln -fs out/Release/node node'` ## Producing a debug build The above alias can be modified slightly to produce a debug build, rather than a release build as shown below: -`alias nnodedebug='./configure && tools/gyp_node.py -f ninja && ninja -C out/Debug && ln -fs out/Debug/node node_g'` +`alias nnodedebug='./configure --ninja && ninja -C out/Debug && ln -fs out/Debug/node node_g'` [Ninja]: https://martine.github.io/ninja/ |