From: Luis Lavena Date: 2008-03-28T14:19:55+09:00 Subject: Re: Bootstrapping Ruby with MinGW: selfhosted and test sandbox! On Mar 27, 9:58 pm, Joel VanderWerf wrote: > This is all working very smoothly for me, following the recipe. > > I ended up with a ruby/mingw32 installation which my program can use to > dynamically compile its parts that are generated C code, and run 20%-50% > faster than using msvc6 and oci. This is also far preferable than > requiring users to have msvc6 installed if they make changes that > require recompilation of the generated C code. > Great, good to know :-) > The only slight hiccup was figuring out that I needed to put > sandbox/ruby_mingw/bin on my PATH, but that's really pretty obvious. > Well, the idea of sandbox/ruby_mingw is be there until it get properly packaged ;-) I suggest you put it into C:/Ruby or something like that, or have a inside your %HOME% a full stack of ruby versions like I do: ruby-185-p114-VC6-rubygems-094 ruby-186-p111-VC6-rubygems-094 ruby-186-p111-VC6-rubygems-094-oci ruby-186-p111-VC6-rubygems-095 ruby-186-p111-VC6-rubygems-101 ruby-186-svn-MINGW-rubygems-101 > I hope someone is able to fix readline, though... I want to try the non-blocking patch Park Heesob created for IO.gets, I don't think it's related, but smell fishy... > > Thanks, Luis! > No problem man, I hope collect a list of the most used gems that want get proper support for MinGW build, now that RubyGems is fixed ;-) Regards, -- Luis Lavena