From: Rich Kilmer <rich@...>
Date: 2002-10-25T22:34:03+09:00
Subject: Re: Visual C++ controversy

From what I understand you can do this.  The extensions used to require
different DLLs, but no longer.  The new win32 dll is "msvcrt-ruby17.dll"
and is the same for MinGW and VC++.  You would have to update the
rbconfig.rb with your compiler/linker settings if  you build/deploy ruby
with one compiler and want to use another one.  If someone could post a
diff between the mingw generated rbconfig and the vc++ one, that's all I
think would be necessary.

-rich

> -----Original Message-----
> From: Lyle Johnson [mailto:lyle@users.sourceforge.net] 
> Sent: Friday, October 25, 2002 9:25 AM
> To: ruby-talk ML
> Subject: Re: Visual C++ controversy
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 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. -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQE9uURSRy8FwLkdsRcRAmKtAKCtWvIX0wmgpPTxQqjTakGmpu9t0QCglMTp
> i4q0dYyVF0P5H5KAMnPf/yU=
> =QdYr
> -----END PGP SIGNATURE-----
> 
> 
> 
>