Build customisation and options¶

The OpenCMISS libraries build framework comes with a default build behaviour that is intended be sufficient for most cases of users. However, if you need to make (well-informed!) changes to the default build configuration, here is what we offer.

There are two configuration files that control how the build framework configures builds. The first is an installation wide configuration file located within your top-level binary dir as OpenCMISSInstallationConfig.cmake. As it’s name suggests the settings in this file are applied to every configuration within the installation. Something very important to take into consideration is this, once the first configuration is created the settings in the installation configuration file can no longer be changed.

The second is a local configuration file located within the configuration root location. This configuration file settings apply across all the different build types of that particular configuration. The local configuration file is seeded from the default configuration, the OpenCMISS default configuration is set by the <manage>/Config/OpenCMISSDefaultConfig file. Any value defined there can be overridden by re-definition in local configuration files, which are created (from a template at <manage>/Templates/OpenCMISSLocalConfig.template.cmake) within your top-level configuration binary dir as OpenCMISSLocalConfig.cmake.

Yes, you have a separate local configuration file for each toolchain/mpi combination!

For example, in the default setting this file is located at

<OPENCMISS_ROOT>/build/manage/release/configs/<ARCH PATH for SYSTEM>/OpenCMISSLocalConfig.cmake

The local config file will be automatically read by CMake upon configuration stage. Any subsequent changes to that file trigger an automatic re-run of cmake to propagate the changes to the current build.