Commit 026ae9d
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -22,14 +22,14 @@ ninja: Entering directory `out/Release` | |||
| 22 | 22 | ||
| 23 | 23 | The bottom line will change while building, showing the progress as | |
| 24 | 24 | `[finished/total]` build steps. This is useful output that `make` does not | |
| 25 | - produce and is one of the benefits of using Ninja. Also, Ninja will likely | ||
| 26 | - compile much faster than even `make -j4` (or | ||
| 27 | - `-j<number of processor threads on your machine>`). You can still pass the | ||
| 28 | - number of processes to run for [Ninja][] using the environment variable `JOBS`. | ||
| 29 | - This will be the equivalent to the `-j` parameter in the regular `make`: | ||
| 25 | + produce and is one of the benefits of using Ninja. When using Ninja, builds | ||
| 26 | + are always run in parallel, based by default on the number of CPUs your | ||
| 27 | + system has. You can use the `-j` parameter to override this behavior, | ||
| 28 | + which is equivalent to the `-j` parameter in the regular `make`: | ||
| 30 | 29 | ||
| 31 | 30 | ```bash | |
| 32 | - JOBS=12 make | ||
| 31 | + make -j4 # With this flag, Ninja will limit itself to 4 parallel jobs, | ||
| 32 | + # regardless of the number of cores on the current machine. | ||
| 33 | 33 | ``` | |
| 34 | 34 | ||
| 35 | 35 | ## Producing a debug build | |
0 commit comments