KitwareMedical / KitwareMedical/SlicerCore
Fix ITK in its own repo and Slicer fork
- Dominant language
- CMake
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
SlicerCore builds against a fork of 3DSlicer's ITK fork... https://github.com/Slicer/ITK/compare/slicer-v5.4.5-2025-11-19-f51594a...AlexyPellegrini:ITK:vtk-sdk-support
- [COMP: Fix vtk-sdk support on Windows](https://github.com/Slicer/ITK/commit/c8a47d2a032b9cd9af8d785412abdb76b6361acd) should be merged in ITK and backported to 3DSlicer fork
- [COMP: Remove INSTALL_NAME_DIR on Mac](https://github.com/Slicer/ITK/commit/7996d7b3124d2506a051ea000ff522983adc1250) is already fixed in upstream of ITK, but 3DSlicer fork is too old. https://github.com/InsightSoftwareConsortium/ITK/commit/5b934cf594b23d52cb276b7bf9313d11bb79827f
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the linked Slicer/ITK comparison and commits c8a47d2 and 7996d7b, then compare them with upstream ITK commit 5b934cf. Trace how the ITK fork is used by SlicerCore and identify the corresponding 3DSlicer fork changes. Done means both fixes are present in ITK and backported to the 3DSlicer fork.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100