I am unable to plugin LWJGL 2.0 with eclipes 3.4.1 SDK

Started by hasan, November 19, 2008, 21:51:22

Previous topic - Next topic

hasan

I have tried my level best to use LWJGL 2.0 with eclipes 3.4.1 , I had followed all instruction which is written on your webpage but It wouldn't work.I extract my lwjgl at the location

"C:\Users\hasan\Downloads\lwjgl-2.0\lwjgl-2.0"
and then I also declared

"-Djava.library.path=C:\Users\hasan\Downloads\lwjgl-2.0\lwjgl-2.0\native\win32"

and inclued all jar files in eclipes by using "Adding External jar" option


One thing more my JRE home path is

"C:\Program Files\Java\jre1.6.0_05"


But the error remain the same. which is shown below


Exception in thread "main" java.lang.UnsatisfiedLinkError: no lwjgl in java.library.path
   at java.lang.ClassLoader.loadLibrary(Unknown Source)
   at java.lang.Runtime.loadLibrary0(Unknown Source)
   at java.lang.System.loadLibrary(Unknown Source)
   at org.lwjgl.Sys$1.run(Sys.java:72)
   at java.security.AccessController.doPrivileged(Native Method)
   at org.lwjgl.Sys.doLoadLibrary(Sys.java:65)
   at org.lwjgl.Sys.loadLibrary(Sys.java:81)
   at org.lwjgl.Sys.<clinit>(Sys.java:98)
   at org.lwjgl.openal.AL.<clinit>(AL.java:59)
   at Lesson1.execute(Lesson1.java:154)
   at Lesson1.main(Lesson1.java:204)



so can someone help me?

Hasan

wolf_m

I'd recommend putting the JARs and the native libs into the project you're making. That way, you don't have to deal with absolute native paths and their respective possible issues like access rights and such; you can instead just give the "VM Arguments" thingie in your Run Configuration paths starting with your project location variable and a path separator that's a slash, like this:
-Djava.library.path="${workspace_loc:MYPROJECT}/libs/lwjgl-1.1.4/native/win32"


In this example, all native libraries for running MYPROJECT's Main Class (as it is configured) on win32 are in the folder you see there.

You can just import the DLLs and the JARs into your project.
You'd accordingly have to include the JARs as non-external, which makes more sense anyway in my book.
One day, there's an upgrade, you forget to delete a folder and update a Run Configuration. That just gets messy.

And I'd recommend updating Java to the recent version.