Probably an error caused during merging.

Implements the dune_add_test mechanism and
applies it to all the dune-common tests.

Conflicts:
	dune/common/test/CMakeLists.txt

It allows ctest to correctly schedule parallel tests
even though running through ctest -j.

This enables users to have several build directories like
build-clang, build-gcc5, build-debug, and still get all
of them ignored.

A list of numbers may be given and the test is executed with all
those processor numbers, unless the user variable DUNE_MAX_TEST_CORES
is exceeded. In sequential builds, tests with a number higher than 1
are discarded.

Nothing needs to be included with proper C++11 compilers.

Old feature support macros which were tested until 2.4, kept around
for one more release. As these are now always supported due to the
new compiler requirements, they are directly defined without an
explicit test.

Conflicts:
	cmake/modules/CMakeLists.txt
	cmake/scripts/CMakeLists.txt

It is outdated.

We aim to document the entire relevant user API. Some functions
from CMake are not worth wrapping, so we need to add them to our
documentation.

Broken/missing references, wrong directives etc.

As documented, tranformTuple should support AddRefTypeEvaluator. As
std::make_tuple will remove references (using std::decay) from the
funtor's return type, the returned tuple would contain copies of the
values. This is not the intended behavior.

This patch adds AddRefTypeEvaluator to the utilitytest and fixes the
return type of transformTuple.

These commits broke compiling / linking if one package was found
but the includes / libraries were not added. We need a different
approach to hide the ENABLE_* trick from the user and keep full
testing capabilities.
This reverts commits 0f12caff
and d75c3a46.

We do not want one such documentation per module, but instead
we would allow people to use it from their module and get a
documentation generated from all the dependent modules. This
needs some changes to the machine.

This includes the following workflow:

* The cmake module path is globbed for any modules matching *.cmake
* The opening comment is parsed for the following rst directives:
  cmake_function, cmake_module, cmake_variables
* From those, a browsable documentation is generated.

To run properly, a python interpreter and sphinx are needed.

If you rely on it, add the deleted CMake files to your module.