Linking problem - unresolved external symbol

[Anakunda]

Hmm I'm not sure about it.
Found a link to MSDN page about defines
http://msdn.microsoft.com/en-us/libr...=vs.80%29.aspx
saying _WIN32 Defined for applications for Win32 and Win64. Always defined.

[Paul McKenzie]

Hmm I'm not sure about it.
Found a link to MSDN page about defines
http://msdn.microsoft.com/en-us/libr...=vs.80%29.aspx
saying _WIN32 Defined for applications for Win32 and Win64. Always defined.

What about the WIN32 preprocessor symbol, without the leading underscore? Same thing with WIN64. Many third-party headers use the non-underscore version (or some variation of them) to distinguish between a 32-bit build and 64-bit builds.

This is where you need to specify the correct preprocessor that the library code uses to distinguish between the two versions. My inclination is to just define WIN64 (or whatever preprocessor the library uses to define a 64-bit build) and let it be, since that has worked for me whenever I build a 64-bit app.

Regards,

Paul McKenzie