Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Paul G." <pgarceau AT comcast DOT net>
Organization:	NewDawn Productions
To:	cygwin AT cygwin DOT com
Date:	Sat, 11 Oct 2003 20:16:33 -0700
MIME-Version:	1.0
Subject:	Re: merging mingw and cygwin
Reply-to:	pgarceau AT attbi DOT com
Message-ID:	<3F886521.31297.165D351@localhost>
In-reply-to:	<20031012020146.GA11314@mdssirds.comp.pge.com>
References:	<5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20031011194820 DOT 02edbe98 AT 127 DOT 0 DOT 0 DOT 1>

On 11 Oct 2003 at 19:01, Edward Peschko wrote:

> > What would be the point?
> 
> lack of end-user confusion... elimination of duplicate development
> effort... elimination of duplicate maintenance effort... the ability
> to compile all unix tools 'native' win32 for those who desire it.

	Umm...Cygwin is setup to compile all, or as many as it is possible to support,  unix/posix tools in a "native" win32 
environment at a cost (in terms of systems resources).  The cost is lower (in terms of systems resources/overhead) 
for Msys than is the cost (in terms of systems resources/overhead and in terms of Unix-like support and Posix 
support) for Cygwin.  In fact it might help to read the documentation (if it hasn't been read) at the Mingw 
(http://www.mingw.org) site to get a better sense of the differences between the two and why those differences exist.

	Paul G.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -