Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Paul G." Organization: NewDawn Productions To: cygwin@cygwin.com Date: Sat, 11 Oct 2003 20:16:33 -0700 MIME-Version: 1.0 Subject: Re: merging mingw and cygwin Reply-to: pgarceau@attbi.com Message-ID: <3F886521.31297.165D351@localhost> In-reply-to: <20031012020146.GA11314@mdssirds.comp.pge.com> References: <5.1.0.14.0.20031011194820.02edbe98@127.0.0.1> Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body 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/