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.

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

The install path for header files can be configured in CMake with the
variable ${CMAKE_INSTALL_INCLUDEDIR}.

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...

Ich a module is not updated to cmake yet, we can have the situation, that the core modules
are built using cmake, but used by autotools. When trying to detect a dune library, we either
explicitly stated the /blablabla/libdunefoo.la file if the the dependency was built using autools,
or used the '-ldunefoo -L/blablabla/' options. This failed with very subtle errors if dune was
also installed globally, e.g. a 2.3 from your favorite distribution. We fix this now in the same
way as we fixed it for autotools. If the module is local, we explicitly state the lib...
either as .la or as .a.

if the user has for some reason old la files from the autotools era,
these can lead to very subtle and hard to understand errors. We now
check for old la files and bail out in case some are found.

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

is_indexable can be used to test whether a type can be indexed (via
operator[]).

Previously, the command vcsetup, which is executed on command 'all',  was not
listed on the help screen.

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.

This reverts commit 9f9bc5c0.

see FS#1576

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

Otherwise UNAME_HH was seen by the shell as the name of the variable,
but actually, the variable is called UNAME and _HH should be appended
after expansion of the variable.

Follow up to the previous patch: if the source file contains hyphens, then
the compiled executable should not have them replaced by underscores.

Each module constructed by duneproject contains a little Hello-world example
program.  The name of the program used to be the name of the module with .cc
appended AND all hyphens replaced by underscores.  Hence a module dune-foo
would containt the program dune_foo.cc.  This patch removes that displacement.
Rationale:
- I see no reason for the replacement in the first place
- File names with hyphens appear to be much more common in Dune world than
  file names with underscores.

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

add missing @

In the past MPI / parallel features were disabled until the
proper flag was added. This patch changes the behavior to
enable MPI iff it is found.

* Autotools: --disable-parallel and --enable-parallel work as
  before but the documentation is a bit clumsy to minimize changes.
* CMake: USE_MPI gets removed, too. It was not used by the Dune
  core modules. The backwards compatible --disable-parallel remains.

@Markus: too much CMake?! ;-)

There is not need to send message that contain no data. It might even
produce problems on  some implementation. Therfore this patch always
checks the size and simply sets the request to inactive (aka
MPI_REQUEST_NULL) if no data would be send or received.

The patch is to be cherry-picked to master if Christian approves.

We fix the option handling when calling "cmake --build", by prepending '--' to the command
line parameters, in order to separate cmake and build parameters, iff the user didn't alrready do
it himself so. Note that this means we assume that the users generally want to pass
parameters to the build command and not to cmake itself.