In addition, ParaView’s git repository and superbuild repository have been tagged with v5.8.0-RC1.
This marks the beginning of the ParaView 5.8.0 release cycle with the final version release slated for the end of January 2020. Release notes will be assembled during the release candidate phase and posted for the final v5.8.0 release.
Please let us know if you find any problems with this release candidate. Some known issues already identified by our earliest testers include:
Anything in particular that needs to be done differently when building additional plugins? With paraview-5.7.0, this all changed (somewhat radically). I’ve now mostly managed to handle that change. Using the same CMakeLists, it seems that there is no longer an install target being created by the paraview_plugin_build() command. Using “make install” thus fails, but even “make all” doesn’t really do much at all.
Name of dependencies and cmake options changed and it can fails quietly depending on how you wrote your dependencies.
Parse the cmake output to make sure you are not missing anything.
Also, take a look into your paraview.plugin and vtk.module to see if their is anything the should be changed. You can share them here.
Does the vtk.module concept also apply to building non-plugins? For example, our Catalyst interface now fails to link in the PythonCatalyst library at all. Tried adding a ${PARAVIEW_LIBRARIES} to the target_link_libraries but that turned out not to work very well at all.
Thanks - that moves me along and the REQUIRED_MODULES is now failing (cannot find ParaView::Core etc). I’ve now checked the diffs between for 5.7.0 and 5.8.0 for ParaViewPlugin.cmake - it doesn’t not look too promising. There is indeed a whole new section in paraview_plugin_build() with INSTALL_EXPORT, INSTALL_HEADERS etc. This looks like it is really going to take a very long time to get any of this working again…
I do not think that is true. I’ve ported a few plugins from 5.7 to 5.8 and it required only a few naming changes. Just remove the not found modules and find the location of the missing include to add the new modules.
Will need to check yet again. Rebuilding some other (non-VTK) bits at the moment. May wish to cross-reference with Andy’s post - seems to be a similar thing that I’ve seen for missing out on the library dependencies (non-plugin).