> 1) Add a ./configure switch to enable some Kissme-specific JNI extensions. > > 2) Add #ifdefs to classpath/include/jni.h to enable Kissme-specific > JNI functions at the end of the function table. These include > functions for entering and exiting Kissme GC points.
What implications does this have for the scenario where Classpath is built as a package (eg .rpm or .deb) and Kissme loads the shared libraries for native IO from this package? Would the package have to be built with the kissme flag? Would it be possible to have Classpath generate two sets of native libraries? One would have the default functionality, the other would call the Kissme JNI functions to enter/exit GC points. John Leuner
signature.asc
Description: This is a digitally signed message part
