"${GDCM_SOURCE_DIR}/src ${GDCM_SOURCE_DIR}/Doc/DoxyPython.txt ${GDCM_SOURCE_DIR}/Doc/DoxyVtkGdmReaderExamples.txt"
)
SET(GDCM_DOCUMENTATION_EXCLUDE_COMMON
- "${GDCM_SOURCE_DIR}/src/gdcmJpeg.cxx"
- "${GDCM_SOURCE_DIR}/src/jdatasrc.cxx"
- "${GDCM_SOURCE_DIR}/src/jdatadst.cxx"
+ "${GDCM_SOURCE_DIR}/src/gdcmJpeg.cxx ${GDCM_SOURCE_DIR}/src/jdatasrc.cxx ${GDCM_SOURCE_DIR}/src/jdatadst.cxx"
)
IF(GDCM_VTK)
# This could be handy for archiving the generated documentation or
# if some version control system is used.
-PROJECT_NUMBER = @GDCM_VERSION_MAJOR@.@GDCM_VERSION_MINOR@.@GDCM_VERSION_PATCH@
+PROJECT_NUMBER = @GDCM_MAJOR_VERSION@.@GDCM_MINOR_VERSION@.@GDCM_BUILD_VERSION@
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
# base path where the generated documentation will be put.
# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
# *.h++ *.idl *.odl
-FILE_PATTERNS = *.cxx *.h
+FILE_PATTERNS = *.h *.cxx
# The RECURSIVE tag can be used to turn specify whether or not subdirectories
# should be searched for input files as well. Possible values are YES and NO.
# directories that contain example code fragments that are included (see
# the \include command).
-EXAMPLE_PATH = @GDCM_SOURCE_DIR@/gdcmPython/demo @GDCM_SOURCE_DIR@/vtk
+EXAMPLE_PATH = @GDCM_SOURCE_DIR@/Example @GDCM_SOURCE_DIR@/Testing @GDCM_SOURCE_DIR@/gdcmPython/demo @GDCM_SOURCE_DIR@/vtk
# If the value of the EXAMPLE_PATH tag contains directories, you can use the
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp