Tags: blattms/opm-material
Tags
Update Eigen requirements. Manually imported from opm-autodiff.
Update Eigen requirements. Manually imported from opm-autodiff.
change the version number to the scheme used by eWoms i.e., there is no distinction between the "API version" and the "Release version" anymore. IMO, the split scheme is just confusing for no benefit because we are handling API/ABI changes in a pretty relaxed manner anyway: i.e., whenever the "release version" gets incremented, the "API version" needs to follow suite!
Install header-only pkgconfig file to generic lib/ The previous version assumed that we had libraries, and thus always installs the .pc file in the multi-arch library directory. However, we now have modules which does not have a library, but whose header files still need to be located. Since the lib/ directory is usually in the pkgconfig search path, it is natural to put them there.
Install header-only pkgconfig file to generic lib/ The previous version assumed that we had libraries, and thus always installs the .pc file in the multi-arch library directory. However, we now have modules which does not have a library, but whose header files still need to be located. Since the lib/ directory is usually in the pkgconfig search path, it is natural to put them there.
Allow static linking for SuiteSparse to be forced If -DSUITESPARSE_USE_STATIC=ON, then the build system will only look for static versions of the libraries that are part of SuiteSparse, even if dynamic/shared versions are present on the system. Thus, the default of preferring dynamic libraries can be overridden. SuiteSparse is rarely built ourselves, but still uncommon enough to not be present on computing clusters. This patch allows us to install the libraries on a workstation, for instance from package suitesparse-devel and link to it statically without having to maintain our own build tree.