As we have bumped our compiler requirements to GCC 4.4+, we can now
require the compiler to support C++11.

This patch updates both the autotools and the CMake tests to produce an
error if the compiler doesn't support either -std=c++11 or -std=c++0x.

It also renames the tests from ..0X to ..11 and renames the configure
options from --disable-gxx0xcheck to --disable-cxx11check and removes a
couple of redundant calls to the autotools macro.

Arne Morten Kvarving authored 10 years ago and Christoph Grüninger committed 10 years ago

dune_deprecated_cppflags.m4 was removed in 2a4965d9
CheckSharedPtr.cmake was removed in 7205583c

Deprecate header and macro dune_static_assert.
Use static_assert instead.

They cased compiler warnings.

With this patch the default is again building static libraries unless
one specifies -DBUILD_SHARED=True to cmake. This is not a fix but a
workaround for flyspray #1429
https://dune-project.org/flyspray/index.php?do=details&task_id=1429

Previously running make test if there was a symlink int the path to the module.
This caused make test to fail. This patch fixes this by extracting the
path without symlinks.

Dependencies in the dune.module without a required version failed.

Now <= and >= are correctly treated.

Du to typo the length of the modules and version list of the suggestion
differed. This patch fixes this.

If we do not do that the length of the list of modules and corresponding versions
will differ as empty values will be neglected when appending to a list

In this patch we rename dune_process_depedency_tree to
dune_process_depedency_macros because it actually just
include the macros of all modules that we depend on.
I addition we fix a bug that resulted in not executing the module's
own macro if there was only one dependency and now always process
it here.

Somehow we ended up putting CMAKE_PROJECT_SOURCE_DIR/lib into the
linker path. There should not be any library there and it should
not be needed for linking anyway. Additionally it causes warnings
in dune-grid-howto. Therefore this patch simply removes it.

The name of the file changed in one of the recent patches. This
change is now also reflected in the install directive. Fixes #1426

Previously, we used >=0.0. if there was no version information in the
dependes and suggests clause of a dune.module file. This breaks with
the new more strict version checking. Therefore with this revision no
version gets set if it does not appear in dune.module

Before we tried to search for dune-common twice (once without a version
and then with the required version). Unfortunately this breaks because
we are adding the same library target twice. With this patch we only
search for a module once.

Before this patch we always relied on dunecontrol/pkg-config to check
for the correct version. With this patch we include this functionality
also when building packges with dunecontrol for this use part of the version
checking of cmake (or pkg-config if there are packages without CMake support).
Basically we let CMake check wether the major and minor version matches and
afterwards use the information from the dune.module file. This should make
it possible to have several versions of DUNE installed and still always use
the correct version. During fixing these issues we noticed that our version
files were not recognized because the carried the wrong name. Now we use the
correct name <dune-module>-config-version.cmake.

This fixes FS#1422.

Replace tabs by spaces.

One of the latest patches prevent the macros of the current module
form being executed. This patch fixes this by including the module
in the dependency tree.

When making the entries of ALL_DEPENDENCIES unique, we skipped modules that
did not ship a Dune<ModuleName>Macros.cmake macro. This caused their libraries
to be missing in DUNE_LIBS. This patch fixes this situation.

Previously we already processed dune.module but in a much later stage during
configure. Dependencies are contained in dune.module. Therefore there is no
need to replicate them in the CMake package configuration files. With this
patch we now always process dune.module directly after finding the DUNE module.
In addition we set ${DUNE_MOD_NAME}_(DEPENDS|SUGGESTS} in the CMake environment.
As with this change DUNE_MOD_NAME will usually be set to to dune-common, we
also changed to using ProjectName and ProjectVersion (the canonical CMake names)
to refer to the current module and version.

Previously we checked whether the extracted Version evaluated to
True. Unfortunately, there lazy people like me that like use a version
of 0 for testing, which evaluates to False and breaks configure.
With this patch we allow 0 to and just test wether the version consists
of characters.

With new modules there were cases where cmake/modules was not in the
modules path which made configuration fail. This patch fixes this case.