Skip to content

Commit c82cc17

Browse files
hsbtclaude
andcommitted
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>
1 parent c0b352c commit c82cc17

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

‎README.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ Native extensions are automatically compiled with AddressSanitizer when using `r
3131
Regarding Windows ruby master builds, `mingw` is a MSYS2/MinGW build, and `head` & `ucrt` are MSYS2/UCRT64 builds.
3232

3333
`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.
3435
`mswin-4.0` installs the latest 4.0.x release and `mswin-head` the master build.
3536
`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.
3637
The available versions are listed in [windows-mswin-versions.json](windows-mswin-versions.json).

0 commit comments

Comments
 (0)