so i need to compile a bunch of stuff on windows.  some third party stuff and
ruby extensions to those third party libs.  everything i do __must__ be
compatible with the one-click installer, here's what i'm thinking might be a
good approach:

   assumption : i've read that the latest one-click installer is compatible with
   mingw output

   assumption : all extensions and libs in question compile under mingw


   step one : configure a ruby from the __same__ sources used for one-click
   installer using something like

     ./configure --with-gcc='gcc -mno-cygwin' --enable-shared --prefix='c:\ruby'

   step two : build

     make

   step three : do not install!

   step four : clobber the one-click installer's rbconfig.rb with the one just
   created!  the idea here is that this rbconfig can be used to

     ruby ./extconf.rb

   and create a Makefile that will be setup for the mingw toolchain but
   producing output that will be compatible with the vc++ compiled one-click
   ruby

   step five : compile any third party libs using mingw

   step six : compile any ruby extensions against these as normal


has anyone done anything like this?  does it sound resonable?

kind regards.

-a
-- 
be kind whenever possible... it is always possible.
- h.h. the 14th dali lama