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: Mon, 11 Nov 2002 11:32:29 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: The gcc compile flag -mwin32 & _WIN32 Message-ID: <20021111163229.GB21778@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <5 DOT 1 DOT 1 DOT 6 DOT 0 DOT 20021111225151 DOT 00a95620 AT mail DOT ozemail DOT com DOT au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.1.1.6.0.20021111225151.00a95620@mail.ozemail.com.au> User-Agent: Mutt/1.5.1i On Mon, Nov 11, 2002 at 10:55:59PM +1100, Warren Dale wrote: >At 06:27 11/11/2002, Tim Prince wrote: >>The cygwin-specific gcc compile flag -mwin32 causes the _WIN32 macro to be >>defined. Certain cygwin applications predate that arrangement, so confusion >>is understandable. > >Where can I can find documentation on "-mwin32"? gcc -v --help cgf -- Please do not send me personal email with cygwin questions or observations. Use the resources at http://cygwin.com/ . -- 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/