Samuel's Tech Blog

I now also managed to start blipkit from inside Eclipse.

The trick was to start the whole eclipse (The eclipse using for building Bioclipse) preceded with LD_PRELOAD=...the path to libjpl.so , and before that adding the paths to where libjava.so and libjvm.so are located.

So I created the following startup script for eclipse:

export LD_LIBRARY_PATH="/usr/lib/jvm/java-1.5.0-sun-1.5.0.19/jre/lib/i386/client/:/usr/lib/jvm/java-1.5.0-sun-1.5.0.19/jre/lib/i386/"
LD_PRELOAD=/usr/local/lib/pl-5.7.15/lib/i686-linux/libjpl.so /home/samuel/program/eclipse/eclipse &

More details are found in my previous blog post "Finally got blipkit started from java via jpl".

Gotta learn how to make this more platform independent. Found some interesting reading here:

• http://wiki.eclipse.org/Equinox_Launcher#Finding_a_VM.2C_Using_JNI_Invocation_or_Executing_Java
• http://wiki.eclipse.org/FAQ_How_do_I_run_Eclipse%3F

Hopefully the above tricks are only needed on Linux. Chris, author of BLIPKIT says he never had any troubles using blipkit from java (via JPL) on Mac OS, and I've heard that integrating SWI-Prolog is easier on windows, since there the Prolog kernel is packaged in a dll.

So, now continuing with the other steps in a previous blog post.