Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: using gcc to build non-cygwin binaries
Date:	Fri, 5 Aug 2005 15:07:45 +0100
MIME-Version:	1.0
In-Reply-To:	<Pine.LNX.4.62.0508050902350.32085@ns.pyerotechnics.com>
Message-ID:	<SERRANOMVMbKSnt9F3i000000c0@SERRANO.CAM.ARTIMI.COM>

----Original Message----
>From: Jason Pyeron
>Sent: 05 August 2005 14:04

> Can gcc produce standard win32 dll/exe?
> 
> That is not linked to cygwin?

  Yes, use the -mno-cygwin flag (as well as -shared if building a .dll).
That will give you an .exe or .dll that is essentially a mingw application,
i.e. win32 native, and does not link against the cygwin dll or libraries at
all.

  Of course, without cygwin, you can't use any of the POSIX APIs it
implements.  You can still use the limited subset implemented in mingw
though.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/

- Raw text -