为什么会出现__imp____glutInitWithExit@12和无法解析的外部符号
2013-04-17 18:18
405 查看
在编写OpenGL程序时,当使用到glut库时,编译能够成功,但是在执行的时候,就会 出现__imp____glutInitWithExit@12和无法解析的外部符号和__imp____glutCreateWindowWithExit@8无法解析。
这个问题的解决:在#include <GL/glut.h>之前(一定要在其前)加上下列代码:
#ifndef GLUT_DISABLE_ATEXIT_HACK
#define GLUT_DISABLE_ATEXIT_HACK
#endif
原因:
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. */
我理解把它当成Glut 库使用时的一个瑕疵。只要我们使用了OpenGL使用库(glut),都会出现这样的问题。
所以需要定义#define GLUT_DISABLE_ATEXIT_HACK,解决此瑕疵。
上面这段英文来自:http://apps.hi.baidu.com/share/detail/31027308
这个问题的解决:在#include <GL/glut.h>之前(一定要在其前)加上下列代码:
#ifndef GLUT_DISABLE_ATEXIT_HACK
#define GLUT_DISABLE_ATEXIT_HACK
#endif
原因:
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. */
我理解把它当成Glut 库使用时的一个瑕疵。只要我们使用了OpenGL使用库(glut),都会出现这样的问题。
所以需要定义#define GLUT_DISABLE_ATEXIT_HACK,解决此瑕疵。
上面这段英文来自:http://apps.hi.baidu.com/share/detail/31027308
相关文章推荐
- 为什么会出现__imp____glutInitWithExit@12和无法解析的外部符号?
- 为什么会出现__imp____glutInitWithExit@12和无法解析的外部符号?
- 为什么会出现__imp____glutInitWithExit@12和无法解析的外部符号?
- 为什么会出现__imp____glutInitWithExit@12和无法解析的外部符号?
- error LNK2019: 无法解析的外部符号 __imp__UuidToStringW@8,该符号在函数 "private: class ATL::CStringT<wchar_t,class S
- error LNK2001: 无法解析的外部符号 __imp__MessageBoxA@16
- error LNK2001: 无法解析的外部符号 _WindowsDeleteString@4、_WindowsCreateStringReference@16、 __imp__RoGetActiva
- 无法解析的外部符号 __imp__timeGetTime@02
- OpenGL中无法解析的外部符号 __imp____glutInitWithExit@12和__imp____glutCreateWindowWithExit@8
- error LNK2001:无法解析的外部符号 __imp____glewCreateShader
- error LNK2001: 无法解析的外部符号 __imp__RegEnumKeyExA@32
- 无法解析的外部符号 __imp__TransparentBlt@44
- error LNK2001: 无法解析的外部符号 __imp__RegEnumKeyExA@32
- 无法解析的外部符号 __imp__curl_easy_init
- 最近利用cocos2d-X做游戏遇见这样一个“无法解析的外部符号 __imp__glLineWidth@4”情况
- openGL产生的 error LNK2001: 无法解析的外部符号 __imp_glBegin
- 关于编译eMule0.48a 提示: zlib.lib(gzio.obj) : error LNK2019: 无法解析的外部符号 __imp__strerror ,该符号在函数 _gzerror 中被引用
- VS链接提示无法解析的外部符号 __imp__fopen解决办法
- VS2008 error LNK2019: 无法解析的外部符号 __imp___vsnprintf,该符号在函数 _StringVPrintfWorkerA@
- error LNK2019: 无法解析的外部符号 __imp__InitCommonControlsEx@4,该符号在函数 _WinMainN@16 中被引用