Hi,
some of you might have noticed that I am preparing an inofficial DUNE
2.2.1 release with support for CMake and some new features of ISTL.
They are now quite stable an I was able to compile
opm-core,omp-porsol, dune-cornerpoint, and opm-upscaling with it.
Still the approach that I used is a little bit orthogonal to the OPM
approach. The dunecontrol script of the cmake branches detects that it
can use CMake to build the opm modules. It therefore directly call
cmake instead of configure. Unfortunately this means that all
--with{,out}-... --{en,dis}able-... get ignored and the external
software will not be found.
A quickfix would be to extract the pathes provided with
--with-<package>=... and simply add them to the CMAKE_PREFIX_PATH
variable. This hopefully ensures that the find_xxx functions succeed
in most cases.
Of course this means on cannot disable features, but
at least for me that is not important. Are there any objections?
Using this approach inside of the handmade configure files might also
reduce the maintainance effort and reduce errors due to missing
--with-<package> treatment in it.
Cheers,
Markus
--
Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de
Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany, USt-Id: DE279960836
Tel.: +49 (0) 160 97590858 Fax: +49 (0)322 1108991658
Please notice the new address!
_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm
