[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [PROPOSAL] New Virtual Packages and way to handle Classpath



> I haven't used JNI much, so it would be nice if someone who packages a JNI
> library could chip in here and provide some insight about what's necesary, and
> how they use to find it.

For libreadline-java:

It builds explicitly against gcj and gcjh with the /usr/include/jni.h
provided by libgcj4-dev.  This is done so the package build is
guaranteed to work out of the box regardless of a user's alternatives,
default $JAVA_HOME (which may be appropriate for their day-to-day work
but not for building libreadline-java), etc.

Since it's a library, it doesn't have a startup script and so at runtime
it uses whatever JVM is running its parent app.  However, it works with
kaffe (or at least will work with kaffe once the patch for #167936 is
properly applied), gij and blackdown without any additional command-line
options (beyond putting libreadline-java.jar in the classpath).  This is
in part assured by the policy requirements that all JVMs search
/usr/lib/jni for JNI modules.

Not sure if this is the sort of information you were asking for.

b. :)



Reply to: