Cannot build Base: can't find file to patch

In Situ Support
1

Hi,

I successfully linked a code to Catalyst-v5.6.0-Base-Enable-Python-Essentials-Extras-Rendering-Base, but some writers, e.g. XMLHierarchicalBoxDataWriter and XMLUniformGridAMRWriter, are scrubbed away and not available in the catalyst editions. I am trying to build my extended edition, and to include these writers. As a first step I try to rebuild Base as it is. I made a copy of Base as myBase, and run catalyze.py, but it fails while applying patches (see below).

What do I miss here? Any help is highly appreciated.

Thanks,

Ted

[ews00734@Catalyst $] python catalyze.py -r /ascldap/users/tesari/projects/paraview -i Editions/myBase/ -o ~/projects/myBase

Processing Editions/myBase/
patching file ParaViewCore/ClientServerCore/Core/CMakeLists.txt
Hunk #1 FAILED at 34.
Hunk #2 FAILED at 48.
Hunk #3 FAILED at 108.
3 out of 3 hunks FAILED – saving rejects to file ParaViewCore/ClientServerCore/Core/CMakeLists.txt.rej
can’t find file to patch at input line 33
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

|diff --git a/ParaViewCore/ClientServerCore/Core/module.cmake b/ParaViewCore/ClientServerCore/Core/module.cmake
|index f17c4df…f0db074 100644
|— a/ParaViewCore/ClientServerCore/Core/module.cmake

+++ b/ParaViewCore/ClientServerCore/Core/module.cmake

File to patch: ^CTraceback (most recent call last):
File “catalyze.py”, line 418, in
main()
File “catalyze.py”, line 413, in main
process(config)
File “catalyze.py”, line 344, in process
copy_paths(config, manifest[‘modules’])
File “catalyze.py”, line 214, in copy_paths
run_patches(config, path_entry)
File “catalyze.py”, line 151, in run_patches
p.wait()
File “/ascldap/users/tesari/local/python-2.7.16/lib/python2.7/subprocess.py”, line 1099, in wait
pid, sts = _eintr_retry_call(os.waitpid, self.pid, 0)
File “/ascldap/users/tesari/local/python-2.7.16/lib/python2.7/subprocess.py”, line 125, in _eintr_retry_call
return func(*args)
KeyboardInterrupt

2

Are you using master? Or a released 5.6.0?

3

I pull from gitlab.kitware.com/paraview/paraview.git

4

master doesn’t support the catalyze.py scripts. See https://gitlab.kitware.com/paraview/paraview/issues/18800 for details. In the meantime, I suggest using the release branch to do catalyze.py-based builds.

5

Thanks for the info. I checkout release, but now cmake cannot
find vtkModuleAPI and vtkModuleMacros. Just to make sure, I did a
fresh clone,

git clone --recursive ParaView
cd ParaView
git pull
git submodule update --init
git checkout --track -b release origin/release

  Still fails with the same error (see below). Could you advice,

please?

Thanks,

Ted

CMake Error at CMakeLists.txt:662 (include):

       include could not find load file:

         vtkModuleAPI

     CMake Error at CMakeLists.txt:663 (include):

       include could not find load file:

         vtkModuleMacros

     CMake Error at CMake/ParaViewModuleTop.cmake:44

(vtk_add_to_module_search_path):

       Unknown CMake command "vtk_add_to_module_search_path".

     Call Stack (most recent call first):

       CMakeLists.txt:689 (include)
6

The submodule update --recursive --init should be done after checking out ParaView’s release branch.

7

We should inform better of this, we still have too many users failing this step.

8

There’s code in the common-superbuild which detects out-of-date submodules. ParaView could copy it to detect it for VTK and the other submodules.

9

This is what I had in mind, yes.