opm-upscaling

mirror of https://github.com/OPM/opm-upscaling.git synced 2025-02-25 18:45:23 -06:00

Single-phase and steady-state upscaling methods

Go to file

Arne Morten Kvarving c2a49b8495 added: MAINTAINERS file with maintainer information		2013-09-23 12:56:34 +02:00
attic	explicitly include <iostream> in files which use std::cout or std::cerr	2013-09-05 12:45:02 +02:00
cmake	require opm-core from the opm-material module	2013-09-11 13:16:54 +02:00
debian	Alert package maintainer about versioned dir option	2013-08-27 09:31:07 +02:00
doc/doxygen	Remove remnants of the Autotools build system	2013-02-22 23:25:45 +01:00
examples	fixed: enable running upscale_elasticity compiled against MPI enabled libraries	2013-09-16 17:10:11 +02:00
m4	Compatibility module for dunecontrol-driven clients	2013-08-10 20:03:21 +02:00
opm	changed: make the matrixops helpers a normal c++ class	2013-09-11 19:00:17 +02:00
redhat	Alert package maintainer about versioned dir option	2013-08-27 09:31:07 +02:00
tests	Skip empty lines when comparing upscaling results.	2013-09-11 21:30:55 +02:00
.gitignore	Ignore generated class doc. when building in-tree	2013-03-07 10:56:27 +01:00
CMakeLists_files.cmake	added: tests for upscale_elasticity	2013-09-11 19:00:17 +02:00
CMakeLists.txt	Build executables before running tests	2013-09-11 00:06:56 +02:00
configure	Search for directory containing build scripts	2013-08-16 23:16:57 +02:00
CTestConfig.cmake	Import cmake/ from commit 5f82198c in opm-core	2013-02-22 23:25:21 +01:00
dune.module	Add a label field to the project information	2013-08-10 20:35:22 +02:00
MAINTAINERS	added: MAINTAINERS file with maintainer information	2013-09-23 12:56:34 +02:00
README	Remove remnants of the Autotools build system	2013-02-22 23:25:45 +01:00
TestUpscalingBinaries.cmake	added: tests for upscale_elasticity	2013-09-11 19:00:17 +02:00

README

Preparing the Sources
=========================

Additional to the software mentioned in README you'll need the
following programs installed on your system:

  cmake >= 2.8

Getting started
---------------

If these preliminaries are met, you should run 

  dunecontrol all

which will find all installed dune modules as well as all dune modules 
(not installed) which sources reside in a subdirectory of the current 
directory. Note that if dune is not installed properly you will either
have to add the directory where the dunecontrol script resides (probably 
./dune-common/bin) to your path or specify the relative path of the script.

On your project and all uninstalled DUNE source modules found the script 
will then calls the GNU autoconf/automake to create a ./configure-script 
and the Makefiles. Afterwards that configure script will be called and the
modules will be build using make all

Most probably you'll have to provide additional information to dunecontrol 
(e. g. compilers, configure options) and/or make options. 

The most convenient way is to use options files in this case. The files
defining three variables:

AUTOGEN_FLAGS    flags passed to autogen
CONFIGURE_FLAGS  flags passed to configure
MAKE_FLAGS       flags passed to make

An example options file might look like this:

#use this options to autogen, configure and make if no other options are given
AUTOGEN_FLAGS="--ac=2.50 --ac=1.8" #Forces automake 2,50 and autoconf 1.8
CONFIGURE_FLAGS="CXX=g++-3.4 --prefix=/install/path" #force g++-3.4 as compiler
MAKE_FLAGS=install #Per default run make install instead of simply make

If you save this information into example.opts you can path the opts file to
dunecontrol via the --opts option, e. g.

  dunecontrol --opts=example.opts all

To get a full list of available configure flags just run

  dunecontrol configure --help

after running at least 
  dunecontrol autogen

More info
---------

See

     dunecontrol --help
   
for further options.


The full build-system is described in the dune-common/doc/buildsystem (SVN version) or under share/doc/dune-common/buildsystem if you installed DUNE!

$Id: duneproject 5842 2010-01-20 18:48:34Z joe $