------art_5091_19521880.1153174382015
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 7/17/06, Alex Young <alex / blackkettle.org> wrote:

> Alexandru Popescu wrote:
> > Guys any hints for this? Sorry for pushing it to the top, but I am
> > still wondering what shall I use.
> >
> > once again thanks for any hints and ideas,
> Your options are as follows:
>
> - Rely on the kindness of others to provide Win32 builds of C extensions
> that you need.
> - Obtain MS VC6 (somehow) and compile them yourself.
> - Obtain MinGW GCC and friends and compile them yourself.
>
> In the first and second case, you can use the One-Click Installer Ruby.
> In the third case, you'll either need to compile Ruby yourself, or use
> the MinGW build from ruby-lang.org.
>
> In any of the three cases, you will be relying on the C extension in
> question having been tested on Windows previously, unless you are
> willing to be the test case yourself.
>
> I don't know about Borland's offerings here  - they may or may not be
> appropriate.
>
> My money's on MinGW for the medium-long term.  I believe (Curt?  You
> there?) that the OCI will be converted to a MinGW build in future.


No doubt, the compiler situation on Windows is a mess. There is some new
news, Austin Zeigler has been working with the Microsoft VC++ team (who was
dismayed to learn the Ruby on Windows was compiled with VC++ 6) to resolve
the issues with Ruby and VC2005.

I'll probably take over working with MS on this at some point. If we can get
this working, then
VC2005 express would definitely be the preferred solution. If that fails,
then it will be MinGW.

Curt

------art_5091_19521880.1153174382015--