This is the mail archive of the
cygwin-apps@sources.redhat.com
mailing list for the Cygwin project.
RE: Cygwin Problem
- To: "'Jason Tishler'" <Jason dot Tishler at dothill dot com>
- Subject: RE: Cygwin Problem
- From: "Norman Vine" <nhv at cape dot com>
- Date: Fri, 9 Feb 2001 11:01:01 -0500
- Cc: <cygwin-apps at sources dot redhat dot com>
- Reply-To: <nhv at cape dot com>
Jason Tishler writes:
>
>On Fri, Feb 09, 2001 at 10:06:05AM -0500, Norman Vine wrote:
>> It seems as if the newest stuff does not -D_WIN32 like it used to.
>>
>> Chris warned that this would cause lot's of things to break.
>>
>> I had to add a -mwin32 to all the gcc flags to get Python to compile.
>>
>> I am not sure that this is the best way because -mwin32 may do more
>> then we want. -mwin32 is also only in the latest gcc ( 2.95.2.7 )
>>
>> Any suggestions
>
>Unfortunately, I believe that the right solution is to do as Chuck did
>in the following (see the first paragraph):
>
> http://sources.redhat.com/ml/cygwin/2001-02/msg00244.html
>
I do not think that this is the same problem
Hopefully this dumb example will illustrate my point better
Cheers
Norman Vine
/* jnk.c -- -mwin32 switch test
$ gcc -DWIN32 jnk.c
jnk.c:1: windows.h: No such file or directory
$ gcc -mwindows jnk.c
jnk.c:1: windows.h: No such file or directory
$ gcc -mwin32 jnk.c
$ a
A dumb test
*/
#include <windows.h>
int main(int argc, char **argv)
{
printf("A dumb test\n");
return 0;
}