Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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:	Tim Prince <tprince AT computer DOT org>
Reply-To:	tprince AT computer DOT org
To:	Eric Belhomme <eric DOT belhomme AT free DOT fr>, cygwin AT cygwin DOT com
Subject:	Re: how-to use _WIN32 preprocessor with cygwin ?
Date:	Sun, 10 Nov 2002 11:27:51 -0800
References:	<Xns92C2C61BC83D7ericbelhommefreefr AT 80 DOT 91 DOT 224 DOT 249>
In-Reply-To:	<Xns92C2C61BC83D7ericbelhommefreefr@80.91.224.249>
MIME-Version:	1.0
Message-Id:	<20021110192754.9C6662CA74@inet1.ywave.com>

On Sunday 10 November 2002 10:24, Eric Belhomme wrote:

> #ifndef _WIN32
> # include <inttypes.h>
> #else
> # include "myheader.h"
> #endif
>
> So as I readen on the cygwin FAQ, _WIN32 sould be declared ans "myheader.h"
> sould be used instead of <inttypes.h> but that' not the case :-(
>
> So i deduce the _WIN32 preprocessor is not known under cygwin environment.
> I wonder I have to declare something, somewhere, but as I said in intro,
> I'm not familliar with the gnu C compiller...

The cygwin-specific gcc compile flag -mwin32 causes the _WIN32 macro to be 
defined.  Certain cygwin applications predate that arrangement, so confusion 
is understandable.
-- 
Tim Prince

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