Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
Reply-To:	<nhv AT cape DOT com>
From:	"Norman Vine" <nhv AT cape DOT com>
To:	<cygwin-apps AT cygwin DOT com>
Subject:	RE: gcc 2.95.3-1 and -mwin32
Date:	Sat, 17 Mar 2001 19:17:30 -0500
Message-ID:	<000b01c0af40$d328ad40$a300a8c0@nhv>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook 8.5, Build 4.71.2232.26
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To:	<3AB3F2F1.5ABD6A12@ece.gatech.edu>
Importance:	Normal

Charles S. Wilson writes:
>>
>Robert Collins asked:
>> Will -mwin32 still be present? I think it should if you 
>> do not define WIN32.
>
>This complicates things somewhat; there would be *three* 
>separate behaviors:

Hmm.. 
I think I see "four" mutually exclusive distinct behaviors

<  $WIN32 below means 
     WIN32 _WIN32 __WIN32 __WIN32__ >

1) default 
   include  /usr/include/w32api  
   don't #define $WIN32
   #define __CYGWIN__

2) -mwin32
   include  /usr/include/w32api 
   #define $WIN32
   #define __CYGWIN__

3) -mno-win32 
   don't include  /usr/include/w32api 
   don't #define $WIN32
   #define __CYGWIN__

4) -mno-cygwin 
   include  /usr/include/mingw 
   include  /usr/include/w32api
   #define $WIN32  
   #define __MINGW32__ 
   don't #define __CYGWIN__

Cheers

Norman Vine

- Raw text -