Update CMake variables to new names (#289)

Author: davidscn

pages/docs/dev-docs/dev-tooling.md

@@ -106,9 +106,9 @@ cmake \
    -DCMAKE_CXX_CPPCHECK="cppcheck;--enable=all" \
    -DCMAKE_CXX_CPPLINT="cpplint.py" \
    -DCMAKE_CXX_INCLUDE_WHAT_YOU_USE="path/to/iwyu;-p;." \
-   -DPRECICE_PythonActions=ON \
-   -DPRECICE_MPICommunication=ON \
-   -DPRECICE_PETScMapping=ON \
+   -DPRECICE_FEATURE_PYTHON_ACTIONS=ON \
+   -DPRECICE_FEATURE_MPI_COMMUNICATION=ON \
+   -DPRECICE_FEATURE_PETSC_MAPPING=ON \
    $PRECICE_ROOT
 make -j $(nproc)
 ```

pages/docs/installation/installation-source-advanced.md

@@ -32,7 +32,7 @@ To build preCICE as a static library, you can set `-DBUILD_SHARED_LIBS=OFF`.
 
 The library provides native bindings for C and Fortran.
 They are called native as they are compiled into the resulting library.
-If you know what you are doing, you can disable them by specifying `-DPRECICE_ENABLE_C=OFF`, or `-DPRECICE_ENABLE_FORTRAN=OFF`.
+If you know what you are doing, you can disable them by specifying `-DPRECICE_BINDINGS_C=OFF`, or `-DPRECICE_BINDINGS_FORTRAN=OFF`.
 
 **We highly discourage you to do this, as the resulting binaries will not be compatible with C or Fortran adapters!**
 
@@ -75,5 +75,5 @@ For using a non-default MPI implementation one can steer the [CMake MPI discover
 Example - building with MPICH:
 
 ```bash
-cmake -DPRECICE_MPICommunication=ON -DMPI_CXX_COMPILER=/usr/bin/mpicxx.mpich ..
+cmake -DPRECICE_FEATURE_MPI_COMMUNICATION=ON -DMPI_CXX_COMPILER=/usr/bin/mpicxx.mpich ..
 ```

pages/docs/installation/installation-source-configuration.md

@@ -39,27 +39,27 @@ Assemble your CMake command and run it to configure preCICE.
 This example builds the release version of preCICE with the PETSc mapping and the user-defined python actions off, which will be installed in the prefix `~/software/precice`.
 
 ```bash
-cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=~/software/precice -DPRECICE_PETScMapping=OFF -DPRECICE_PythonActions=OFF ..
+cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=~/software/precice -DPRECICE_FEATURE_PETSC_MAPPING=OFF -DPRECICE_FEATURE_PYTHON_ACTIONS=OFF ..
 ```
 
 Option | Type | Default | Description
 --- | --- | --- | ---
 [`BUILD_SHARED_LIBS`](https://cmake.org/cmake/help/v3.10/variable/BUILD_SHARED_LIBS.html?highlight=build_shared_libs) | Boolean | ON | Build as a shared library.
 [`CMAKE_BUILD_TYPE`](https://cmake.org/cmake/help/v3.10/variable/CMAKE_BUILD_TYPE.html) | String | `Debug` | Choose Debug, Release, or RelWithDebInfo.
 [`CMAKE_INSTALL_PREFIX`](https://cmake.org/cmake/help/v3.10/variable/CMAKE_INSTALL_PREFIX.html) | Path | `/usr/local` | The prefix used in the installation step.
-`PRECICE_MPICommunication` | Boolean | ON | Build with MPI.
+`PRECICE_FEATURE_MPI_COMMUNICATION` | Boolean | ON | Build with MPI.
 [`MPI_CXX_COMPILER`](https://cmake.org/cmake/help/v3.10/module/FindMPI.html#variables-for-locating-mpi) | Path | | MPI compiler wrapper to use for detection.
-`PRECICE_PETScMapping` | Boolean | ON | Build with PETSc (for MPI-parallel RBF mapping), requires `PRECICE_MPICommunication=ON`.
-`PRECICE_PythonActions` | Boolean | ON | Build support for python actions.
+`PRECICE_FEATURE_PETSC_MAPPING` | Boolean | ON | Build with PETSc (for MPI-parallel RBF mapping), requires `PRECICE_FEATURE_MPI_COMMUNICATION=ON`.
+`PRECICE_FEATURE_PYTHON_ACTIONS` | Boolean | ON | Build support for python actions.
 `PYTHON_EXECUTABLE` | Path | | Path to the python interpreter to use.
 [`BUILD_TESTING`](https://cmake.org/cmake/help/v3.10/module/CTest.html#module:CTest) | Boolean | ON | Build and register the tests.
 `PRECICE_RELEASE_WITH_ASSERTIONS` | Boolean | OFF | Enables assertions in release builds.
 `PRECICE_RELEASE_WITH_DEBUG_LOG` | Boolean | OFF | Enables debug logging in release builds.
 `PRECICE_RELEASE_WITH_TRACE_LOG` | Boolean | OFF | Enables trace logging in release builds.
 `PRECICE_InstallTest` | Boolean | OFF | Install `testprecice` and test configuration files.
-`PRECICE_Packages` | Boolean | ON | Enable package configuration.
-`PRECICE_ENABLE_C` | Boolean | ON | Enable the native C bindings.
-`PRECICE_ENABLE_FORTRAN` | Boolean | ON | Enable the native Fortran bindings.
+`PRECICE_CONFIGURE_PACKAGE_GENERATION` | Boolean | ON | Enable package configuration.
+`PRECICE_BINDINGS_C` | Boolean | ON | Enable the native C bindings.
+`PRECICE_BINDINGS_FORTRAN` | Boolean | ON | Enable the native Fortran bindings.
 `PRECICE_ALWAYS_VALIDATE_LIBS` | Boolean | OFF | Force CMake to always validate required libraries.
 `PRECICE_TEST_TIMEOUT_LONG` | Integer | 180 | Timeout for big test suites
 `PRECICE_TEST_TIMEOUT_SHORT` | Integer | 20 | Timeout for small test suites

pages/docs/installation/installation-source-dependencies.md

@@ -205,7 +205,7 @@ Please double check if there are no system packages before attempting to build t
 | Required     | 3.6  | 3.12  |
 | Incompatible | 3.12 |  <-   |
 
-[PETSc](https://www.mcs.anl.gov/petsc/) is used for RBF mappings and is highly recommended for large cases. For small/medium-size cases, preCICE can still do an RBF mapping in parallel without PETSc. If you don't need this feature, you may specify `-DPRECICE_PETScMapping=off` when building preCICE.
+[PETSc](https://www.mcs.anl.gov/petsc/) is used for RBF mappings and is highly recommended for large cases. For small/medium-size cases, preCICE can still do an RBF mapping in parallel without PETSc. If you don't need this feature, you may specify `-DPRECICE_FEATURE_PETSC_MAPPING=off` when building preCICE.
 
 We require at least version 3.12. For preCICE versions earlier than v2.1.0, PETSc version between 3.6 and 3.12 might still work, but needs to be built with 64bit index sizes. In particular on [Ubuntu 18.04, we require at least 3.12](https://github.com/precice/precice/issues/115).
 
@@ -236,7 +236,7 @@ Finally, in some cases you may need to have PETSc in your `CPATH`, `LIBRARY_PATH
 | Required NumPy         |      |  1.17 |
 | Incompatible NumPy     | 1.17 |  None |
 
-You only need [Python](https://www.python.org/) if you want to use the Python action interface (only used for rare applications). If you don't need this feature, you may specify `-DPRECICE_PythonActions=off`.
+You only need [Python](https://www.python.org/) if you want to use the Python action interface (only used for rare applications). If you don't need this feature, you may specify `-DPRECICE_FEATURE_PYTHON_ACTIONS=off`.
 In particular, you don't need to build with Python if you only want to use the [preCICE Python bindings](installation-bindings-python.html).
 
 You probably already have Python installed. However, in order to use the Python interface, you also need to install NumPy and the header files for Python and NumPy. On Debian/Ubuntu, install the packages `python3-numpy` and `python3-dev`.
@@ -245,7 +245,7 @@ You probably already have Python installed. However, in order to use the Python
 
 preCICE requires an implementation of the MPI-3 specification, which is provided by all major vendors including OpenMPI, MPICH, and Intel MPI.
 
-You can build preCICE without [MPI](https://en.wikipedia.org/wiki/Message_Passing_Interface#Official_implementations) in case of compatibility issues with a certain solver (e.g. a closed source solver with a binary-distributed MPI version, or when running on Windows). To do so, use `-DPRECICE_MPICommunication=OFF` when building with CMake. In such a case, you can still use TCP/IP sockets instead. This might, however, result in lower performance and is, therefore, not recommended if not necessary.
+You can build preCICE without [MPI](https://en.wikipedia.org/wiki/Message_Passing_Interface#Official_implementations) in case of compatibility issues with a certain solver (e.g. a closed source solver with a binary-distributed MPI version, or when running on Windows). To do so, use `-DPRECICE_FEATURE_MPI_COMMUNICATION=OFF` when building with CMake. In such a case, you can still use TCP/IP sockets instead. This might, however, result in lower performance and is, therefore, not recommended if not necessary.
 
 Please note that many MPI implementations implement the client-server functionality in various ways.
 They often require special setup such as environment variables, servers or infrastructure setup.
@@ -291,7 +291,7 @@ sudo apt update && \
 sudo apt install build-essential cmake libeigen3-dev libxml2-dev libboost-all-dev python3-dev python3-numpy
 ```
 
-If you don't plan to use RBF mappings in large parallel cases you can continue without installing PETSc and build with `-DPRECICE_PETScMapping=OFF`.
+If you don't plan to use RBF mappings in large parallel cases you can continue without installing PETSc and build with `-DPRECICE_FEATURE_PETSC_MAPPING=OFF`.
 If you need PETSc, follow the steps in the [PETSc](#petsc) section and you are done.
 
 ### Debian 11 Bullseye
@@ -314,7 +314,7 @@ apt update && \
 apt install build-essential cmake libeigen3-dev libxml2-dev libboost-all-dev python3-dev python3-numpy
 ```
 
-If you don't plan to use RBF mappings in large parallel cases you can continue without installing PETSc and build with `-DPRECICE_PETScMapping=OFF`.
+If you don't plan to use RBF mappings in large parallel cases you can continue without installing PETSc and build with `-DPRECICE_FEATURE_PETSC_MAPPING=OFF`.
 If you need PETSc, follow the steps in the [PETSc](#petsc) section and you are done.
 
 ### Fedora 36
@@ -340,7 +340,7 @@ module load mpi/openmpi-x86_64
 In case you use the docker image of fedora, you need to install the support for environment modules first: `sudo dnf install environment-modules`
 {% endnote %}
 
-If you don't plan to use RBF mappings in large parallel cases you can continue without installing PETSc and build with `-DPRECICE_PETScMapping=OFF`. You may need this with older preCICE and Fedora versions (e.g. preCICE v2.1 on Fedora 32 or earlier, see a [related issue](https://github.com/precice/precice/issues/864).
+If you don't plan to use RBF mappings in large parallel cases you can continue without installing PETSc and build with `-DPRECICE_FEATURE_PETSC_MAPPING=OFF`. You may need this with older preCICE and Fedora versions (e.g. preCICE v2.1 on Fedora 32 or earlier, see a [related issue](https://github.com/precice/precice/issues/864).
 
 ### Rocky Linux 9
 
@@ -366,7 +366,7 @@ Rocky Linux very closely follows the conventions previously set by CentOS. We fi
    module load mpi/openmpi-x86_64
    ```
 
-4. Unfortunately, [PETSc does not seem to be available in this distribution.](https://pkgs.org/search/?q=petsc), so we need to switch that off later when building preCICE. If you don't plan to use RBF mappings in large parallel cases, you can continue without installing PETSc and build preCICE with `-DPRECICE_PETScMapping=OFF`. If you need PETSc, follow the steps in the [PETSc](#petsc) section and you are done.
+4. Unfortunately, [PETSc does not seem to be available in this distribution.](https://pkgs.org/search/?q=petsc), so we need to switch that off later when building preCICE. If you don't plan to use RBF mappings in large parallel cases, you can continue without installing PETSc and build preCICE with `-DPRECICE_FEATURE_PETSC_MAPPING=OFF`. If you need PETSc, follow the steps in the [PETSc](#petsc) section and you are done.
 
 ### CentOS 8
 
@@ -404,7 +404,7 @@ This system requires to install some tools in a fixed order.
    module load mpi/openmpi-x86_64
    ```
 
-4. Unfortunately, the PETSc package (`petsc-openmpi-devel`) in this distribution is too old. If you don't plan to use RBF mappings in large parallel cases you can continue without installing PETSc, and build preCICE with `-DPRECICE_PETScMapping=OFF`. If you need PETSc, follow the steps in the [PETSc](#petsc) section and you are done.
+4. Unfortunately, the PETSc package (`petsc-openmpi-devel`) in this distribution is too old. If you don't plan to use RBF mappings in large parallel cases you can continue without installing PETSc, and build preCICE with `-DPRECICE_FEATURE_PETSC_MAPPING=OFF`. If you need PETSc, follow the steps in the [PETSc](#petsc) section and you are done.
 
 ### CentOS 7
 
@@ -474,7 +474,7 @@ cmake -DEIGEN3_INCLUDE_DIR=/usr/include/eigen3 <options as usual>
 If you don't already have a fitting combination of MPI and PETSc (not shown here), disable the respective features when configuring preCICE:
 
 ```bash
-cmake -DPRECICE_MPICommunication=OFF -DPRECICE_PETScMapping=OFF <options as usual>
+cmake -DPRECICE_FEATURE_MPI_COMMUNICATION=OFF -DPRECICE_FEATURE_PETSC_MAPPING=OFF <options as usual>
 ```
 
 See also a related [discussion on the preCICE forum](https://precice.discourse.group/t/compiling-precice-on-opensuse-leap/1148/4) for more details.

pages/docs/installation/installation-source-troubleshooting.md

@@ -20,7 +20,7 @@ This is also the method of choice when using a [virtual environment](https://doc
 Example:
 
 ```bash
-cmake -DPRECICE_PythonActions=ON -DPYTHON_EXECUTABLE=/usr/bin/python3.8 .
+cmake -DPRECICE_FEATURE_PYTHON_ACTIONS=ON -DPYTHON_EXECUTABLE=/usr/bin/python3.8 .
 ```
 
 ### PETSc could not be found

pages/docs/installation/installation-special-systems.md

@@ -43,7 +43,7 @@ libxml2 is part of the `-devel` packages, which are loaded by default on the log
 (3) Build preCICE. For PETSc, the library path and include path need to be defined explicitly:
 
 ```bash
-cmake -DBUILD_SHARED_LIBS=ON -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX="my/install/prefix" -DPRECICE_PETScMapping=ON -DPETSc_INCLUDE_DIRS="$PETSC_DIR/include" -DPETSc_LIBRARIES="$PETSC_DIR/lib/libpetsc.so" -DPRECICE_PythonActions=OFF /path/to/precice/source
+cmake -DBUILD_SHARED_LIBS=ON -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX="my/install/prefix" -DPRECICE_FEATURE_PETSC_MAPPING=ON -DPETSc_INCLUDE_DIRS="$PETSC_DIR/include" -DPETSc_LIBRARIES="$PETSC_DIR/lib/libpetsc.so" -DPRECICE_FEATURE_PYTHON_ACTIONS=OFF /path/to/precice/source
 
 make install -j 16
 ```
@@ -881,6 +881,6 @@ module list
 
 rm -rf build
 mkdir -p build && cd build
-cmake -DBUILD_SHARED_LIBS=ON -DMPI_CXX_COMPILER=mpigcc -DCMAKE_BUILD_TYPE=Debug -DPRECICE_PythonActions=OFF ..
+cmake -DBUILD_SHARED_LIBS=ON -DMPI_CXX_COMPILER=mpigcc -DCMAKE_BUILD_TYPE=Debug -DPRECICE_FEATURE_PYTHON_ACTIONS=OFF ..
 make -j
 ```