Skip to content

Commit

Permalink
doc: improved parallel specification
Browse files Browse the repository at this point in the history
PR-URL: #42679
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
mawaregetsuka authored and bengl committed May 30, 2022
1 parent 71074ee commit f90a3d7
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions doc/contributing/building-node-with-ninja.md
Original file line number Diff line number Diff line change
@@ -22,14 +22,14 @@ ninja: Entering directory `out/Release`

The bottom line will change while building, showing the progress as
`[finished/total]` build steps. This is useful output that `make` does not
produce and is one of the benefits of using Ninja. Also, Ninja will likely
compile much faster than even `make -j4` (or
`-j<number of processor threads on your machine>`). You can still pass the
number of processes to run for [Ninja][] using the environment variable `JOBS`.
This will be the equivalent to the `-j` parameter in the regular `make`:
produce and is one of the benefits of using Ninja. When using Ninja, builds
are always run in parallel, based by default on the number of CPUs your
system has. You can use the `-j` parameter to override this behavior,
which is equivalent to the `-j` parameter in the regular `make`:

```bash
JOBS=12 make
make -j4 # With this flag, Ninja will limit itself to 4 parallel jobs,
# regardless of the number of cores on the current machine.
```

## Producing a debug build

0 comments on commit f90a3d7

Please sign in to comment.