How To Avoid Problems Associated with Installing New SDKs
Article ID: 194614
Article Last Modified on 6/29/2004
APPLIES TO
- Microsoft Visual C++ 4.0 Standard Edition
- Microsoft Visual C++ 5.0 Enterprise Edition
- Microsoft Visual C++ 6.0 Enterprise Edition
- Microsoft Visual C++ 5.0 Professional Edition
- Microsoft Visual C++ 6.0 Professional Edition
- Microsoft Visual C++ 6.0 Standard Edition
This article was previously published under Q194614
SUMMARY
When you install Microsoft SDKs that were not provided with Microsoft
Visual C++, you might have build problems. The resulting build errors are
typically the result of problems where a symbol is not defined, and
therefore a compiler error such as the following is issued:
[source filename](line number) : error C2065: 'symbol name' : undeclared
identifier
A linker error such as the following may also be issued:
[object filename] : error LNK2001 unresolved external symbol
"[undecorated symbol name]" (decorated symbol name)
MORE INFORMATION
When you install Microsoft SDKs, compare the header and library dates in
the SDK files with the files that were provided with Visual C++. If the SDK
files are newer, you should place the SDK directories before the default
Visual C++ INCLUDE and LIB directories listed in the Directories tab of the
Options dialog box (accessed from the Tools menu).
Additional query words: software development kit
Keywords: kberrmsg kbhowto kbide KB194614