解决Opengl编译时error LNK2001: 无法解析的外部符号 __imp____glutInitWithExit@12

GLUT_DISABLE_ATEXIT_HACK

1>blendequ.cpp
1>正在链接...
1>blendequ.obj : error LNK2001: 无法解析的外部符号 __imp____glutInitWithExit@12
1>blendequ.obj : error LNK2001: 无法解析的外部符号 __imp____glutCreateWindowWithExit@8
1>E:\program practice\vs2005\blendequ\Debug\blendequ.exe : fatal error LNK1120: 2 个无法解析的外部命令
1>生成日志保存在“file://e:\program practice\vs2005\blendequ\blendequ\Debug\BuildLog.htm”
1>blendequ - 3 个错误，0 个警告
========== 生成: 0 已成功, 1 已失败, 0 最新, 0 已跳过 ==========

为什么出现这个错误，这是我在国外的网站上找到的原因，和大家分享一下：

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. *