Francesco Montorsi
2010-03-03 22:11:24 UTC
Hi Vaclav,
I've found that for all MSVC formats Bakefile always defines the WIN32
symbol... this is at least misleading on 64bit platforms: all source files gets
compiled with /DWIN32 and with no 64-bit symbols (apparently).
The definition of symbol WIN32 is not really required since the cl compiler
automatically defines the _WIN32 symbol on 32 bit platforms and both the _WIN32
and _WIN64 symbols on 64 bit platforms...
should this be considered a bakefile bug which has to be fixed (by removing the
relative <define>WIN32</define> line) ?
Thanks,
Francesco
PS: this problem was found while discussing 64bit compilation of wxWidgets; see
http://groups.google.com/group/wx-
dev/browse_thread/thread/3c7579dcf0b98567/eeed0161aa30ef31#eeed0161aa30ef31
I've found that for all MSVC formats Bakefile always defines the WIN32
symbol... this is at least misleading on 64bit platforms: all source files gets
compiled with /DWIN32 and with no 64-bit symbols (apparently).
The definition of symbol WIN32 is not really required since the cl compiler
automatically defines the _WIN32 symbol on 32 bit platforms and both the _WIN32
and _WIN64 symbols on 64 bit platforms...
should this be considered a bakefile bug which has to be fixed (by removing the
relative <define>WIN32</define> line) ?
Thanks,
Francesco
PS: this problem was found while discussing 64bit compilation of wxWidgets; see
http://groups.google.com/group/wx-
dev/browse_thread/thread/3c7579dcf0b98567/eeed0161aa30ef31#eeed0161aa30ef31