pvpython and pvbatch executables are not created in the standalone build of CMB

Computational Model Builder (CMB)
1

I built the standalone version of CMB, relying on the superbuild of SMTK. My bin directory only contains modelbuilder.conf and the modelbuilder executable.

On the other hand, if I build CMB as part of the superbuild, the pvpython and pvbatch executables are there.

Is there a CMake option to build pvpython in the standalone CMB build too?

2

pvpython and pvbatch come from ParaView; they should already be present in the ParaView that CMB is building with.

3

Indeed, they are in the ParaView bin dir of the CMB superbuild (superbuild/paraview/build/bin/).

What is the reasoning behind the choice that when CMB is built as part of the superbuild pvpython is copied to the CMB bin directory, while pvpython is not copied when build as a standalone?

4

The superbuild uses a shared install tree for all projects. ParaView installs it there, then CMB (when built with the superbuild) does so as well. CMB has not logic to do anything with the pvpython or pvbatch executables itself.

5

Then how to run SMTK Python code, such as the first_steps.py tutorial, without running them in the Python Shell of CMB?

6

I typically set the CMAKE_INSTALL_PREFIX of builds I do outside of the superbuild to match the install directory of the superbuild. This way, I can install CMB to the same directory where all of its dependencies live. Note that CMake provides an install_manifest.txt file inside the build directory that you can use to remove it should you wish to avoid polluting the superbuild install directory with external software.

1 Like