CMake exports the major and minor components of the module version, but
not the revision. This patch fixes that omission.

I was bitten again by not properly cleaning build directories
while testing build system features. With this patch, the feature
* builds the symlinks in finalize_project instead of dune_project
  Only there the existence of the subdirectories in the build tree
  is guaranteed.
* The globbing expression is sane again.
* Properly excludes build directories
* works with cmake 2.8 and 3.1, per-module or global out-of-source builds.

We got the workaround_9220 code from Eigen. Now we
use the code as the Eigen project does, see for
example their file lapack/CMakeLists.txt.
This fixes the Fortran detection with Visual Studio
2015 CTP 6.

Patching the dune core modules just to have the advantages of
symlinks to the source tree is a bad idea. The patch introduces
a check for the variable DUNE_SYMLINK_TO_SOURCE_TREE instead, which
enables the macro if set.

CMake 3.1 issued a lot of warnings because it tried to symlink:
- git specific subdirs that are not present in the build tree
- build directories that are a subdir of the source instead of a sibling

The change
- adds a symlink iff a CMakeLists file was found in the source dir.
- excludes such build directory.

Tarballs can be built using "make package_source". But they contain
all files from the source directory. There is a way to ignore files.

We assume anyway that stdint.h and memrory are provided. The
according macros are never used. They were probably provided
to stay as compatible to Autotools as possible.
This fixes FS#1605.

It is already printed as the comment of the custom command.

Similar to last commit:
This macro was split off from DuneMacros.cmake in commit
e63ea0cf, but the new macro file was
not included in the list of installed modules.

Felix Gruber authored 10 years ago and Christoph Grüninger committed 10 years ago

This macro was split off from DuneMacros.cmake in commit
e63ea0cf, but the new macro file was
not included in the list of installed macros.

It seems the exclusion macros need to have a full list of headers
to work. This is hopefully the last commit...

The property must exist in order to have the exclusion macros work.
I only tested dune common which has no exclusions...

Thanks to Andreas Buhr for noticing!

As proposed in FS1584, make headercheck is now disabled by
default in cmake. This fact and how to enable it is printed
upon "make headercheck".

Apparently, that code never for executed/tested...

Together with the last patch, this fixes FS#1592.

[Typetraits][Compatibility] Provide partial backwards compatibility for is_indexable on old GCC versions

Older GCC versions have some nasty bugs related to SFINAE and indexing
with operator[]. This patch adds a configuration check for those
problems and a partial backwards compatibility hack for those older
compilers that is sufficient for our current use case in the VTK
writer.

GCC 4.4, I'm looking at you

The file DuneMacros.cmake is very crowded. Macros that belong
together should be placed in a separate module in order to increase
the visibility of its documentation IMO.

I accidentally commited them.

This is e.g. needed for dune-alugrid and might be a first step for
getting rid off the ParMETIS dependency.

Since CMake 3.1 the if() command no longer automatically dereferences
variables named in quoted or bracket arguments.
This fixes FS#1567.

It caused that pthread.h was not found as clang does not like
to get -std=c++11 passed.

With a compiler name given to CMAKE_CXX_COMPILER (instead of a path),
the name is correctly expanded on the first run of cmake, but as soon
as the buil didrectory is existent, it is for obscure reasons expanded
into ${CMAKE_BINARY_DIR}/.... To avoid having users run into this bug,
the expanded compiler variable is matched with the build directory prefix.
In that case, an error is issued.

There is still a warning issued in that case.

Taken from #FS1535, where Carsten has posted this code.

It needs to be linked in some cases. The way of checking whether
it is needed is taken from Find{BLAS,LAPACK}.cmake . This fix was
needed as part of a larger fix for the test of parallel alugrid.

RECOMMENDED created new categories in the summary.
Technically there are no differences.

add symlinks to the build tree, which point to files in the source tree.
Foreach file given in "files", a symlink of that name is created in the
corresponding build directory. Use for ini files, grid files etc. A warning
is issued on Windows systems.

Add a symlink called src_dir to all directories in the build tree.
That symlink points to the corresponding directory in the source tree.
Call the macro from the toplevel CMakeLists.txt file of your project.
You can also call it from some other directory, creating only symlinks
in that directory and all directories below. A warning is issued on
Windows systems.

This way they appear in the summary.

Tried to include CheckSymbolExists instead of CheckFunctionExists.
The wrong include only triggered in a very rare case, where
the module had not been included from elsewhere in the project.

Also, a typo in a library variable.

The regex wrongly matched directories ending in "test",
cf. FS#1553.