# Library Linking Errors with VS 2005 Solution

**URL:** <https://discourse.glfw.org/t/library-linking-errors-with-vs-2005-solution/477>\
**Category:** support\
**Created:** [December 20, 2008, 12:29am UTC](https://discourse.glfw.org/t/library-linking-errors-with-vs-2005-solution/477 "2008-12-20T00:29:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [December 20, 2008, 12:29am UTC](https://discourse.glfw.org/t/library-linking-errors-with-vs-2005-solution/477/1 "2008-12-20T00:29:49Z")

</div>

**[dbrust](https://sourceforge.net/u/dbrust/)** wrote on [Saturday, December 20, 2008](https://sourceforge.net/p/glfw/discussion/247562/thread/2ddb80b3/#6b6b):

Hello,

I’d love try out this library, but I’m getting some linking errors when trying to compile GLFW. The solution opens fine in VS 2005, but building gives the following linking errors:

1\>------ Build started: Project: GLFWDLL, Configuration: Debug Win32 ------  
1\>Linking…  
1\> Creating library C:\Users\dbrust\Desktop\glfw-2.6\glfw\support\msvc80\Debug\GLFWDLL.lib and object C:\Users\dbrust\Desktop\glfw-2.6\glfw\support\msvc80\Debug\GLFWDLL.exp  
1\>win32\_init.obj : error LNK2019: unresolved external symbol \_glfwEnable@4 referenced in function \_\_glfwPlatformTerminate  
1\>win32\_window.obj : error LNK2001: unresolved external symbol \_glfwEnable@4  
1\>window.obj : error LNK2001: unresolved external symbol \_glfwEnable@4  
1\>win32\_window.obj : error LNK2019: unresolved external symbol \_glfwDisable@4 referenced in function \_\_glfwWindowCallback@16  
1\>window.obj : error LNK2001: unresolved external symbol \_glfwDisable@4  
1\>C:\Users\dbrust\Desktop\glfw-2.6\glfw\support\msvc80\Debug\GLFWDLL.dll : fatal error LNK1120: 2 unresolved externals  
1\>Build log was saved at "file://c:\Users\dbrust\Desktop\glfw-2.6\glfw\support\msvc80\Debug\BuildLog.htm"  
1\>GLFWDLL - 6 error(s), 0 warning(s)

Any help will be greatly appreciated!

Thanks,  
Darren

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [December 20, 2008, 2:07am UTC](https://discourse.glfw.org/t/library-linking-errors-with-vs-2005-solution/477/2 "2008-12-20T02:07:38Z")

</div>

**[elmindreda](https://sourceforge.net/u/elmindreda/)** wrote on [Saturday, December 20, 2008](https://sourceforge.net/p/glfw/discussion/247562/thread/2ddb80b3/#0faf):

That’s a known bug caused by me messing up the VC project files. The fix is in Subversion and I’m trying to get a release out that makes it official.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [December 22, 2008, 1:41am UTC](https://discourse.glfw.org/t/library-linking-errors-with-vs-2005-solution/477/3 "2008-12-22T01:41:11Z")

</div>

**[dbrust](https://sourceforge.net/u/dbrust/)** wrote on [Monday, December 22, 2008](https://sourceforge.net/p/glfw/discussion/247562/thread/2ddb80b3/#6b6b/1f7f):

Thanks for the info. I checked in SVN on the trunk, but there is only the initial check in. I wasn’t able to find it elsewhere. Could you point me in the right direction?

Thanks,  
Darren

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/glfw/original/1X/b8cdefe6b61b8d5aee6c43b2c56e9cf5eabecfe4.svg) [@system](https://discourse.glfw.org/u/system)\
**Post date:** [December 22, 2008, 1:07pm UTC](https://discourse.glfw.org/t/library-linking-errors-with-vs-2005-solution/477/4 "2008-12-22T13:07:08Z")

</div>

**[elmindreda](https://sourceforge.net/u/elmindreda/)** wrote on [Monday, December 22, 2008](https://sourceforge.net/p/glfw/discussion/247562/thread/2ddb80b3/#6b6b/1f7f/9316):

The fix may well have been committed before the conversion from CVS.