If you want to install the archive, extract it to your favorite directory (we call it $TOPDIR).
And after that, add $TOPDIR\bin to PATH environment variable.
Some extension libraries depend on DLLs that are not included theses packages.
- curses.so : depend of PDCurses
- dbm.so : depend on GDBM
- gdbm.so : depend on GDBM
- iconv.so : depend on Iconv
- openssl.so : depend on OpenSSL
- readline.so : depend on readline
- tcltklib.so : depend on Tcl/Tk
- zlib.so : depend on Zlib
You can get binaries of PDCurses, GDBM, OpenSSL, readline and Zlib at Porting Libraries to Win32.
You can get binary of Iconv at Meadowy.org; iconv-1.8.win32.zip
You can get binary of Tcl/Tk at ActiveState; ActiveTcl
When using the x64-mswin64 binary, you have to install this package.
Ruby-mswin32 is a Ruby binary which runs on 32bit versions of Windows (Windows95, Windows98, Windows Me, Windows NT, Windows 2000, WindowsXP, Windows 2003 Server, Windows Vista and Windows Server 2008).
There are 6 ports which run on Windows. They are called mswin32, cygwin, mingw32, bccwin32, interix, and djgpp.
The differences are...
- mswin32
-
Compiled by Microsoft Visual C++. This is the most 'standard' binary from the common point-of-view in the Windows world. But we cannot use some parts of characteristic functions which ruby on UNIX has. After 1.7.3, mswin32 has binary level compatibility of extension libraries with mingw32.
RUBY_PLATFORM is *-mswin32.
- cygwin
-
Compiled by gcc, and run on cygwin environment. Cygwin environment provides Windows with UNIX-like environment, so, ruby-cygwin runs about like ruby on UNIX (expectably).
RUBY_PLATFORM is *-cygwin.
- mingw32
-
Compiled by gcc. Since most of the source code of ruby-mingw32 is the same as ruby-mswin32, the behaviors of it are almost the same as that of ruby-mswin32 (probably). After 1.7.3, mingw32 has binary level compatibility of extension libraries with mswin32.
RUBY_PLATFORM is *-mingw32.
- bccwin32
-
Compiled by Borland C++. Most source code of ruby-bccwin32 are as common as ruby-mswin32, but the runtime library is not same. So, there are some little differences with the behaviors (probably). This is officially supported with version 1.7 or later.
RUBY_PLATFORM is *-bccwin32.
- interix
-
Compiled by gcc, and run on SFU(Services for UNIX) environment. SFU environment provides Windows with POSIX compatible environment, so, ruby-interix runs like ruby on UNIX (hopefully).
RUBY_PLATFORM is *-interix3.
- djgpp
-
Compiled by DJGPP. This binary is for DOS, so it can run on DOS, too. We cannot use many of functions which are in Windows and are not in DOS (networking, dynamic extensions loading, etc.).
RUBY_PLATFORM is *-msdosdjgpp.
On this site, only mswin32 is treated among the above. You can find others (cygwin, mingw32, and djgpp) on Ruby binaries written by Mr. Watanabe. And you can find bccwin32 on Ruby written by Mr. Konishi (but the page is written in Japanese). And you can find interix on Tool Warehouse for SFU/Interix.
After 1.9.0, 64bit versions Windows (x64 editions of Windows XP, Windows 2003 Server, Windows Vista and Windows Server 2008) are also supported. (IA64 editions are maybe supported, too, but no one tested it).
This site also treats mswin64 version of ruby.
This site is to distribute Ruby-mswin32 binaries and to announce recent changes to the Ruby-mswin32 source tree.
This is NOT the offcial site of Ruby.
You should use the binaries that you can get from here on your own risk.
If you have some comments or questions, please send e-mail to me.
Please tell me if you feel that some sentences are funny-sounding. Since I'm not familiar with English, there will be many funny-sounding sentences.
Ruby is an object-oriented script language.
Please see Ruby official site.
comment
Wolfgang Nadasi-Donner [After installing the package for Ruby 1.9 () I stated it an got the following error Message (Example):]usa [Unset RUBYOPT environment variable.]
Kal [How do I install the dependent dlls? Do I just download the zip files and extract the dll files to "$TOPDIR\bin"? Some of the packages also contain other files (like exe files) in their respective "bin" directories; do I need those as well? What about ActiveTcl? That thing comes with an installer; so do I just install it through the installer or do I need to copy some files as well?]
usa [Install them to the directory for which you hope. Of course, don't forget to set PATH for such directories. "$TOPDIR\bin" is one of the good choices.]
Kal [I'm confused. >_<]
Claus Folke Brobak [I am wondering why the old "zlib-1.1.4" (zlib.dll) is required and not the newer "zlib-1.2.x" (zlib1.dll)? The "One-Click Installer" seems to use the newer "zlib-1.2.x". You can read more here: "http://www.zlib.net/DLL_FAQ.txt".]
Bek [Renaming the file 'zlib1.dll' in '%your_ruby_install_path%/bin' in 'zlib.dll' should fix the problem.]
Zuzi [After run commands of the Ruby, some error raided saying **.dll can not be found. eg. readline.dll when using irb. How to solve the problem? The version i use is 1.9.1 binary - mswin32.]
Nick [These commands are barely legible. They don't spell out clear dependencies in that they don't include version numbers. At the very least the links should be directly to a file.]
Eckhard [I got some error messages that indicates a problem with the OpenSSl library I downloaded via the link above.]
Goran [This is so not helping anybody! Thank ya!]
Keygen Kyleigh [It's really provoking point of view. ]
jayden [That's very thought-provoking point of view. I intend to return to this site very soon.]
serialpost [A very good web site..The content needs to be updated more often. The videos have been up for some time ]