I know the EclipseP5Exporter has technically been replaced, but according to the wiki, its replacement doesn't do exports yet, so I still need it.
Why does the exporter package so many .jar files into it's output? Neither the in-app Processing exporter, or the default mac app exporter in eclipse do that.
My guess is that they're there in case Java isn't installed on the target machine. Can I remove these from the lib folder for the exported exe without messing something up? 'These' being everything except core.jar and <myAppName>.jar .
Yeah I figured that would be necessary, just thought I'd see if anyone had any deeper knowledge on the subject. By experimentation, it would appear that the only .jars that you need are: core.jar <myAppName>.jar jsse.jar sunjce_provider.jar sunpkcs11.jar ui.jar
and if using opengl: jogl.jar gluegen-rt.jar opengl.jar and their associated native files.
Caveat: only tested so far on my mac, and only tested to see if the game would start up and display its basic scene. Interestingly, removing ui.jar during testing appeared to cause some kind of hang in the JVM itself, as putting the file back still wouldn't let the app start. Shortly after my firefox and even the console became unresponsive, and I had to reboot. Which for some reason reset the mac spotlight indexing. All this may be a one-time/unreproducible bug, but I'm none too keen to keep testing it. ><
The kind of files I was able to remove included: apple_provider.jar charsets.jar classes.jar j3dcore.jar jai_core.jar JavaRuntimeSupport.jar jce.jar localedata.jar mlibwrapper_jai.jar
and several others.
Leave a comment on gordoncsa's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic