Has anyone tried building jnilib bundles with the autotools suite
(autoconf, automake and libtool)?
The recommended command-line method I've seen documented requires source
files. To make this work with a configure script (that wants to compile
the object files first), I've seen code like this in one project's
Makefile.am:
bundle:
rm -rf jni/*.o
c++ -bundle -I/System/Library/Frameworks/JavaVM.framework/Headers
\
-I. -DHAVE_STRSTREAM -o libhippoplot.jnilib -framework JavaVM \
jni/*.cxx pattern/*.cxx reps/*.cxx src/*.cxx transforms/*.cxx \
functions/*.cxx
You'll note the first thing it does is delete all the object files created
by previous Makefile steps! In addition, this target exists outside of the
whole libtool domain--it should be managing details of how to build a
shared library.
Right now I have my JNI code portable between UNIX and MinGW32 (GNU tools
on Windows) with a single configure script. I'd love to be able to do the
same for MacOS X; I'm planning on writing an article on portable JNI
using autotools. Any help?
Thanks in advance!
--kd
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
