Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-Id:	<4.3.1.2.20010830093245.02235f08@pop.ma.ultranet.com>
X-Sender:	lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer:	QUALCOMM Windows Eudora Version 4.3.1
Date:	Thu, 30 Aug 2001 09:34:52 -0400
To:	Jesper Eskilson <jojo AT virtutech DOT se>, cygwin AT cygwin DOT com
From:	"Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject:	Re: Up-to-date info on '-mno-cygwin' vs. Mingw32
In-Reply-To:	<u67heupyemn.fsf@rachel.vtab.com>
Mime-Version:	1.0

At 07:24 AM 8/30/2001, Jesper Eskilson wrote:
>Hi!
>
>I'm trying to get my hands on some up-to-date info on what the
>difference (if any) is between building binaries using Cygwin's gcc
>with the -mno-cygwin flag and using the Mingw32 suite. Mumit Khans
>-mno-cygwin howto seems a little bit out-of-date.
>
>/Jesper
>-- 


The difference is in the build environment, not the result.  If you 
like using Cygwin based tools (make, grep, sed, etc), use Cygwin's gcc
and -mno-cygwin to target Win32 without cygwin1.dll.  Otherwise, use 
the Mingw toolset.


Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -