LWJGL Forum

Programming => Lightweight Java Gaming Library => Topic started by: Orangy Tang on September 24, 2004, 21:40:49

Title: wglAllocateMemoryNV unsatisfied link error with .92
Post by: Orangy Tang on September 24, 2004, 21:40:49
I seem to be hitting an unsatisfied link error with the latest build, has anyone else had any similar problems?
java.lang.UnsatisfiedLinkError: wglAllocateMemoryNV
at org.lwjgl.opengl.NVVertexArrayRange.wglAllocateMemoryNV(Native Method)
at com.shavenpuppy.jglib.opengl.nvidia.NvidiaMemory.doCreate(NvidiaMemory.java:89)

I'm sure I've got my jars + lib path setup correctly, because by the time this error happens I've already managed to create a display, mouse and keyboard. :shock:

Any ideas? Or is the build just broken in this bit?
Title: wglAllocateMemoryNV unsatisfied link error with .92
Post by: Matzon on September 24, 2004, 22:05:22
uhm, when did you get that build?
I think we released a 0.92 that had that bug, but fixed it the day after and uploaded a new build
Title: wglAllocateMemoryNV unsatisfied link error with .92
Post by: Orangy Tang on September 24, 2004, 22:32:45
Hmm, just re-downloaded and tried again, although the filesize on the zip is different I'm still getting the same error.
Title: wglAllocateMemoryNV unsatisfied link error with .92
Post by: Matzon on September 25, 2004, 00:45:03
if you're running win32 - could you try this build
http://matzon.dk/lwjgl/builds/lwjgl-win32-0.92.zip
Title: wglAllocateMemoryNV unsatisfied link error with .92
Post by: Orangy Tang on September 25, 2004, 12:15:59
Cheers, thats fixed it. Was that the UPX compression breaking things?
Title: wglAllocateMemoryNV unsatisfied link error with .92
Post by: Matzon on September 25, 2004, 12:36:49
no, it was a define WIN32, that was wrong, and thus didn't include that windows specific method. UPX still works fine (to the best of my knowledge)
Title: wglAllocateMemoryNV unsatisfied link error with .92
Post by: oNyx on September 28, 2004, 11:30:33
Cheers Matzon. I downloaded the latest version from sf.net several times (last try was some hours ago) and I got 1.5 binaries each time.

So... whenever you release a new version, release it with a different name. Otherwise sf won't be able to distribute it (across it's mirrors) correctly.