Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: improve ninja build for --built-in-modules-path #53007

Merged
merged 2 commits into from
May 17, 2024
Merged

doc: improve ninja build for --built-in-modules-path #53007

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
562db7d
doc: improve ninja build for --built-in-modules-path
jakecastelli May 15, 2024
a3e30ce
Update doc/contributing/building-node-with-ninja.md
jakecastelli May 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions doc/contributing/building-node-with-ninja.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@ doing so can be significantly quicker than using `make`. Please see
[Ninja][] is supported in the Makefile. Run `./configure --ninja` to configure
the project to run the regular `make` commands with Ninja.

When modifying only the JS layer in `lib`, you can use:

```bash
./configure --ninja --node-builtin-modules-path "$(pwd)"
```

For example, `make` will execute `ninja -C out/Release` internally
to produce a compiled release binary, It will also execute
`ln -fs out/Release/node node`, so that you can execute `./node` at
Expand Down