# Build Paraview-5.11.0 with Legacy Catalyst (v1)
**URL:** https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315
**Category:** ParaView Support
**Tags:** catalyst
**Created:** [February 1, 2023, 5:32pm UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315 "2023-02-01T17:32:29Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@m.novak](https://discourse.paraview.org/u/m.novak)
#### Post date: [February 1, 2023, 5:32pm UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/1 "2023-02-01T17:32:29Z")
Dear support.
I am trying to build paraview-5.11.0 with the latest spack release.
Is it possible to configure it in a way in which Legacy catalyst will get built?
I checked release notes and in 5.9.0 it is stated legacy catalyst will be supported
until further notice. Have I missed the notice?
---
### Author:  [@mirenradia](https://discourse.paraview.org/u/mirenradia)
#### Post date: [February 1, 2023, 5:37pm UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/2 "2023-02-01T17:37:10Z")
Legacy Catalyst is enabled with the `+catalyst` option (see ParaView spack package info [here](https://packages.spack.io/package.html?name=paraview)). Catalyst2 support is the separate `libcatalyst` option.
---
### Author:  [@m.novak](https://discourse.paraview.org/u/m.novak)
#### Post date: [February 1, 2023, 5:51pm UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/3 "2023-02-01T17:51:20Z")
Thank you for the swift reply. I tried +catalyst~libcatalyst, however, this does not produce libcatalyst.so anymore.
---
### Author:  [@mirenradia](https://discourse.paraview.org/u/mirenradia)
#### Post date: [February 1, 2023, 6:13pm UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/4 "2023-02-01T18:13:18Z")
I presume you are using a suitable `build_edition` (e.g. the default `canonical` one). What other options do you have? I’m not all that familiar with building ParaView using Spack so I’m not sure I can help you much further.
FWIW, I don’t think Catalyst2 and Catalyst1 are mutually exclusive in a ParaView build so the `~libcatalyst` option is unnecessary (though it’s disabled by default anyway).
---
### Author:  [@m.novak](https://discourse.paraview.org/u/m.novak)
#### Post date: [February 2, 2023, 10:07am UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/5 "2023-02-02T10:07:51Z")
you are right, if I select +catalyst+libcatalyst libcatalyst-paraview.so and libcatalyst-vtk gets produced.
---
### Author:  [@mirenradia](https://discourse.paraview.org/u/mirenradia)
#### Post date: [February 2, 2023, 10:09am UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/6 "2023-02-02T10:09:10Z")
I think `libcatalyst-.so` are Catalyst2 libraries unless I’m mistaken.
---
### Author:  [@m.novak](https://discourse.paraview.org/u/m.novak)
#### Post date: [February 2, 2023, 11:25am UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/7 "2023-02-02T11:25:56Z")
yes, you are right +catalyst+libcatalyst, has libcatalyst-\*.so and libcatalyst.so are all catalyst-v2.
---
### Author:  [@m.novak](https://discourse.paraview.org/u/m.novak)
#### Post date: [February 3, 2023, 2:45pm UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/8 "2023-02-03T14:45:56Z")
> spack install paraview+mpi+qt+catalyst@5.11.0 %gcc
does not seem to have catalyst at all.
paraview-config.cmake states
```auto
if (0) # paraview_has_catalyst
set("${CMAKE_FIND_PACKAGE_NAME}_CATALYST_DIR"
"${${CMAKE_FIND_PACKAGE_NAME}_PREFIX_PATH}/")
endif ()
```
cmake log says:
Manually-specified variables were not used by the project:
VTK\_MODULE\_USE\_EXTERNAL\_ParaView\_vtkcatalyst
Would somebody be able to share CMakeCache that produces catalyst v1 with paraview-5.11.0?
---
### Author:  [@mirenradia](https://discourse.paraview.org/u/mirenradia)
#### Post date: [February 6, 2023, 10:38am UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/9 "2023-02-06T10:38:49Z")
> [@m.novak](#):
>
> Would somebody be able to share CMakeCache that produces catalyst v1 with paraview-5.11.0?
Here is my [CMakeCache.txt](https://discourse.paraview.org/uploads/short-url/ioCRNghLZ2TIJvVOYFWrKKH7PtO.txt) (223.7 KB). Note that I used the [superbuild](https://gitlab.kitware.com/paraview/paraview-superbuild) rather than Spack (since the Spack build does not currently support OSPRay).
> [@m.novak](#):
>
> cmake log says:
> Manually-specified variables were not used by the project:
> VTK\_MODULE\_USE\_EXTERNAL\_ParaView\_vtkcatalyst
It’s weird that it complains about `VTK_MODULE_USE_EXTERNAL_ParaView_vtkcatalyst` given it seems like the Spack package script only seems to explicitly set this CMake variable for 5.10 ([this line](https://github.com/spack/spack/blob/07d7c32d79eb2f8a843aafc78e1d3ad4711b8ede/var/spack/repos/builtin/packages/paraview/package.py#L407)).
---
### Author:  [@m.novak](https://discourse.paraview.org/u/m.novak)
#### Post date: [February 6, 2023, 11:41am UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/10 "2023-02-06T11:41:42Z")
Thank you for the share of the CMakeCache.txt. I had a brief look and it seems this is set for catalyst-v2: `catalyst_DIR:PATH=.../paraview/build-v5.11.0/install/lib/cmake/catalyst-2.0`
Are you sure your build also contains the legacy catalyst?
---
### Author:  [@mirenradia](https://discourse.paraview.org/u/mirenradia)
#### Post date: [February 6, 2023, 11:51am UTC](https://discourse.paraview.org/t/build-paraview-5-11-0-with-legacy-catalyst-v1/11315/11 "2023-02-06T11:51:34Z")
Yes, I use it with a simulation code instrumented with legacy Catalyst1. This particular build has support for both Catalyst1 and Catalyst2.