Build and Install¶
Obtaining the source¶
To obtain the Catalyst source locally, clone the official code repository using Git.
git clone https://gitlab.kitware.com/paraview/catalyst.git
Catalyst uses CMake to generate build system scripts and projects, such as Makefiles or Ninja build files. While IDE generators (Xcode and Visual Studio) are supported, Ninja is highly recommended.
To do a fresh build, start with an empty directory as follows:
mkdir catalyst-build cd catalyst-build ccmake -G Ninja [path to catalyst source directory] # do the build ninja # optionally, run tests ctest # do the install ninja install
ccmake is a graphical GUI that lets you specify various options for CMake.
Alternately, those options can be specified on command line to
-Doption=value) parameters as follows:
cmake -G Ninja -DCATALYST_BUILD_TESTING:BOOL=ON ... [path to catalyst src dir]
-G Ninja results in CMake generating build files for Ninja. You can
switch to using any other supported generator of your choice. See CMake Docs
for details. In that case,
ninja will be replaced by the appropriate build
tool in the steps above.
Supported CMake Options¶
Important CMake options that affect how Catalyst is built are:
ON): choose whether to build static or shared libraries for Catalyst. To support switching of Catalyst implementation at runtime, you must build with
ON): choose whether to build the stub Catalyst implementation. When building Catalyst only to develop another Catalyst API implementation, you may turn this option to
catalystlibrary will be built.
ON): enable/disable testing. Running the tests using
ctestafter a build has succeeded is a good way to verify that your build is functional.
Debug): this is used to choose whether to add debugging symbols to the build. Supported values are
CMAKE_INSTALL_PREFIX: path where to install the libraries and headers when requested.