Linker Tools Error LNK2001

unresolved external symbol "symbol"

Code will generate this error message if it references something (like a function, variable, or label) that the linker can’t find in all the libraries and object files it searches. In general, there are two reasons this error occurs: what the code asks for doesn’t exist (the symbol is spelled incorrectly or uses the wrong case, for example), or the code asks for the wrong thing (you are using mixed versions of the libraries?some from one version of the product, others from another version).

Numerous kinds of coding and build errors can cause LNK2001. Several specific causes are listed below, and some have links to more detailed explanations.

Coding Problems

  • Mismatched case in your code or module-definition (.DEF) file can cause LNK2001. For example, if you named a variable “var1” in one C++ source file and tried to access it as “VAR1” in another, you would receive this error. The solution is to exactly match the case of the symbol in all references.

  • A project that uses function inlining yet defines the functions in a .CPP file rather than in the header file can cause LNK2001.

  • If you are using C++, make sure to use extern “C” when calling a C function from a C++ program. By using extern “C” you force the use of the C naming convention. Be aware of compiler switches like /Tp or /Tc that force a file to be compiled as a C (/Tc) or C++ (/Tp) file no matter what the filename extension, or you may get different function names than you expect.

  • Attempting to reference functions or data that don't have external linkage causes LNK2001. In C++, inline functions and const data have internal linkage unless explicitly specified as extern.

  • A missing function body or variable will cause LNK2001. Having just a function prototype or extern declaration will allow the compiler to continue without error, but the linker will not be able to resolve your call to an address or reference to a variable because there is no function code or variable space reserved.

  • Name decoration incorporates the parameters of a function into the final decorated function name. Calling a function with parameter types that do not match those in the function declaration may cause LNK2001.

  • Incorrectly included prototypes will cause the compiler to expect a function body that is not provided. If you have both a class and non-class implementation of a function F, beware of C++ scope-resolution rules.

  • When using C++, make sure that you include the implementation of a specific function for a class and not just a prototype in the class definition.

  • Attempting to call a pure virtual function from the constructor or destructor of an abstract base class will cause LNK2001 since by definition a pure virtual function has no base class implementation.

  • Only global functions and variables are public.

    Functions declared with the static modifier by definition have file scope. Static variables have the same limitation. Trying to access any static variables from outside of the file in which they are declared can result in a compile error or LNK2001.

    A variable declared within a function (a local variable) can only be used within the scope of that function.

    C++ global constants have static linkage. This is different than C. If you try to use a global constant in C++ in multiple files you get error LNK2001. One alternative is to include the const initializations in a header file and include that header in your .CPP files when necessary, just as if it was a function prototype. Another alternative is to make the variable non-constant and use a constant reference when assessing it.

Compiling and Linking Problems

  • The names of the Microsoft run-time and MFC libraries needed at link time are included in the object file module by the Microsoft compiler. If you use the /NOD (/NODEFAULTLIB) option, these libraries will not be linked into the project unless you have explicitly included them. Using /NOD will cause error LNK2001 in this case.

  • If you are using Unicode and MFC, you will get an unresolved external on _WinMain@16 if you don’t create an entrypoint to wWinMainCRTStartup. Use the /ENTRY option or type this value in the Project Settings dialog box. (To find this option in the development environment, click Settings on the Project menu, then click the Link tab, and click Output in the Category box.) See Unicode Programming Summary.

    See the following Knowledge Base articles located in the Online Information System for more information. An easy way to reach an article is to copy a "Q" number above, open the Search dialog box from the Help menu and select the Query tab, then paste the number into the first text box and press ENTER.
    • Q125750   "PRB: Error LNK2001: '_WinMain@16': Unresolved External Symbol"

    • Q131204   "PRB: Wrong Project Selection Causes LNK2001 on _WinMain@16"

    • Q100639   "Unicode Support in the Microsoft Foundation Class Library"
  • Linking code compiled with /MT with the library LIBC.LIB causes LNK2001 on _beginthread, _beginthreadex, _endthread, and _endthreadex.

  • When compiling with /MD, a reference to "func" in your source becomes a reference "__imp__func" in the object since all the run-time is now held within a DLL. If you try to link with the static libraries LIBC.LIB or LIBCMT.LIB, you will get LNK2001 on __imp__func. If you try to link with MSVCxx.LIB when compiling without /MD you will not always get LNK2001, but you will likely have other problems.

  • Linking code compiled with an explicit or implicit /ML to the LIBCMT.LIB causes LNK2001 on _errno.

  • Linking with the release mode libraries when building a debug version of an application can cause LNK2001. Similarly, using an /Mxd option (/MLd, /MTd, or /MDd) and/or defining _DEBUG and then linking with the release libraries will give you potential unresolved externals (among other problems). Linking a release mode build with the debug libraries will also cause similar problems.

  • Mixing versions of Microsoft libraries and compiler products can be problematic. A new compiler version's libraries may contain new symbols that cannot be found in the libraries included with previous versions. Use DUMPBIN to find out if a symbol is in a 32-bit object file or library.

  • There is currently no standard for C++ naming between compiler vendors or even between different versions of a compiler. Therefore linking object files compiled with other compilers may not produce the same naming scheme and thus cause error LNK2001.

  • Mixing inline and non-inline compile options on different modules can cause LNK2001. If a C++ library is created with function inlining turned on (/Ob1 or /Ob2) but the corresponding header file describing the functions has inlining turned off (no inline keyword), you will get this error. To prevent this problem, have the inline functions defined with inline in the header file you are going to include in other files.

  • If you are using the #pragma inline_depth compiler directive, make sure you have a value of 2 or greater set, and make sure you are using the /Ob1 or /Ob2 compiler option.

  • Omitting the LINK option /NOENTRY when creating a resource-only DLL will cause LNK2001.

  • Using incorrect /SUBSYSTEM or /ENTRY settings can cause LNK2001. For example, if you write a character-based application (a console application) and specify /SUBSYSTEM:WINDOWS, you will get an unresolved external for WinMain. For more information on these options and entry points, see the /SUBSYSTEM and /ENTRY linker options.

