I was mostly thinking about the regular dune release (with autotools), for OPM dunecontrols uses cmake no matter what. If this is easier to get to work with the dune cmake branch, then that is what we will support.
It could be easier for you to use the second build approach (I detailed what I did in a previous mail). One thing that may come in handy for that is to use "cmake -C myopts.cmake ../opm-core" from within opm-core-build (for example). My options file looks like this (on CentOS 5). Note that the CACHE STRING "comment" part is necessary for things to work smoothly. set(CMAKE_C_COMPILER "gcc" CACHE STRING "C compiler") set(CMAKE_CXX_COMPILER "g++" CACHE STRING "C++ compiler") set(CMAKE_Fortran_COMPILER "gfortran" CACHE STRING "Fortran compiler") set(CMAKE_INCLUDE_PATH "/work/include" CACHE STRING "Include path") set(CMAKE_LIBRARY_PATH "/work/lib64" CACHE STRING "Library path") set(dune-common_ROOT "/home/atgeirr/dune/dune-common-2.2.1" CACHE STRING "Path to dune-common") set(dune-geometry_ROOT "/home/atgeirr/dune/dune-geometry-2.2.1" CACHE STRING "Path to dune-geometry") set(dune-grid_ROOT "/home/atgeirr/dune/dune-grid-2.2.1" CACHE STRING "Path to dune-grid") set(dune-istl_ROOT "/home/atgeirr/dune/dune-istl-2.2.1" CACHE STRING "Path to dune-istl") set(SUPERLU_ROOT "/home/atgeirr/install/SuperLU_4.3" CACHE STRING "Path to SuperLU") set(ERT_ROOT "/home/atgeirr/install/ert-install" CACHE STRING "Path to ERT") set(PRECOMPILE_HEADERS OFF CACHE BOOL "Precompiled headers") Den 15. mars 2013 kl. 10:16 skrev Lars Vingli Odsæter: > On 15. mars 2013 09:49, Atgeirr Rasmussen wrote: >> I suggest that the following build-methods should be characterised as >> 'supported' and all other ways should be ignored. >> >> 1. Using dunecontrol to build all modules at once, including the dune core >> modules. >> 2. Using cmake to build our modules one by one but in the same directory, >> with all deps either in system locations or specified locations (this is >> what I do). >> > With dunecontrol do you mean dunecontrol with cmake or autotools (or both)? I > am currently trying to build DUNE/OPM with cmake using dunecontrol on rhel 5. > I am using the release-cmake-2.2 version of the DUNE core modules. I am close > to succeeding, issue #31 of opm-porsol must be resolved and possibly some > small fixes of opm-porsol and opm-upscaling that corresponds to pull request > #16 of dune-cornerpoint. > > Lars > > _______________________________________________ > Opm mailing list > [email protected] > http://www.opm-project.org/mailman/listinfo/opm _______________________________________________ Opm mailing list [email protected] http://www.opm-project.org/mailman/listinfo/opm
