JInput webstart demo

Engines, Libraries and Tools JInput
#41

Hi

Ok, I messed up the webstart ant script that compiles the jars. I’ve updated it and uploaded the results, far smaller :slight_smile:

I’m not sure what you mean by the packages not having the other binaries. On the server where the files are I just did

$ tar -tzf jinput_linux_2005-06-19.tgz
jinput.jar
libjinput-linux.so

$ tar -tzf jinput_osx_2005-06-27.tgz
jinput.jar
libjinput.jnilib

so the .so and .jnilib are there

There are 4 parts that each platform needs, the jutils jar for the plugin components, the coreAPI parts, the java plugin parts, and the native lib parts. Unlike jogl for example, the platform specific plugins do not have a common native interface. Where jogl has all the java parts in common on all platforms, jinput doesn’t. I could have created a shared jar that contained the coreAPI components and the jutils parts, and then for each platform have a java plugin jar and a native lib jar. This would have saved on server disk space. What I ended up doing, was for each platform, putting the coreAPI, jutils and the java plugin parts in one jar, and the lib in another. I thought this would make it simple for people to steal the jars from where they are now if they wanted too. Also, server disk space is not an issue.

Endolf

#42

Could be a Winzip <-> tgz thing I guess… I check again tonight.

What I’m really confused about is the single jar thing. I though there was now

1 uber jar for all java
3 native libs.

?

Kev

#43

You responded whilst I was adding the explination to my above post :slight_smile:

Endolf

#44

I think you should name the jar files distinctly then. eg. jinput_win32.jar, jinput_linux.jar, jinput_osx.jar

When Java people see a JAR file they don’t think of it being platform specific.

#45

Hi

They are. Check out the listing of the files here

Endolf.

#46

Ah, I was commenting based on the message three spaces up that showed the contents of the .tgz files. That showed just “jinput.jar”