Hi,
I don't want to rely on one-click installer anymore and I want to learn how to install ruby manually. Do you have any resource for this?
Thanks a lot.
Cheers
Hi,
I don't want to rely on one-click installer anymore and I want to learn how to install ruby manually. Do you have any resource for this?
Thanks a lot.
Cheers
Well, if you're on a mac I'd recommend macports. There's a good post on it here that's still valid.
If you're on windows and don't want to use the one-click installer you can install cygwin and build ruby through it. Here's a post I found.
I'd start with the one-click installer, probably by taking a good look inside the source on RubyForge (disclaimer, I haven't actually done this...). These guys clearly know how to build Ruby on Windows from source, so I'd be inclined to see how they did it.
Beyond that, did you know you can download the 1.8.7 Windows binary from the ruby-lang.org downloads page? That page also has the current stable 1.8.7 source
setup.rb
gem install rails
, once that installs then do: rails test_project
You might also need libeay32.dll and ssleay32.dll, found in OpenSSL: http://www.slproweb.com/products/Win32OpenSSL.html
I've pretty much concluded that Ruby 1.8.7 just isn't stable yet for Windows. I was able to get it running on one Vista machine following the instructions above but not my laptop.
For the laptop I followed the following steps and everything seems to be working so far:
I would only follow these directions as a last resort if the instructions above don't work.
Before you wag a finger at me and scold me for this approach...
please consider that I spent ~8 hours reading and trying everything possible and was able to use the approach above successfully on another computer. I'm open to other suggestions!
If you are looking for a place to get all those *.dll - here is a trick - if you install ruby one-click-installer for ruby 1.8.6 - it has all of those dlls in c:\ruby1.8.6\bin (assuming you installed it there). I was playing with PIK gem (rvm for windows) and ran into that problem for ruby 1.9.1 and after copying those dlls everything worked perfectly. Of course, those dlls are somewhat old, so if ruby1.9.1 or 1.8.7 relies on any new features in those dlls there might be a potential for a bug, but I haven't noticed anything so far and it beats hunting down them on internet.