Re: Packaging a library, with JNI and javadocs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Well the -java name extension should only (have I written that in policy?)
> be used for arch-independent packages. I would recommend an -jni name
> extension instead.
Hmm.. I packaged libreadline-java (a small JNI library with a couple of
wrapper classes) with the -java extension as a result of (my understanding
of) the java policy. :)
Is there a particular reason to distinguish between native Java classes and
classes with JNI implementations? As far as whoever's using them is
concerned, they appear the same, no?
The only issue I could think of was that you want the JVM to find the JNI
library in its default search path; I resolved this by putting the
corresponding C library in /usr/lib, and this appears to work fine from what
testing I've done.
> > Now, I've packaged a few simple programs before but never Java. Are
> > there any small packages out there which use JNI I could look at for
> > examples?
Well, I can offer libreadline-java for you to look at, but that of course
doesn't mean it's done the Right Way.
Ben. :)
- --
Ben Burton
benb@acm.org | bab@debian.org
Public Key: finger bab@debian.org
I don't hide much, but sometimes people don't understand that I
talk about them. Then we sit in the same room and they haven't got a clue.
That's also the reason why I don't want to explain every detail of my work.
- Tori Amos, Haaggsche Courant, 1994
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE9gDUFMQNuxza4YcERAveyAJwIoRRtUWWua+Ez5Hq2w9Z8HonJfACghY+f
hhXMy4/UrZrg/Xm9HInh7jQ=
=wBI7
-----END PGP SIGNATURE-----
Reply to: