RubyInstaller 2.1.4 released

Ruby 2.1.4

This new version of Ruby also brings new changes to RubyInstaller.

Similar to 2.0.0, the packages will be provided in two versions:
32bits (x86) and 64bits (x64).

This is possible thanks to newer compiler provided by mingw-w64 project.

Same DevKit used for version 2.0.0 is required for this version.

Important information

Please note that the installers in this release are not digitally
signed
.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

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.

It is our recommendation you use 32bits until these issues are solved.

If you have a 64bits version of Windows, you can still use 32bits, as
there
is no performance issue around it.

Ruby 2.1.x is brand new

While officially 2.1.x is stable, that doesn’t mean all the software
will
magically work on it.

Use 2.1.4 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.1 compatible

Ruby 2.1 introduces ABI breakage which means compiled C extensions with
previous
1.9.3 or 2.0.0 will not run against Ruby 2.1.

DO NOT install Ruby 2.1 on top of existing Ruby 1.9.3 or 2.0.0, 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.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

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:

MD5:

df20891e25c1b72fe9f66a9ba95dd7e7 *ruby-2.1.4-doc-chm.7z
fcfba33c49495371dbe24d4534a286ff *ruby-2.1.4-i386-mingw32.7z
debe002022929b0afff5bad8f4d5039c *ruby-2.1.4-x64-mingw32.7z
cba755c388c2254d0182b00dc0726dd0 *rubyinstaller-2.1.4-x64.exe
56ce24a6bd422adb3e21b903cc1818cf *rubyinstaller-2.1.4.exe

SHA256

df8b6c928672ab85b83ba1cd123ca0a932e3a691496c320f7919a89ea7b52f10

*ruby-2.1.4-doc-chm.7z
a0909ee86b8e2492e3696f4a7decd9dbe041562cdf66a5bc0080c239e68ca7fe
*ruby-2.1.4-i386-mingw32.7z
c6148c9521cd167c1c8eff4b14bf8caba079cccc4f7e8c5e00e7299f3cca2ab3
*ruby-2.1.4-x64-mingw32.7z
7abd94bb78f3dbecbb02a2370b05cdbd1dbf176afe887b66c742f506cf32472a
*rubyinstaller-2.1.4-x64.exe
1155b8eab79f6818ae4b09fec6a180da31c8bed6f81c3747ce5a6434b37c6d86
*rubyinstaller-2.1.4.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/10/27/ruby-2-1-4-released/

Enhancements:

  • Upgraded Ruby 2.1 to version 2.1.4