[cmake] Build system always uses DUNE modules from the system

[blattms]

I have the following tree:

opm-2.10
|___ dune-common
         |__ opm-parallel
|___ ....
|___ opm-simulators
         |__ opm-parallel

This kind of build setup used to automatically pick up the dune libraries from below opm-2.10 and not the ones on the system, but now I end up with the ones from the system

opm-2.10$ ls dune-*/opm-parallel/lib/libdune*
dune-common/opm-parallel/lib/libdunecommon.a       dune-grid/opm-parallel/lib/libdunealbertagrid3d.a
dune-geometry/opm-parallel/lib/libdunegeometry.a   dune-grid/opm-parallel/lib/libdunegrid.a
dune-grid/opm-parallel/lib/libdunealbertagrid1d.a  dune-uggrid/opm-parallel/lib/libduneuggrid.a
dune-grid/opm-parallel/lib/libdunealbertagrid2d.a
opm-2.10$ ldd opm-simulators/opm-parallel/bin/flow| grep libdune
	libdunegeometry.so.2.9.0 => /lib/x86_64-linux-gnu/libdunegeometry.so.2.9.0 (0x00007f25271eb000)
	libdunecommon.so.2.9.0 => /lib/x86_64-linux-gnu/libdunecommon.so.2.9.0 (0x00007f25271ce000)
opm-2.10$ grep -i dune opm-simulators/opm-parallel/CMakeCache.txt 
# For build in directory: /home/mblatt/src/dune/opm-2.10/opm-simulators/opm-parallel
CMAKE_FIND_PACKAGE_REDIRECTS_DIR:STATIC=/home/mblatt/src/dune/opm-2.10/opm-simulators/opm-parallel/CMakeFiles/pkgRedirects
PYTHON_GENERATE_DOCSTRINGS_PY:FILEPATH=/home/mblatt/src/dune/opm-2.10/opm-common/opm-parallel/python/generate_docstring_hpp.py
PYTHON_INSTALL_PY:FILEPATH=/home/mblatt/src/dune/opm-2.10/opm-common/opm-parallel/python/install.py
//The directory containing a CMake configuration file for dune-alugrid.
dune-alugrid_DIR:PATH=dune-alugrid_DIR-NOTFOUND
//The directory containing a CMake configuration file for dune-common.
dune-common_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/dune-common
//The directory containing a CMake configuration file for dune-fem.
dune-fem_DIR:PATH=dune-fem_DIR-NOTFOUND
//The directory containing a CMake configuration file for dune-geometry.
dune-geometry_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/dune-geometry
//The directory containing a CMake configuration file for dune-grid.
dune-grid_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/dune-grid
//The directory containing a CMake configuration file for dune-istl.
dune-istl_DIR:PATH=/usr/lib/cmake/dune-istl
//The directory containing a CMake configuration file for dune-uggrid.
dune-uggrid_DIR:PATH=/usr/lib/x86_64-linux-gnu/cmake/dune-uggrid
opm-simulators_BINARY_DIR:STATIC=/home/mblatt/src/dune/opm-2.10/opm-simulators/opm-parallel
opm-simulators_SOURCE_DIR:STATIC=/home/mblatt/src/dune/opm-2.10/opm-simulators
CMAKE_CACHEFILE_DIR:INTERNAL=/home/mblatt/src/dune/opm-2.10/opm-simulators/opm-parallel
CMAKE_HOME_DIRECTORY:INTERNAL=/home/mblatt/src/dune/opm-2.10/opm-simulators
opm-2.10$ 

Maybe I am doing something wrong here?

Is this fixed by #5091 et al.?

[blattms]

This is so strange. I will do another clean build to double check.

[blattms]

Clean build, same problem. Note that I am not using dunecontrol, only CMake files loaded with -C (dunecontrol would hopefully set dune-module_DIR).

As a developer I like the ability to build with different versions of DUNE without too much effort, even if the admin has decided to install DUNE on the system.

Whether this is needed for a release is up to debate (or users that compile themselves).

[blattms]

I'll do a fix.

[atgeirr]

As a developer I like the ability to build with different versions of DUNE without too much effort, even if the admin has decided to install DUNE on the system.

Possible workaround: install dune to a custom location and set that in cmake with -DCMAKE_PREFIX_PATH. Maybe that will pick that over the system install?

[blattms]

Sure you can work around but you will have to put a lot of paths there, though

[blattms]

BTW this also breaks using dumux together with opm-grid and checked out dune modules.