From: Mark Probert <probertm@...>
Date: 2002-10-27T04:27:15+09:00
Subject: Re: Visual C++ controversy

"Gavin Sinclair" <gsinclair@soyabean.com.au> wrote : 
>
> From: "Lyle Johnson" <lyle@users.sourceforge.net>
>> 
>> MikkelFJ wrote:
>> 
>> | I'd like to know more about how well mingw integrates with the
>> | Visual C++ Ruby distribution.
>> 
>> It is my understanding that one can use either MinGW *or* Visual C++
>> to compile extension modules for the Visual C++ build of Ruby. If
>> that's true, and if someone can put together some crystal-clear
>> instructions about what's required to pull this off, it should do a
>> lot to quell people's fears.
> 
> 
> This is allegedly the case in Ruby 1.7, not 1.6.
> 

Doesn't appear to work, in my case.  I have extensions that work
fine when compiled and installed on 1.7.2 mswin or when compiled
and installed under 1.7.3 mingw.  It core dumps (that's the message) 
if I used the mingw produced Lib.so shared library with the mswin 
distribution.

Perhaps it is the dot release.  More likely it is the config file/dll
setup that Rich mentioned.

-mark.