Closed kwhat closed 4 years ago
@kwhat may want to take a look at this https://github.com/mojohaus/maven-native/issues/17
Yah, I was reading that earlier... maintaining backward compatibility is really a lost cause <1.8 || <11. It seems that jdkIncludePath really doesn't do anything meaningful unless you specify <javahOS/>
, even when only compiling native src without javah.
I finally got it working, took a bit of monkeying but it works well, thanks!
I am seeing errors like
fatal error: jni.h: No such file or directory
when trying to use jdkIncludePath in a compile goal. What does this configuration do, and more importantly why doesn't it add an include (-I) to the C src compilation? If this is for something else and I still need to add a<source><directory>${java.home}/include</directory></source>
why does it even exist?