doc/Doxyfile
changeset 1063 d53a12d49262
parent 1030 c8a41699e613
child 1064 5f0a20861a77
equal deleted inserted replaced
44:65b8e8130726 45:844d39061a03
     1 # Doxyfile 1.3.9
     1 # Doxyfile 1.4.0
     2 
     2 
     3 # This file describes the settings to be used by the documentation system
     3 # This file describes the settings to be used by the documentation system
     4 # doxygen (www.doxygen.org) for a project
     4 # doxygen (www.doxygen.org) for a project
     5 #
     5 #
     6 # All text after a hash (#) is considered a comment and will be ignored
     6 # All text after a hash (#) is considered a comment and will be ignored
    33 OUTPUT_DIRECTORY       = 
    33 OUTPUT_DIRECTORY       = 
    34 
    34 
    35 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 
    35 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 
    36 # 4096 sub-directories (in 2 levels) under the output directory of each output 
    36 # 4096 sub-directories (in 2 levels) under the output directory of each output 
    37 # format and will distribute the generated files over these directories. 
    37 # format and will distribute the generated files over these directories. 
    38 # Enabling this option can be useful when feeding doxygen a huge amount of source 
    38 # Enabling this option can be useful when feeding doxygen a huge amount of 
    39 # files, where putting all generated files in the same directory would otherwise 
    39 # source files, where putting all generated files in the same directory would 
    40 # cause performance problems for the file system.
    40 # otherwise cause performance problems for the file system.
    41 
    41 
    42 CREATE_SUBDIRS         = NO
    42 CREATE_SUBDIRS         = NO
    43 
    43 
    44 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 
    44 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 
    45 # documentation generated by doxygen is written. Doxygen will use this 
    45 # documentation generated by doxygen is written. Doxygen will use this 
    78 REPEAT_BRIEF           = NO
    78 REPEAT_BRIEF           = NO
    79 
    79 
    80 # This tag implements a quasi-intelligent brief description abbreviator 
    80 # This tag implements a quasi-intelligent brief description abbreviator 
    81 # that is used to form the text in various listings. Each string 
    81 # that is used to form the text in various listings. Each string 
    82 # in this list, if found as the leading text of the brief description, will be 
    82 # in this list, if found as the leading text of the brief description, will be 
    83 # stripped from the text and the result after processing the whole list, is used 
    83 # stripped from the text and the result after processing the whole list, is 
    84 # as the annotated text. Otherwise, the brief description is used as-is. If left 
    84 # used as the annotated text. Otherwise, the brief description is used as-is. 
    85 # blank, the following values are used ("$name" is automatically replaced with the 
    85 # If left blank, the following values are used ("$name" is automatically 
    86 # name of the entity): "The $name class" "The $name widget" "The $name file" 
    86 # replaced with the name of the entity): "The $name class" "The $name widget" 
    87 # "is" "provides" "specifies" "contains" "represents" "a" "an" "the"
    87 # "The $name file" "is" "provides" "specifies" "contains" 
       
    88 # "represents" "a" "an" "the"
    88 
    89 
    89 ABBREVIATE_BRIEF       = 
    90 ABBREVIATE_BRIEF       = 
    90 
    91 
    91 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
    92 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
    92 # Doxygen will generate a detailed section even if there is only a brief 
    93 # Doxygen will generate a detailed section even if there is only a brief 
    93 # description.
    94 # description.
    94 
    95 
    95 ALWAYS_DETAILED_SEC    = NO
    96 ALWAYS_DETAILED_SEC    = NO
    96 
    97 
    97 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited 
    98 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 
    98 # members of a class in the documentation of that class as if those members were 
    99 # inherited members of a class in the documentation of that class as if those 
    99 # ordinary class members. Constructors, destructors and assignment operators of 
   100 # members were ordinary class members. Constructors, destructors and assignment 
   100 # the base classes will not be shown.
   101 # operators of the base classes will not be shown.
   101 
   102 
   102 INLINE_INHERITED_MEMB  = NO
   103 INLINE_INHERITED_MEMB  = NO
   103 
   104 
   104 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
   105 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
   105 # path before files name in the file list and in the header files. If set 
   106 # path before files name in the file list and in the header files. If set 
   179 # will result in a user-defined paragraph with heading "Side Effects:". 
   180 # will result in a user-defined paragraph with heading "Side Effects:". 
   180 # You can put \n's in the value part of an alias to insert newlines.
   181 # You can put \n's in the value part of an alias to insert newlines.
   181 
   182 
   182 ALIASES                = 
   183 ALIASES                = 
   183 
   184 
   184 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources 
   185 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 
   185 # only. Doxygen will then generate output that is more tailored for C. 
   186 # sources only. Doxygen will then generate output that is more tailored for C. 
   186 # For instance, some of the names that are used will be different. The list 
   187 # For instance, some of the names that are used will be different. The list 
   187 # of all members will be omitted, etc.
   188 # of all members will be omitted, etc.
   188 
   189 
   189 OPTIMIZE_OUTPUT_FOR_C  = NO
   190 OPTIMIZE_OUTPUT_FOR_C  = NO
   190 
   191 
   371 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 
   372 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 
   372 # in the documentation.
   373 # in the documentation.
   373 
   374 
   374 SHOW_DIRECTORIES       = YES
   375 SHOW_DIRECTORIES       = YES
   375 
   376 
       
   377 # The FILE_VERSION_FILTER tag can be used to specify a program or script that 
       
   378 # doxygen should invoke to get the current version for each file (typically from the 
       
   379 # version control system). Doxygen will invoke the program by executing (via 
       
   380 # popen()) the command <command> <input-file>, where <command> is the value of 
       
   381 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 
       
   382 # provided by doxygen. Whatever the progam writes to standard output 
       
   383 # is used as the file version. See the manual for examples.
       
   384 
       
   385 FILE_VERSION_FILTER    = 
       
   386 
   376 #---------------------------------------------------------------------------
   387 #---------------------------------------------------------------------------
   377 # configuration options related to warning and progress messages
   388 # configuration options related to warning and progress messages
   378 #---------------------------------------------------------------------------
   389 #---------------------------------------------------------------------------
   379 
   390 
   380 # The QUIET tag can be used to turn on/off the messages that are generated 
   391 # The QUIET tag can be used to turn on/off the messages that are generated 
   399 # parameters in a documented function, or documenting parameters that 
   410 # parameters in a documented function, or documenting parameters that 
   400 # don't exist or using markup commands wrongly.
   411 # don't exist or using markup commands wrongly.
   401 
   412 
   402 WARN_IF_DOC_ERROR      = YES
   413 WARN_IF_DOC_ERROR      = YES
   403 
   414 
       
   415 # This WARN_NO_PARAMDOC option can be abled to get warnings for 
       
   416 # functions that are documented, but have no documentation for their parameters 
       
   417 # or return value. If set to NO (the default) doxygen will only warn about 
       
   418 # wrong or incomplete parameter documentation, but not about the absence of 
       
   419 # documentation.
       
   420 
       
   421 WARN_NO_PARAMDOC       = NO
       
   422 
   404 # The WARN_FORMAT tag determines the format of the warning messages that 
   423 # The WARN_FORMAT tag determines the format of the warning messages that 
   405 # doxygen can produce. The string should contain the $file, $line, and $text 
   424 # doxygen can produce. The string should contain the $file, $line, and $text 
   406 # tags, which will be replaced by the file and line number from which the 
   425 # tags, which will be replaced by the file and line number from which the 
   407 # warning originated and the warning text.
   426 # warning originated and the warning text. Optionally the format may contain 
       
   427 # $version, which will be replaced by the version of the file (if it could 
       
   428 # be obtained via FILE_VERSION_FILTER)
   408 
   429 
   409 WARN_FORMAT            = "$file:$line: $text"
   430 WARN_FORMAT            = "$file:$line: $text"
   410 
   431 
   411 # The WARN_LOGFILE tag can be used to specify a file to which warning 
   432 # The WARN_LOGFILE tag can be used to specify a file to which warning 
   412 # and error messages should be written. If left blank the output is written 
   433 # and error messages should be written. If left blank the output is written 
   423 # directories like "/usr/src/myproject". Separate the files or directories 
   444 # directories like "/usr/src/myproject". Separate the files or directories 
   424 # with spaces.
   445 # with spaces.
   425 
   446 
   426 INPUT                  = mainpage.dox \
   447 INPUT                  = mainpage.dox \
   427                          graphs.dox \
   448                          graphs.dox \
   428                          undir_graphs.dox \ 
   449                          undir_graphs.dox \
   429                          named-param.dox \
   450                          named-param.dox \
   430                          maps.dox \
   451                          maps.dox \
   431                          coding_style.dox \
   452                          coding_style.dox \
   432                          groups.dox \
   453                          groups.dox \
   433                          namespaces.dox \
   454                          namespaces.dox \
   434 			 license.dox \
   455                          license.dox \
   435                          developpers_interface.dox \
   456                          developpers_interface.dox \
   436                          ../src/lemon \
   457                          ../src/lemon \
   437                          ../src/lemon/concept \
   458                          ../src/lemon/concept \
   438                          ../src/test/test_tools.h
   459                          ../src/test/test_tools.h
   439 
   460 
   440 # If the value of the INPUT tag contains directories, you can use the 
   461 # If the value of the INPUT tag contains directories, you can use the 
   441 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   462 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   442 # and *.h) to filter out the source-files in the directories. If left 
   463 # and *.h) to filter out the source-files in the directories. If left 
   443 # blank the following patterns are tested: 
   464 # blank the following patterns are tested: 
   444 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp 
   465 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx 
   445 # *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
   466 # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
   446 
   467 
   447 FILE_PATTERNS          = 
   468 FILE_PATTERNS          = 
   448 
   469 
   449 # The RECURSIVE tag can be used to turn specify whether or not subdirectories 
   470 # The RECURSIVE tag can be used to turn specify whether or not subdirectories 
   450 # should be searched for input files as well. Possible values are YES and NO. 
   471 # should be searched for input files as well. Possible values are YES and NO. 
   456 # excluded from the INPUT source files. This way you can easily exclude a 
   477 # excluded from the INPUT source files. This way you can easily exclude a 
   457 # subdirectory from a directory tree whose root is specified with the INPUT tag.
   478 # subdirectory from a directory tree whose root is specified with the INPUT tag.
   458 
   479 
   459 EXCLUDE                = 
   480 EXCLUDE                = 
   460 
   481 
   461 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories 
   482 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or 
   462 # that are symbolic links (a Unix filesystem feature) are excluded from the input.
   483 # directories that are symbolic links (a Unix filesystem feature) are excluded 
       
   484 # from the input.
   463 
   485 
   464 EXCLUDE_SYMLINKS       = NO
   486 EXCLUDE_SYMLINKS       = NO
   465 
   487 
   466 # If the value of the INPUT tag contains directories, you can use the 
   488 # If the value of the INPUT tag contains directories, you can use the 
   467 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
   489 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
   471 
   493 
   472 # The EXAMPLE_PATH tag can be used to specify one or more files or 
   494 # The EXAMPLE_PATH tag can be used to specify one or more files or 
   473 # directories that contain example code fragments that are included (see 
   495 # directories that contain example code fragments that are included (see 
   474 # the \include command).
   496 # the \include command).
   475 
   497 
   476 EXAMPLE_PATH           = ../src/demo ../LICENSE .
   498 EXAMPLE_PATH           = ../src/demo \
       
   499                          ../LICENSE \
       
   500                          .
   477 
   501 
   478 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 
   502 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 
   479 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   503 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   480 # and *.h) to filter out the source-files in the directories. If left 
   504 # and *.h) to filter out the source-files in the directories. If left 
   481 # blank all files are included.
   505 # blank all files are included.
   980 EXPAND_AS_DEFINED      = 
  1004 EXPAND_AS_DEFINED      = 
   981 
  1005 
   982 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
  1006 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
   983 # doxygen's preprocessor will remove all function-like macros that are alone 
  1007 # doxygen's preprocessor will remove all function-like macros that are alone 
   984 # on a line, have an all uppercase name, and do not end with a semicolon. Such 
  1008 # on a line, have an all uppercase name, and do not end with a semicolon. Such 
   985 # function macros are typically used for boiler-plate code, and will confuse the 
  1009 # function macros are typically used for boiler-plate code, and will confuse 
   986 # parser if not removed.
  1010 # the parser if not removed.
   987 
  1011 
   988 SKIP_FUNCTION_MACROS   = YES
  1012 SKIP_FUNCTION_MACROS   = YES
   989 
  1013 
   990 #---------------------------------------------------------------------------
  1014 #---------------------------------------------------------------------------
   991 # Configuration::additions related to external references   
  1015 # Configuration::additions related to external references   
  1033 #---------------------------------------------------------------------------
  1057 #---------------------------------------------------------------------------
  1034 # Configuration options related to the dot tool   
  1058 # Configuration options related to the dot tool   
  1035 #---------------------------------------------------------------------------
  1059 #---------------------------------------------------------------------------
  1036 
  1060 
  1037 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
  1061 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
  1038 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or 
  1062 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 
  1039 # super classes. Setting the tag to NO turns the diagrams off. Note that this 
  1063 # or super classes. Setting the tag to NO turns the diagrams off. Note that 
  1040 # option is superseded by the HAVE_DOT option below. This is only a fallback. It is 
  1064 # this option is superseded by the HAVE_DOT option below. This is only a 
  1041 # recommended to install and use dot, since it yields more powerful graphs.
  1065 # fallback. It is recommended to install and use dot, since it yields more 
       
  1066 # powerful graphs.
  1042 
  1067 
  1043 CLASS_DIAGRAMS         = YES
  1068 CLASS_DIAGRAMS         = YES
  1044 
  1069 
  1045 # If set to YES, the inheritance and collaboration graphs will hide 
  1070 # If set to YES, the inheritance and collaboration graphs will hide 
  1046 # inheritance and usage relations if the target is undocumented 
  1071 # inheritance and usage relations if the target is undocumented 
  1066 # will generate a graph for each documented class showing the direct and 
  1091 # will generate a graph for each documented class showing the direct and 
  1067 # indirect implementation dependencies (inheritance, containment, and 
  1092 # indirect implementation dependencies (inheritance, containment, and 
  1068 # class references variables) of the class with other documented classes.
  1093 # class references variables) of the class with other documented classes.
  1069 
  1094 
  1070 COLLABORATION_GRAPH    = YES
  1095 COLLABORATION_GRAPH    = YES
       
  1096 
       
  1097 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 
       
  1098 # will generate a graph for groups, showing the direct groups dependencies
       
  1099 
       
  1100 GROUP_GRAPHS           = YES
  1071 
  1101 
  1072 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and 
  1102 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and 
  1073 # collaboration diagrams in a style similar to the OMG's Unified Modeling 
  1103 # collaboration diagrams in a style similar to the OMG's Unified Modeling 
  1074 # Language.
  1104 # Language.
  1075 
  1105 
  1105 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
  1135 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
  1106 # will graphical hierarchy of all classes instead of a textual one.
  1136 # will graphical hierarchy of all classes instead of a textual one.
  1107 
  1137 
  1108 GRAPHICAL_HIERARCHY    = YES
  1138 GRAPHICAL_HIERARCHY    = YES
  1109 
  1139 
       
  1140 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES 
       
  1141 # then doxygen will show the dependencies a directory has on other directories 
       
  1142 # in a graphical way. The dependency relations are determined by the #include
       
  1143 # relations between the files in the directories.
       
  1144 
       
  1145 DIRECTORY_GRAPH        = YES
       
  1146 
  1110 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
  1147 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
  1111 # generated by dot. Possible values are png, jpg, or gif
  1148 # generated by dot. Possible values are png, jpg, or gif
  1112 # If left blank png will be used.
  1149 # If left blank png will be used.
  1113 
  1150 
  1114 DOT_IMAGE_FORMAT       = png
  1151 DOT_IMAGE_FORMAT       = png
  1140 
  1177 
  1141 MAX_DOT_GRAPH_HEIGHT   = 1024
  1178 MAX_DOT_GRAPH_HEIGHT   = 1024
  1142 
  1179 
  1143 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 
  1180 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 
  1144 # graphs generated by dot. A depth value of 3 means that only nodes reachable 
  1181 # graphs generated by dot. A depth value of 3 means that only nodes reachable 
  1145 # from the root by following a path via at most 3 edges will be shown. Nodes that 
  1182 # from the root by following a path via at most 3 edges will be shown. Nodes 
  1146 # lay further from the root node will be omitted. Note that setting this option to 
  1183 # that lay further from the root node will be omitted. Note that setting this 
  1147 # 1 or 2 may greatly reduce the computation time needed for large code bases. Also 
  1184 # option to 1 or 2 may greatly reduce the computation time needed for large 
  1148 # note that a graph may be further truncated if the graph's image dimensions are 
  1185 # code bases. Also note that a graph may be further truncated if the graph's 
  1149 # not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT). 
  1186 # image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH 
  1150 # If 0 is used for the depth value (the default), the graph is not depth-constrained.
  1187 # and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default), 
       
  1188 # the graph is not depth-constrained.
  1151 
  1189 
  1152 MAX_DOT_GRAPH_DEPTH    = 0
  1190 MAX_DOT_GRAPH_DEPTH    = 0
       
  1191 
       
  1192 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 
       
  1193 # background. This is disabled by default, which results in a white background. 
       
  1194 # Warning: Depending on the platform used, enabling this option may lead to 
       
  1195 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to 
       
  1196 # read).
       
  1197 
       
  1198 DOT_TRANSPARENT        = NO
       
  1199 
       
  1200 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 
       
  1201 # files in one run (i.e. multiple -o and -T options on the command line). This 
       
  1202 # makes dot run faster, but since only newer versions of dot (>1.8.10) 
       
  1203 # support this, this feature is disabled by default.
       
  1204 
       
  1205 DOT_MULTI_TARGETS      = NO
  1153 
  1206 
  1154 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
  1207 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
  1155 # generate a legend page explaining the meaning of the various boxes and 
  1208 # generate a legend page explaining the meaning of the various boxes and 
  1156 # arrows in the dot generated graphs.
  1209 # arrows in the dot generated graphs.
  1157 
  1210