Previously this was only set if run_default_configure was executed
before. Ergo dunecontrol make did try to use cmake even if USE_CMAKE=no
was set. This fixes flyspray 1560.
https://dune-project.org/flyspray/index.php?do=details&task_id=1560

It sets LOCAL_USE_CMAKE for the current module depending on USE_CMAKE
and whether there actually is CMake support for this module.
This will make it more easy to use the same check in all run_*
directives.

With a compiler name given to CMAKE_CXX_COMPILER (instead of a path),
the name is correctly expanded on the first run of cmake, but as soon
as the buil didrectory is existent, it is for obscure reasons expanded
into ${CMAKE_BINARY_DIR}/.... To avoid having users run into this bug,
the expanded compiler variable is matched with the build directory prefix.
In that case, an error is issued.

It needs to be linked in some cases. The way of checking whether
it is needed is taken from Find{BLAS,LAPACK}.cmake . This fix was
needed as part of a larger fix for the test of parallel alugrid.

The UMFPack test has been added after CMake, so I simply
didnt know that it should be placed here, too.

The compatibility layer disabled MPI whenever it did not find
the --enable-parallel flag. This is overeager and harmful if users
are gradually switching to replacing the configure flags with real
cmake flags.

Consider an opts file, with the following content:
CMAKE_FLAGS="-DUSE_MPI=ON"

The compatibility layer would now parse the non-existent CONFIGURE_FLAGS
variable for an --enable-parallel option and disable MPI because it was
not found. The -DCMAKE_DISABLE_FIND_PACKAGE_MPI=TRUE supersedes the USE_MPI=ON
and we get a sequential build.

The fix applied in this patch removes the else clause and only adds
cmake flags when the --enable-parallel flag was found. To still explicitly
allow to force sequential builds, the --disable-parallel flag is parsed
in the same manner.

RECOMMENDED created new categories in the summary.
Technically there are no differences.

This way they appear in the summary.

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.

If LAPACK is not available, it return 77 indicating skipped test

Like we do for Autotools.
This is only supported for CMake 3.0 or newer. Oder versions ignore
the property and report the test as failed.

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.