[seacas] Update to 2025-10-14 [vtk] Update to 9.6.2 [f3d] Update to 3.5.0#52532
[seacas] Update to 2025-10-14 [vtk] Update to 9.6.2 [f3d] Update to 3.5.0#52532dg0yt wants to merge 31 commits into
Conversation
dg0yt
changed the title
|
Reminder to self: Update vtk-compile-tools. Lock version with vtk for CI. |
dg0yt
changed the title
https://gitlab.kitware.com/vtk/vtk/-/merge_requests/12079 it still uses it but it is now a real 3rd party dependency. |
What I see is a new dependency "viskores". It might even be related to vtk-m. But ... the frontpage of viskores.org uses "vtk-m" only in the title. They suggest I should "learn more about the original toolkit" but this link leads to vtk, not vtk-m. So my conclusion is that viskores does not want to be associated with vtk-m... |
From the viskores repo "Learning Rescources" :
|
IMHO they try really hard to avoid spelling this out :-) |
probably a funding issue. One of the reviewers probably said that they need to be separated from VTK to get funded at all so they renamed the project to make it separately fundable from VTK as their own little project. Otherwise I dont see why they needed to make this step away from vtk. That said i dont have any insight in the matter I am just assuming that is what happened here. |
This reverts commit cf422e8.
| - void AddArg(const fmt::detail::named_arg<char_type, T>& fmtArg) | ||
| +#if FMT_VERSION >= 120200 | ||
| + void AddArg(const fmt::named_arg<T, char_type>& fmtArg) | ||
| +#else | ||
| void AddArg(const fmt::detail::named_arg<char_type, T>& fmtArg) | ||
| +#endif |
There was a problem hiding this comment.
2 participants
A set of outdated ports which must be updated together. And which must be updated to unblock other port updates (gdal, cgns).
Context:
graph TD; f3d-->vtk; f3d-->septag-dmon; paraview-->cgns; paraview-->gdal; paraview-->vtk; seacas-->cgns; vcpkg-ci-paraview-->paraview; vtk-->gdal vtk-->seacas;FTR vtk no longer uses vtk-m (aka vtkm).