Dominic Kempf authored 10 years ago and Christoph Grüninger committed 10 years ago

We dont provide a custom find module, so we need to update
the property after executing the system wide find module.

Dominic Kempf authored 10 years ago and Christoph Grüninger committed 10 years ago

The libraries are taken from DUNE_LIBS and from the
global property ALL_PKG_LIBS. This change is necessary
to drop the add_dune_*_flags macros in the future.

Otherwise the headers in dune-grid-howto and and in
dune-multidomain/tests cannot be checked.

With CMake 3.1 variable indication with the @ symbol is
no longer valid, use ${} instead, cf. CMP0053. The @ is
only allowed for configuration files which are transformed.

The generated files are the same with CMake 3.1~rc2 and
CMake 2.8.6.

Moved from dune-istl's config.h.cmake. Otherwise it cannot
be shared with other modules using ParMETIS.

This specialization was missing and made it impossible to parse bitsets.
The implementation uses the specialization for bool. It was not possible
to reuse the parseRange method, because a bitset doesnt have begin() and end().

While the following is legal c++11

  array<T,n> foo = { t1, t2, ...}

older compilers (namely gcc-4.4) issue a warning on missing braces.

This reverts commit d26e5ed3.
We have to wait until our minimal required compiler is GCC 4.7
or newer.
Thanks to Carsten for the heads-up.

The signature changed in C++11 which we require now.
To get more details see the mailinglost in October 2012.

It should be std::endl.
Courtesy of GCC 5-svn, it refuses to compile these.

GCC warns about it.

While gcc supports them (as extension) runtime sized arrays
are not standard c++. They are not even contained in c++14
but postponed to a later TS.

Use output of find_package(MPI) consistent.

In dune-grid we want to export the path to the grid example files. To do this
without a handwritten package configuration file, We add a custom section
to it that can be filled by the modules using the variable DUNE_CUSTOM_PKG_CONFIG_SECTION
before finalizing the cmake build system. For dune-grid we export the variable
DUNE_MODULE_SRC_DOCDIR that points to the installed documentation and the path to
the source files of the documenation in the installed and not-installed module, respectively.

Suggested modules are quite often not available and for a large
number of suggested modules the output is very cluttered.
The error message is anyway printed manually.

Pass --no-cmake to dunecontrol to force the use of autotools.
If no build directory is given, make files, libararies and
executables are in <module-dir>/build-cmake/ .
Further information in FS#1000 and FS#1500.

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.

The warning was spilled out for every module for every command,
even for update.
The build directory is announced by CMake's configure anyway.
Now it is printed for make, too.

CMAKE can now be set in the shell or the opts file, if both are set
the shell has higher priority.
This feature was dropped in …aef001c21e3a9 to fix FS#1518.

Add "@relatesalso null_deleter", this includes the documentation for the
function with null_deleter but also leaves a standalone version.  Document
what is so special about the shared_ptr the function returns.  Mention the
#include needed to get the function.

"C", no matter what locale is currently set.

[parametertree][locale][fs1528] Check ParameterTree::get() with a locale using "," as the decimal seperator.

ParameterTrees are usually read from configuration files.  The format of the
configuration file should not depend on the locale.

For the commandline parser it would likewise be surprising if "progname -param
0.5" stopped working in a german locale.

Not long ago these kinds of errors would not even generate a diagnosis due to
FS#1527.  However, the locale of the program is "C" by default, so probably
not many poeple are actually affected by this problem.  It can happen however
that other libraries linked into the same program set the locale from the
environment.

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

ParameterTree::get("key", def).

These overloads were using atoi() resp. atof(), effectively ignoring junk at
the end of values.  This led to the situation where a floating point value
"0.5" could be parsed as an int "0" without any diagnostic.

assert() works only in debug builds (without -DNDEBUG).  Instead, implement
our own check_assert().

I took the formula from

 http://en.wikipedia.org/wiki/Eigenvalue_algorithm  (retrieved lated August 2014).

Wikipedia claims to have taken it from

 Smith, Oliver K. (April 1961), Eigenvalues of a symmetric 3 × 3 matrix,
 Communications of the ACM 4 (4): 168, doi:10.1145/355578.366316

I did not check stability of efficiency of this, but no problems related to
either are mentioned in the literature.  The main reason I need the closed-form
expression is to be able to pipe it into an algorithmic differentiation system.

Rip out the complete test for eigenValuesNonSym and replace it by the Rosser matrix test from fieldmatrixtest.cc

The old test was complete nonsense: an implementation of some sort of strange
undocumented shape function set that happened to need eigenvalues for something.
Lots of undocumented code, and no checks at all whether the values obtained
by eigenValuesNonSym actually make sense.

Only, for the particular choice of parameters used, eigenValuesNonSym was never
called.  Yes, you read this correctly: these hundreds of lines of code didn't
actually test anything.

The new test is copied form fieldmatrixtest.cc and adapted for DynamicMatrix
types.  It computes eigenvalues of a given 8x8 matrix and compares with the known
results.  Unfortunately, the test matrix is only symmetric.  Tests with more
general matrices are left for another day.

Rather than assuming the caller has set it to the correct size already.
Setting the size in the method eigenValuesNonSym itself makes code
more robust.  Plus, the time needed for that should be negligible
compared to the actual eigenvalue computations.

The AmiraMesh format is so obscure that we should not clutter the code we
generate by references to it.  If people really want AmiraMesh support they
can still add the flags, just like they have to do for many other things.