src/work/Doxyfile
author jacint
Fri, 07 Jan 2005 08:40:13 +0000
changeset 1058 dddb01f98796
parent 1006 aa8c2f05b9ab
child 1065 340fe3cbb145
permissions -rw-r--r--
undirgrafbug
     1 # Doxyfile 1.3.6
     2 
     3 # This file describes the settings to be used by the documentation system
     4 # doxygen (www.doxygen.org) for a project
     5 #
     6 # All text after a hash (#) is considered a comment and will be ignored
     7 # The format is:
     8 #       TAG = value [value, ...]
     9 # For lists items can also be appended using:
    10 #       TAG += value [value, ...]
    11 # Values that contain spaces should be placed between quotes (" ")
    12 
    13 #---------------------------------------------------------------------------
    14 # Project related configuration options
    15 #---------------------------------------------------------------------------
    16 
    17 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
    18 # by quotes) that should identify the project.
    19 
    20 PROJECT_NAME           = LEMON
    21 
    22 # The PROJECT_NUMBER tag can be used to enter a project or revision number. 
    23 # This could be handy for archiving the generated documentation or 
    24 # if some version control system is used.
    25 
    26 PROJECT_NUMBER         = 0.3
    27 
    28 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
    29 # base path where the generated documentation will be put. 
    30 # If a relative path is entered, it will be relative to the location 
    31 # where doxygen was started. If left blank the current directory will be used.
    32 
    33 OUTPUT_DIRECTORY       = 
    34 
    35 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 
    36 # documentation generated by doxygen is written. Doxygen will use this 
    37 # information to generate all constant output in the proper language. 
    38 # The default language is English, other supported languages are: 
    39 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, 
    40 # Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en 
    41 # (Japanese with English messages), Korean, Korean-en, Norwegian, Polish, Portuguese, 
    42 # Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
    43 
    44 OUTPUT_LANGUAGE        = English
    45 
    46 # This tag can be used to specify the encoding used in the generated output. 
    47 # The encoding is not always determined by the language that is chosen, 
    48 # but also whether or not the output is meant for Windows or non-Windows users. 
    49 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES 
    50 # forces the Windows encoding (this is the default for the Windows binary), 
    51 # whereas setting the tag to NO uses a Unix-style encoding (the default for 
    52 # all platforms other than Windows).
    53 
    54 USE_WINDOWS_ENCODING   = NO
    55 
    56 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
    57 # include brief member descriptions after the members that are listed in 
    58 # the file and class documentation (similar to JavaDoc). 
    59 # Set to NO to disable this.
    60 
    61 BRIEF_MEMBER_DESC      = YES
    62 
    63 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
    64 # the brief description of a member or function before the detailed description. 
    65 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
    66 # brief descriptions will be completely suppressed.
    67 
    68 REPEAT_BRIEF           = NO
    69 
    70 # This tag implements a quasi-intelligent brief description abbreviator 
    71 # that is used to form the text in various listings. Each string 
    72 # in this list, if found as the leading text of the brief description, will be 
    73 # stripped from the text and the result after processing the whole list, is used 
    74 # as the annotated text. Otherwise, the brief description is used as-is. If left 
    75 # blank, the following values are used ("$name" is automatically replaced with the 
    76 # name of the entity): "The $name class" "The $name widget" "The $name file" 
    77 # "is" "provides" "specifies" "contains" "represents" "a" "an" "the"
    78 
    79 ABBREVIATE_BRIEF       = 
    80 
    81 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
    82 # Doxygen will generate a detailed section even if there is only a brief 
    83 # description.
    84 
    85 ALWAYS_DETAILED_SEC    = NO
    86 
    87 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited 
    88 # members of a class in the documentation of that class as if those members were 
    89 # ordinary class members. Constructors, destructors and assignment operators of 
    90 # the base classes will not be shown.
    91 
    92 INLINE_INHERITED_MEMB  = NO
    93 
    94 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
    95 # path before files name in the file list and in the header files. If set 
    96 # to NO the shortest path that makes the file name unique will be used.
    97 
    98 FULL_PATH_NAMES        = NO
    99 
   100 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
   101 # can be used to strip a user-defined part of the path. Stripping is 
   102 # only done if one of the specified strings matches the left-hand part of 
   103 # the path. It is allowed to use relative paths in the argument list. 
   104 # If left blank the directory from which doxygen is run is used as the 
   105 # path to strip.
   106 
   107 STRIP_FROM_PATH        = 
   108 
   109 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
   110 # (but less readable) file names. This can be useful is your file systems 
   111 # doesn't support long names like on DOS, Mac, or CD-ROM.
   112 
   113 SHORT_NAMES            = NO
   114 
   115 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
   116 # will interpret the first line (until the first dot) of a JavaDoc-style 
   117 # comment as the brief description. If set to NO, the JavaDoc 
   118 # comments will behave just like the Qt-style comments (thus requiring an 
   119 # explicit @brief command for a brief description.
   120 
   121 JAVADOC_AUTOBRIEF      = NO
   122 
   123 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
   124 # treat a multi-line C++ special comment block (i.e. a block of //! or /// 
   125 # comments) as a brief description. This used to be the default behaviour. 
   126 # The new default is to treat a multi-line C++ comment block as a detailed 
   127 # description. Set this tag to YES if you prefer the old behaviour instead.
   128 
   129 MULTILINE_CPP_IS_BRIEF = NO
   130 
   131 # If the DETAILS_AT_TOP tag is set to YES then Doxygen 
   132 # will output the detailed description near the top, like JavaDoc.
   133 # If set to NO, the detailed description appears after the member 
   134 # documentation.
   135 
   136 DETAILS_AT_TOP         = YES
   137 
   138 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
   139 # member inherits the documentation from any documented member that it 
   140 # re-implements.
   141 
   142 INHERIT_DOCS           = NO
   143 
   144 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
   145 # tag is set to YES, then doxygen will reuse the documentation of the first 
   146 # member in the group (if any) for the other members of the group. By default 
   147 # all members of a group must be documented explicitly.
   148 
   149 DISTRIBUTE_GROUP_DOC   = NO
   150 
   151 # The TAB_SIZE tag can be used to set the number of spaces in a tab. 
   152 # Doxygen uses this value to replace tabs by spaces in code fragments.
   153 
   154 TAB_SIZE               = 8
   155 
   156 # This tag can be used to specify a number of aliases that acts 
   157 # as commands in the documentation. An alias has the form "name=value". 
   158 # For example adding "sideeffect=\par Side Effects:\n" will allow you to 
   159 # put the command \sideeffect (or @sideeffect) in the documentation, which 
   160 # will result in a user-defined paragraph with heading "Side Effects:". 
   161 # You can put \n's in the value part of an alias to insert newlines.
   162 
   163 ALIASES                = 
   164 
   165 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources 
   166 # only. Doxygen will then generate output that is more tailored for C. 
   167 # For instance, some of the names that are used will be different. The list 
   168 # of all members will be omitted, etc.
   169 
   170 OPTIMIZE_OUTPUT_FOR_C  = NO
   171 
   172 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources 
   173 # only. Doxygen will then generate output that is more tailored for Java. 
   174 # For instance, namespaces will be presented as packages, qualified scopes 
   175 # will look different, etc.
   176 
   177 OPTIMIZE_OUTPUT_JAVA   = NO
   178 
   179 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of 
   180 # the same type (for instance a group of public functions) to be put as a 
   181 # subgroup of that type (e.g. under the Public Functions section). Set it to 
   182 # NO to prevent subgrouping. Alternatively, this can be done per class using 
   183 # the \nosubgrouping command.
   184 
   185 SUBGROUPING            = YES
   186 
   187 #---------------------------------------------------------------------------
   188 # Build related configuration options
   189 #---------------------------------------------------------------------------
   190 
   191 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
   192 # documentation are documented, even if no documentation was available. 
   193 # Private class members and static file members will be hidden unless 
   194 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
   195 
   196 EXTRACT_ALL            = NO
   197 
   198 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
   199 # will be included in the documentation.
   200 
   201 EXTRACT_PRIVATE        = YES
   202 
   203 # If the EXTRACT_STATIC tag is set to YES all static members of a file 
   204 # will be included in the documentation.
   205 
   206 EXTRACT_STATIC         = NO
   207 
   208 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
   209 # defined locally in source files will be included in the documentation. 
   210 # If set to NO only classes defined in header files are included.
   211 
   212 EXTRACT_LOCAL_CLASSES  = YES
   213 
   214 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
   215 # undocumented members of documented classes, files or namespaces. 
   216 # If set to NO (the default) these members will be included in the 
   217 # various overviews, but no documentation section is generated. 
   218 # This option has no effect if EXTRACT_ALL is enabled.
   219 
   220 HIDE_UNDOC_MEMBERS     = YES
   221 
   222 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
   223 # undocumented classes that are normally visible in the class hierarchy. 
   224 # If set to NO (the default) these classes will be included in the various 
   225 # overviews. This option has no effect if EXTRACT_ALL is enabled.
   226 
   227 HIDE_UNDOC_CLASSES     = YES
   228 
   229 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
   230 # friend (class|struct|union) declarations. 
   231 # If set to NO (the default) these declarations will be included in the 
   232 # documentation.
   233 
   234 HIDE_FRIEND_COMPOUNDS  = NO
   235 
   236 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 
   237 # documentation blocks found inside the body of a function. 
   238 # If set to NO (the default) these blocks will be appended to the 
   239 # function's detailed documentation block.
   240 
   241 HIDE_IN_BODY_DOCS      = NO
   242 
   243 # The INTERNAL_DOCS tag determines if documentation 
   244 # that is typed after a \internal command is included. If the tag is set 
   245 # to NO (the default) then the documentation will be excluded. 
   246 # Set it to YES to include the internal documentation.
   247 
   248 INTERNAL_DOCS          = NO
   249 
   250 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
   251 # file names in lower-case letters. If set to YES upper-case letters are also 
   252 # allowed. This is useful if you have classes or files whose names only differ 
   253 # in case and if your file system supports case sensitive file names. Windows 
   254 # users are advised to set this option to NO.
   255 
   256 CASE_SENSE_NAMES       = YES
   257 
   258 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
   259 # will show members with their full class and namespace scopes in the 
   260 # documentation. If set to YES the scope will be hidden.
   261 
   262 HIDE_SCOPE_NAMES       = YES
   263 
   264 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
   265 # will put a list of the files that are included by a file in the documentation 
   266 # of that file.
   267 
   268 SHOW_INCLUDE_FILES     = YES
   269 
   270 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
   271 # is inserted in the documentation for inline members.
   272 
   273 INLINE_INFO            = YES
   274 
   275 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
   276 # will sort the (detailed) documentation of file and class members 
   277 # alphabetically by member name. If set to NO the members will appear in 
   278 # declaration order.
   279 
   280 SORT_MEMBER_DOCS       = NO
   281 
   282 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 
   283 # brief documentation of file, namespace and class members alphabetically 
   284 # by member name. If set to NO (the default) the members will appear in 
   285 # declaration order.
   286 
   287 SORT_BRIEF_DOCS        = NO
   288 
   289 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 
   290 # sorted by fully-qualified names, including namespaces. If set to 
   291 # NO (the default), the class list will be sorted only by class name, 
   292 # not including the namespace part. 
   293 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
   294 # Note: This option applies only to the class list, not to the 
   295 # alphabetical list.
   296 
   297 SORT_BY_SCOPE_NAME     = NO
   298 
   299 # The GENERATE_TODOLIST tag can be used to enable (YES) or 
   300 # disable (NO) the todo list. This list is created by putting \todo 
   301 # commands in the documentation.
   302 
   303 GENERATE_TODOLIST      = YES
   304 
   305 # The GENERATE_TESTLIST tag can be used to enable (YES) or 
   306 # disable (NO) the test list. This list is created by putting \test 
   307 # commands in the documentation.
   308 
   309 GENERATE_TESTLIST      = YES
   310 
   311 # The GENERATE_BUGLIST tag can be used to enable (YES) or 
   312 # disable (NO) the bug list. This list is created by putting \bug 
   313 # commands in the documentation.
   314 
   315 GENERATE_BUGLIST       = YES
   316 
   317 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
   318 # disable (NO) the deprecated list. This list is created by putting 
   319 # \deprecated commands in the documentation.
   320 
   321 GENERATE_DEPRECATEDLIST= YES
   322 
   323 # The ENABLED_SECTIONS tag can be used to enable conditional 
   324 # documentation sections, marked by \if sectionname ... \endif.
   325 
   326 ENABLED_SECTIONS       = 
   327 
   328 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
   329 # the initial value of a variable or define consists of for it to appear in 
   330 # the documentation. If the initializer consists of more lines than specified 
   331 # here it will be hidden. Use a value of 0 to hide initializers completely. 
   332 # The appearance of the initializer of individual variables and defines in the 
   333 # documentation can be controlled using \showinitializer or \hideinitializer 
   334 # command in the documentation regardless of this setting.
   335 
   336 MAX_INITIALIZER_LINES  = 30
   337 
   338 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated 
   339 # at the bottom of the documentation of classes and structs. If set to YES the 
   340 # list will mention the files that were used to generate the documentation.
   341 
   342 SHOW_USED_FILES        = YES
   343 
   344 #---------------------------------------------------------------------------
   345 # configuration options related to warning and progress messages
   346 #---------------------------------------------------------------------------
   347 
   348 # The QUIET tag can be used to turn on/off the messages that are generated 
   349 # by doxygen. Possible values are YES and NO. If left blank NO is used.
   350 
   351 QUIET                  = NO
   352 
   353 # The WARNINGS tag can be used to turn on/off the warning messages that are 
   354 # generated by doxygen. Possible values are YES and NO. If left blank 
   355 # NO is used.
   356 
   357 WARNINGS               = YES
   358 
   359 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
   360 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
   361 # automatically be disabled.
   362 
   363 WARN_IF_UNDOCUMENTED   = YES
   364 
   365 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 
   366 # potential errors in the documentation, such as not documenting some 
   367 # parameters in a documented function, or documenting parameters that 
   368 # don't exist or using markup commands wrongly.
   369 
   370 WARN_IF_DOC_ERROR      = YES
   371 
   372 # The WARN_FORMAT tag determines the format of the warning messages that 
   373 # doxygen can produce. The string should contain the $file, $line, and $text 
   374 # tags, which will be replaced by the file and line number from which the 
   375 # warning originated and the warning text.
   376 
   377 WARN_FORMAT            = "$file:$line: $text"
   378 
   379 # The WARN_LOGFILE tag can be used to specify a file to which warning 
   380 # and error messages should be written. If left blank the output is written 
   381 # to stderr.
   382 
   383 WARN_LOGFILE           = doxygen.log
   384 
   385 #---------------------------------------------------------------------------
   386 # configuration options related to the input files
   387 #---------------------------------------------------------------------------
   388 
   389 # The INPUT tag can be used to specify the files and/or directories that contain 
   390 # documented source files. You may enter file names like "myfile.cpp" or 
   391 # directories like "/usr/src/myproject". Separate the files or directories 
   392 # with spaces.
   393 
   394 INPUT                  = ../../doc/mainpage.dox \
   395 			 ../../doc/graphs.dox \
   396                          ../../doc/maps.dox ../../doc/coding_style.dox \
   397                          ../../doc/groups.dox \
   398                          ../lemon \
   399                          ../lemon/concept \
   400                          ../test/test_tools.h \
   401                          klao/debug.h \
   402                          jacint/max_flow.h \
   403                          jacint/max_matching.h \ 
   404 			 marci/bfs_dfs.h \
   405 	  		 marci/bfs_dfs_misc.h \
   406                          marci/lp/lp_solver_wrapper.h \
   407 			 jacint/graph_gen.h \
   408 			 marci/max_bipartite_matching.h \
   409 			 marci/bipartite_graph_wrapper.h \
   410 			 alpar/graph_to_eps.cc \
   411                          deba \
   412                          
   413 
   414 # If the value of the INPUT tag contains directories, you can use the 
   415 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   416 # and *.h) to filter out the source-files in the directories. If left 
   417 # blank the following patterns are tested: 
   418 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp 
   419 # *.h++ *.idl *.odl *.cs *.php *.php3 *.inc
   420 
   421 FILE_PATTERNS          = 
   422 
   423 # The RECURSIVE tag can be used to turn specify whether or not subdirectories 
   424 # should be searched for input files as well. Possible values are YES and NO. 
   425 # If left blank NO is used.
   426 
   427 RECURSIVE              = NO
   428 
   429 # The EXCLUDE tag can be used to specify files and/or directories that should 
   430 # excluded from the INPUT source files. This way you can easily exclude a 
   431 # subdirectory from a directory tree whose root is specified with the INPUT tag.
   432 
   433 EXCLUDE                = 
   434 
   435 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories 
   436 # that are symbolic links (a Unix filesystem feature) are excluded from the input.
   437 
   438 EXCLUDE_SYMLINKS       = NO
   439 
   440 # If the value of the INPUT tag contains directories, you can use the 
   441 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
   442 # certain files from those directories.
   443 
   444 EXCLUDE_PATTERNS       = 
   445 
   446 # The EXAMPLE_PATH tag can be used to specify one or more files or 
   447 # directories that contain example code fragments that are included (see 
   448 # the \include command).
   449 
   450 EXAMPLE_PATH           = 
   451 
   452 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 
   453 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   454 # and *.h) to filter out the source-files in the directories. If left 
   455 # blank all files are included.
   456 
   457 EXAMPLE_PATTERNS       = 
   458 
   459 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
   460 # searched for input files to be used with the \include or \dontinclude 
   461 # commands irrespective of the value of the RECURSIVE tag. 
   462 # Possible values are YES and NO. If left blank NO is used.
   463 
   464 EXAMPLE_RECURSIVE      = NO
   465 
   466 # The IMAGE_PATH tag can be used to specify one or more files or 
   467 # directories that contain image that are included in the documentation (see 
   468 # the \image command).
   469 
   470 IMAGE_PATH             = 
   471 
   472 # The INPUT_FILTER tag can be used to specify a program that doxygen should 
   473 # invoke to filter for each input file. Doxygen will invoke the filter program 
   474 # by executing (via popen()) the command <filter> <input-file>, where <filter> 
   475 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
   476 # input file. Doxygen will then use the output that the filter program writes 
   477 # to standard output.
   478 
   479 INPUT_FILTER           = 
   480 
   481 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
   482 # INPUT_FILTER) will be used to filter the input files when producing source 
   483 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
   484 
   485 FILTER_SOURCE_FILES    = NO
   486 
   487 #---------------------------------------------------------------------------
   488 # configuration options related to source browsing
   489 #---------------------------------------------------------------------------
   490 
   491 # If the SOURCE_BROWSER tag is set to YES then a list of source files will 
   492 # be generated. Documented entities will be cross-referenced with these sources. 
   493 # Note: To get rid of all source code in the generated output, make sure also 
   494 # VERBATIM_HEADERS is set to NO.
   495 
   496 SOURCE_BROWSER         = YES
   497 
   498 # Setting the INLINE_SOURCES tag to YES will include the body 
   499 # of functions and classes directly in the documentation.
   500 
   501 INLINE_SOURCES         = NO
   502 
   503 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
   504 # doxygen to hide any special comment blocks from generated source code 
   505 # fragments. Normal C and C++ comments will always remain visible.
   506 
   507 STRIP_CODE_COMMENTS    = YES
   508 
   509 # If the REFERENCED_BY_RELATION tag is set to YES (the default) 
   510 # then for each documented function all documented 
   511 # functions referencing it will be listed.
   512 
   513 REFERENCED_BY_RELATION = YES
   514 
   515 # If the REFERENCES_RELATION tag is set to YES (the default) 
   516 # then for each documented function all documented entities 
   517 # called/used by that function will be listed.
   518 
   519 REFERENCES_RELATION    = YES
   520 
   521 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
   522 # will generate a verbatim copy of the header file for each class for 
   523 # which an include is specified. Set to NO to disable this.
   524 
   525 VERBATIM_HEADERS       = YES
   526 
   527 #---------------------------------------------------------------------------
   528 # configuration options related to the alphabetical class index
   529 #---------------------------------------------------------------------------
   530 
   531 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
   532 # of all compounds will be generated. Enable this if the project 
   533 # contains a lot of classes, structs, unions or interfaces.
   534 
   535 ALPHABETICAL_INDEX     = YES
   536 
   537 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
   538 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
   539 # in which this list will be split (can be a number in the range [1..20])
   540 
   541 COLS_IN_ALPHA_INDEX    = 2
   542 
   543 # In case all classes in a project start with a common prefix, all 
   544 # classes will be put under the same header in the alphabetical index. 
   545 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
   546 # should be ignored while generating the index headers.
   547 
   548 IGNORE_PREFIX          = 
   549 
   550 #---------------------------------------------------------------------------
   551 # configuration options related to the HTML output
   552 #---------------------------------------------------------------------------
   553 
   554 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
   555 # generate HTML output.
   556 
   557 GENERATE_HTML          = YES
   558 
   559 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
   560 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   561 # put in front of it. If left blank `html' will be used as the default path.
   562 
   563 HTML_OUTPUT            = html
   564 
   565 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
   566 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
   567 # doxygen will generate files with .html extension.
   568 
   569 HTML_FILE_EXTENSION    = .html
   570 
   571 # The HTML_HEADER tag can be used to specify a personal HTML header for 
   572 # each generated HTML page. If it is left blank doxygen will generate a 
   573 # standard header.
   574 
   575 HTML_HEADER            = 
   576 
   577 # The HTML_FOOTER tag can be used to specify a personal HTML footer for 
   578 # each generated HTML page. If it is left blank doxygen will generate a 
   579 # standard footer.
   580 
   581 HTML_FOOTER            = 
   582 
   583 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading 
   584 # style sheet that is used by each HTML page. It can be used to 
   585 # fine-tune the look of the HTML output. If the tag is left blank doxygen 
   586 # will generate a default style sheet. Note that doxygen will try to copy 
   587 # the style sheet file to the HTML output directory, so don't put your own 
   588 # stylesheet in the HTML output directory as well, or it will be erased!
   589 
   590 HTML_STYLESHEET        = 
   591 
   592 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 
   593 # files or namespaces will be aligned in HTML using tables. If set to 
   594 # NO a bullet list will be used.
   595 
   596 HTML_ALIGN_MEMBERS     = YES
   597 
   598 # If the GENERATE_HTMLHELP tag is set to YES, additional index files 
   599 # will be generated that can be used as input for tools like the 
   600 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm) 
   601 # of the generated HTML documentation.
   602 
   603 GENERATE_HTMLHELP      = NO
   604 
   605 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
   606 # be used to specify the file name of the resulting .chm file. You 
   607 # can add a path in front of the file if the result should not be 
   608 # written to the html output directory.
   609 
   610 CHM_FILE               = 
   611 
   612 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
   613 # be used to specify the location (absolute path including file name) of 
   614 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 
   615 # the HTML help compiler on the generated index.hhp.
   616 
   617 HHC_LOCATION           = 
   618 
   619 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
   620 # controls if a separate .chi index file is generated (YES) or that 
   621 # it should be included in the master .chm file (NO).
   622 
   623 GENERATE_CHI           = NO
   624 
   625 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
   626 # controls whether a binary table of contents is generated (YES) or a 
   627 # normal table of contents (NO) in the .chm file.
   628 
   629 BINARY_TOC             = NO
   630 
   631 # The TOC_EXPAND flag can be set to YES to add extra items for group members 
   632 # to the contents of the HTML help documentation and to the tree view.
   633 
   634 TOC_EXPAND             = NO
   635 
   636 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at 
   637 # top of each HTML page. The value NO (the default) enables the index and 
   638 # the value YES disables it.
   639 
   640 DISABLE_INDEX          = NO
   641 
   642 # This tag can be used to set the number of enum values (range [1..20]) 
   643 # that doxygen will group on one line in the generated HTML documentation.
   644 
   645 ENUM_VALUES_PER_LINE   = 4
   646 
   647 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
   648 # generated containing a tree-like index structure (just like the one that 
   649 # is generated for HTML Help). For this to work a browser that supports 
   650 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, 
   651 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are 
   652 # probably better off using the HTML help feature.
   653 
   654 GENERATE_TREEVIEW      = YES
   655 
   656 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
   657 # used to set the initial width (in pixels) of the frame in which the tree 
   658 # is shown.
   659 
   660 TREEVIEW_WIDTH         = 250
   661 
   662 #---------------------------------------------------------------------------
   663 # configuration options related to the LaTeX output
   664 #---------------------------------------------------------------------------
   665 
   666 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
   667 # generate Latex output.
   668 
   669 GENERATE_LATEX         = NO
   670 
   671 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
   672 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   673 # put in front of it. If left blank `latex' will be used as the default path.
   674 
   675 LATEX_OUTPUT           = latex
   676 
   677 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 
   678 # invoked. If left blank `latex' will be used as the default command name.
   679 
   680 LATEX_CMD_NAME         = latex
   681 
   682 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
   683 # generate index for LaTeX. If left blank `makeindex' will be used as the 
   684 # default command name.
   685 
   686 MAKEINDEX_CMD_NAME     = makeindex
   687 
   688 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
   689 # LaTeX documents. This may be useful for small projects and may help to 
   690 # save some trees in general.
   691 
   692 COMPACT_LATEX          = YES
   693 
   694 # The PAPER_TYPE tag can be used to set the paper type that is used 
   695 # by the printer. Possible values are: a4, a4wide, letter, legal and 
   696 # executive. If left blank a4wide will be used.
   697 
   698 PAPER_TYPE             = a4wide
   699 
   700 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
   701 # packages that should be included in the LaTeX output.
   702 
   703 EXTRA_PACKAGES         = 
   704 
   705 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
   706 # the generated latex document. The header should contain everything until 
   707 # the first chapter. If it is left blank doxygen will generate a 
   708 # standard header. Notice: only use this tag if you know what you are doing!
   709 
   710 LATEX_HEADER           = 
   711 
   712 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
   713 # is prepared for conversion to pdf (using ps2pdf). The pdf file will 
   714 # contain links (just like the HTML output) instead of page references 
   715 # This makes the output suitable for online browsing using a pdf viewer.
   716 
   717 PDF_HYPERLINKS         = YES
   718 
   719 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
   720 # plain latex in the generated Makefile. Set this option to YES to get a 
   721 # higher quality PDF documentation.
   722 
   723 USE_PDFLATEX           = YES
   724 
   725 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
   726 # command to the generated LaTeX files. This will instruct LaTeX to keep 
   727 # running if errors occur, instead of asking the user for help. 
   728 # This option is also used when generating formulas in HTML.
   729 
   730 LATEX_BATCHMODE        = NO
   731 
   732 # If LATEX_HIDE_INDICES is set to YES then doxygen will not 
   733 # include the index chapters (such as File Index, Compound Index, etc.) 
   734 # in the output.
   735 
   736 LATEX_HIDE_INDICES     = NO
   737 
   738 #---------------------------------------------------------------------------
   739 # configuration options related to the RTF output
   740 #---------------------------------------------------------------------------
   741 
   742 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
   743 # The RTF output is optimized for Word 97 and may not look very pretty with 
   744 # other RTF readers or editors.
   745 
   746 GENERATE_RTF           = NO
   747 
   748 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
   749 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   750 # put in front of it. If left blank `rtf' will be used as the default path.
   751 
   752 RTF_OUTPUT             = rtf
   753 
   754 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
   755 # RTF documents. This may be useful for small projects and may help to 
   756 # save some trees in general.
   757 
   758 COMPACT_RTF            = NO
   759 
   760 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
   761 # will contain hyperlink fields. The RTF file will 
   762 # contain links (just like the HTML output) instead of page references. 
   763 # This makes the output suitable for online browsing using WORD or other 
   764 # programs which support those fields. 
   765 # Note: wordpad (write) and others do not support links.
   766 
   767 RTF_HYPERLINKS         = NO
   768 
   769 # Load stylesheet definitions from file. Syntax is similar to doxygen's 
   770 # config file, i.e. a series of assignments. You only have to provide 
   771 # replacements, missing definitions are set to their default value.
   772 
   773 RTF_STYLESHEET_FILE    = 
   774 
   775 # Set optional variables used in the generation of an rtf document. 
   776 # Syntax is similar to doxygen's config file.
   777 
   778 RTF_EXTENSIONS_FILE    = 
   779 
   780 #---------------------------------------------------------------------------
   781 # configuration options related to the man page output
   782 #---------------------------------------------------------------------------
   783 
   784 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
   785 # generate man pages
   786 
   787 GENERATE_MAN           = NO
   788 
   789 # The MAN_OUTPUT tag is used to specify where the man pages will be put. 
   790 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   791 # put in front of it. If left blank `man' will be used as the default path.
   792 
   793 MAN_OUTPUT             = man
   794 
   795 # The MAN_EXTENSION tag determines the extension that is added to 
   796 # the generated man pages (default is the subroutine's section .3)
   797 
   798 MAN_EXTENSION          = .3
   799 
   800 # If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
   801 # then it will generate one additional man file for each entity 
   802 # documented in the real man page(s). These additional files 
   803 # only source the real man page, but without them the man command 
   804 # would be unable to find the correct page. The default is NO.
   805 
   806 MAN_LINKS              = NO
   807 
   808 #---------------------------------------------------------------------------
   809 # configuration options related to the XML output
   810 #---------------------------------------------------------------------------
   811 
   812 # If the GENERATE_XML tag is set to YES Doxygen will 
   813 # generate an XML file that captures the structure of 
   814 # the code including all documentation.
   815 
   816 GENERATE_XML           = NO
   817 
   818 # The XML_OUTPUT tag is used to specify where the XML pages will be put. 
   819 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   820 # put in front of it. If left blank `xml' will be used as the default path.
   821 
   822 XML_OUTPUT             = xml
   823 
   824 # The XML_SCHEMA tag can be used to specify an XML schema, 
   825 # which can be used by a validating XML parser to check the 
   826 # syntax of the XML files.
   827 
   828 XML_SCHEMA             = 
   829 
   830 # The XML_DTD tag can be used to specify an XML DTD, 
   831 # which can be used by a validating XML parser to check the 
   832 # syntax of the XML files.
   833 
   834 XML_DTD                = 
   835 
   836 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will 
   837 # dump the program listings (including syntax highlighting 
   838 # and cross-referencing information) to the XML output. Note that 
   839 # enabling this will significantly increase the size of the XML output.
   840 
   841 XML_PROGRAMLISTING     = YES
   842 
   843 #---------------------------------------------------------------------------
   844 # configuration options for the AutoGen Definitions output
   845 #---------------------------------------------------------------------------
   846 
   847 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
   848 # generate an AutoGen Definitions (see autogen.sf.net) file 
   849 # that captures the structure of the code including all 
   850 # documentation. Note that this feature is still experimental 
   851 # and incomplete at the moment.
   852 
   853 GENERATE_AUTOGEN_DEF   = NO
   854 
   855 #---------------------------------------------------------------------------
   856 # configuration options related to the Perl module output
   857 #---------------------------------------------------------------------------
   858 
   859 # If the GENERATE_PERLMOD tag is set to YES Doxygen will 
   860 # generate a Perl module file that captures the structure of 
   861 # the code including all documentation. Note that this 
   862 # feature is still experimental and incomplete at the 
   863 # moment.
   864 
   865 GENERATE_PERLMOD       = NO
   866 
   867 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate 
   868 # the necessary Makefile rules, Perl scripts and LaTeX code to be able 
   869 # to generate PDF and DVI output from the Perl module output.
   870 
   871 PERLMOD_LATEX          = NO
   872 
   873 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 
   874 # nicely formatted so it can be parsed by a human reader.  This is useful 
   875 # if you want to understand what is going on.  On the other hand, if this 
   876 # tag is set to NO the size of the Perl module output will be much smaller 
   877 # and Perl will parse it just the same.
   878 
   879 PERLMOD_PRETTY         = YES
   880 
   881 # The names of the make variables in the generated doxyrules.make file 
   882 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 
   883 # This is useful so different doxyrules.make files included by the same 
   884 # Makefile don't overwrite each other's variables.
   885 
   886 PERLMOD_MAKEVAR_PREFIX = 
   887 
   888 #---------------------------------------------------------------------------
   889 # Configuration options related to the preprocessor   
   890 #---------------------------------------------------------------------------
   891 
   892 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
   893 # evaluate all C-preprocessor directives found in the sources and include 
   894 # files.
   895 
   896 ENABLE_PREPROCESSING   = YES
   897 
   898 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
   899 # names in the source code. If set to NO (the default) only conditional 
   900 # compilation will be performed. Macro expansion can be done in a controlled 
   901 # way by setting EXPAND_ONLY_PREDEF to YES.
   902 
   903 MACRO_EXPANSION        = NO
   904 
   905 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 
   906 # then the macro expansion is limited to the macros specified with the 
   907 # PREDEFINED and EXPAND_AS_PREDEFINED tags.
   908 
   909 EXPAND_ONLY_PREDEF     = NO
   910 
   911 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 
   912 # in the INCLUDE_PATH (see below) will be search if a #include is found.
   913 
   914 SEARCH_INCLUDES        = YES
   915 
   916 # The INCLUDE_PATH tag can be used to specify one or more directories that 
   917 # contain include files that are not input files but should be processed by 
   918 # the preprocessor.
   919 
   920 INCLUDE_PATH           = 
   921 
   922 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 
   923 # patterns (like *.h and *.hpp) to filter out the header-files in the 
   924 # directories. If left blank, the patterns specified with FILE_PATTERNS will 
   925 # be used.
   926 
   927 INCLUDE_FILE_PATTERNS  = 
   928 
   929 # The PREDEFINED tag can be used to specify one or more macro names that 
   930 # are defined before the preprocessor is started (similar to the -D option of 
   931 # gcc). The argument of the tag is a list of macros of the form: name 
   932 # or name=definition (no spaces). If the definition and the = are 
   933 # omitted =1 is assumed.
   934 
   935 PREDEFINED             = DOXYGEN
   936 
   937 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 
   938 # this tag can be used to specify a list of macro names that should be expanded. 
   939 # The macro definition that is found in the sources will be used. 
   940 # Use the PREDEFINED tag if you want to use a different macro definition.
   941 
   942 EXPAND_AS_DEFINED      = 
   943 
   944 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
   945 # doxygen's preprocessor will remove all function-like macros that are alone 
   946 # on a line, have an all uppercase name, and do not end with a semicolon. Such 
   947 # function macros are typically used for boiler-plate code, and will confuse the 
   948 # parser if not removed.
   949 
   950 SKIP_FUNCTION_MACROS   = YES
   951 
   952 #---------------------------------------------------------------------------
   953 # Configuration::additions related to external references   
   954 #---------------------------------------------------------------------------
   955 
   956 # The TAGFILES option can be used to specify one or more tagfiles. 
   957 # Optionally an initial location of the external documentation 
   958 # can be added for each tagfile. The format of a tag file without 
   959 # this location is as follows: 
   960 #   TAGFILES = file1 file2 ... 
   961 # Adding location for the tag files is done as follows: 
   962 #   TAGFILES = file1=loc1 "file2 = loc2" ... 
   963 # where "loc1" and "loc2" can be relative or absolute paths or 
   964 # URLs. If a location is present for each tag, the installdox tool 
   965 # does not have to be run to correct the links.
   966 # Note that each tag file must have a unique name
   967 # (where the name does NOT include the path)
   968 # If a tag file is not located in the directory in which doxygen 
   969 # is run, you must also specify the path to the tagfile here.
   970 
   971 TAGFILES               = 
   972 
   973 # When a file name is specified after GENERATE_TAGFILE, doxygen will create 
   974 # a tag file that is based on the input files it reads.
   975 
   976 GENERATE_TAGFILE       = 
   977 
   978 # If the ALLEXTERNALS tag is set to YES all external classes will be listed 
   979 # in the class index. If set to NO only the inherited external classes 
   980 # will be listed.
   981 
   982 ALLEXTERNALS           = NO
   983 
   984 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 
   985 # in the modules index. If set to NO, only the current project's groups will 
   986 # be listed.
   987 
   988 EXTERNAL_GROUPS        = YES
   989 
   990 # The PERL_PATH should be the absolute path and name of the perl script 
   991 # interpreter (i.e. the result of `which perl').
   992 
   993 PERL_PATH              = /usr/bin/perl
   994 
   995 #---------------------------------------------------------------------------
   996 # Configuration options related to the dot tool   
   997 #---------------------------------------------------------------------------
   998 
   999 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
  1000 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or 
  1001 # super classes. Setting the tag to NO turns the diagrams off. Note that this 
  1002 # option is superseded by the HAVE_DOT option below. This is only a fallback. It is 
  1003 # recommended to install and use dot, since it yields more powerful graphs.
  1004 
  1005 CLASS_DIAGRAMS         = YES
  1006 
  1007 # If set to YES, the inheritance and collaboration graphs will hide 
  1008 # inheritance and usage relations if the target is undocumented 
  1009 # or is not a class.
  1010 
  1011 HIDE_UNDOC_RELATIONS   = NO
  1012 
  1013 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 
  1014 # available from the path. This tool is part of Graphviz, a graph visualization 
  1015 # toolkit from AT&T and Lucent Bell Labs. The other options in this section 
  1016 # have no effect if this option is set to NO (the default)
  1017 
  1018 HAVE_DOT               = YES
  1019 
  1020 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 
  1021 # will generate a graph for each documented class showing the direct and 
  1022 # indirect inheritance relations. Setting this tag to YES will force the 
  1023 # the CLASS_DIAGRAMS tag to NO.
  1024 
  1025 CLASS_GRAPH            = YES
  1026 
  1027 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 
  1028 # will generate a graph for each documented class showing the direct and 
  1029 # indirect implementation dependencies (inheritance, containment, and 
  1030 # class references variables) of the class with other documented classes.
  1031 
  1032 COLLABORATION_GRAPH    = YES
  1033 
  1034 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and 
  1035 # collaboration diagrams in a style similar to the OMG's Unified Modeling 
  1036 # Language.
  1037 
  1038 UML_LOOK               = NO
  1039 
  1040 # If set to YES, the inheritance and collaboration graphs will show the 
  1041 # relations between templates and their instances.
  1042 
  1043 TEMPLATE_RELATIONS     = YES
  1044 
  1045 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 
  1046 # tags are set to YES then doxygen will generate a graph for each documented 
  1047 # file showing the direct and indirect include dependencies of the file with 
  1048 # other documented files.
  1049 
  1050 INCLUDE_GRAPH          = YES
  1051 
  1052 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 
  1053 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each 
  1054 # documented header file showing the documented files that directly or 
  1055 # indirectly include this file.
  1056 
  1057 INCLUDED_BY_GRAPH      = YES
  1058 
  1059 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will 
  1060 # generate a call dependency graph for every global function or class method. 
  1061 # Note that enabling this option will significantly increase the time of a run. 
  1062 # So in most cases it will be better to enable call graphs for selected 
  1063 # functions only using the \callgraph command.
  1064 
  1065 CALL_GRAPH             = YES
  1066 
  1067 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
  1068 # will graphical hierarchy of all classes instead of a textual one.
  1069 
  1070 GRAPHICAL_HIERARCHY    = YES
  1071 
  1072 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
  1073 # generated by dot. Possible values are png, jpg, or gif
  1074 # If left blank png will be used.
  1075 
  1076 DOT_IMAGE_FORMAT       = png
  1077 
  1078 # The tag DOT_PATH can be used to specify the path where the dot tool can be 
  1079 # found. If left blank, it is assumed the dot tool can be found on the path.
  1080 
  1081 DOT_PATH               = 
  1082 
  1083 # The DOTFILE_DIRS tag can be used to specify one or more directories that 
  1084 # contain dot files that are included in the documentation (see the 
  1085 # \dotfile command).
  1086 
  1087 DOTFILE_DIRS           = 
  1088 
  1089 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width 
  1090 # (in pixels) of the graphs generated by dot. If a graph becomes larger than 
  1091 # this value, doxygen will try to truncate the graph, so that it fits within 
  1092 # the specified constraint. Beware that most browsers cannot cope with very 
  1093 # large images.
  1094 
  1095 MAX_DOT_GRAPH_WIDTH    = 1024
  1096 
  1097 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height 
  1098 # (in pixels) of the graphs generated by dot. If a graph becomes larger than 
  1099 # this value, doxygen will try to truncate the graph, so that it fits within 
  1100 # the specified constraint. Beware that most browsers cannot cope with very 
  1101 # large images.
  1102 
  1103 MAX_DOT_GRAPH_HEIGHT   = 1024
  1104 
  1105 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 
  1106 # graphs generated by dot. A depth value of 3 means that only nodes reachable 
  1107 # from the root by following a path via at most 3 edges will be shown. Nodes that 
  1108 # lay further from the root node will be omitted. Note that setting this option to 
  1109 # 1 or 2 may greatly reduce the computation time needed for large code bases. Also 
  1110 # note that a graph may be further truncated if the graph's image dimensions are 
  1111 # not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT). 
  1112 # If 0 is used for the depth value (the default), the graph is not depth-constrained.
  1113 
  1114 MAX_DOT_GRAPH_DEPTH    = 0
  1115 
  1116 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
  1117 # generate a legend page explaining the meaning of the various boxes and 
  1118 # arrows in the dot generated graphs.
  1119 
  1120 GENERATE_LEGEND        = YES
  1121 
  1122 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 
  1123 # remove the intermediate dot files that are used to generate 
  1124 # the various graphs.
  1125 
  1126 DOT_CLEANUP            = YES
  1127 
  1128 #---------------------------------------------------------------------------
  1129 # Configuration::additions related to the search engine   
  1130 #---------------------------------------------------------------------------
  1131 
  1132 # The SEARCHENGINE tag specifies whether or not a search engine should be 
  1133 # used. If set to NO the values of all tags below this one will be ignored.
  1134 
  1135 SEARCHENGINE           = YES