On Mon, 11 Oct 2004, David Berry wrote:
> Not sure what the background is, and I've never really looking into
> JNI, but why does JNI need access to anything other than the top level
> monolith entry points:
>
> SUBROUTINE NDFPACK_MON( STATUS )
> etc (plus of course various PCS systems)?
>
Whatever the interface, the question is how we install the complete
ndfpack monolith as a shared library.
Should there be _jni variants of all the link scripts? [since JNI replaces
many of the ADAM libraries with java variants].
I think I agree with Mark that the JNI build should happen in the kappa
build tree. On the other hand, a "public" shared library interface to each
monolith would be interesting since that would allow me to load kappa
directly into perl. [thereby removing the need for any messaging in
oracdr]
I'm still not clear what will happen when ccdpack and kappa are loaded
into the same server [given the symbol clash]. In principal a public
libkappa would be a 2 line edit to Makefile.am (just make sure libkapsub
doesn't become public) using LIBADD as is done in GKS. It may simply be
quicker to try it than to talk about it.
Tim
|