Bugfix change from function to macro

This change is similar to commit 89be4e14: After find_package_append_to
changed from function to macro to pick up the configuration not only
from the module itself but also from everything it pulled it, the
variable MODULE is overwritten (variable module in lower case is a
parameter, so it is replaced in the source body). Thus, the test in the
end is not whether *this* module was found, but if its last dependency
was! This made the build crash only in some projects but not in others.
Merge pull request #34 from rolk/034_tinyxml

Similar to OPM/opm-core#205
Follow changes to opm-core.
Added support for FastAMG if that is available.
Documented previously undocumented paramerters of solve method
Merge pull request #35 from atgeirr/combined

Adapt to changes in OPM/opm-core#203
Disable the other examples that uses C++11 features too
Merge pull request #31 from rolk/031_constexpr

error: 'constexpr' does not name a type
Replaced compile time warning about missing fast AMG with a runtime warning in verbose mode.
Merge pull request #36 from blattms/release-dune-cmake

Add support for AMG improvements when using inofficial 2.2 DUNE release with CMake support
added: debian packaging control files
Merge pull request #38 from akva2/debian_packaging

added: debian packaging control files
input files to co2_sim_test and a tutorial explaning how to run it
a tutorial to explain how to run a simple blackoil model with its corresponing input file and python script to generate figures
changed to include paths to the new examples
copied from opm-core to have unified layout and style in the documentation
Indicate failure to find header with blank string

Use empty string instead of zero, so it can be tested with #ifdef as
well as #if in the C++ source code.
Indicate failure to find header with blank string

Use empty string instead of zero, so it can be tested with #ifdef as
well as #if in the C++ source code.
Prepend source directory to include path

If the dependencies have files with relative paths that are ambigious
to our own, we want our version to be the first candidate for inclusion.
This is a variant of the reason for why we always include the build
directory first (and still does).
Don't search system directories when path given

If the user has given a path to the module, then the system paths should
not be searched, as these may contain an old and outdated version. We
don't necessarily want that just because there was a problem with our
own installation!