We follow the advice of upstream and use only empty endif() and
else() statements in new code. The removal of the optional argument
is only in generated scripts.

Add missing files, remove ancient buildsystem stuff and stuff where it is
unclear where it comes from.

[test][typetraits][warnings] Split the test for deprecated functionality in typetraits.hh into its own testcase.  That way I can simply disable deprecation warnings there.

There was a mechanism with apparently similar goal involving the define
DISABLE_DEPRECATED_METHOD_CHECKS.  However, I could not figure out how that
was intended to work, the only occurances of DISABLE_DEPRECATED_METHOD_CHECKS
were in typetraitstest.hh.  Probably you were supposed to set that define by
hand in your CPPFLAGS, which I consider unacceptable.

The section is empty since the code was split into the dune-geometry
module.

Since fda5a9e0 AlignmentOf always uses
std::alignment_of and the fallback implementation is no longer used.

It's more CMake style.

Since de430584 HAVE_DUNE_HASH is
always defined.

Nicolas Schwenck authored 9 years ago and Christoph Grüninger committed 9 years ago

floating comparisons

Some downstream modules like pdelab and dumux already abandoned the
current bahaviour of building tests on make test. The testing infrastructure
does throw them error messages during make test though. This commi introduces
the switch DUNE_DISABLE_TEST_MAGIC which may be set by downstream modules
to disable the magic. To see how to switch a downstream module, see:

http://conan2.iwr.uni-heidelberg.de/git/pdelab/dune-pdelab/commit/dc5ef4b39f5be5690457f0bbfe008b1f45d5fd98

Point to proposal for C++17 make_array(), and point out the differences of our
implementation.

That inhibits RVO and actually makes the code slower.  And even if the
compiler decides against RVO, the standard requires that he moves from the
object, if possible.  See Scott Meyers "Effective Modern C++", second half of
Item 25.

Thanks Markus Blatt for noticing.

Marco Agnese authored 9 years ago and Jö Fahlke committed 9 years ago

Use std::array instead of Dune::array.
[make_array] use variadic template instead of different specialization

This has to be done as each module puts dune-common_MODULE_PATH into
CMAKE_MODULE_PATH to find the DUNE's cmake macros. This should be removed
when building the complete CMAKE_MODULE_PATH module path (in reverse order
of the dependency). Unfortunately, the conditional to check whether
the variable dune-common_MODULE_PATH is set was incorrect. This commit fixes
this.

I hope that this fixes FS 1686
https://dune-project.org/flyspray/index.php?do=details&task_id=1686

Please merge to the release

- add question concerning configure options
- add question concerning disabling options
- mention deletion of CMakeCache.txt

Update CXXFLAG question.
More proof reading and line wrapping.

- Get rid of \\ at end of paragraphs
- Fix various misspellings
- add some convenience macros
- add myself as co-author
- break long lines which were modified anyway

Commit 4878943f actuall did change
the default behavior, it effectifly disabled LaTex for some users.
To disable LaTeX pass -DCMAKE_DISABLE_FIND_PACKAGE_LATEX=TRUE

* feature/FS1683-improve-iteratorrange:
  [IteratorRange][Release] Make IteratorRange default-constructible and copyable

IteratorRanges are convenient for storing ranges of iterators into a
larger container, e.g. for the per-codim GeometryTypes in an
IndexSet. Unfortunately, you can't just create an array of
IteratorRanges right now because they can neither be copied, nor are
they default-constructible.

This patch fixes that problem and also adds a second typedef
const_iterator to make IteratorRange work in contexts where the
iterating code isn't using range-based for and assumes a const object.

Otherwise it collides with the config.h.cmake for in-source builds.
The generated file is called config_collected.h.cmake.
Thanks to Robert for the heads-up.

Setting a policy must be guarded as older CMake version do not
know about the policy.

CMake >= 2.8.12 can optionally use @rpath to embed dynamic linker paths
into shared libraries on OS X. This greatly improves reliability with
libraries in non-standard locations and should definitely be turned on
by default.