# ParaView 5.8.0 Release Candidate 1 available for download
**URL:** https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359
**Category:** Announcements
**Tags:** releases
**Created:** [January 16, 2020, 11:42pm UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359 "2020-01-16T23:42:17Z")
**Posts on this page:** 14
**Page:** 1
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [January 16, 2020, 11:42pm UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/1 "2020-01-16T23:42:18Z")
The ParaView team is excited to announce that ParaView 5.8.0-RC1 (Release Candidate 1) is available for download at
[https://www.paraview.org/download/](https://www.paraview.org/download/)
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:
[Wrong case for names in Catalyst script.](https://gitlab.kitware.com/paraview/paraview/issues/19573) - fixed
[Split vertical and horizontal icons are switched] ([https://gitlab.kitware.com/paraview/paraview/issues/19575](https://gitlab.kitware.com/paraview/paraview/issues/19575)) - fixed
[Preview menu item is grayed out](https://gitlab.kitware.com/paraview/paraview/issues/19578) - fixed
[paraview.simple.GetOpenGLInformation() fails](https://gitlab.kitware.com/paraview/paraview/issues/19580) - fixed
[“Hover points on” not updated when switching geometries](https://gitlab.kitware.com/paraview/paraview/issues/19574)
[CMake configure CATALYST edition can’t find ParaView::RemotingViews](https://gitlab.kitware.com/paraview/paraview/issues/19579)
[ParaView 5.8.0-RC1: build failure on MSVC 2017](https://gitlab.kitware.com/paraview/paraview/issues/19581)
[texturemaptosphere hangs in parallel](https://gitlab.kitware.com/paraview/paraview/issues/19585)
Thanks!
The ParaView team
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 22, 2020, 3:33am UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/2 "2020-01-22T03:33:30Z")
- No .zip package are available for windows, is that intended ?
- The .exe installer propose to install “runtime” and “superbuild” component. What does these do ?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [January 22, 2020, 3:44pm UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/3 "2020-01-22T15:44:01Z")
> [@mwestphal](#):
>
> No .zip package are available for windows, is that intended ?
The .zip files for Windows are now uploaded and available on the downloads page.
> [@mwestphal](#):
>
> The .exe installer propose to install “runtime” and “superbuild” component. What does these do ?
[https://gitlab.kitware.com/paraview/paraview-superbuild/issues/143](https://gitlab.kitware.com/paraview/paraview-superbuild/issues/143)
---
### Author:  [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [January 27, 2020, 7:15pm UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/4 "2020-01-27T19:15:32Z")
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.
Cheers,
/mark
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 28, 2020, 3:03am UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/5 "2020-01-28T03:03:37Z")
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.
---
### Author:  [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [January 28, 2020, 8:34am UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/6 "2020-01-28T08:34:24Z")
> [@mwestphal](#):
>
> 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.
Hi @mwestphal - I appreciate the offer. Instead of posting directly, here is a [browsable link](https://develop.openfoam.com/modules/visualization/tree/develop/src).
The simpler plugins is for [blockMesh reading](https://develop.openfoam.com/modules/visualization/tree/develop/src/paraview-plugins/blockMeshReader) - the [CMakeLists-Project57](https://develop.openfoam.com/modules/visualization/tree/develop/src/paraview-plugins/blockMeshReader/CMakeLists-Project57.txt) contains the `paraview_plugin_build()` with [paraview.plugin](https://develop.openfoam.com/modules/visualization/tree/develop/src/paraview-plugins/blockMeshReader/plugin/paraview.plugin) and [vtk.module](https://develop.openfoam.com/modules/visualization/tree/develop/src/paraview-plugins/blockMeshReader/plugin/reader/vtk.module).
Does the vtk.module concept also apply to building non-plugins? For example, our [Catalyst interface](https://develop.openfoam.com/modules/visualization/tree/develop/src/catalyst/CMakeLists-Project.txt) 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.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 28, 2020, 8:41am UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/7 "2020-01-28T08:41:25Z")
@olesenm: in your paraview.plugin, replace `PARAVIEW_BUILD_QT_GUI` by `PARAVIEW_USE_QT`
This is a silent fail and it should be fixed somehow @utkarsh.ayachit @ben.boeckel .
---
### Author:  [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [January 28, 2020, 9:46am UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/8 "2020-01-28T09:46:17Z")
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…
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 28, 2020, 12:14pm UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/9 "2020-01-28T12:14:40Z")
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.
---
### Author:  [@olesenm](https://discourse.paraview.org/u/olesenm)
#### Post date: [January 28, 2020, 2:06pm UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/10 "2020-01-28T14:06:58Z")
Will need to check yet again. Rebuilding some other (non-VTK) bits at the moment. May wish to cross-reference with [Andy’s post](https://discourse.paraview.org/t/cmakelists-txt-for-catalyst-5-8/3434) - seems to be a similar thing that I’ve seen for missing out on the library dependencies (non-plugin).
---
### Author:  [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [January 31, 2020, 3:48pm UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/11 "2020-01-31T15:48:31Z")
We can provide backwards compat for that. I’ll have an MR up.
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [February 16, 2020, 1:59pm UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/12 "2020-02-16T13:59:39Z")
How about scheduled python 3 support?
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [February 16, 2020, 4:02pm UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/13 "2020-02-16T16:02:27Z")
We started shipping Windows and Linux binaries with Python 3 beginning with ParaView 5.7. Python 3 support in the macOS version is not yet available.
---
### Author:  [@MBG](https://discourse.paraview.org/u/MBG)
#### Post date: [February 16, 2020, 7:46pm UTC](https://discourse.paraview.org/t/paraview-5-8-0-release-candidate-1-available-for-download/3359/14 "2020-02-16T19:46:42Z")
@cory.quammen does the Python 3 support still planned for ParaView 5.8 release on MacOS?