CMake scripts for painless usage of Tim Davis' SuiteSparse (CHOLMOD,UMFPACK,AMD,LDL,SPQR,...) and METIS from Visual Studio and the rest of Windows/Linux/OSX IDEs supported by CMake. The project includes precompiled BLAS/LAPACK DLLs for easy use with Visual C++.
The goal is using one single CMake code to build against SuiteSparse in standard Linux package systems (e.g. libsuitesparse-dev
) and in manual compilations under Windows.
Credits: Jose Luis Blanco (Universidad de Almeria); Jerome Esnault (INRIA).
(1) Install CMake.
(2) Only for Linux/Mac: Install LAPACK & BLAS. In Debian/Ubuntu: sudo apt-get install liblapack-dev libblas-dev
(3) Clone or download this project (latest release) and extract it somewhere in your disk, say SP_ROOT
.
SP_ROOT
with the original sources from each project:
SuiteSparse
: SuiteSparse/*
into SP_ROOT/SuiteSparse/*
.METIS
: (Optional, only if need METIS for partitioning)metis-X.Y.Z/*
into SP_ROOT/metis/*
.cmake_policy(SET CMP0022 NEW)
right after the line project(METIS)
in metis/CMakeLists.txt
.(4) Run CMake (cmake-gui), then:
SP_ROOT
SP_ROOT/build
CMAKE_INSTALL_PREFIX
or (in Windows) SUITESPARSE_INSTALL_PREFIX
to some other directory different than "Program Files" or "/usr/local" so the INSTALL command does not require Admin privileges.GKLIB_PATH
to the correct path SP_ROOT/metis/GKlib
.HAVE_COMPLEX
is OFF by default to avoid errors related to complex numbers in some compilers. (5) Compile and install:
In Visual Studio, open SuiteSparseProject.sln
and build the INSTALL
project in Debug and Release. You may get hundreds of warnings, but it's ok.
In Unix: Just execute make install
or sudo make install
if you did set the install prefix to /usr/*
(6) Notice that a file SuiteSparseConfig.cmake
should be located in your install directory. It will be required for your programs to correctly build and link against SuiteSparse
.
(7) Only for Windows: You will have to append CMAKE_INSTALL_PREFIX\lib*\lapack_blas_windows\
and CMAKE_INSTALL_PREFIX\lib*
to the environment variable PATH
before executing any program, for Windows to localize the required BLAS/Fortran libraries (.DLL
s).
Example CMake programs are provided for testing, based on Tim Davis' code in his manual:
#...
# ------------------------------------------------------------------
# Detect SuiteSparse libraries:
# If not found automatically, set SuiteSparse_DIR in CMake to the
# directory where SuiteSparse was built.
# ------------------------------------------------------------------
LIST(APPEND CMAKE_MODULE_PATH "${CMAKE_SOURCE_DIR}/..") # Add the directory where FindSuiteSparse.cmake module can be found.
set(SuiteSparse_USE_LAPACK_BLAS ON)
find_package(SuiteSparse QUIET NO_MODULE) # 1st: Try to locate the *config.cmake file.
if(NOT SuiteSparse_FOUND)
set(SuiteSparse_VERBOSE ON)
find_package(SuiteSparse REQUIRED) # 2nd: Use FindSuiteSparse.cmake module
include_directories(${SuiteSparse_INCLUDE_DIRS})
else()
message(STATUS "Find SuiteSparse : include(${USE_SuiteSparse})")
include(${USE_SuiteSparse})
endif()
MESSAGE(STATUS "SuiteSparse_LIBS: ${SuiteSparse_LIBRARIES}")
# ------------------------------------------------------------------
# End of SuiteSparse detection
# ------------------------------------------------------------------
#...
#TARGET_LINK_LIBRARIES(MY_PROGRAM ${SuiteSparse_LIBRARIES})
Remember to set SuiteSparse_DIR
to the install directory, if CMake does not find it automatically. This will not be required when suitesparse is available as a system library in a Unix/Linux environment.
Porting SuiteSparse
to CMake wasn't trivial because this package makes extensive usage of a one-source-multiple-objects philosophy by compiling the same sources with different compiler flags, and this ain't directly possible to CMake's design.
My workaround to this limitation includes auxiliary Python scripts and dummy source files, so the whole thing became large enough to be worth publishing online so many others may benefit.