On Fri, 17 Dec 2004, Norman Gray wrote:
> Alternatively, why is the JNI stuff necessarily under java/? Would it
> not make more sense to generate the JNI library and classes as part of
> the `classic' build? In the end, all that JNI is, is a new interface
> to some classic libraries. The major client of this interface is in
> the java/ tree, yes, but that doesn't mean it can't be built
> separately. This would also mean that the java/ tree would be pure(r)
> Java.
The header files which define the native function prototypes
are built from the corresponding java classes using javah, so there
is a definite reason that the native libraries are compiled in the
java tree. I suppose(?) the header files aren't essential for
compiling the code, but you'd lose a lot of important compiler
warnings. Also the native libraries need to get put into jar files
for WebStart use (and in general the java system wants to install
them in sensible places).
This is not necessarily to say that the JNI stuff {c,sh}ouldn't
be built in classic, but there are issues.
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|