From: Benoit Cerrina <benoit.cerrina@...>
Date: 2001-10-03T06:52:16+09:00
Subject: [ruby-talk:21957] Re: Let's work on Windows support

> I seem to remember that versions of Python compiled with MinGW can't have
> extensions compiled for them using VC++ and vice-versa. I could be wrong.
This
> would be a pain. Ideally, (see the APR thread :) the source COULD compile
> under any ANSI C compiler (VC++, MinGW, Cygwin or even LCC).
you just hit the point... we need it not only to compile but also to link
dynamically.
I believe the problems starts to pop_up when trying to load an extension
compiled
with another set of tools.
However there is a good reason why it is not a fatality:
    All mingw32 compiled apps have to dynamically load with a bunch of dll
compiled
    by msVC (all of windows as a matter of fact) therefore it is possible.
I believe
    problems start to creep when you start to have #ifdef mingw and #ifdev
VC not
    covering the same base.  It may also come from compile time flags.
Benoit