Fixed BUG #12311. Changed ParaView version number policy.
We now use "git describe" to determine the version for ParaView. Thus we no longer have to use minor/major version number trick for releases. "git describe" returns a string such as "v3.10.1-1701-g427f283". The version is then set as follows: Major: 3 Minor: 10 Patch: 1 Full : 3.10.1-1701-g427f283 If Full=="Major.Minor.Patch", then it's treated as a release. Release candidates can be tagged as "x.y.z-rcN" and the version will be set correctly. If git cannot determine the source version correctly, then "CMake/.paraview.version" file is searched for and we try to parse the version string from this file. It's a fatal error is both these approaches fail.
Showing
- Applications/ParaView/CMakeLists.txt 1 addition, 6 deletionsApplications/ParaView/CMakeLists.txt
- CMake/ParaViewDetermineVersion.cmake 74 additions, 0 deletionsCMake/ParaViewDetermineVersion.cmake
- CMakeLists.txt 19 additions, 17 deletionsCMakeLists.txt
- ParaViewConfig.cmake.in 1 addition, 1 deletionParaViewConfig.cmake.in
- vtkPVConfig.h.in 0 additions, 1 deletionvtkPVConfig.h.in
Loading
Please register or sign in to comment