I’m very pleased to announce the release of RubyInstaller packages for
Ruby
2.0.0-p594
Installers and 7z binary packages are available from bintray.com:
Ruby 2.0.0-p594
This new version of Ruby also brings new changes to RubyInstaller.
Starting with 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.
This means newer DevKit package is required to use with 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.0.0 is brand new
While officially 2.0.0 is stable, that doesn’t mean all the software
will
magically work on it.
Use 2.0.0 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.0 compatible
Ruby 2.0 introduces ABI breakage which means compiled C extensions with
previous
1.9.3 will not run against Ruby 2.0.
DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3, 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 older 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:
- For 32bits Ruby 2.0.0: download and install
DevKit-mingw64-32-4.7.2 - For 64bits Ruby 2.0.0: download and install
DevKit-mingw64-64-4.7.2
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:
- 32-bit programs are not detected when using x64-mingw32 builds · Issue #221 · oneclick/rubyinstaller · GitHub
- Make dk.rb support x64 ruby by petemounce · Pull Request #237 · oneclick/rubyinstaller · GitHub
MD5:
9b89cb76941f1ffb821b9cc829644503 *ruby-2.0.0-p594-doc-chm.7z
fa132c0c7965b159f3770002d0138e83 *ruby-2.0.0-p594-i386-mingw32.7z
6e9bdafb2793e6b1d9ffc672235dc6d6 *ruby-2.0.0-p594-x64-mingw32.7z
f55531333d99e7264005088f786e1a64 *rubyinstaller-2.0.0-p594-x64.exe
b42ae989e0faadb0fd47ff2e65d7995f *rubyinstaller-2.0.0-p594.exe
SHA256
ae9ded24b60c748d12e54a61ab7c2eec2a7cac9c9dca74890e8cd5c9694fdf98
*ruby-2.0.0-p594-doc-chm.7z
f64fe7471c84f62db9600a75b80be6cc5dfcf2c0280bcd3eb2ad6c454728dc53
*ruby-2.0.0-p594-i386-mingw32.7z
0089d780afad6762d0dbfff17b96bf2f65b4195aa506cfca31f4e380c2612fcb
*ruby-2.0.0-p594-x64-mingw32.7z
d4f1983d8034e1ac737f7438ae8286771597f6ee09a168058ac3ee762b978076
*rubyinstaller-2.0.0-p594-x64.exe
7cedaed26ddcbf53ddae69ccce9b1171e3558fe3f49cf052b71b5f27b06ad1d7
*rubyinstaller-2.0.0-p594.exe
Official Announcement:
https://www.ruby-lang.org/en/news/2014/10/27/ruby-2-0-0-p594-is-released/
Enhancements:
- Upgraded Ruby 2.0.0 to patchlevel 594
- Upgraded libyaml to version 0.1.6