Skip to content

Commit c22e442

Browse files
authored
docs: add guidance on unsupported architectures to README.md (#160)
This will at least give people a clue of where to start if they want to pre-compile a Node.js binary for an unsupported architecture.
1 parent e8f9863 commit c22e442

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -90,6 +90,14 @@ dashes, for example `node18-macos-x64` or `node14-linux-arm64`:
9090

9191
(element) is unsupported, but you may try to compile yourself.
9292

93+
If your target is available in the assets of the latest [pkg-fetch release](https://github.com/yao-pkg/pkg-fetch/releases),
94+
`pkg` downloads the pre-compiled Node.js binary from that project. Otherwise,
95+
or if you specify the `--build` option, it will build the binary from source
96+
(takes a very long time).
97+
Pre-compiled Node.js binaries for some unsupported architectures and
98+
instructions for using them are available in the [pkg-binaries](https://github.com/yao-pkg/pkg-binaries)
99+
project.
100+
93101
You may omit any element (and specify just `node14` for example).
94102
The omitted elements will be taken from current platform or
95103
system-wide Node.js installation (its version and arch).

0 commit comments

Comments
 (0)