Arne Vajh?j wrote:
Mike Schilling wrote:
Having said that, suppose for the sake of argument that you'd
constructed seperate JNI for Windows, Mac, and Linux [1], and were
happy that you'd now solved the problem for all of your likely
users.
What's the best way to package your application? Do you need three
different versions, or is there some magic that will allow the app
to
locate and load the proper version of the JNI library at runtime?
I would go for an installer generator that know all 3 OS'es.
No simple packaging solution.
Yeah, that's what I thouight. That's one of the reasons I try as
hard as I can to avoid JNI. Imagine if you could do the following:
1. Put a JNI-path entry in a jar file's manifest
2. This would point to a JNI library, indexed by os.name, os.arch, and
os.version
Developing JNI would still be a bit onerous, but shipping JNI-using
apps would be a breeze. And adding new platforms would be
straightforward for either the developer or the end-user.