vtk: update to 9.4.0 #22790
Open
vtk: update to 9.4.0 #22790
+107
−243
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Is there an upstream issue? |
MehdiChinoune
force-pushed
the
vtk-clang-19
branch
3 times, most recently
from
b1faf37 to
4cc6222
Compare
MehdiChinoune
force-pushed
the
vtk-clang-19
branch
from
4cc6222 to
653d2dd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fails to build with libc++-19, reported upstream but as usual VTK developers don't fix issues about compatibility with versions of packages other than the ones they build with.
If someone has enough experience with c++, please consider fixing it.
The issue is blocking updating protobuf to 29.1 and gdal to 3.10.0
If no fix for the issue, I will drop some packages (freecad, avogadolibs/avogadro, paraview and itk) and rebuild the others without vtk (OpenCV and OpenCASCADE).