Using OpenCMISS Libraries From SDK¶
Having already downloaded and installed the SDK on your computer the following instructions will get you set up and started using the OpenCMISS libraries.
The SDK provides pre-compiled binaries of all the OpenCMISS libraries and can be used to develop your own applications against them using either the directly exposed APIs or provided bindings to C or Python languages. Check the downloads section for current packages.
In addition to the SDK, you need a local MPI installation if you want to run parallel code with OpenCMISS-Iron.
As the use is different depending on the intended API, please see the appropriate sections below.
Using the Fortran or C API¶
We recommend that you use CMake to develop applications using the OpenCMISS libraries (OpenCMISS libraries are built using CMake), of which you need version 3.4.0 or newer. Instructions for other ways of using the installed SDK libraries in your development environment will be added later.
An outline of a CMake script for understanding how to use OpenCMISS libraries in your application is given below. An exemplar
CMakeLists.txt could look like:
# This is my application which uses OpenCMISS libraries cmake_minimum_required(VERSION 3.4.0) project(MyOpenCMISSApplication LANGUAGES C Fortran) find_package(OpenCMISSLibs <VERSION> REQUIRED COMPONENTS [Iron|Zinc] CONFIG)
This will look for an OpenCMISS libraries package information file, which is contained in your SDK installation. It will also verify that the found SDK does in fact match your currently configured toolchain and MPI choice. Then, to add OpenCMISS-powered libraries and executables, use:
# For a library use add_library(mylib <SOURCES>) target_link_libraries(mylib PRIVATE opencmiss) # For an executable use add_executable(myexec <SOURCES>) target_link_libraries(mylib PRIVATE opencmiss)
If you wanted to add a test for your binaries/libraries, you can conveniently use:
# Add a test that runs your binary add_test(myapptest myexec) add_opencmiss_environment(myapptest)
add_opencmiss_environment function will set up the test environment to contain the necessary library paths.
The testing can then be run using CTest
Finally, to configure your application, you need to set the variable
OpenCMISSLibs_DIR to your SDK installation
folder in CMake (define in CMake-GUI or set via
-DOpenCMISSLibs_DIR in command line).
If suitable, you may also define the
OpenCMISSLibs_DIR variable in your environment. This way you dont have to specify it when
configuring your own component builds through CMake/manage.
Windows only If you chose the default install location, CMake can pick up the installation via system default paths and you dont have to