# Building ParaView 5.11-RC1 with ParaView-Catalyst enabled
**URL:** https://discourse.paraview.org/t/building-paraview-5-11-rc1-with-paraview-catalyst-enabled/10222
**Category:** In Situ Support
**Created:** [August 30, 2022, 4:16pm UTC](https://discourse.paraview.org/t/building-paraview-5-11-rc1-with-paraview-catalyst-enabled/10222 "2022-08-30T16:16:50Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [August 30, 2022, 4:16pm UTC](https://discourse.paraview.org/t/building-paraview-5-11-rc1-with-paraview-catalyst-enabled/10222/1 "2022-08-30T16:16:50Z")
Hello,
I’m having trouble building ParaView 5.11-RC1 with ParaView-Catalyst enabled. I am getting:
```auto
CMake Warning at VTK/CMake/vtkModule.cmake:4573 (find_package):
By not providing "Findcatalyst.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "catalyst",
but CMake did not find one.
Could not find a package configuration file provided by "catalyst"
(requested version 2.0) with any of the following names:
catalystConfig.cmake
catalyst-config.cmake
Add the installation prefix of "catalyst" to CMAKE_PREFIX_PATH or set
"catalyst_DIR" to a directory containing one of the above files. If
"catalyst" provides a separate development package or SDK, be sure it has
been installed.
Call Stack (most recent call first):
VTK/IO/CatalystConduit/CMakeLists.txt:7 (vtk_module_find_package)
CMake Error at VTK/CMake/vtkModule.cmake:4579 (message):
Could not find the catalyst external dependency.
Call Stack (most recent call first):
VTK/IO/CatalystConduit/CMakeLists.txt:7 (vtk_module_find_package)
```
I have read the release notes but do not understand whether I am supposed to provide Catalyst or whether ParaView-Catalyst is still provided in ParaView.
Thanks,
Alexandre
---
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [August 30, 2022, 4:17pm UTC](https://discourse.paraview.org/t/building-paraview-5-11-rc1-with-paraview-catalyst-enabled/10222/2 "2022-08-30T16:17:16Z")
FYI @nicolas.vuaille , thanks.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [August 30, 2022, 9:18pm UTC](https://discourse.paraview.org/t/building-paraview-5-11-rc1-with-paraview-catalyst-enabled/10222/3 "2022-08-30T21:18:15Z")
Alex,
catalyst has moved outside of ParaView. You’ll need to build it and point ParaView to it. Please see the script `paraview/VTK/.gitlab/ci/docker/fedora34/install_catalyst.sh` for an example how to do that.
The release notes [state this](https://gitlab.kitware.com/paraview/paraview/-/blob/master/Documentation/release/ParaView-5.11.0.md#conduit-module-has-moved-to-vtk-and-catalyst-is-now-an-external-dependency), but I agree it could be clearer.
---
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [August 30, 2022, 9:33pm UTC](https://discourse.paraview.org/t/building-paraview-5-11-rc1-with-paraview-catalyst-enabled/10222/4 "2022-08-30T21:33:25Z")
Hey Cory,
Thanks for your answer. I was confused whether external dependency to VTK meant it was neither in VTK nor ParaView or whether it was external to VTK but in ParaView.
Which branch/tag of Catalyst do you recommend? ParaView/release or v2.0.0-rc2?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [August 31, 2022, 1:18am UTC](https://discourse.paraview.org/t/building-paraview-5-11-rc1-with-paraview-catalyst-enabled/10222/5 "2022-08-31T01:18:19Z")
ParaView binaries are being built with git commit `3f7871c0a2e737cb9ed35fc1c2208456fcc00a0e` of catalyst, so I recommend that.
---
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [August 31, 2022, 3:24pm UTC](https://discourse.paraview.org/t/building-paraview-5-11-rc1-with-paraview-catalyst-enabled/10222/6 "2022-08-31T15:24:36Z")
Thank you for your help.
I am indeed able to build ParaView when my environment provides a built Catalyst. However, my simulation code is no longer able to pick up the ParaView-Catalyst implementation at run time. I get:
```auto
failed to open library: /lib64/catalyst/libcatalyst-paraview.so: cannot open shared object file: No such file or directory
```
My LD\_LIBRARY\_PATH does provide
```auto
/lib64/catalyst/libcatalyst-paraview.so
```
I also provide $CATALYST\_IMPLEMENTATION\_NAME=paraview.
Has the way of switching between Catalyst implementations changed?
---
### Author:  [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [September 2, 2022, 7:18am UTC](https://discourse.paraview.org/t/building-paraview-5-11-rc1-with-paraview-catalyst-enabled/10222/7 "2022-09-02T07:18:14Z")
Did you also add `CATALYST_IMPLEMENTATION_PATHS` pointing to the .so dir ?
Also, with both `CATALYST_XXX` env, I’m not sure `LD_LIBRARY_PATH` is still needed (but need double check)
---
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [September 2, 2022, 2:55pm UTC](https://discourse.paraview.org/t/building-paraview-5-11-rc1-with-paraview-catalyst-enabled/10222/8 "2022-09-02T14:55:03Z")
Hi Nicolas,
Thank you for your help, it is working now. I had not set that variable. Indeed, it is not necessary for the `LD_LIBRARY_PATH` to point to `libcatalyst-paraview.so`.
To sum up, here is the solution:
- Build Catalyst ([https://gitlab.kitware.com/paraview/catalyst](https://gitlab.kitware.com/paraview/catalyst))
- Build ParaView with `-DPARAVIEW_ENABLE_CATALYST=ON` as a cmake argument. Tell cmake where to look for Catalyst by providing `$catalyst_DIR`
- The simulation code runtime environment should contain Catalyst, ParaView and:
$CATALYST\_IMPLEMENTATION\_NAME = paraview
$CATALYST\_IMPLEMENTATION\_PATHS = \/lib64/catalyst