OilfieldToolsNet/opm-simulators
4
0
Fork 0
mirror of https://github.com/OPM/opm-simulators.git synced 2024-11-25 02:30:18 -06:00
Code Issues Packages Projects Releases Wiki Activity
fd4f5f5a26
opm-simulators/CMakeLists.txt

80 lines
3.1 KiB
CMake
Raw Normal View History

Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
# -*- mode: cmake; tab-width: 2; indent-tabs-mode: t; truncate-lines: t; compile-command: "cmake -Wdev" -*-
# vim: set filetype=cmake autoindent tabstop=2 shiftwidth=2 noexpandtab softtabstop=2 nowrap:
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
###########################################################################
# #
# Note: The bulk of the build system is located in the cmake/ directory. #
# This file only contains the specializations for this particular #
# project. Most likely you are interested in editing one of these #
# files instead: #
# #
# dune.module Name and version number #
# CMakeLists_files.cmake Path of source files #
# cmake/Modules/${project}-prereqs.cmake Dependencies #
# #
###########################################################################
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
cmake_minimum_required (VERSION 2.8)
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
# additional search modules
Add a small bootstrapper to locate build system Currently this bootstrapper only finds the macros that are located in the cmake/ tree in this project. Projects that don't carry their own build system can specify search locations here.
2013-08-14 14:31:53 -05:00
find_path (OPM_MACROS_ROOT cmake/Modules/OpmInit.cmake
PATHS ${opm-macros_ROOT}
${CMAKE_CURRENT_SOURCE_DIR}
DOC "Path to build system macros and scripts"
NO_DEFAULT_PATH
)
list (APPEND CMAKE_MODULE_PATH "${OPM_MACROS_ROOT}/cmake/Modules")
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Added sim_fibo_ad_test, running two identical simulations with the SPE1 case
2013-11-26 05:55:41 -06:00
option( INCLUDE_NON_PUBLIC_TESTS "Include the tests which need non-public data" OFF)
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
# not the same location as most of the other projects? this hook overrides
macro (dir_hook)
endmacro (dir_hook)
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
# project information is in dune.module. Read this file and set variables.
# we cannot generate dune.module since it is read by dunecontrol before
# the build starts, so it makes sense to keep the data there then.
include (OpmInit)
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
# list of prerequisites for this particular project; this is in a
# separate file (in cmake/Modules sub-directory) because it is shared
# with the find module
include (${project}-prereqs)
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
# read the list of components from this file (in the project directory);
# it should set various lists with the names of the files to include
include (CMakeLists_files.cmake)
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
macro (config_hook)
# opm_need_version_of ("dune-common")
endmacro (config_hook)
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
macro (prereqs_hook)
endmacro (prereqs_hook)
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
macro (sources_hook)
endmacro (sources_hook)
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
macro (fortran_hook)
endmacro (fortran_hook)
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
macro (tests_hook)
endmacro (tests_hook)
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
# all setup common to the OPM library modules is done here
include (OpmLibMain)
Complete import of CMake support from OPM-Core
2013-05-15 03:40:00 -05:00
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
# download Eigen if user doesn't have the correct version
added: download and build eigen3 from git if not found on system
2013-07-09 04:37:56 -05:00
if (NOT EIGEN3_FOUND)
Separate build concerns for better maintainability Introduce a main build file which uses modules in the cmake/ directory for most of its bulk work, which agains retrieve information from files in the root of the source tree (dune.module, CMakeLists_files.cmake) to get information about the project. Thus, the cmake/ directory is shared between all the projects down to the last bit; only project-specific customizations go into the main file in form of _hook macros (which are called in specific places).
2013-08-02 07:07:33 -05:00
message (STATUS "Downloading Eigen3")
include (ExternalProject)
externalProject_Add (Eigen3
GIT_REPOSITORY git://github.com/OPM/eigen3
UPDATE_COMMAND git checkout 9f6cc779c101b87184076322603f496e5fdd0432
CMAKE_ARGS -DEIGEN_TEST_NO_OPENGL=1 -DEIGEN_BUILD_PKGCONFIG=0 -DCMAKE_INSTALL_PREFIX=${CMAKE_BINARY_DIR}/eigen3-installed
)
include_directories (${CMAKE_BINARY_DIR}/eigen3-installed/include/eigen3)
add_dependencies (opmautodiff Eigen3)
added: download and build eigen3 from git if not found on system
2013-07-09 04:37:56 -05:00
endif (NOT EIGEN3_FOUND)
Reference in New Issue Copy Permalink