LWJGL Eclipse Update Site

Started by Matzon, December 14, 2008, 19:25:29

Previous topic - Next topic


Hi Matzon, I was able to install it.

I could not launch the Test View however -

Eclipse Exception message:
Could not create the view: Plug-in "org.lwjgl.test" was unable to instantiate class "org.lwjgl.testview.LWJGLTestView".

Note that it's my first time trying to use org.lwjgl, but the test application in the 2.5 download package did work for me.


It does indeed work. :D Thanks very much for getting to this so quickly. In the meantime, I went ahead and got Jen's build working for 2.5. I've put it up on:


**Please note that this is temporary -- folks should not expect this dependency to stick around**

Obviously you can feel free to just copy it over to lwjgl.org/updates but I'm not sure if that's the best thing to do or not. The not ideal part is that I have not really fixed Jen's build so that it is automated, and I have *not* tested it on anything but OS X 64bit. Here are the steps I took:

1. Imported org.lwjgl.eclipseplugins into my workspace.
2. Followed all of the directions in readme.txt. That failed with some sort of obscure eclipse dependency ant error. :) But what it did do was copy all of the artifacts needed into the plugin skeletons. This is actually the hard part.
3. Imported the projects in org.lwjgl.eclipseplugins/build/plugins into the same workspace. This could theoretically create issues with file synchronization but in practice I think it is alright. If you're super anal you could do that in a fresh workspace.
4. Made some fixes to the imported org.lwjgl. These are pretty obvious, but the most significant is to change new path to    <classpathentry exported="true" kind="lib" path="native/windows/"/> from win32 and remove exported packages from MANIFEST.MF that don't exist anymore. If you want to repeat this and have problems feel free to contact me. milesparker @ the usual domain.
4. Copy org.lwjgl.updatesite/site.xml to org.lwjgl.feature/category.xml or wherever it makes sense.
5. Use the oh so passé and not at all automated PDE "Deployable Feature" export to create the site. The only change is to add the category.xml site under options.

Obviously, it would be nice to automate this and not so hard I think but there isn't much point to automating the part above without taking care of the stuff that the ant script is doing now. A job for Buckminster? :o..


Same with MilesParker's 2.5.  I think I can safely blame my setup :)

Error loading LWJGL
at org.eclipse.core.internal.runtime.Activator.getURLConverter(Activator.java:313)
at org.eclipse.core.runtime.FileLocator.resolve(FileLocator.java:227)
at org.lwjgl.Activator.start(Activator.java:58)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:783)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:774)


I wasn't actually testing using the test view but I just did and it works for both versions on my machine. So I can test for my own apps, what is your setup?

BTW if you're curious about what AMP project is doing with this, check out:




(go to 7:40 to see the 3D stuff.)

You've probably already all seen the GEF3D project that AMP 3D relies on, but if not..