From: Eli Green <eli.green@...>
Date: 2001-10-31T10:01:27+09:00
Subject: [ruby-talk:23887] Re: Ruby's use of cygwin and commercial use !

Ruby compiled with MinGW will operate completely independently of Cygwin. The
executables compiled with MinGW have no requirements that MSVC ones wouldn't.

So MinGW is JUST a C compiler. With a little poking and prodding, it is even
possible to get MinGW and MSVC to recognize each other's libraries.

from Steve Tuckner on 2001-10-31 at 07:26:52:
> What does it mean to run ruby with mingw in cygwin? Is everything OkeDokey
> with that?
> 
> -----Original Message-----
> From: Awash in a Sea of Entropy [mailto:feoh@fourfuzzies.org]
> Sent: Tuesday, October 30, 2001 4:24 PM
> To: ruby-talk@ruby-lang.org
> Subject: [ruby-talk:23872] Re: Ruby's use of cygwin and commercial use!
> 
> 
> On Wed, 31 Oct 2001, Armin Roehrl wrote:
> 
> > Dave, maybe you want to setup a "vote" for that on rubygarden.
> > 
> > I vote for mingw.
> > 	Armin
> > 
> > >
> > > Should the InstallShield version switch to mingw? We'd lose fork and
> > > some popen functionality, but we'd also lose the cygwin issues.
> 
> I vote mingw.  cygwin is a great tool but is more trouble than it's
> worth.  I'd prefer Ruby to be a more 'generic' Win32 platform when running
> under Windows, and as it stands every time I install Ruby on a new system
> I have to fight with cygwin1.dll issues because the Ruby install conflicts
> with my current cygwin installation.
> 
> -Chris

-- 
This will all be on the test. Please study it.
Eli Green
Codedogs