> >./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. >
Just a thought. In the old 3.1.4b javaDX, one set a number of ENV VARs pointing to appropriate paths for java bits and pieces. Seems like if configure prompted you right at the beginning for the necessary paths, then wrapped them into the command above, one would not come back an hour later to see it waiting; or if you set ENV VARs, you could start it and walk away immediately. That's of course if there is not a standard location for these on the various systems that can be reliably found. Chris Pelkie Vice President/Scientific Visualization Producer Conceptual Reality Presentations, Inc. 30 West Meadow Drive Ithaca, NY 14850 [EMAIL PROTECTED] (607) 257-8335 or (607) 254-8794
