Thanks James, Karsten
That works thanks!
I then found that I needed to use mvn deploy:deploy-file to get the jar
into my local repo instead of mvn install:install-file otherwise maven
didn't create the necessary supporting files and I got a no supported
algorithms found error when I ran lein
You can see the actual path used by doing this in the repl:
(System/getProperty java.library.path)
I found it best to wrap native libs in a jar with this internal structure:
/META-INF/MANIFEST.MF
/native/linux/x86
/native/linux/x86_64
/native/macosx/x86
/native/macosx/x86_64
/native/windows/x86
I just upgraded from leiningen version 1.5.2 to 2.0.0 and noticed that the
native library path no longer seems to be set correctly.
Here is my project file:
(defproject naojure 0.1.0-SNAPSHOT
:description Clojure wrapper for Aldebaran Robotics java NAOQI binding.
Depends on the Aldebaran jar
Have a look at this:
http://nakkaya.com/2010/04/05/managing-native-dependencies-with-leiningen/
在 2013-3-22，上午6:55，Dave Snowdon dave.snow...@gmail.com 写道：
I just upgraded from leiningen version 1.5.2 to 2.0.0 and noticed that the
native library path no longer seems to be set correctly.
