解决VS 2010调用OpenGL时遇到的问题:error LNK2019
2014-01-03 10:12
519 查看
引自:http://blog.csdn.net/jasonleesjtu/article/details/8700167
问题1、error LNK2019: unresolved external symbol __imp____glutInitWithExit@12 referenced in function _glutInit_ATEXIT_HACK@8
solution:
Try define the following line right before including the header, glut.h.
#define GLUT_DISABLE_ATEXIT_HACK
为什么出现这个错误,这是我在网站上找到的原因,和大家分享一下:
Win32 has an annoying issue where there are multiple C run-time
libraries (CRTs). If the executable is linked with a different CRT
from the GLUT DLL, the GLUT DLL will not share the same CRT static
data seen by the executable. In particular, atexit callbacks registered
in the executable will not be called if GLUT calls its (different)
exit routine). GLUT is typically built with the
"/MD" option (the CRT with multithreading DLL support), but the Visual
C++ linker default is "/ML" (the single threaded CRT).
One workaround to this issue is requiring users to always link with
the same CRT as GLUT is compiled with. That requires users supply a
non-standard option. GLUT 3.7 has its own built-in workaround where
the executable's "exit" function pointer is covertly passed to GLUT.
GLUT then calls the executable's exit function pointer to ensure that
any "atexit" calls registered by the application are called if GLUT
needs to exit.
Note that the __glut*WithExit routines should NEVER be called directly.
To avoid the atexit workaround, #define GLUT_DISABLE_ATEXIT_HACK. */
问题1、error LNK2019: unresolved external symbol __imp____glutInitWithExit@12 referenced in function _glutInit_ATEXIT_HACK@8
solution:
Try define the following line right before including the header, glut.h.
#define GLUT_DISABLE_ATEXIT_HACK
为什么出现这个错误,这是我在网站上找到的原因,和大家分享一下:
Win32 has an annoying issue where there are multiple C run-time
libraries (CRTs). If the executable is linked with a different CRT
from the GLUT DLL, the GLUT DLL will not share the same CRT static
data seen by the executable. In particular, atexit callbacks registered
in the executable will not be called if GLUT calls its (different)
exit routine). GLUT is typically built with the
"/MD" option (the CRT with multithreading DLL support), but the Visual
C++ linker default is "/ML" (the single threaded CRT).
One workaround to this issue is requiring users to always link with
the same CRT as GLUT is compiled with. That requires users supply a
non-standard option. GLUT 3.7 has its own built-in workaround where
the executable's "exit" function pointer is covertly passed to GLUT.
GLUT then calls the executable's exit function pointer to ensure that
any "atexit" calls registered by the application are called if GLUT
needs to exit.
Note that the __glut*WithExit routines should NEVER be called directly.
To avoid the atexit workaround, #define GLUT_DISABLE_ATEXIT_HACK. */
相关文章推荐
- 解决VS 2010调用OpenGL时遇到的问题
- error LNK2019: unresolved external symbol "__declspec(dllimport) void 遇到的问题以及解决办法
- VS下QT插件 连接数据库出现error LNK2019: 无法解析的外部符号QSqlDatabase问题解决
- 编译遇到问题该如何解决?“error LNK2019: 无法解析的外部符号”
- OpenGL编程中遇到error LNK2019: 无法解析的外部符号 __imp____glutInitWithExit@12等问题
- 解决PCL MLS : error LNK2019; error LNK2001 virtual MovingLeastSquares process performProcessing问题
- 怎样解决CodeBlocks运行VS编写的OpenGL项目时遇到的各种问题的
- VS2015下解决:error LNK2019: 无法解析的外部符号 __iob_func解决方案
- Jquery跨域调用(JSONP)遇到error问题的解决
- VS2015下解决:error LNK2019: 无法解析的外部符号 __iob_func
- VS2013 OpenGL 开发程序时: error LNK2019: 无法解析的外部符号 __imp____glutInitWithExit@12,error LNK2019: 无法解析的外部符号 __imp____glutCreateWindowWithExit@8
- VS2015下解决:error LNK2019: 无法解析的外部符号 __iob_func
- vs2008编译时出现问题解决方法:MSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol _WinMain@16
- 初学opengl(一)第一个opengl程序及error LNK2019: unresolved external symbol的解决
- C++ 遇到error LNK2019: unresolved external symbol "public: void __thisca的问题
- 在cocos2dx2.2.3中遇到的error LNK2019: 无法解析的外部符号 _libiconv_closexxxxxxx的解决办法
- 如何解决VS2010 MySql Connect C 链接mysql:error LNK2019: 无法解析外部符号的问题
- error LNK2019: 无法解析的外部符号 问题的解决办法
- 在Python中调用glutInit遇到OpenGL.error.NullFunctionError的解决方法
- 如何解决window下VP9的VS版本遇到的LNK问题