Illegal 'undefined length UN DataElement' :

[gdcm.git] / Doc / doxygen.config.in

diff --git a/Doc/doxygen.config.in b/Doc/doxygen.config.in
index 07677910a55587c2e6c95d0c183b4814b040b95b..8103cd5d968bc50c320c6bb2b92d116f744d5a98 100644 (file)
--- a/Doc/doxygen.config.in
+++ b/Doc/doxygen.config.in
@@ -23,7 +23,7 @@ PROJECT_NAME           = gdcm
 # 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. 
@@ -301,7 +301,7 @@ WARN_LOGFILE           =
 # directories like "/usr/src/myproject". Separate the files or directories 
 # with spaces.
 
-INPUT  = @GDCM_DOXYGEN_INPUT@
+INPUT  = @GDCM_DOCUMENTATION_INPUT@
 
 # If the value of the INPUT tag contains directories, you can use the 
 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
@@ -310,7 +310,7 @@ INPUT  = @GDCM_DOXYGEN_INPUT@
 # *.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. 
@@ -322,7 +322,7 @@ RECURSIVE              = NO
 # excluded from the INPUT source files. This way you can easily exclude a 
 # subdirectory from a directory tree whose root is specified with the INPUT tag.
 
-EXCLUDE                = @GDCM_DOXYGEN_EXCLUDE@
+EXCLUDE                = @GDCM_DOCUMENTATION_EXCLUDE@
 
 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories 
 # that are symbolic links (a Unix filesystem feature) are excluded from the input.
@@ -339,14 +339,14 @@ EXCLUDE_PATTERNS       =
 # directories that contain example code fragments that are included (see 
 # the \include command).
 
-EXAMPLE_PATH           = @GDCM_SOURCE_DIR@/gdcmPython/demo
+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 
 # and *.h) to filter out the source-files in the directories. If left 
 # blank all files are included.
 
-EXAMPLE_PATTERNS       = 
+EXAMPLE_PATTERNS       = *.py *.cxx
 
 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
 # searched for input files to be used with the \include or \dontinclude 
@@ -785,7 +785,7 @@ CLASS_DIAGRAMS         = YES
 # toolkit from AT&T and Lucent Bell Labs. The other options in this section 
 # have no effect if this option is set to NO (the default)
 
-HAVE_DOT               = NO
+HAVE_DOT               = @GDCM_DOCUMENTATION_HAVE_DOT@
 
 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 
 # will generate a graph for each documented class showing the direct and 
@@ -840,7 +840,7 @@ DOT_IMAGE_FORMAT       = png
 # The tag DOT_PATH can be used to specify the path where the dot tool can be 
 # found. If left blank, it is assumed the dot tool can be found on the path.
 
-DOT_PATH               = 
+DOT_PATH               = @GDCM_DOCUMENTATION_DOT_PATH@
 
 # The DOTFILE_DIRS tag can be used to specify one or more directories that 
 # contain dot files that are included in the documentation (see the