Installing gdcm from sources

Requirements

• For the core C++ library you shall need a C++ compiler with the "list" and "map" STL containers.
  Gdcm is developped and tested under:
  • GNU/linux (gcc 3.2.x)
  • Win32/VC++ 6.x
• Cmake is used by gdcm for generating Un*x makefiles or VC++ projects. Grab latest release (at least 2.0.3).
• Optionnaly, for the VTK wrappers you will additionaly need :
• Optionnaly, for the Python wrappers you will additionaly need :
  • Python version 2.2.x
  • Swig at least version 1.3.17x (in order to handle C++ member overloading, shadow classes and static methods)
    • Rpms for GNU/linux: swig13-1.3.17-1.i386.rpm, swig13-1.3.17-1.src.rpm.
    • for Win32 you shall need to compile the sources

Step by step recompilation

• Retrieve gdcm the sources through cvs. We shall refer to this source directory as gdcmSources.
• Create a compile directory (e.g. gdcmBin) that we shall refer as gdcmBINARY. Change working directory to gdcmBINARY.
• Invoke ccmake (from gdcmBINARY) with gdcmSources as source directory.
  Hit "c" for a first automatic configuration of your platteform
• Select the options that suite your needs. Basically this means toggling ON or OFF the following parameters
  • GDCM_DOXYGEN if you wish to generate the doxygen documentation,
  • GGDCM_VTK if you wish to generate the VTK wrappers,
  • GDCM_WRAP_PYTHON if you wish to generate the Python wrappers.
• Among the other options, you might consider toggling ON or OFF the following parameters
  • BUILD_EXAMPLES if you wish to generate the C++ gdcm examples,
  • BUILD_TESTING if you wish to generate gdcm test suite. When doing so you will need to retrieve gdcmData i.e. the set of Dicom image used in the test suite.

  ---