Do the winelib and winegcc tools and so on define WIN32?

[Jonathan Wilson]

If not, they should (IMHO). Any compiler that provides windows.h & friends 
and proporting to act like a win32 compiler (i.e. accepting win32 code and 
so on) should be defining WIN32. Testing #ifdef WIN32 is the easiest way to 
say "if we are building on windows do x, if not do y"
And, for all practical purposes (from the perspective of source code 
anyway), building on winelib should be the same as building on windows 
(isnt that the point of winelib)

MingW, Visual C++ and Cygwin with -mno-cygwin (which is basicly MingW) all 
define WIN32. And I would assume that Watcom, Borland and others probobly 
do as well although I dont have those to check.

[Steven Edwards]

--- Jonathan Wilson  wrote:
> If not, they should (IMHO). Any compiler that provides windows.h & friends 
> and proporting to act like a win32 compiler (i.e. accepting win32 code and 
> so on) should be defining WIN32. Testing #ifdef WIN32 is the easiest way to 
> say "if we are building on windows do x, if not do y"
> And, for all practical purposes (from the perspective of source code 
> anyway), building on winelib should be the same as building on windows 
> (isnt that the point of winelib)
>
> MingW, Visual C++ and Cygwin with -mno-cygwin (which is basicly MingW) all 
> define WIN32. And I would assume that Watcom, Borland and others probobly 
> do as well although I dont have those to check.

They do its just winegcc is not ready to build the whole WINE package.
http://cvs.winehq.com/cvsweb/wine/tools/winegcc.c?rev=1.16&content-type=...

Thanks
Steven

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

[Dimitrie O. Paun]

On July 22, 2003 11:23 pm, Jonathan Wilson wrote:
> If not, they should (IMHO). Any compiler that provides windows.h & friends
> and proporting to act like a win32 compiler (i.e. accepting win32 code and
> so on) should be defining WIN32. Testing #ifdef WIN32 is the easiest way to
> say "if we are building on windows do x, if not do y"

Yes, you are correct that they should. And winegcc does defines the following:
  WIN32, _WIN32, __WIN32, __WIN32__, __WINNT, __WINNT__, __WINE__, etc.

Take your pick.