From 188590db8269e3fb422bca194ea1ec6c364d94c2 Mon Sep 17 00:00:00 2001 From: Gael Guennebaud Date: Wed, 27 Jul 2016 15:07:35 +0200 Subject: Add instructions for LAPACKE+Accelerate --- doc/UsingBlasLapackBackends.dox | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'doc/UsingBlasLapackBackends.dox') diff --git a/doc/UsingBlasLapackBackends.dox b/doc/UsingBlasLapackBackends.dox index a3ffdda57..caa597122 100644 --- a/doc/UsingBlasLapackBackends.dox +++ b/doc/UsingBlasLapackBackends.dox @@ -43,6 +43,13 @@ Do not miss this \link TopicUsingIntelMKL page \endlink for further discussions In order to use an external BLAS and/or LAPACK library, you must link you own application to the respective libraries and their dependencies. For LAPACK, you must also link to the standard Lapacke library, which is used as a convenient think layer between %Eigen's C++ code and LAPACK F77 interface. Then you must activate their usage by defining one or multiple of the following macros (\b before including any %Eigen's header): +\note For Mac users, in order to use the lapack version shipped with the Accelerate framework, you also need the lapacke library. +Using MacPorts, this is as easy as: +\code +sudo port install lapack +\endcode +and then use the following link flags: \c -framework \c Accelerate \c /opt/local/lib/lapack/liblapacke.dylib + -- cgit v1.2.3
\c EIGEN_USE_BLAS Enables the use of external BLAS level 2 and 3 routines (compatible with any F77 BLAS interface)
\c EIGEN_USE_LAPACKE Enables the use of external Lapack routines via the Lapacke C interface to Lapack (compatible with any F77 LAPACK interface)