Trouble building tux test with VS 2005

  • Article

Here is a heads up from one of our Developer's Tools Devs, Marty Larson:

This is something I discovered yesterday, and thought you all might
appreciate a heads up. If you try to build tux tests with VS 2005, you'll
run into this problem.

The default build settings in VS 2005 do not match the settings that the OS
was built with. VS tries to be C++ compliant, and treats wchar_t as a native
type. The OS tries to be backward compatible, and turns off that behavior.

This is only a problem when a dll exports a C++ interface (like kato does).
You'll see the following errors:

error LNK2019: unresolved external symbol "__declspec(dllimport) public: int
__cdecl CKato::EndLevel(wchar_t const *,...)"
(__imp_?EndLevel@CKato@@QAAHPB_WZZ) referenced in function ShellProc
error LNK2019: unresolved external symbol "__declspec(dllimport) public: int
__cdecl CKato::BeginLevel(unsigned long,wchar_t const *,...)"
(__imp_?BeginLevel@CKato@@QAAHKPB_WZZ) referenced in function ShellProc
error LNK2019: unresolved external symbol "__declspec(dllimport) public: int
__cdecl CKato::Log(unsigned long,wchar_t const *,...)"
(__imp_?Log@CKato@@QAAHKPB_WZZ) referenced in function ShellProc

To fix this, go to Project --> Properties --> Configuration Properties -->
C/C++ --> Language, and set 'Treat wchar_t as Built-in Type' to No.

--
Marty Larson [MS]
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
https://www.microsoft.com/info/cpyright.htm

Posted by Don Gambrell