@@ -42,16 +42,16 @@ platforms in production.
42
42
| GNU/Linux | Tier 1 | kernel >= 2.6.32, glibc >= 2.12 | x64, arm | |
43
43
| GNU/Linux | Tier 1 | kernel >= 3.10, glibc >= 2.17 | arm64 | |
44
44
| macOS/OS X | Tier 1 | >= 10.11 | x64 | |
45
- | Windows | Tier 1 | >= Windows 7/2008 R2/2012 R2 | x86, x64 | vs2017 |
46
- | SmartOS | Tier 2 | >= 15 < 16.4 | x86, x64 | see note1 |
45
+ | Windows | Tier 1 | >= Windows 7/2008 R2/2012 R2 | x86, x64 | [ 2 ] ( #fn2 ) , [ 3 ] ( #fn3 ) , [ 4 ] ( #fn4 ) |
46
+ | SmartOS | Tier 2 | >= 15 < 16.4 | x86, x64 | [ 1 ] ( #fn1 ) |
47
47
| FreeBSD | Tier 2 | >= 10 | x64 | |
48
48
| GNU/Linux | Tier 2 | kernel >= 3.13.0, glibc >= 2.19 | ppc64le >=power8 | |
49
49
| AIX | Tier 2 | >= 7.1 TL04 | ppc64be >=power7 | |
50
50
| GNU/Linux | Tier 2 | kernel >= 3.10, glibc >= 2.17 | s390x | |
51
51
| GNU/Linux | Experimental | kernel >= 2.6.32, glibc >= 2.12 | x86 | limited CI |
52
52
| Linux (musl) | Experimental | musl >= 1.0 | x64 | |
53
53
54
- note1 - The gcc4.8-libs package needs to be installed, because node
54
+ < em id = " fn1 " >1</ em >: The gcc4.8-libs package needs to be installed, because node
55
55
binaries have been built with GCC 4.8, for which runtime libraries are not
56
56
installed by default. For these node versions, the recommended binaries
57
57
are the ones available in pkgsrc, not the one available from nodejs.org.
@@ -60,19 +60,22 @@ note1 - The gcc4.8-libs package needs to be installed, because node
60
60
by Joyent. SmartOS images >= 16.4 are not supported because
61
61
GCC 4.8 runtime libraries are not available in their pkgsrc repository
62
62
63
- * Note* : On Windows, running Node.js in windows terminal emulators like ` mintty `
64
- requires the usage of [ winpty] ( https://github.com/rprichard/winpty ) for
65
- Node's tty channels to work correctly (e.g. ` winpty node.exe script.js ` ).
63
+ <em id =" fn2 " >2</em >: Tier 1 support for building on Windows is only on 64 bit
64
+ hosts. Support is experimental for 32 bit hosts.
65
+
66
+ <em id =" fn3 " >3</em >: On Windows, running Node.js in Windows terminal emulators
67
+ like ` mintty ` requires the usage of [ winpty] ( https://github.com/rprichard/winpty )
68
+ for the tty channels to work correctly (e.g. ` winpty node.exe script.js ` ).
66
69
In "Git bash" if you call the node shell alias (` node ` without the ` .exe `
67
70
extension), ` winpty ` is used automatically.
68
71
69
- The Windows Subsystem for Linux (WSL) is not directly supported, but the
70
- GNU/Linux build process and binaries should work. The community will only
71
- address issues that reproduce on native GNU/Linux systems. Issues that only
72
- reproduce on WSL should be reported in the
73
- [ WSL issue tracker] ( https://github.com/Microsoft/WSL/issues ) . Running the
74
- Windows binary (` node.exe ` ) in WSL is not recommended, and will not work
75
- without adjustment (such as stdio redirection).
72
+ < em id = " fn4 " >4</ em >: The Windows Subsystem for Linux (WSL) is not directly
73
+ supported, but the GNU/Linux build process and binaries should work. The
74
+ community will only address issues that reproduce on native GNU/Linux
75
+ systems. Issues that only reproduce on WSL should be reported in the
76
+ [ WSL issue tracker] ( https://github.com/Microsoft/WSL/issues ) . Running the
77
+ Windows binary (` node.exe ` ) in WSL is not recommended, and will not work
78
+ without adjustment (such as stdio redirection).
76
79
77
80
### Supported toolchains
78
81
@@ -88,7 +91,7 @@ Depending on host platform, the selection of toolchains may vary.
88
91
89
92
#### Windows
90
93
91
- * Visual Studio 2017 or the Build Tools thereof
94
+ * Visual Studio 2017 with the Windows 10 SDK on a 64 bit host.
92
95
93
96
#### OpenSSL asm support
94
97
0 commit comments