From 1b5f0e595b10488e8edebfab90c0672853a35b07 Mon Sep 17 00:00:00 2001 From: Christopher Faylor Date: Sun, 10 Nov 2002 19:38:26 +0000 Subject: [PATCH] * how-programming.texinfo: Document _WIN32 more fully. --- winsup/doc/ChangeLog | 4 ++++ winsup/doc/how-programming.texinfo | 6 ++++++ 2 files changed, 10 insertions(+) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index abec5fe43..0075f86be 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,7 @@ +2002-11-10 Christopher Faylor + + * how-programming.texinfo: Document _WIN32 more fully. + 2002-10-22 Joshua Daniel Franklin * ntsec.sgml: Correct some minor grammatical errors. diff --git a/winsup/doc/how-programming.texinfo b/winsup/doc/how-programming.texinfo index aa23b186f..26adf0cc9 100644 --- a/winsup/doc/how-programming.texinfo +++ b/winsup/doc/how-programming.texinfo @@ -564,6 +564,12 @@ we thought it would be a good idea for compatibility with VC++ code to follow their example. We use _MFC_VER to indicate code that should be compiled with VC++. +_WIN32 is only defined when you use either the -mno-cygwin or -mwin32 +gcc command line options. This is because Cygwin is supposed to be a +Unix emulation environment and defining _WIN32 confuses some programs +which think that they have to make special concessions for a Windows +environment which Cygwin handles automatically. + @subsection How should I port my Unix GUI to Windows? There are two basic strategies for porting Unix GUIs to Windows.