You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c82cc17
Browse filesBrowse the repository at this point in the historyBrowse files
Explain when to pick mswin over the RubyInstaller builds
The README said what mswin is but not when to use it, which leaves users unsure which of the two Windows builds to choose.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,7 @@ Native extensions are automatically compiled with AddressSanitizer when using `r
31
31
Regarding Windows ruby master builds, `mingw` is a MSYS2/MinGW build, and `head` & `ucrt` are MSYS2/UCRT64 builds.
32
32
33
33
`mswin` is CRuby built with MSVC, available on Windows only.
34
+
Use it to test that native extensions build and work with MSVC. The default Windows versions stay on RubyInstaller, which most precompiled gems target.
34
35
`mswin-4.0` installs the latest 4.0.x release and `mswin-head` the master build.
35
36
`mswin` alone also installs the master build for now but will install the latest release in the future, so use `mswin-head` to keep testing master.
36
37
The available versions are listed in [windows-mswin-versions.json](windows-mswin-versions.json).
0 commit comments