Find package Eigen3 for CMake

by

Since Eigen3 is completely header only, all you ever need is the path to the include directory. And this one, you are already defining manually anyway. So there is no real need for a FindEigen3.cmake or FIND_PACKAGE call.

Simply use

INCLUDE_DIRECTORIES ( "$ENV{EIGEN3_INCLUDE_DIR}" )

or

SET( EIGEN3_INCLUDE_DIR "$ENV{EIGEN3_INCLUDE_DIR}" )
IF( NOT EIGEN3_INCLUDE_DIR )
    MESSAGE( FATAL_ERROR "Please point the environment variable EIGEN3_INCLUDE_DIR to the include directory of your Eigen3 installation.")
ENDIF()
INCLUDE_DIRECTORIES ( "${EIGEN3_INCLUDE_DIR}" )

A few notes:

  1. If you want to access the content of a CMake variable, make sure to use ${...}
  2. $ENV{....} accesses environment variables.
  3. The second example will stop with an error if the environment variable is not set (and, thus, EIGEN3_INCLUDE_DIR cmake variable is empty)
  4. Be careful to use quotation marks around (evaluated) variables if they could contain whitespace. Otherwise, CMake will interpret it as a list.
  5. If you want to use custom find modules, make sure to either place them in you CMake installation or, as @Fraser pointed out above, make sure to point CMAKE_MODULE_PATH to the directory where it is. Not sure, but it could be that CMake checks the current directory as well automatically (where your CMakeLists.txt resides. Anyhow, setting EIGEN3_INCLUDE_DIR is totally unrelated to the location of FindEigen3.cmake
  6. However, it could be that your FindEigen3 script evaluates this variable to determine the location of your Eigen3 installation.
  7. Alternatively, self-built CMake-based projects often provide a <PackageName>Config.cmake. If you point a variable called <PackageName>_DIR to the directory containing this file, you can use FIND_PACKAGE( <PackageName> ...) as normal. See documentation of FIND_PACKAGE for details.

More Related Contents:

  1. Is it better to specify source files with GLOB or each file individually in CMake?
  2. CMake: use a custom linker
  3. Passing compiler options cmake
  4. CMake add_custom_command not being run
  5. What is the modern method for setting general compile flags in CMake?
  6. Getting a CMake Error: Cannot specify link libraries for target which is not built by the project
  7. Switching between GCC and Clang/LLVM using CMake
  8. How do I tell CMake to link in a static library in the source directory?
  9. CMake: Print out all accessible variables in a script
  10. How to set warning level in CMake?
  11. How to set linker flags for OpenMP in CMake’s try_compile function
  12. How to make CMake reconfiguration depend on custom file?
  13. CMake: how create a single shared library from all static libraries of subprojects?
  14. CMake – linking to library downloaded from ExternalProject_add()
  15. Does CMake offer a method to set the working directory for a given build system to use when running/debugging the project?
  16. CMake: How to add dependency on linker script for executable
  17. Correct way to use third-party libraries in cmake project
  18. How do I debug CMakeLists.txt files?
  19. How to Trace CMakeLists.txt [duplicate]
  20. Add all files under a folder to a CMake glob?
  21. Using CMake, how do I get verbose output from CTest?
  22. How can I add linker flag for libraries with CMake?
  23. How to configure Eclipse CDT for cmake?
  24. How to use CMake to find and link to a library using install-export and find_package?
  25. CMake : Changing name of Visual Studio and Xcode exectuables depending on configuration in a project generated by CMake
  26. Passing compiler options in CMake command line
  27. How to strip trailing whitespace in CMake variable?
  28. Linking GLEW with CMake
  29. How to print all the properties of a target in cmake?
  30. How to add a custom build type to CMake? (targeting make)

Leave a Comment