[Insight-developers] ITK + find_package(DCMTK NO_MODULE) progress/success

Williams, Norman K norman-k-williams at uiowa.edu
Fri Feb 22 14:47:01 EST 2013


SoŠ this one is kind of a thing that has a lot of moving parts.

1. I have a patch submitted to DCMTK, that properly generates
DCMTKConfig.cmake & other files, to support find_package(DCMTK NO_MODULE).
 This is currently a branch on the InsightSoftwareConsortium/DCMTK repo we
set up a couple of weeks ago:
https://github.com/InsightSoftwareConsortium/DCMTK/tree/AddProperConfig

2. I have a gerrit topic here http://review.source.kitware.com/#/c/9954/
That is designed to build against the fixed DCMTK.

3. I have a text fixture project on Github that combines all these things:
https://github.com/Chaircrusher/DCMTK_ITK_TESTFIXTURE

Now the ultimate goal is that everyone (where for me that means ITK,
BRAINSTools, Slicer) use the find_package(DCMTK NO_MODULE) syntax; this is
ultimately a more robust solution.  The problem is in the near term, there
are too many dependent things going on.

My patch for ITK depends on the patched DCMTK.  It might be possible to
maintain backwards compatibility with the old find_package and unpatched
DCMTK, but I'm not sure how to implement that.  Would it be as simple as
this?

find_package(DCMTK NO_MODULE QUIET)
if(NOT DCMTK_FOUND)
  find_package(DCMTK REQUIRED QUIET)
  if(NOT DCMTK_FOUND)
    message(FATAL_ERROR "DCMTK package not found. Please set DCMTK_DIR and
re-run CMake")
  endif()
endif()
--
Kent Williams norman-k-williams at uiowa.edu






________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
________________________________


More information about the Insight-developers mailing list