From: "James M. Lawrence" <quixoticsycophant@...>
Date: 2008-10-06T09:42:00+09:00
Subject: Re: Making/Compiling Gems on Windows with MinGW


>> Keep in mind that the ruby version you're using *must* be the one
>> build with MinGW, and will not work with the one build with VC6. To
>> spot this difference run "ruby -v" and see the platform information.
>> 
>> mswin32: VC6 build
>> mingw32: MinGW (GCC) build
>> 
> 
> I appreciate that - I was not aware of the fact that they had to 
> 'match'. I've definitely got the VC6 build, so that's most likely my 
> problem.

Just to clarify, mingw32 is C-wise ABI compatible with VC6.  The 
difference is in the runtime library linked into the final ruby 
executable.

For example you can use mingw to compile extensions for the one-click 
installer, even though that ruby is linked to the VC6 msvcrt.  Since an 
extension is not a binary .exe, the mingw runtime isn't needed and isn't 
linked in.

Note C++ is always ABI-incompatible across compilers, as name mangling 
and runtime implementations (exceptions, rtti, etc) are different (even 
purposefully different to avoid possible mix-ups).
-- 
Posted via http://www.ruby-forum.com/.