Installing gdcm and gdcmPython

Requirements

• For the core C++ library you shall need a C++ compiler with the and STL containers. Gdcm is developped and tested under:
  1. GNU/linux (gcc 2.96.x)
  2. Win32/VC++ 6.x
• For gdcmPython you shall need:
  1. Python version 2.2.x
  2. Swig 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 *
     *

Un*x

Starting from cvs sources.

• Retrieve the sources through cvs,
• cd gdcm
• ./autogen.sh --help in order to select your preferences
• ./autogen.sh to launch the usual automake/autoconf process e.g.
  1. ./autogen.sh --prefix=/where/ever/you/want to configure the script to force installation in a specified place.
  2. ./autogen.sh --enable-python to generate the python wrappers (a.k.a. gdcmPython)
  3. ./autogen.sh --enable-vtk to generate the vtk clases that shallow wrap gdcm,
  4. ./autogen.sh --enable-doxygen to generate the doxygen based documentation
• make
• make instal
• As usual, you can optionnally:
  1. make clean
  2. make CFLAGS='-g' CXXFLAGS='-DPUB_DICT_PATH=\"/usr/local/share/gdcm/\" -D__STDC_LIMIT_MACROS' if you are in hurry and want to omit "-g -O2" default flags
  3. make snapshot

Starting from the sources (snapshot).

The process is exactly the same as the one using the cvs sources (see above) except that you shall use ./configure instead of ./autogen.sh

Windows

• Retrieve the sources through the tarball
• Launch VC++ by opening the gdcm.dsw workspace.
• Proceed with building the required projects.

---