Create a manifest list of needed objects on Catalyst script creation.
Here is a fabulous feature request from Tom O:
There needs to be a bit more design work on the Catalyst export from ParaView. At a minimum, an exported Catalyst script should have a manifest list describing the required run-time environment and the size of that environment. Catalyst can then look at a script manifest and decide if it can run the script or not based on how it was compiled. Even better, we can give a manifest to the Catalyst build system and have it only include those parts of ParaView in the build.
Watney's position is not unreasonable from the perspective of someone using the ParaView GUI, getting something to work, and then expecting that something to also work in Catalyst. As an HPC code developer, Micah would like minimal bloat from TPLs included in (snip). Catalyst needs to have some formal mechanisms to satisfy the demands of both extremes.