I started developing ruby more than a year ago, on windows, which might not be the ideal platform :)

But i started out with the standard one-click installer, ruby version 1.8.6, which up until recently served me fine and is an easy way to start. But when i felt the need to install metric_fu, i found out it just does not install on top of the old ruby 1.8.6 (mswin32). Now i know that for ruby 1.8.7 (mingw32) a development kit exists, which would allow compilation of all native code. So, normally, all plugins that were giving me problems before (e.g. thin!) should be able to be installed using that.

Also the new rubyinstaller versions are known to be quicker, because they are using a more recent and efficient compiler (mingw), and ruby 1.9.1 should inherently be even more efficient (by design). But i was looking for an easy way to migrate and test ruby versions. I know that there exist a ruby version manager (rvm), but it only works on linux and mac. But luckily, for windows, there is pik.

It is really easy to install:

> gem install pik

> pik_install c:\windows\system32

[the choice to use windows\system32 is maybe not entirely kosher, but it is an easy way to add something to the path, always ;) Maybe i should have used c:\ruby\pik\bin and added that to the path.]

Then add the current version as the default:

> ruby -v
ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32]
> pik add
Adding:  186: ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32]
   Located at:  c:/ruby/bin

Then you can download the new versions, e.g. ruby 1.8.7. and 1.9.1 from rubyinstaller and install them each into their own folder. E.g. c:\ruby\187-p249\ and then issue the following command:

> pik add c:\ruby\1.8.7-p249\bin
> pik add c:\ruby\1.9.1-p378\bin
** Adding:  191: ruby 1.9.1p378 (2010-01-10 revision 26273) [i386-mingw32]
 Located at:  c:\ruby\1.9.1-p378\bin
> pik list
186: ruby 1.8.6 (2008-08-11 patchlevel 287) [i386-mswin32] *
187: ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]
191: ruby 1.9.1p378 (2010-01-10 revision 26273) [i386-mingw32]

But of course, the second problem is that the one-click installer also includes a lot gems by default, while the new rubyinstaller is almost empty.

So first i installed the development kit from rubyinstaller. I needed to extract that inside the each ruby folder, and change a few settings (configure), like described here, i needed to edit my /devkit/msys/1.0.11/etc/fstab settings file, and replace c:\ruby by my actual ruby-installation folder, in my case something like c:\ruby\1.8.7-p249.

I create a small batch-file to install all the missing gems:

rem default windows gems

call gem install win32-api
call gem install win32-clipboard
call gem install win32-dir
call gem install win32-eventlog
call gem install win32-file
call gem install win32-file-stat
call gem install win32-process
call gem install win32-sapi
call gem install win32-service
call gem install win32-sound
call gem install win32console
call gem install windows-api
call gem install windows-pr

call gem install hpricot
call gem install nokogiri

call gem install wxruby


call gem install rails
call gem install will_paginate
call gem install mongrel
call gem install mongrel_service
call gem install formtastic

rem database gems

call gem install sqlite3-ruby
call gem install ruby-oci8
call gem install activerecord-oracle_enhanced-adapter

call gem install builder

call gem install calendar_date_select
call gem install cgi_multipart_eof_fix
call gem install composite_primary_keys
call gem install log4r
call gem install ezcrypto

rem testing

call gem install cucumber
call gem install cucumber-rails

call gem install factory_girl

call gem install remarkable
call gem install rspec
call gem install rspec-rails

But i still encountered an error on the gems that needed to build native extensions:

C:\WINDOWS>gem install hpricot
Building native extensions.  This could take a while...
ERROR:  Error installing hpricot:
        ERROR: Failed to build gem native extension.

c:/Ruby/1.9.1-p378/bin/ruby.exe extconf.rb
checking for stdio.h... yes
creating Makefile

MAKE Version 5.2  Copyright (c) 1987, 2000 Borland
Fatal: '/c/Ruby/1.9.1-p378/include/ruby-1.9.1/ruby.h' does not exist - don't know how to make it

Gem files will remain installed in c:/Ruby/1.9.1-p378/lib/ruby/gems/1.9.1/gems/hpricot-0.8.2 for inspection.
Results logged to c:/Ruby/1.9.1-p378/lib/ruby/gems/1.9.1/gems/hpricot-0.8.2/ext/fast_xs/gem_make.out

It took a good nights rest to figure that one out: i have Borland’s Cbuilder 5 installed on my system to be able to maintain ancient software. So i had to remove that entry from my path, and after that all gems that needed native building went smoothly, except mongrel_service.
Now everything installed just fine, inside my 1.8.7 system. Doing the same on ruby 1.9.1 took a lot longer, or so it seemed definitely. I think partly that is because ruby 1.9.1 seems to maintain a class cache? But i am not sure of that.
But what surprised me even more is that actually all gems installed without any problem, except win32-service and because of that, mongrel_service. As explained here, this issue is known and due to the fact that the library relies on specific MSVC behaviour that mingw does not support. But i think i can create a service from about any executable or batch file.

But i read here that i have to issue the following command:

c:\ruby> gem install mongrel_service --prerelease

The pre-release version removes the dependency of win32-service, and so it works again.

So now i can start testing my applications inside 1.8.7 and 1.9.1 on windows, try using thin, and get metric_fu up and running.