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
To: cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
Path: not-for-mail
From: Eric Belhomme <eric DOT belhomme AT free DOT fr>
Subject: how-to use _WIN32 preprocessor with cygwin ?
Date: Sun, 10 Nov 2002 18:24:44 +0000 (UTC)
Organization: Rico Spirit
Lines: 30
Message-ID: <Xns92C2C61BC83D7ericbelhommefreefr@80.91.224.249>
NNTP-Posting-Host: hole.ricospirit.net
X-Trace: main.gmane.org 1036952684 23323 62.4.22.83 (10 Nov 2002 18:24:44 GMT)
X-Complaints-To: usenet AT main DOT gmane DOT org
NNTP-Posting-Date: Sun, 10 Nov 2002 18:24:44 +0000 (UTC)
User-Agent: Xnews/4.06.22

hi,

First, I'm not familliar with cygwin nand gcc, so i'm sure my question is 
trivial, but i didn't found how to resolve it. (sorry for the noise)

I just installed cygwin on my win2k computer to try to compile a linux based  
lib (the libprelude)

The problem is libprelude uses some glibc6 APIs included on <inttypes.h>. I 
tried to resolve the problem on doing my own include file and replace all 
<inttypes.h> includes by this code :

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

Thanks for your attention ;)

-- 
Rico (RicoSpirit) - http://www.ricospirit.net




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