Ignore QtCreator project settings

QtCreator stores a file containing amongst other things the path to where
your build tree is and what parameters you used for the configuration
process. These data is user-specific and should not be stored in version
control.
Allow package dir. to be specified with _ROOT suffix

If one sets the variable foo_DIR it will cause CMake to look for a
configuration file in that directory. In case we want to set the root
directory to an installation which doesn't have a config-mode CMake
module, and use the find module provided by ourself, we need a separate
variable that can hold the location of this directory and the most
common suffix for this seems to be _ROOT (an alternative is _PREFIX)
Find module for Ensemble-based Reservoir Tools (ERT)

Although ERT is built with CMake, it does not yet provide a config-mode
module in its build directory. This also means that the find module must
be pointed to an installation, not a build directory.
Search for ERT and include in build if found

If the OpenMP flag is added to the build, this should probably be
propagated to the user programs as well.
Dependencies' directories can be spec. on cmd. line

Instead of having to run `ccmake` or looking up which variables that
must be set, the configure driver is now enhanced to recognize options
that sets the installation directories for some of the dependencies.
Allow to disable the inclusion of some libraries

Setting these options will cause these libraries to be dropped, even if
they can be found with automatic probes.
Use full path to packages specified

CMake will change to the source directory when processing the
CMakeLists.txt file which causes relative paths to be based on this
instead of at the build directory which is probably assumed by the
user.
Don't strip debug symbols from libraries

Infer the type of library from the target and only activate debug symbol
stripping if it is an executable format. Note that this changes the
signature of the strip_debug_symbols macro.
Make building libraries static or shared selectable

Default is still to make a shared object because this is the most
versatile target (it can be included in other shared objects as well
as executables).

Note that due to limitations in CMake, either a shared or a static
library can be built, but not both. (This is due to the fact that on
Windows, an import library has the same name as a static library).
Generate customized Doxyfile for each build
Use paths from build-spec. instead of relative paths
Generate documentation in a custom target

The targets are named after the similar targets when using Autotools.
Disable tons of warnings in building documentation

The volume of warnings generated for the documentation completely drowns
out anything else useful. Until we have fixed more of the comments, this
should be disabled as to focus on problems with the code instead.
Don't expect human interaction in build

If the build fails, we want the error logged to a file, not that the
build hangs on a terminal (which may even not exist!)
Make documentation installable

If `make install` is run, the document is included if and only if
it has already been built. If `make install-html` is run, then the
documentation is always generated first, before installation. To
build the documentation separately from installation use `make doc`
Explain why globs can be used to enumerate source code

The documentation argues against it, but I believe it uses flawed
reasoning.
Keep build dir tidy by relocating Fortran modules

If we are building in-source, we don't want to have a bunch of output
files in the root directory; instead we put them in CMakeFiles/ where
all the rest of the object files go.
Status update