[doc] `COMPILE_FLAGS` only takes a single value



See merge request !133

[cleanup] Remove scripts related to Autotools, old online testing



See merge request !130

Relict from the Autotools era

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

Remove the `autogen` command from `dunecontrol`.  After the removal of
autotools support, running `dunecontrol autogen` would just return an
error anyway:

```
    $ ./dunecontrol --only=dune-common autogen
    [...]
    ./dune-common/bin/dunecontrol: line 341: run_default_autogen: command not found
    [...]
```

In addition the `dune-autogen` script was already removed in
4935e077.

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

The `m4create` command was only useful for modules using autotools.

Remove scripts related to autotool



See merge request !122

[cleanup] Remove stamp-vc and related code



See merge request !125

Document how to make tests depend on optional dune modules

CMAKE_GUARD allows to do that, but the syntax was not clear.  This merge request adds a short description.

See merge request !126

This can be used with an std::integer_sequence. If a
matching entry is found the given function is executed
with _statically_ encoded matching value.
This does, e.g., allow to make a dynamic value static
if it's in a known range.

By using decltype(auto) we can also handle returned references.
Unfortunately some constexpr qualifiers have to be dropped because
they are not supproted with gcc-4.9

Feature/fix doxygen



See merge request !129

We prefer lower-case commands and empty ifs

The problem was, that UseLATEX.cmake introduced a target "html"
which interfierred with the Doxygen's OUTPUT html. The latter
is no longer a relative path but an absoulte one.
This fixes #41

Since Hybrid::ifElse() is essentially an if statement, having
support for return values looks strange. However, this is not
visible if you don't use it and allows to at least partially
emulate returning from functions inside of ifElse()-branches.

Before you could not return from those branches, because they
are functions themselves that 'eat up' the return statement.
Now you can at least return values for cases where both
branches would return.

  template<class T
  auto fooOrBar(T t) {
    return ifElse(models<HasFoo, T>(), [&](auto id) {
      return id(t).foo();
    }, [&](auto id) {
      return id(t).bar();
    });
  }

Mind the additional "return" in front of ifElse() that
which is needed to forward the returned value
Notice that it's not required that both branches have the same
return type if isElse() is in static mode.

By using "std::integral_constant<bool, *>" instead of "constexpr bool"
as return type for Dune::models(), the result can directly be used
in Dune::Hybrid::ifElse():

  T t;
  ifElse(models<HasFoo, T>(), [&](auto id) {
    id(t).foo();
  }, [&](auto id) {
    id(t).bar();
  });

Before one would have to create the integral constant manually
to turn ifElse() into static mode. The change is backward compatible
because integral_constant<bool, *> casts to bool.

Notice that this change requires a small reorganization of code.
To use models() internally we need a forward declaration which
is not possible if the type is deduced (as it is now). Hence
a new function Imp:models() with "constexpr bool" return type
is added for internal use. Its result is encoded as integral_constant
by the actual interface method.

This implements the helper template bool_constant from
C++17 in namespace Dune::Std. This is just an alias for
std::integral_constant<bool, *> that makes code more readable.

If the standard feature checks indicate its existence in
std:: or std::experimental:: it's pulled from there.

Add IsNumber trait, extending std::is_arithmetic

Since it's very difficult to make progress on !52, I'll start to break it up into smaller, less controversial changes. This is the first piece that I'd also like to use in other places. An `IsNumber` trait allows us to determine when we've hit the bottom in a recursion without a `blocklevel` and things like `FieldVector<ctype, 1>`.

`IsNumber` is currently true for: floating point types, gmp fields, and such types wrapped in `std::complex`.

See merge request !105

Cleanup/remove remaining autotools



See merge request !124

Fix install path of module macros.

According to @bernd.flemisch in staging/dune-uggrid!21:
The install directory has to be ${DUNE_INSTALL_MODULEDIR}. Otherwise, the file will not be found by dune_process_dependency_macros from DuneMacros.cmake.

See merge request !123

According to @bernd.flemisch in staging/dune-uggrid!21:
The install directory has to be ${DUNE_INSTALL_MODULEDIR}. Otherwise, the file will not be found by dune_process_dependency_macros from DuneMacros.cmake.

Feature/remove autotools

Finally, after 4.5 years of discussion, development and testing, we get rid of Autotools! 🍾 Thanks to Markus, Dominic and everybody who joined this journey.

The Dune website no longer uses WML, so can get rid of the Autotools. I propose to merge this branch and see what happens. There are more Autotools left-overs, we have to find and remove them. If everything goes well, we can remove Autotools from the other core modules as well.

See merge request !118

It converted to Autotools configure flags to CMake flags.

README.SVN explained differences to tarball sources like
running autogen; with CMake such differences no longer exists.