Packages will be provided in two versions:
32bits (x86) and 64bits (x64).
Same DevKit used for version 2.0.0 is required for this version.
Please note that the installers in this release are not digitally signed.
You can read more about this in post at RubyInstaller group:
Choosing 32bits vs 64bits
Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.
Things are pretty close, however it is still our recommendation you use a 32bit release.
If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.
Ruby 2.3.X is brand new
While officially 2.3 is stable, that doesn't mean all the software will magically work on it.
Use 2.3 for development and verify your application, scripts and tools works properly before deciding to run this in your production environment.
Existing pre-compiled gems might not be Ruby 2.# compatible
Ruby 2.3 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.3.
DO NOT install Ruby 2.3 on top of existing Ruby 2.2.x or earlier, or try to use compiled extensions with it.
You will be required to force compilation of those gems:
gem install <name> --platform=ruby
This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.
Please check each gem documentation and recent releases.
Do not use other DevKit version than the one recommended
This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.
Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.
Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.
To be clear:
- Download and install
DevKit-mingw64-32-4.7.2for 32bits Ruby
- Download and install
DevKit-mingw64-64-4.7.2for 64bits Ruby
There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:
388524ce450123c25e2d799f6a670b96 *ruby-2.3.3-doc-chm.7z 0baf1559473512468d150df14a20a37a *ruby-2.3.3-i386-mingw32.7z 7ec844390d2e66cfa5fa5a6d1cebc80a *ruby-2.3.3-x64-mingw32.7z b2688631f3eac70dc45a1735ba8ef748 *rubyinstaller-2.3.3-x64.exe 0447f419345bcad7e34dbca8d42b09d0 *rubyinstaller-2.3.3.exe
6e011a18ffa34b40301be3c2dfffa81df3012e98e0e93575052b8d5314f45ebe *ruby-2.3.3-doc-chm.7z 5022ef928f0296abede90f1cf4346250d69f6298c648cad6279938f64eca29fa *ruby-2.3.3-i386-mingw32.7z 92b97ac3eb380f3f1b7b655a328668cf02b2846ad3c20135bd51f45f4c1cbfc8 *ruby-2.3.3-x64-mingw32.7z 3d0a4ad06c5503e1cb88827443593969e689ac96b5161140b08f0becb7b792cf *rubyinstaller-2.3.3-x64.exe 43110f9bcd8a067d69409507cad6a43f1fcf05e8bd64d096dd9df47475de50f3 *rubyinstaller-2.3.3.exe
- Upgraded Ruby 2.3 to 2.3.3
- Upgraded OpenSSL to 1.0.2j
- Upgraded libffi to 3.2.1
- Upgraded LibYAML to 0.1.7
- Upgraded tcl & tk to 8.5.19