Brian Jones wrote:
> Could someone email me what it would take to make the native libs
> useful for installation?  I'm assuming we basically need some sort of
> shared library, possibly several, all installed appropriately for
> whatever VM we are using.  The more details the better.

The Hackers Guide gives my view of library layout.  Roughly, one shared
library per package, loaded in a static initializer.  Named libXXX.so where
XXX is the package name.  (I many have actually used libjaphar_XXX.so
because Japhar used to require that).  Plus maybe a common library. 
Interlibrary dependencies are broken in libtool, so I don't know for sure
how we'll make this all work.  I had to link my java.io libraries with "ld"
by hand.

Oh, and I'd install the libraries in the JVM specific "lib" directory.  I
don't think classpath needs its own directory space for this.

Which brings up a point.  John, you said you got "Hello, World" to work with
classpath.  Were you using Sun's java.io for this?  If you got my java.io
native libraries to build and install properly using automake/libtool, you
are a better man than me.  Especially since they depend on your old method
id caching library which may or may not be part of CVS anymore.

-- 
Aaron M. Renn ([EMAIL PROTECTED]) http://www.urbanophile.com/arenn/

Reply via email to