Norbert Unterberg wrote:
> 2006/2/25, Joseph Galbraith <galb@vandyke.com>:
>
>>> We use WIN32, not _WIN32, and this define is obviously not necessary.
>> We might want to consider changing that, since it
>> appears that WIN32 isn't defined when building for
>> 64-bit, but _WIN32 is.
>>
>> In other words, _WIN32 appears to be the correct define
>> if you mean #if "this is the win32 api" and WIN32 appears
>> to be the correct define if you mean "this is the
>> 32-bit version of the win32 api."
>
> It seems to be differernt.
> _WIN32 is the documented predefined macro that is always defined on
> both 32 and 64 bit windows platform.
> _WIN64 is predefined for 64 bit windows only.
> WIN32 is not defined automatically. However, all MS wizard generated
> project files I've seen seem to manually define WIN32 on the command
> line when invoking the compiler. I think this is a relict from early
> windows compilers (used to distinguish between 16 bit and 32 bit code)
> and kept for compatibility with old code.
Attention here: WIN32 isn't defined automatically anymore with VS2005
(and VC-Express). You have to manually add this to compile projects
which rely on that define.
So I'd stay away from WIN32 if possible and use _WIN32 instead.
(that's why we had some big problems compiling apr with VS2005 when we
switched until we patched the build files accordingly).
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 25 14:37:04 2006