[armedbear-devel] c++ library FreeLing from ABCL

Ville Voutilainen ville.voutilainen at gmail.com
Wed Jul 10 14:09:24 UTC 2013

On 10 July 2013 17:00, Alexandre Rademaker <arademaker at gmail.com> wrote:

> I have tried both System.load and System.loadSystem. Apparently the
> problem is how the abcl is initiated:
> Following @Alessio suggestion, that is, using abcl.jar in the
> classpath and start the org.arbedbear.lisp.Main, it works:
> urca:java arademaker$ java -Djava.library.path=. -cp
> freeling.jar:/usr/local/abcl-bin-1.1.1/abcl.jar
> org.armedbear.lisp.Main
> Armed Bear Common Lisp 1.1.1
> Java 1.6.0_51 Apple Inc.
> Java HotSpot(TM) 64-Bit Server VM
> Low-level initialization completed in 0.494 seconds.
> Startup completed in 2.187 seconds.
> Loading /Users/arademaker/.abclrc completed in 9.59 seconds.
> Type ":help" for a list of available commands.
> CL-USER(1): (jstatic "loadLibrary" "java.lang.System" "freeling_javaAPI")
> CL-USER(2): (jnew "edu.upc.freeling.MacoOptions" "en")
> #<edu.upc.freeling.MacoOptions edu.upc.freeling.MacoOptions at 716....
> {11ACBF5C}>
> But following my original way, that is, start abcl using the -jar
> option, it fails!! Why is that? What is the right way to start ABCL?

See eg. http://manuelselva.wordpress.com/2009/02/10/java-cp-and-jar/.
It seems that -jar causes -cp to be ignored...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/armedbear-devel/attachments/20130710/8cee2b8d/attachment.html>

More information about the armedbear-devel mailing list