(cherry picked from commit 0031e54d)
Signed-off-by: Carsten Gräser <graeser@dune-project.org>

are on Ubuntu.

(cherry picked from commit f9c79378)
Signed-off-by: Carsten Gräser <graeser@dune-project.org>

The test for __cxa_demangle(), which is used by Dune::className() to
demangle type names, doesn't work on my clang 3.6. Apparently, clang
requires the user to include <typeinfo> before <cxxabi.h>. While
classname.hh already does this, the build system tests don't, causing the
feature to get disabled on clang.

Fixed by adding the include to the build system tests.

(cherry picked from commit 70f52c0d)
Signed-off-by: Steffen Müthing <muething@dune-project.org>

Ansgar Burchardt authored 9 years ago and Christoph Grüninger committed 9 years ago

(cherry picked from commit bc5578c4)

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.

[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

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.

We simply get the flags from ACX_PTHREAD.  If we are compiling natively, we
run a test program to check whether that worked.  Otherwise we print a warning
and assume that threading works.

With the removal of the fall-back code for many C++11 features
like shared_ptr or hash, we no longer need Boost in
dune-common.
If your model has relies on a boost check, add the call to
the buildsystem of your module. The Dune-islt commit
…3ee92f05012 is an example what must be done.

"Makefile.in", "*.o", etc. need only be listed in the toplevel .gitignore, the
rules are applied recursively.

Test programs etc. should be listed as "/program" in their directory's
.gitignore, so they are not accidentially ignored in a lower level directory.

Macro to use C++11 feature noexcept specifier.
Add test for CMake and autotools.

There is more macro magic to be removed.

With GCC 4.4 or newer HAVE_INTEGRL_CONSTANT, HAVE_STD_HASH, and
HAVE_TYPE_TRAITS is always 1, no further testing necessary.
The test defines will be removed after the next Dune release.

This was used for backwards compatibility only.

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

Its call was removed from dune_mpi.m4 back in 2012.

Deprecate header and macro dune_static_assert.
Use static_assert instead.

They cased compiler warnings.

This patch adds an AutoTools test that tests whether the compiler
supports the 'final' keyword.  It defines the DUNE_FINAL preprocessor
macro, which expands to 'final' if the keyword is supported, and
is empty otherwise.