
- RUBY DOWNLOAD FOR WINDOWS INSTALL
- RUBY DOWNLOAD FOR WINDOWS 32 BIT
- RUBY DOWNLOAD FOR WINDOWS ARCHIVE
- RUBY DOWNLOAD FOR WINDOWS PORTABLE
This config # file is generated by the 'ruby dk.rb init' step and may be modified # before running the 'ruby dk.rb install' step. # This configuration file contains the absolute path locations of all # installed Rubies to be enhanced to work with the DevKit.

We should see what has been written to the configuration file. These are only Rubies that are supported by DevKit at the moment. Keys that are searched are Software\RubyInstaller\MRI and Software\RubyInstaller\Rubinius. Finally it stores path in the array which is returned as a result of the method.

If it finds one, it reads InstallLocation string value and replaces Windows path separator, backslash ( '\'), with path separator which is correctly handled by MinGW – forward slash ( '/'). This is regular expression that corresponds to three numbers ( \d) separated by dots ( \.). Script searches key within HKLM ( HKEY_LOCAL_MACHINE) and HKCU ( HKEY_CURRENT_USER) passed as an argument for sub-key that matches version pattern /\d\.\d\.\d/. gsub ( '\\', '/' ) puts ' found RubyInstaller v%s at %s' % ris << ri_root end end end end rescue Win32 :: Registry :: Error end end ris end open ( skey ) do | ver_key | ri_root = ver_key.
RUBY DOWNLOAD FOR WINDOWS INSTALL
each_key do | skey, wtime | # read the install location if a version subkey if skey =~ /\d\.\d\.\d/ ri_key.

Let's execute it now and check the output:ĭef self. You will find dk.rb file in C:\Ruby\DevKit directory. RubyInstaller's DevKit comes with Ruby script, dk.rb, that is used to inject it to all Ruby versions you have installed on the system. Before you go on with DevKit installation check your system for any of these. bash_profile) in user's home directory and these files can be a cause of DevKit malfunctioning. Usually these tools keep their configuration files (. If you have Cygwin or other MSYS/MinGW build tools in the path you should remove them. You have to take some precautions if you want to assure proper DevKit functioning. Throughout the book I'll assume DevKit is located at C:\Ruby\DevKit. It is recommended to unpack DevKit to a path without spaces since MSYS tools do not handle such paths correctly.
RUBY DOWNLOAD FOR WINDOWS ARCHIVE
Go ahead and download RubyInstaller's Ruby DevKit self extracting archive and unpack it.
RUBY DOWNLOAD FOR WINDOWS 32 BIT
For Ruby 2.2 DevKit is based on 32 bit MinGW 4.7.2 compiler suite for Windows. It is a set of MSYS and MinGW based build tools that make it easy and simple to build native C/C++ Ruby extensions. One of the goals of RubyInstaller project was to make it possible to install gems written in C/C++ on Windows. No matter if you use Linux, OS X or Windows operating system you must have build tools in order to install such gems.
/Tk-Demo_using_Tk_8.6.6_on_Windows_10_November_2016-5c5b182d46e0fb0001849b10.jpg)
Second type of gems are written in C/C++ and require build tools capable of compiling C/C++ source and creating shared libraries. First type of gems are either completely written in Ruby or have pre-built binaries for a system they are installed on. Gems that during installation do not require external tools and those that require them. Ruby gems can roughly be divided into two types.
RUBY DOWNLOAD FOR WINDOWS PORTABLE
