On Mon, 11 Oct 2004, Alasdair Allan wrote:
> Mark Taylor wrote:
> > Alasdair Allan wrote:
> > > Does anyone have any suggestions on how to link to this stuff
> > > elegantly?
> >
> > 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.
>
> This sounds like a decent plan, unless anyone has any massive objectios
> to me doing it this way I'll start fiddling with KAPPA to see if I can
> make this work. I might stick it on a branch if it looks to tricky...
Hi Al,
a little while back I played around and got a starconf-based build working
for JNIAST. This is still sitting on a JNIAST branch "BRANCH-starconf" as
I haven't found time to look at JNIHDS and SPLAT (and Mark and I decided
we didn't actually gain much from this, so there's been no urgency).
I mention it as it should demostrate how to get libtool to build a
dlopen'able library for loading into Java.
Cheers,
Peter.
|