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: Wed, 4 May 2005 13:47:02 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Using -mno-cygwin flag Message-ID: <20050504174702.GX24661@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050504091922 DOT GD7475 AT monster DOT octa4 DOT net> <42789D45 DOT 6F74436D AT dessent DOT net> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050504130201 DOT 03c80150 AT pop DOT prospeed DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i On Wed, May 04, 2005 at 01:32:19PM -0400, Sam Steingold wrote: >> * Larry Hall [2005-05-04 13:02:44 -0400]: >> >> At 12:53 PM 5/4/2005, you wrote: >>>> * Brian Dessent [2005-05-04 03:00:37 -0700]: >>>> >>>> -mno-cygwin does not just "make things that doesn't depend on the >>>> cygwin DLL", it removes Cygwin from the equation entirely. >>> >>>this is very unfortunate, actually. things like berkeley-db, >>>postgresql, pcre &c all have a native win32 port, and it it a pity that >>>-mno-cygwin does not use them. >> >>That's something to take up with the MinGW folks (www.mingw.org). > >I am not quite clear on the exact relationship between cygwin and MinGW >project (I assumed that they are independent except that cygwin >includes parts of MinGW). Why would I want to talk to them? > >I think that cygwin should include the native ports of packages for >which such ports exist - as a matter of policy. I don't see any reason to duplicate the work of the people who are already providing native windows ports. -mno-cygwin is mainly a convenience for people who need to write trivial windows programs. It isn't intended to be used to port huge non-cygwin projects to windows. It can be used to do that with some added work, but I think I'm being pretty consistent in saying that supporting non-cygwin applications is not a high-priority goal for the cygwin project. >Note that I cannot switch to MinGW completely because it does not >support X, so I am either stuck with using cygwin (for no technical >reason), or with two separate independent development systems (Cygwin >and MinGW). You can install the mingw toolchain and use it with cygwin with no problem (Danny are you reading this?). MinGW and cygwin are not mutually exclusive. 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/