Jump to content

  • Log In with Google      Sign In   
  • Create Account


#Actualnoizex

Posted 06 January 2013 - 02:47 AM

You're not linking to static glfw.lib and DLL at the same time somehow? Also consider switching to GLFW 3.0 and compiling it yourself for your platform. It's almost release-ready, I'm using it for a year and didn't have a single problem (except for name-changes that happened during development of lib, but its just minor inconvenience).

By the way, any reason why you're not linking GLFW as static lib?

#2noizex

Posted 06 January 2013 - 02:47 AM

You're not linking to static glfw.lib and DLL at the same time somehow? Also consider switching to GLFW 3.0 and compiling it yourself for your platform. It's almost release-ready, I'm using it for a year and didn't have a single problem (except for name-changes that happened during development of lib, but its just minor inconvenience).

By the way, any reason why you're not linking GLFW as static lib?

#1noizex

Posted 06 January 2013 - 02:47 AM

You're not linking to static glfw.lib at the same time somehow? Also consider switching to GLFW 3.0 and compiling it yourself for your platform. It's almost release-ready, I'm using it for a year and didn't have a single problem (except for name-changes that happened during development of lib, but its just minor inconvenience).

 

By the way, any reason why you're not linking GLFW as static lib?


PARTNERS