[ITK] No GDCMConfig.cmake

Matt McCormick matt.mccormick at kitware.com
Mon Feb 23 13:27:29 EST 2015


Hi Nigel,

Yes, ITK's internal GDCM is not intended to be used by other libraries.

To have a shared version of GDCM, build GDCM outside of ITK, perhaps
using the MITK build of GDCM, then point ITK to this version of GDCM
by setting ITK_USE_SYSTEM_GDCM to ON, and pointing CMake to your GDCM
build.

HTH,
Matt

On Mon, Feb 23, 2015 at 12:18 PM, Nigel Mcfarlane
<Nigel.Mcfarlane at beds.ac.uk> wrote:
> I am using ITK 4.5.2 and I have found that GDCMConfig.cmake is not built.
> This means that there is no handle by which an external library can find and
> use ITK’s version of GDCM.
>
>
>
> My problem is that I’m trying to build MITK, which includes both ITK and
> GDCM as third-party libraries.  If I point MITK’s superbuild at the existing
> ITK on my system, I get a version clash between ITK’s GDCM and the one
> downloaded by MITK.  I was intending to solve this by pointing MITK at the
> GDCM in ITK, but it seems that ITK does not export its copy of GDCM for
> external use.
>
>
>
> The line which would have created it is:
>
> C:\ITK\InsightToolkit-4.5.2\Modules\ThirdParty\GDCM\src\gdcm\CMakeLists.txt
>
> #SUBDIRS(CMake/ExportConfiguration)
>
>
>
> This has been deliberately commented out to prevent the export of GDCM.  Is
> there a reason for this, such as the library being altered, patched or
> incomplete?
>
>
>
> Thank you
>
> Nigel McFarlane
>
> University of Bedfordshire, UK
>
>
>
>
> _______________________________________________
> Community mailing list
> Community at itk.org
> http://public.kitware.com/mailman/listinfo/community
>


More information about the Community mailing list