Fixes for upgraded DCMTK and web-assembly build

[jadh4v]

(This is a work in progress)
Updates to DCMQI library after upgrading DCMTK to a later commit (InsightSoftwareConsortium/DCMTK@0c72275).
Upgrade CMake minimum version to better support sub-project mode when overriding default CMAKE variable values.
These updates are related to the effort to add DICOM SEG Object read/write capabilities in ITK-wasm.

Current DCMTK fork used by ITK-wasm (includes patches for web assembly build): https://github.com/InsightSoftwareConsortium/DCMTK/tree/20240311_DCMTK_PATCHES_FOR_ITK-wasm

[fedorov]

This work might be related, @michaelonken ran into some issues that have not been resolved: #493.

@rfloca would you like to check this out to see if this creates any issues for MITK?

[fedorov]

For the reference, here's configuration of DCMTK for Slicer: https://github.com/Slicer/Slicer/blob/main/SuperBuild/External_DCMTK.cmake

DCMTK apps selected https://github.com/Slicer/Slicer/blob/main/CMake/SlicerBlockInstallDCMTKApps.cmake#L5

[fedorov]

MITK DCMTK config: https://github.com/MITK/MITK/blob/master/CMakeExternals/DCMTK.cmake (right now uses DCMTK-3.6.7 from upstream https://github.com/MITK/MITK/blob/master/CMakeExternals/DCMTK.cmake#L33-L34).

[thewtex]

We are seeing Windows segfaults on other packages on GitHub Actions starting this week-ish.

One approach that may help is the CMake minimum version bump re::

CMake Warning at D:/a/ITKParabolicMorphology/ITK/CMake/ITKModuleExternal.cmake:15 (message):
-- This is needed to allow proper setting of CMAKE_MSVC_RUNTIME_LIBRARY.
-- Do not be surprised if you run into link errors of the style:
  LNK2038: mismatch detected for 'RuntimeLibrary': value 'MTd_Static' doesn't match value 'MDd_Dynamic' in module.obj
  cmake_minimum_required must be at least 3.16.3
Call Stack (most recent call first):
  CMakeLists.txt:7 (include)

Edit: related commit: InsightSoftwareConsortium/ITK@4b010e7

[fedorov]

@jadh4v @thewtex @michaelonken let's try to use this discord channel for coordination: https://discord.gg/3vZakgNS

[thewtex]

FYI re:

• Backport security fixes to patched-DCMTK-3.6.6_20210115 commontk/DCMTK#14
• https://www.cvedetails.com/cve/CVE-2022-2119/

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

The ITK-Wasm DCMQI / DCMTK modules address this issue without any changes needed to DCMTK. Access in the Wasm runtime is contained only to the directories of the files passed.

[thewtex]

Of interest:

actions/runner-images@a615999#diff-d3119a278ce9ce80fc4b5af63a1112fb3a044aec3e6002d838e8eb26d7a3a499R475-R480

[rfloca]

This work might be related, @michaelonken ran into some issues that have not been resolved: #493.

@rfloca would you like to check this out to see if this creates any issues for MITK?

I'll do. But it might take 2-3 weeks. Currently is a lot todo and I have to see when I find the time. Please excuse that I cannot react faster.

[jadh4v]

I have locally tested the super-build and tests on windows 11 VS2022. All tests are passing. Ran into a build issue regarding DCMTK targets. I have a temp fix for it locally, but will consult with others for more appropriate fix.

[jcfr]

After discussing with @jadh4v , I suggest we ensure dcmqi can support being built against a newer DCMTK without updating the version currently used in its external project.

In the short term, this will allow ITK wasm to build dcmqi against a newer version of DCMTK.

In the medium term (likely during the upcoming Slicer project week), we will work on:

• Update DCMTK version used in Slicer & CTK. See COMP: Update DCMTK to version 3.6.7 Slicer/Slicer#6709
• Update DCMTK version used in dcmqi

The includes of headers available only in newer DCMTK could be made conditionally after including dcmtk/config/osconfig.h and using PACKAGE_VERSION_NUMBER.

cc: @michaelonken