Export Problems

  • When you are porting an application from 16 to 32 bits, LNK2001 can occur. The current 32-bit module-definition (.DEF) file syntax requires that __cdecl, __stdcall, and __fastcall functions be listed in the EXPORTS section without underscores (undecorated). This differs from the 16-bit syntax, where they must be listed with underscores (decorated). For more information, see the description of the EXPORTS section of module-definition files.

  • Any export listed in the .DEF file and not found will cause LNK2001. This could be because it does not exist, is spelled incorrectly, or uses decorated names (.DEF files do not take decorated names). 

This error message is followed by fatal error LNK1120.

The following sections give more detailed information on some of the issues named in the above list.

### 解决Visual Studio Error LNK2001 Unresolved External Symbol #### 错误概述 当遇到`error LNK2001: unresolved external symbol`时,这通常意味着链接器未能找到某些函数或变量的具体实现。这类错误经常发生在静态成员、全局对象初始化以及跨模块调用的情况下。 #### 常见原因及解决方案 #### 缺少库文件或路径配置不当 确保项目设置中包含了所有必要的库文件,并且这些库的位置已被正确指定给链接器。可以通过以下方式检查并修正: - **属性管理器** -> **Linker (链接器)** -> **General (常规)** -> **Additional Library Directories (附加库目录)** - 添加缺失的`.lib`文件到项目的输入项里:**Configuration Properties (配置属性)** -> **Linker (链接器)** -> **Input (输入)** -> **Additional Dependencies (附加依赖项)**[^1] #### 函数声明与定义不匹配 确认源码中的每一个外部符号都有对应的实现部分。对于C++程序而言,特别要注意类方法是否被正确定义而非仅仅声明。例如: ```cpp // MyClass.h 中有如下声明 class MyClass { public: void doSomething(); }; // 而MyClass.cpp中有相应的实现 void MyClass::doSomething() { /* 实现 */ } ``` 如果只存在声明而无实际代码,则会产生此类型的链接期错误[^4]。 #### 使用了不同的运行时库版本 在同一工程内混合使用多线程/单线程版或其他不同版本的标准C/C++ runtime library可能导致此类问题。统一整个应用程序使用的RTTI选项非常重要。可以在编译器设置里面调整: - 打开项目属性对话框; - 寻找 C/C++ -> Code Generation -> Runtime Library 设置项; - 将其设为一致的选择,比如 `/MDd`(Debug Multithreaded DLL),而不是一部分采用`/MT`另一些则用了其他形式[^2]. #### 宏定义冲突 有时开发者可能会无意间重载了一些系统级别的宏名,像`_DLL`, 这样做容易引起内部命名空间污染进而造成难以预料的结果。建议避免覆盖任何已知的关键字或保留词作为预处理器指令的一部分: ```cpp #define _DLL // 不推荐这样做 ``` #### 头文件包含顺序不对 虽然这不是直接引发LNK2001的原因之一,但是不良的#include语句排列也可能间接影响最终生成的目标文件能否正常工作。遵循良好的实践原则——先引入标准库头文件再加入自定义组件能减少潜在风险[^3]. ---
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值