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 Date: Mon, 13 Oct 2003 15:59:34 -0700 From: Yitzchak Scott-Thoennes To: cygwin@cygwin.com Subject: Re: merging mingw and cygwin Message-ID: <20031013225934.GA2956@efn.org> References: <20031012052757.GB12191@mdssirds.comp.pge.com> <1065936902.844.19.camel@localhost> <20031012062347.GA12677@mdssirds.comp.pge.com> <20031013190000.GB20245@mdssirds.comp.pge.com> <20031013203527.GA25036@mdssirds.comp.pge.com> <20031013213226.GC25036@mdssirds.comp.pge.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Organization: bs"d On Mon, Oct 13, 2003 at 03:20:49PM -0700, Andrew DeFaria wrote: > Edward Peschko wrote: > >MINGW and/or NO_CYGWIN simply wrap all of this up in a nice user friendly > >package. > > > Let us know how your first implementation of this concept goes... mungewin-0.01? More seriously, if there are problems with -mno-cygwin building Mingw ports, perhaps you should report these as bugs. About Mingw modes for things other than gcc, I personally don't want the cygwin tools I use bloated or slowed down by having to have a separate run mode, and I haven't seen any report of an actual problem that would be solved by this. -- 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/