Original Post
Edit: new problems... I don't need to edit the environment variables. I have my jogl.dll in my C:\jdk1.5.0\jre\bin. I now know this is the default path to java.library.path; however, when i make my own system env variable called java.library.path, and set it to C:\Program Files\Java\jre1.5.0\bin, and put jogl.dll there, it can't be found by java.exe (which is in c:\jdk1.5.0\bin). Why is this? I tried making my own CLASSPATH variable, but I predict that will fail too and i'll end up having to do -classpath c:\jdk1.5.0\jre\lib\ext every time I want to compile a jogl app. What should I do about this? What directory is the "default" classpath? Am I right in puting jogl.jar in c:\jdk1.5.0\jre\lib\ext? I'll probably find out soon enough, but I just want to heare peoples' thoughts on that. I am satisfied with having my sdk directory hold my libraries, but there's something else... I got the run-time linking errors again spit out by java.exe when i'm running JoglTest.class (which basically just does a System.loadLibrary("jogl")). A message box pops up saying cannot load jawt.dll dependency [for jogl.dll]. That is, jogl.dll imports from jawt.dll which is another library that java.exe must find. Now, you'd think that having jawt.dll and jogl.dll in the same directory (where jawt.dll resides in the sdk)--c:\jdk1.5.0\jre\bin--would be alright, but for some reason I get that link error. Now, being intuitive as I am I said 'I remember reading that windows searches for .dlls starting with the current directory and working all the way to c:\windows\system32 (where you can usually find any installed .dll). So, shocked as to why jawt.dll couldn't be found in the same directory jogl.dll was in, I went ahead and copied jawt.dll into system32 folder. What happens again? -- another link error, but this time if you read carefully it says awt.dll, not jawt.dll. So one would assume jawt.dll depends on awt.dll (sort of like swing depends on awt), so being intuitive again I copied awt.dll into system32. Ta-da! It finally works -- no link errors. Okay, now that I can actually load a library from my erm... library path, I can continue learning the jogl api. But it still bugs me that I had to put jawt.dll and awt.dll that were in c:\jdk1.5.0\jre\bin in system32 in order for jogl.dll which is also in c:\jdk1.5.0\jre\bin to be loaded. Any takers? [Edited by - temp_ie_cant_thinkof_name on October 9, 2004 5:35:03 AM]