Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 12 Oct 2003 00:08:07 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: merging mingw and cygwin Message-ID: <20031012040807.GA20101@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <5 DOT 1 DOT 0 DOT 14 DOT 0 DOT 20031011194820 DOT 02edbe98 AT 127 DOT 0 DOT 0 DOT 1> <3F886521 DOT 31297 DOT 165D351 AT localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F886521.31297.165D351@localhost> User-Agent: Mutt/1.4.1i On Sat, Oct 11, 2003 at 08:16:33PM -0700, Paul G. wrote: >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. I doubt that the overhead for Msys is any different than Cygwin's. Msys came from cygwin, remember? cgf -- 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/