By default, the new falgs are prepended to the list of flags. This way,
the most general libraries (whihc are usually checked first) appear at
the end of the list. Adding the APPEND option to the call allows to
explicitly append them at the end.

This happens in the case of a typo, which is nasty to find.

If set, at the end of each configure run the set of registered flags will
be printed.

Until now, the global properties that hold the collection of flags
for all packages have been updated manually in each find module. It
might be convenient for developers to put this into a macro that
uses CMakeParseArguments.

The module DuneMacros.cmake is very crowded. Macros that are important
to end users and whose documentation should be clearly visible is
better placed in a separate file IMO. The new file is included from
DuneMacros.

This propbably the best spot to safe the user from himself!

Tried to include CheckSymbolExists instead of CheckFunctionExists.
The wrong include only triggered in a very rare case, where
the module had not been included from elsewhere in the project.

Also, a typo in a library variable.

The regex wrongly matched directories ending in "test",
cf. FS#1553.

Previously we did not catch patterns at the start of the line.
Seems like sed cannot handle [ ^] as the meaning of
^ is the not operator here and not the line beginning.

Unfortunately environment variables with these names are not honored by CMake's
FindMPI. Therefore this commit translates them to MPI_{C,CXX}_COMPILER and
adds them to CMAKE_FLAGS before calling cmake.

When deciding which variable to put before cmake as environment variables
our sed pattern did not check for the beginning of a word or line. Therefore
MPICC=bla would be converted to CC=bla.
With this commit we make sure that there is eihter a beginning of a line or
a whitespace before the variable.

This files is the latest version from Eigen3. They already fixed
our issue FS#1540.
The Eigen project is licensed under MPL 2 and this file stays
MPL2 licensed.

This enables ninja-build and other build systems to be called
correctly.
Targets can be passed by adding "--target <targetname>

No comment/response from the other interested parties, so I assume this is OK.

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.