Yeah, Austin got it right.The official Japanese build of ruby for
windows (ruby-mswin32) uses vc++6, and almost all available binaries
for various extensions are also built with vc++6.
When I moved to vc++7 for 1.8.2 it cause a lot of subtle problems.
Starting with 1.8.4 I'm actually using the ruby-mswin32 build as a
based and adding more extensions on top of it. The have got a number
of things right that I always had problems with (Tk/Tcl support,
iconv, readline, etc.). So it was also a relief to start with a base
where those pieces were already problem included.
Curt
···
On 3/31/06, Austin Ziegler <halostatue@gmail.com> wrote:
On 3/31/06, Joel VanderWerf <vjoel@path.berkeley.edu> wrote:
> Hm, any plans to migrate the One-Click Installer to VC++2003?
...
The One-Click Installer for 1.8.2 was on VC++2003. However, because
the most common free compiler (mingw/msys) was not compatible with it
and any number of other reasons, 1.8.4 is now based on the Ruby 1.8.4
build built in Japan (I'm sorry; my mind is blanking on the name of
the site and the person behind it) which is built with VC6 -- and is
NO LONGER AVAILABLE to users.
That's one reason I'm working on 1.8.4 with VC++ 2005 in my
(completely nonexistent) free time so that people can get VC++ 2005
and *build* things on Windows quickly and easily.
At least once I've figured out how to do it. It's not as easy as it
might first appear, and the *official* version of zlib is never
compiled against anything but MSVCR6.DLL (e.g., VC6) so to have a
compatible zlib, you have to compile it yourself. It's a pain in the
ass.
I need to start proof reading my responses before I hit "Send" -- I'm
embarrassed at the number of grammatical errors in my little post
above! 
···
On 3/31/06, Curt Hibbs <ml.chibbs@gmail.com> wrote:
On 3/31/06, Austin Ziegler <halostatue@gmail.com> wrote:
> On 3/31/06, Joel VanderWerf <vjoel@path.berkeley.edu> wrote:
> > Hm, any plans to migrate the One-Click Installer to VC++2003?
>
> ...
>
> The One-Click Installer for 1.8.2 was on VC++2003. However, because
> the most common free compiler (mingw/msys) was not compatible with it
> and any number of other reasons, 1.8.4 is now based on the Ruby 1.8.4
> build built in Japan (I'm sorry; my mind is blanking on the name of
> the site and the person behind it) which is built with VC6 -- and is
> NO LONGER AVAILABLE to users.
>
> That's one reason I'm working on 1.8.4 with VC++ 2005 in my
> (completely nonexistent) free time so that people can get VC++ 2005
> and *build* things on Windows quickly and easily.
>
> At least once I've figured out how to do it. It's not as easy as it
> might first appear, and the *official* version of zlib is never
> compiled against anything but MSVCR6.DLL (e.g., VC6) so to have a
> compatible zlib, you have to compile it yourself. It's a pain in the
> ass.
Yeah, Austin got it right.The official Japanese build of ruby for
windows (ruby-mswin32) uses vc++6, and almost all available binaries
for various extensions are also built with vc++6.
When I moved to vc++7 for 1.8.2 it cause a lot of subtle problems.
Starting with 1.8.4 I'm actually using the ruby-mswin32 build as a
based and adding more extensions on top of it. The have got a number
of things right that I always had problems with (Tk/Tcl support,
iconv, readline, etc.). So it was also a relief to start with a base
where those pieces were already problem included.
Curt