106 Use of cmake

The website provides some generic description of CMake. Some information about the use of cmake appears on the Ceda SDK for Windows webpage.

There was a dependency bug when using cmake 3.17 onwards, so for a while we were stuck using cmake 3.16, but this is now fixed.

Links

• Ceda SDK version
• Build configuration
• Compiler switches
• Python
• wxWidgets
• boost
• Global properties
• cedaSetSourceRoot
• cedaRunXcppOnWorkspace
• EndOfConfigurationHook
• cedaTarget
• Java
• cmake-generate-output.txt
• cmake-build-output.txt
• dependency issue when using cmake 3.17 onwards
• Using cmake to build MFC projects

Setting the path to the root of the ceda source tree

When you write your CMakeLists.txt file, just after the call to find_package to find the Ceda package you should call the macro cedaSetSourceRoot to set the path to the root of the ceda source tree.

For example:

    find_package(Ceda REQUIRED)
    cedaSetSourceRoot("${CMAKE_CURRENT_SOURCE_DIR}/..")

todo: This is also discussed in Ceda sample programs. It would make sense to properly document how to use CMake when developing ceda based applications in dedicated public web pages, linked by the doco on the sample programs.

How Xcpp projects are built

cmake files under ceda-core

The CMake source files are in the ceda-core repository.