but it set ParaView_FOUND to FALSE so package “ParaView” is considered to
be NOT FOUND. Reason given by package:
The following imported targets are referenced, but are missing:
VTK::FiltersParallelDIY2
I have manully checked my install directory, all files relative to FiltersParallelDIY2 in my ParaView install dir and is path is here:
Additional infomations:
I built ParaView 5.9 offcial released source code with Visual Studio 15 2017 Win64, and plugin project config is same.
Python version is 3.7.5
I have used these project in both ParaView5.7 and ParaView5.8, and have never faced this issue.
So, maybe I missed some new cmake request in new version? or is there any clue to debug this? Thanks!
The plugin project has tons of dependency libraries built with visual studio,
I am afread there are too many works to do compiling all these libs with ninja.
So why paraview config scripts cannot find existing FiltersParallelDIY2 lib in my ParaView_DIR? bug in Visual Studio Compiler ?
Since we find VTK without components, everything from VTK should be available. Can you see if there is a VTK::FiltersParallelDIY2 target in lib/cmake/paraview-5.9/vtk/vtk-targets.cmake?
I also found some message in cmake-trace-expand may help:
D:/ParaView59/lib/cmake/paraview-5.9/HyperTreeGridADR-targets.cmake(104): if(CMAKE_FIND_PACKAGE_NAME )
D:/ParaView59/lib/cmake/paraview-5.9/HyperTreeGridADR-targets.cmake(105): set(ParaView_FOUND FALSE )
D:/ParaView59/lib/cmake/paraview-5.9/HyperTreeGridADR-targets.cmake(106): set(ParaView_NOT_FOUND_MESSAGE The following imported targets are referenced, but are missing: VTK::FiltersParallelDIY2 )
Hmm. Interesting. That HyperTreeGridADR file should be being included after the find_package(VTK). Are there other hints as to why the target isn’t available at that point from the expanded trace?