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

Dominic Kempf authored 10 years ago and Dominic Kempf committed 10 years ago

Autotools users kept complaining, that it is conceptionally
disappointing that targets cannot be build with flags set upon
entering make (e.g. make CXXFLAGS+="-myflag" mytarget). This
patch introduces a small hack, that allows for such feature
in cmake. It is, however, (at least) questionable whether we
want to include it. Still, for your information and convenience:

To use the feature you must:
- be using a CMake generator that is based on Makefiles (defaults to true)
- set the define ALLOW_EXTRA_CXXFLAGS to true, e.g. by including
  CMAKE_FLAGS="-DALLOW_EXTRA_CXXFLAGS=1" in your optsfile.
- reconfigure your project

cmake will then wrap a small shell script around your compiler
and allow you to append the content of an environment variable
to yout compiler flags. Run for above example:
EXTRA_CXXFLAGS="-myflag" make mytarget

The additional flags will be visually confirmed if and only if
you set the verbosity (as always):
EXTRA_CXXFLAGS="-myflag" make VERBOSE=1 mytarget

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

There is no need to limit it to 2 min. For larger modules
like DuMuX this is not enough. Increased timeout to 5 min.

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.

It is INCLUDE_DIRECTORIES and not COMPILE_DIRECTORIES.

Previously, parmetis flags were not added as we used PARMETIS_COMPILE_FLAGS
which does not exist. This patch now sets the properties COMPILE_DEFINITIONS
and INCLUDE_DIRECTORIES for the targets and uses the correct values.

Needed to build the documentation only for make doc.
Avoid name clashes by adding MANGLE_TARGET_NAMES.
With CMake 3.0.0 no more warnings are emitted by
building the documentation.

Whitespace changes where necessary to please the git commit hook.

Previously only dune-foo/bar/*/test worked.
Now dune-foo/test works, too.

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.