On Mon, 11 Oct 2004, Alasdair Allan wrote:
> I haven't tried to build the JNIAPP stuff against the new CVS arrangement
> before and, funnily enough, there are some problems.
>
> It looks like Alan linked the JNIKAPPA stuff against -lkappa -lkapview
> -lkapsub, these look to be intermediate build products for kappa that
> are buried in places like fairly far down the new build tree under the
> new scheme, e.g. /h/jini/checkout/applications/kappa/libkappa/.libs
>
> Does anyone have any suggestions on how to link to this stuff elegantly?
Al,
I would be somewhat tempted to build the jni shared library as part of
the classic KAPPA build rather than as part of the starjava build.
As you know this is not the way that JNIAST/JNIHDS work, but there
are some differences in the situation:
1. In the case of JNIAST/JNIHDS they are linking to well-defined
public APIs (AST/HDS); I presume this isn't the case for KAPPA.
2. There wasn't an autoconf system when I was working out how to
do JNIAST/JNIHDS.
You would presumably put the .c files and .h files (the latter
produced by javah from the java class files) into a jni/ subdirectory
of applications/kappa. As far as automatically producing a
distributable starjava system goes you'd still have to check the
built libraries files into the starjava source tree as JNIAST/JNIHDS
do at present - this isn't ideal, but as long as we have the autoconf
and starjava systems considered as separate entities something like it
will be necessary.
It's just a suggestion - you'll have to look at the details of the
libraries involved and see what you think makes most sense.
Mark
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|