GCC 4.4, I'm looking at you

The file DuneMacros.cmake is very crowded. Macros that belong
together should be placed in a separate module in order to increase
the visibility of its documentation IMO.

I accidentally commited them.

This is e.g. needed for dune-alugrid and might be a first step for
getting rid off the ParMETIS dependency.

Since CMake 3.1 the if() command no longer automatically dereferences
variables named in quoted or bracket arguments.
This fixes FS#1567.

It caused that pthread.h was not found as clang does not like
to get -std=c++11 passed.

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.

There is still a warning issued in that case.

Taken from #FS1535, where Carsten has posted this code.

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.

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

add symlinks to the build tree, which point to files in the source tree.
Foreach file given in "files", a symlink of that name is created in the
corresponding build directory. Use for ini files, grid files etc. A warning
is issued on Windows systems.

Add a symlink called src_dir to all directories in the build tree.
That symlink points to the corresponding directory in the source tree.
Call the macro from the toplevel CMakeLists.txt file of your project.
You can also call it from some other directory, creating only symlinks
in that directory and all directories below. A warning is issued on
Windows systems.

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.

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.

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.

We simply get the flags from find_package(Thread).  If we are compiling
natively, we run a test program to check whether that worked.  Otherwise we
print a warning and assume that threading works.

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.

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.

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.

Dominic Kempf authored 10 years ago and Dominic Kempf committed 10 years ago

Autotools users kept complaining, that it is conceptionally
disappointing that targets cannot be build with flags set upon
entering make (e.g. make CXXFLAGS+="-myflag" mytarget). This
patch introduces a small hack, that allows for such feature
in cmake. It is, however, (at least) questionable whether we
want to include it. Still, for your information and convenience:

To use the feature you must:
- be using a CMake generator that is based on Makefiles (defaults to true)
- set the define ALLOW_EXTRA_CXXFLAGS to true, e.g. by including
  CMAKE_FLAGS="-DALLOW_EXTRA_CXXFLAGS=1" in your optsfile.
- reconfigure your project

cmake will then wrap a small shell script around your compiler
and allow you to append the content of an environment variable
to yout compiler flags. Run for above example:
EXTRA_CXXFLAGS="-myflag" make mytarget

The additional flags will be visually confirmed if and only if
you set the verbosity (as always):
EXTRA_CXXFLAGS="-myflag" make VERBOSE=1 mytarget

Macro to use C++11 feature noexcept specifier.
Add test for CMake and autotools.

With GCC 4.4 or newer HAVE_INTEGRL_CONSTANT, HAVE_STD_HASH, and
HAVE_TYPE_TRAITS is always 1, no further testing necessary.
The test defines will be removed after the next Dune release.

It is INCLUDE_DIRECTORIES and not COMPILE_DIRECTORIES.

Previously, parmetis flags were not added as we used PARMETIS_COMPILE_FLAGS
which does not exist. This patch now sets the properties COMPILE_DEFINITIONS
and INCLUDE_DIRECTORIES for the targets and uses the correct values.

Needed to build the documentation only for make doc.
Avoid name clashes by adding MANGLE_TARGET_NAMES.
With CMake 3.0.0 no more warnings are emitted by
building the documentation.

Whitespace changes where necessary to please the git commit hook.

As we have bumped our compiler requirements to GCC 4.4+, we can now
require the compiler to support C++11.

This patch updates both the autotools and the CMake tests to produce an
error if the compiler doesn't support either -std=c++11 or -std=c++0x.

It also renames the tests from ..0X to ..11 and renames the configure
options from --disable-gxx0xcheck to --disable-cxx11check and removes a
couple of redundant calls to the autotools macro.

Arne Morten Kvarving authored 10 years ago and Christoph Grüninger committed 10 years ago

dune_deprecated_cppflags.m4 was removed in 2a4965d9
CheckSharedPtr.cmake was removed in 7205583c