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?
I could put together some prelinked platform specific libraries I suppose,
and distribute those (in the same wasy jniast works), although in this
case the build-native would be "intersting" to say the least.
I'm not even sure how much KAPPA has been rearranged, and therefore
whether these new *.a files are the straight equivalent to the original
intermediate products Alan was linking against. Does anyone know? Dave
perhaps?
So far it's taken me four days to get both the classic and java stuff to
build to the stage where I could even try and build the JNI wrappers for
KAPPA. This isn't looking good for a JS demo at ADASS at this rate!
Does anyone actually have any ideas what the demo should, well, demo? We
could always use Alan's old scripts, but is there something a bit more
impressive we could do, perhaps pushing tehoutput to one of the new Java
tools? That is, if I get to the stage where it all builds of course!
Al.
|