Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualKoehler

Posted 15 November 2012 - 09:37 AM

You've probably tried some of this already, but here are some possibilities.

If this is happening when you actually run, then you need to place the glew32.dll where your OS can find it (Same dir as your executable would work, which is <Solution dir>\Debug or <Solution dir>\Release.

If you're trying to link statically with glew, you'll need to link to glew32s.lib (for release) and glew32sd.lib (for debug).

Finally, check and see if the first error isn't something like "Couldn't find library glew32.lib". If that's the case, you need to tell the linker about the folder your glew32.lib is in. (Project properties -> Linker -> General, modify "Additional library locations")

#1Koehler

Posted 15 November 2012 - 09:36 AM

You've probably tried some of this already, but here are some possibilities.

If this is happening when you actually run, then you need to place the glew32.dll where your OS can find it (Same dir as your executable would work, which is <Solution dir>\Debug or <Solution dir>\Release.

If you're trying to link statically with glew, you'll need to link to glew32s.lib (for release) and glew32sd.lib (for debug).

Finally, check and see if the first error isn't something like "Couldn't find library glew32.lib". If that's the case, you need to tell the linker about the folder your glew32.lib is in.

PARTNERS