The only problem with building the native libs that I'm aware of is the
include of jni.h. I have two solutions in mind:
1. Configure option: --jni-include-dir=...
2. Include a jni.h with Classpath. This requires changes to our configure
scripts and Makefiles and such, because it should do the same sort of thing
as Japhar, dynamically building the jni.h stuff. It should work, though,
since jni.h is supposed to be VM-independent.
Option 1 is easier, option 2 is more thorough and cleaner. Anyone have any
preferences, reasons to do one over the other? If it's #2, it would be
better if someone else does it. I am aiming for quick-and-dirty,
get-the-damn-thing-working-with-Japhar right now, and I am not liable to
spend a lot of time working on just getting jni.h into the tree.
--John Keiser
