[lisplab-devel] Mac OS X
Knut Skogstrand Gjerden
knut.gjerden at ntnu.no
Fri Feb 19 10:59:27 UTC 2010
Pong!
Sure, it is quite easy (at least if you run SBCL). To link against Apple's blas and lapack, you can put
(defvar *lisplab-libblas-path* #P"/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib"); "Path to BLAS shared object file.")
(defvar *lisplab-liblapack-path* #P"/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib"); "Path to LAPACK shared object file.")
(defvar *lisplab-libfftw-path* #P"/opt/local/lib/libfftw3.dylib"); "Path to FFTW 3 shared object file.")
(defvar *lisplab-libfftw-threads-path* #P"/opt/local/lib/libfftw3_threads.dylib"); "Path to FFTW 3 thread extension shared object file.")
at the top of lisplab.asd. These addresses should be standard on any Mac, so you can just copy-paste, but check if your fftw-library is installed under /opt or /usr.
Then, all you have to do (in SBCL) is to (require 'lisplab) and you are good to go. I usually do this in my .sbclrc-file because I am lazy, but you can do it anywhere in your lisp. If your lisp is not SBCL, you have to do some (asdf load-op ...)-stuff instead, which I do not remember because I never do it.
Knut
On 18. Feb, 2010, at 5:08 PM, Adam Higuera wrote:
> Just pinging the list to see if anyone has had any success building lisplab on Mac OS X.
>
> In particular would someone more knowledgeable than me like to explain what to do about *lisp-blas-path* etc if I want to link against Apple's Accelerate framework?
> _______________________________________________
> lisplab-devel mailing list
> lisplab-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/lisplab-devel
More information about the lisplab-devel
mailing list