Commit 0f0bc98
doc: improve ninja build for --built-in-modules-path
The current ninja build does not work with `--node-builtin-modules-path`
flag without passing `--ninja` as it will use `make` to build from
scratch again.
PR-URL: #53007
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>1 parent e2211a0 commit 0f0bc98
1 file changed
Lines changed: 6 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -7,6 +7,12 @@ doing so can be significantly quicker than using `make`. Please see | |||
| 7 | 7 | [Ninja][] is supported in the Makefile. Run `./configure --ninja` to configure | |
| 8 | 8 | the project to run the regular `make` commands with Ninja. | |
| 9 | 9 | ||
| 10 | + When modifying only the JS layer in `lib`, you can use: | ||
| 11 | + | ||
| 12 | + ```bash | ||
| 13 | + ./configure --ninja --node-builtin-modules-path "$(pwd)" | ||
| 14 | + ``` | ||
| 15 | + | ||
| 10 | 16 | For example, `make` will execute `ninja -C out/Release` internally | |
| 11 | 17 | to produce a compiled release binary, It will also execute | |
| 12 | 18 | `ln -fs out/Release/node node`, so that you can execute `./node` at | |
0 commit comments