Is there anything wrong with this link.exe command line? OpenGL32.lib and Glu32.lib are both found in LIBPATH directories Is it possible that the library is incompatible? Is there a way to link? Exe says that instead of unsolved exotic symbol? Googling shows that have not met this error means that the library is, but there are
e: \ mvs90 \ VC \ bin \ link.exe / DLL / Nologo / INCREMENTAL: NO / debug / pdb: none / LIBPATH: e: \ code \ Python \ Python \ py26 \ libs / LIBPATH: e: \ code \ Python \ Python \ py26 \ PCbuild opengl32.lib glu32.lib / export: init_rabbyt Construction \ temp. win32-2.6-pydebug \ debug \ rabbyt / rabbyt._rabbyt.obj / outside: Construction \ lib.win32-2.6-pydebug \ rabbyt \ _rabbyt_d.pyd / IMPLIB: build \ temp.win32-2.6-pydebug \ debug \ rabbyt \ _rabbyt_d.lib / MANIFESTFILE: Creating \ temp.win32-2.6-pydebug \ debug \ rabbyt \ _rabbyt_d.pyd.manifest library \ te mp.win32-2.6-pydebug \ Debug make \ rabbyt \ _rabbyt_d.lib and build object \ temp.win32-2.6-pydebug \ Debug \ rabbyt \ _rabbyt_d.exp rabbyt._rabbyt.obj: error LNK2019: unresolved external symbol __imp__glOrtho E directory are ferenced in ___pyx_f_6rabbyt_7_rabbyt_set_viewport function: \ code \ Python \ Python \ py26 \ libs 2007/09/27 14:20 12,672 GlU32.Lib 2007/09/27 14:20 76,924 OpenGL32. Lib
It seems that Y has given his success with Sigwin and MSYS These are SAGVIN / GCC or MINGW / GCC export libraries and MSVC is not export library, they will not be valid by Microsoft's Linker, and they will be ignored.
The correct OpenGL32.lib and Glu32.lib files are part of the Windows SDK. For the VS2008 SDK, this is on Celsius. \ Program Files \ Microsoft SDKs \ Windows \ v6.0A \ Lib (your installation may be different)
Glaux.lib has been removed apparently and is no longer included in Windows SDK If you need them, download and install the old VS2005 SDK to get the header and export library. Old SDK "C: \ Program Files \ Microsoft Visual Studio 8 \ VC \ platform will be installed on the SDK", while VS 2008 SDK "C: \ Program Files \ Microsoft SDK's \ Windows \ v6.0 A", then you Simply copy the required files in the respective folder in the related SDK.
You can definitely create with VS 2005 or earlier instead of just mess with SSD.
Comments
Post a Comment