This story has a happy ending. It turns out that instead of typing: ..... CLIPSJNI $ java -Djava.library.path=. -jar CLIPSJNI.jar shown in 7.6.3 of the Interfaces Guide, one should type: ..... CLIPSJNI $ java -Djava.library.path=. -jar CLIPSIDE.jar (CLIPSIDE, not CLIPSJNI) An interesting sign of the times: I made heavy use of ChatGPT which sent me in a number of wrong directions over the last couple of days on this. But the key to making it helpful was to give it the names of key directories and...
Per your suggestion I changed this line in the make file: debian : JAVA_HOME = /usr/lib/jvm/default-java to this: debian : JAVA_HOME = /usr/lib/jvm/java-11-openjdk-armhf/ I redid the 7.6.3 instructions. I jumped back to 7.3 to run the clips JNI, but after running java -Djava.library.path=. –jar CLIPSJNI.jar from the CLIPSJNI directory, I received the following error message: Error: Could not find or load main class –jar Caused by: java.lang.ClassNotFoundException: –jar I saw some posts on the internet...
I am attempting to install the CLIPS JNI-based IDE in Linux (Raspberry Pi / Debian) and keep getting the infamous error message: fatal error: jni.h: No such file or directory #include <jni.h> </jni.h> On my Raspberry PI, Java works fine - I can run regular java programs. I suspect the problem has something to do with my environment variables, which I have set up in the bashrc file like so: export PATH=$PATH:/home/pi/.local/bin/:/home/pi/Documents/CLIPScore/core/ export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-armhf/...