Building an external VTK module generate a hierarchy file in VTK build directory
When building an external VTK module, a hierachy file is generated in the build of VTK.
How to reproduce :
- Build VTK
ls vtk_build/lib/cmake/vtk-9.0/Modules/vtkMyFiltersHierarchy.txt ls: cannot access vtkMyFiltersHierarchy.txt: No such file or directory
- untar SimpleModule.tgz
- cd ~/SimpleModule
- mkdir build
- cd build
- cmake -DVTK_DIR=/path/to/VTK/build/ ..
- make
[...] For vtkMyFilters - updating vtkMyFiltersHierarchy.txt
ls vtk_build/lib/cmake/vtk-9.0/Modules/vtkMyFiltersHierarchy.txt vtk_build/lib/cmake/vtk-9.0/Modules/vtkMyFiltersHierarchy.txt
It can be a very big problem, we definitelly cannot assume external module builder have write access on VTK build directory.
This directory is defined by VTK_MODULES_DIR, which is defined during VTK configuration in VTKConfig.cmake.
Somehow related to paraview/paraview#17982 (closed) and !3493 (merged) paraview/paraview!2366 (merged)
Edited by Mathieu Westphal (Kitware)