From c08859052b1e734722a02f0e68251606208fcd8b Mon Sep 17 00:00:00 2001 From: Franck HOUSSEN Date: Sun, 13 Aug 2023 10:59:53 +0200 Subject: [PATCH] README: document use of *.pc and *.cmake files. --- README.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 409063a8..51625c3e 100644 --- a/README.md +++ b/README.md @@ -286,8 +286,17 @@ $ LIBS="-framework Accelerate" FFLAGS="-ff2c -fno-second-underscore" FCFLAGS="-f ## Using arpack-ng from your own codebase -The *.pc and *.cmake files provided by `arpack-ng` are only pointing to arpack libraries. +The `*.pc` and `*.cmake` files provided by `arpack-ng` are only pointing to arpack libraries. If you need other libraries (like MPI), you must add them alongside arpack (see CMake example below). + +Typically, if you need + +- ARPACK: at compile/link time, you'll need to provide BLAS and LAPACK. + +- ARPACK with eigen support (arpackSolver): at compile/link time, you'll need to provide BLAS, LAPACK and Eigen. + +- PARPACK: at compile/link time, you'll need to provide BLAS, LAPACK and MPI. + Examples are provided in `tstCMakeInstall.sh` and `tstAutotoolsInstall.sh` generated after running cmake/configure. ### With autotools