blob: 97b5352f27cb8f54a9144cd4249c1155316eabfc [file] [log] [blame]
Copyright (c) 2021 in-tech GmbH
This program and the accompanying materials are made
available under the terms of the Eclipse Public License 2.0
which is available at
SPDX-License-Identifier: EPL-2.0
.. _cmake:
Cmake Build Environment
|Op| uses Cmake as default cross-platform build environment.
This section describes the available variables and options.
If available, recommended options are shown in bold.
The first part of this section approaches Cmake from the *command line perspective*.
Adjustments for the corresponding IDEs will follow shortly.
The result of a proper Cmake call is a Makefile, which acts as base for the actual build using ``make`` or, under Windows, ``mingw32-make`` (c.f. :ref:`msys2`).
Hence, the second part of this section describes best practices around the make commands.
.. admonition:: See also
Cmake Documentation:
Generator (Windows only)
To generate MinGW compatible makefiles use ``-G "MinGW Makefiles"`` (c.f. :ref:`msys2`).
Cmake Variables
.. _cmake_prefix_path:
This command makes the prerequisite available to |op| as semicolon-separated list of directories, specifying installation prefixes to be searched by cmake.
Please refer to :ref:`Prerequisites` for the list of mandatory packages and libraries.
Cmake will issue an error, if one prerequisite is missing.
Generally, cmake recognizes installed libraries (e.g. googletest) on its own.
By setting an explicit ``CMAKE_PREFIX_PATH`` for a library, it is possible to override the system libraries.
Use this, when an exact library version, or a customized library shall be used instead.
.. note::
In the following example, non-standard libraries are assumed to be in the folder ``deps/thirdParty``.
**Example** (system libraries **not** set):
.. tabs::
.. tab:: Windows
.. code-block:: bash
cmake -G "MinGW Makefiles"
-D <other variables>\
.. tab:: Linux
.. code-block:: bash
-D <other variables> \
.. warning:: The semicolon ``;`` needs to be escaped (``\;``) unless the string is quoted.
.. note:: Please also read through ref:`openpass_variables` for further useful hints, e.g. why explicitly setting the MinGW path might be a necessary in some situations.
- Install directory used by install, when invoking ``make install``
- Recommendation: ``/OpenPASS/bin/core`` (Linux) | ``C:/OpenPASS/bin/core`` (Windows)
- Used only in conjunction with *Visual Studio Debug Builds* (MSVC), as it distinguishes release/debug DLLs by a postfix ``d``.
- Options: **OFF** | ON
- Specifies the build type on single-configuration generators.
- Typical: Release | Debug
- See:
.. note::
IDEs, as Qt Creator, might set this variable base on the current build type on their own.
- Options: **gcc-10** | gcc-9 | gcc-8
- See:
.. note::
IDEs, as Qt Creator, might set this variable via *kit* settings.
- Options: **g++-10** | g++-9 | g++-8
- See:
.. note::
IDEs, as Qt Creator, might set this variable via *kit* settings.
- Under windows, errors from too long paths could be prevented by setting this value to 255 (maximum).
- See:
.. _cmake_openpass_variables:
OpenPASS Variables
- Activates ccache (see :ref:`prerequisites_ccache`)
- Options: **ON** | OFF
- Build OSI based scenario simulation, also know as openPASS core (slave).
- Options: OFF | **ON**
- Build sphinx based documentation
- Options: OFF | **ON**
- Build sphinx based developer documentation
- Options: **OFF** | ON
.. note:: Automatically activates ``WITH_DOC`` if ON
.. warning:: Building the API doc takes pretty long.
- Add test targets for code coverage analysis (lcov) and HTML report generation (genhtml)
- Options: **OFF** | ON
- Use ``COVERAGE_EXCLUDE`` to remove folders from the analysis
.. note::
The generated files are placed next to the test executable.
Each test will be built without optimization, which will increase the testing run-time.
- Activates the additional build of the GUI provided with |Op| (open source).
- Options: **OFF** | ON
.. note::
Please refer to :ref:`gui_user_guide` for information on the GUI.
- Build unit tests
- Options: OFF | **ON**
- Options: **OFF** | ON
- This enables a fix for detection within the MinGW environment, necessary when using the (for compatibility reasons supported) boost version 1.72.
- See:
- Adjusts if builds are executed in the (Cmake default) folder ``build`` or directly in the specified install directory.
Latter mimics the former qmake behavior let you skip the call ``make install``.
- Options: **OFF** | ON
.. warning::
When skipping ``make install``, dependencies are not copied into the output folder, which could cause crashes due to missing or outdated libraries.
.. _cmake_protobuf_arenas:
- When set, assumes that extended version of OSI is available, by enabling the ``USE_EXTENDED_OSI`` preprocessor variable.
- This variable can be used to enable e.g. customized OSI features:
.. code-block:: c++
#include "osi3/osi_<custom_message>.pb.h"
- Options: **OFF** | ON
- | *Arena allocation is a C++-only feature that helps you optimize your memory usage and improve performance when working with protocol buffers.*
| (from
- Options: **ON** | OFF
.. note::
This feature is only available, if protobuf related libraries are also compiled with arenas (see :ref:`building_osi`).
Fortunately, the implementation falls back to regular allocation if not, which simply results in less performance.
- Copy detected system runtime dependencies to install directory (i.e. MinGW system libraries)
- Options: ON | **OFF**
.. warning::
Under windows, automatic resolution might fail if other MinGW instances are installed.
As several programs use MinGW under the hood, it is recommended to set the used MinGW path in the CMAKE_PREFIX_PATH explicitly:
.. code-block:: bash
CMAKE_PREFIX_PATH = mingw64/bin;\...
- Copy detected third party runtime dependencies to install directory (i.e. required shared libraries found in specified CMAKE_PREFIX_PATH)
- Options: ON | **OFF**
Make Targets/Commands
|Op| defines build targets by major modules or components, such as ``OpenPassSlave`` or ``Algorithm_FmuWrapper``.
After calling Cmake, simply build |op| by calling ``make``.
.. admonition:: See also
Build and Install
- ``make``
- ``make install``
.. warning:
- Right now, there is still an issue with an additinal ``bin`` folder.
After installing, the content of the `./bin` folder needs to be copied into `.`.
- Make install seems to have troubles on some systems when copying the dependencies.
Check if the libraries of e.g. OSI are copied into the execution directory of the core.
- MinGW system libraries are not a dependency visible to make (see :ref:`runmingwexe`).
- ``make <target>``: Build a single target
Executing Tests
- All tests: ``make test ARGS="--output-on-failure -j3"``
- Single test: ``make test OpenPassSlave_Tests ARGS="--output-on-failure -j3"``