From: nobu.nokada@...
Date: 2002-10-03T11:02:49+09:00
Subject: Re: Compiling stuff under Windows: list of problems

Hi,

At Thu, 3 Oct 2002 10:33:49 +0900,
Gavin Sinclair wrote:
> > Note that mingw32 and mswin32(msvc) are runtime-compatible in
> > 1.7 now.
> 
> That's good.  What does it mean?  And what does 1.7 have to do with it?

One extension library is usable from mingw and mswin.

> Using 'extconf' to generate a Makefile will still be incompatible if I use an
> out-of-the-box Ruby compiles by MSVC but want to compile an extension with
> mingw.

Hmmm, perhaps you need rbconfig.rb for mingw and to edit TOPDIR
line in it.  But if you use mignw compiler, it's best and
easiest to compile ruby itself with the compiler.

> > >    b. Borland: difficult to compile Ruby, as
> > >       - you can't run 'configure'
> > >       - there's no pregenerated Makefile
> >
> > Experimental support in 1.7.
> 
> I just downloaded a "stable snapshot" and saw no difference from 1.6 as far as
> Borland is concerned.

It's 1.6 snapshot.  1.7 is "snapshot.tar.gz" without "stable-".

> > > SUMMARY
> > > -------
> > >
> > > Perhaps MinGW is the best bet for Ruby under Windows.  I'll give it another try
> > > and report to the group.
> >
> > Agree, but still it has some problems.
> 
> True.  I can't see a way to generate a Makefile for mingw either.  ... However,
> I just looked at the www.mingw.org again and there is available an MSYS
> package, including bash and sundry other things so that "configure" can be run.

It's certainly a problem, however, I didn't know it.  Instead,
the main subject in my mind was select & thread-switching
issue.

-- 
Nobu Nakada