Pete did have this somewhat working, but it could not locate the jars
for Netscape or for the Cosmo stuff. It also couldn't locate the jni
stuff correctly on the three systems I was on and others had
mentioned this problem. I added the new code so that the jni headers
could be located and the jars could be found. To perform a configure
that does not prompt for any user input, you can add the configure
flags. For example:
./configure --with-java-include-search-path="-I/path2jnih/
-I/path2jnimdh/" --with-java40jar-path=/path2java40jar/java40.jar
--with-cosmojar-path=/path2cosmojar/npcosmop211.jar
In Pete's version, configure had to be editted to place the path to
the Jar files and the jni search path could never be determined and
you would have to edit the java makefiles. To automate, just create a
script that calls configure with your one line with your path
information.
David
Dave,
I just ran configure with the output redirected, and an hour later,
realized that it was sitting there waiting for the user - me - to type in
the jni include info. It looks like this was put in there when you added
the command-line options for java.
I believe the whole purpose of configure is to *automatically* check the
system for stuff, not to ask the user. Prior to your change, it worked in
a pretty reasonable manner, building the javadx stuff if it could find the
pieces it needed, and not building it if it couldn't. Pete put a lot of
work in to have it intelligently look for those pieces. Could you please
put it back in?
Greg
.............................................................................
David L. Thompson The University of Montana
mailto:[EMAIL PROTECTED] Computer Science Department
http://www.cs.umt.edu/u/dthompsn Missoula, MT 59812
Work Phone : (406)257-8530
