Skip to content

CMake Refactor

Issue for CMake refactor.

This project has following components

  • the API spec
  • stub implementation of the API (libcatalyst.so)
  • c/c++ code to help develop other implementations of the API (also libcatalyst.so). this include static libraries (which can be changed to object libraries if appropriate) for conduit + blueprint.
  • debugging tools (e.g. catalyst_replay), examples etc.

On the users side, we need to support two different use-cases.

  1. For simulation developers: there are people who are simply linking against the libcatalyst.so. It's essential this is single library with a single path for all headers.
  2. For Catalyst implementation developers: These are people who are developing custom implementations of the Catalyst API. i.e. provide their own custom libcatalyst.so.

Things to keep in mind:

  • ParaView currently uses catalyst as submodule...need to support externals as well? should we do external only?

cc: @ben.boeckel