Re: [opendx-dev] JNI headers path

["David L. Thompson" <dthompsn@cs.umt.edu>]

The problem is, that not all jni headers are in the same place for 
the jdk. On Suns, Sun automatically installs this in /usr/include/... 
not in the jdk.

It does try to find the jni headers within your jdk if it is not 
specified. If you are getting that it can't find it, then it is not 
in a default area that we are checking. If you let me know where your 
jni headers are, we can determine whether checking this location 
should be added.

Pete's code is still being used--it was added back in around 4.0.9. 
So it is not possible to find the jni headers which are required for 
compiling some of the javadx code.

David

>Why do we have to check for JNI Headers.  When JDK is installed, the JNI
>headers are definitely present
>in jdk/include.  Checking the JNI headers extra seems to me adding
>uncessary comand to
>configure like
>
>./conifgure --with-jni--header-path=balh --with-jdk--path=blah
>--this-is-year-2000=blah and blah blah add 100 more here
>
>checking for javah... javah
>checking for java... /usr/bin/java
>checking for valid jni headers path... no
>configure: warning: JavaDX will be skipped during compilation due to
>limitations.
>checking for dirent.h that defines DIR... yes
>
>
>This seems to me idiosyncratic way of supplying 100 commands to
>./configure.
>
>In the begining when Pete added JAVADX it was much simplere, that to
>check for the presence of only
>JDK.
>
>I syggest these extra stuff should be removed, it maked life more
>compilcated.
>
>Thanks
>Suhaib

-- 
.............................................................................
David L. Thompson                          The University of Montana
mailto:dthompsn@cs.umt.edu                 Computer Science Department
http://www.cs.umt.edu/u/dthompsn           Missoula, MT  59812
                                            Work Phone : (406)257-8530