Dominik Thoennes authored 3 years ago and Christoph Schwarzmeier committed 3 years ago

instead of the custom walberla_add_module the `add_library` command is now used for all folders in `src` to create libraries which can then be used as cmake targets

Michael Kuron authored 4 years ago and Markus Holzer committed 4 years ago

Some optional components use Boost MultiArray and PropertyTree, so we still include the headers if available.
We also still search std::experimental for any, filesystem and optional because some otherwise C++17-compliant compilers did not support them in std until recently.

Markus Holzer authored 4 years ago and Dominik Thoennes committed 4 years ago

also clean up some old leftovers nearby

use cuda as a first level language in CMake with `enable_language(CUDA)`
enable tests where cuda and codegen are both activated
various minor fixes

This new function does the actual generation using pystencils and creates a target library that can be used as a dependency as usual. One should not list the python script itself anymore in add_executable.
Convention: Use the AppName as a prefix for the generated lib!

Example Usage:

waLBerla_generate_target_from_python( NAME AppNameGeneratedLib FILE GenerateKernel.py OUT_FILES Kernel.h Kernel.cpp)

waLBerla_add_executable ( NAME AppNameGeneratedLibTest DEPENDS GeneratedLib)

CMake: don't use CMAKE_CXX14_STANDARD_COMPILE_OPTION directly, instead go through CMAKE_CXX_STANDARD

This option is OFF by default.
If turned on cmake will notify if a target cannot be build due to a missing module.

- proper escaping of braces when passing JSON to python
- pass information if walberla was built with CUDA to pystencils
  to support apps that use GPU optionally

- information from CMake to codegen: double/float, OpenMP, ...