1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/src/work/Doxyfile Sat May 08 15:56:00 2004 +0000
1.3 @@ -0,0 +1,1123 @@
1.4 +# Doxyfile 1.3.6
1.5 +
1.6 +# This file describes the settings to be used by the documentation system
1.7 +# doxygen (www.doxygen.org) for a project
1.8 +#
1.9 +# All text after a hash (#) is considered a comment and will be ignored
1.10 +# The format is:
1.11 +# TAG = value [value, ...]
1.12 +# For lists items can also be appended using:
1.13 +# TAG += value [value, ...]
1.14 +# Values that contain spaces should be placed between quotes (" ")
1.15 +
1.16 +#---------------------------------------------------------------------------
1.17 +# Project related configuration options
1.18 +#---------------------------------------------------------------------------
1.19 +
1.20 +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
1.21 +# by quotes) that should identify the project.
1.22 +
1.23 +PROJECT_NAME = HugoLib
1.24 +
1.25 +# The PROJECT_NUMBER tag can be used to enter a project or revision number.
1.26 +# This could be handy for archiving the generated documentation or
1.27 +# if some version control system is used.
1.28 +
1.29 +PROJECT_NUMBER = 0.1
1.30 +
1.31 +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
1.32 +# base path where the generated documentation will be put.
1.33 +# If a relative path is entered, it will be relative to the location
1.34 +# where doxygen was started. If left blank the current directory will be used.
1.35 +
1.36 +OUTPUT_DIRECTORY =
1.37 +
1.38 +# The OUTPUT_LANGUAGE tag is used to specify the language in which all
1.39 +# documentation generated by doxygen is written. Doxygen will use this
1.40 +# information to generate all constant output in the proper language.
1.41 +# The default language is English, other supported languages are:
1.42 +# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch,
1.43 +# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en
1.44 +# (Japanese with English messages), Korean, Korean-en, Norwegian, Polish, Portuguese,
1.45 +# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
1.46 +
1.47 +OUTPUT_LANGUAGE = English
1.48 +
1.49 +# This tag can be used to specify the encoding used in the generated output.
1.50 +# The encoding is not always determined by the language that is chosen,
1.51 +# but also whether or not the output is meant for Windows or non-Windows users.
1.52 +# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
1.53 +# forces the Windows encoding (this is the default for the Windows binary),
1.54 +# whereas setting the tag to NO uses a Unix-style encoding (the default for
1.55 +# all platforms other than Windows).
1.56 +
1.57 +USE_WINDOWS_ENCODING = NO
1.58 +
1.59 +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
1.60 +# include brief member descriptions after the members that are listed in
1.61 +# the file and class documentation (similar to JavaDoc).
1.62 +# Set to NO to disable this.
1.63 +
1.64 +BRIEF_MEMBER_DESC = YES
1.65 +
1.66 +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
1.67 +# the brief description of a member or function before the detailed description.
1.68 +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
1.69 +# brief descriptions will be completely suppressed.
1.70 +
1.71 +REPEAT_BRIEF = NO
1.72 +
1.73 +# This tag implements a quasi-intelligent brief description abbreviator
1.74 +# that is used to form the text in various listings. Each string
1.75 +# in this list, if found as the leading text of the brief description, will be
1.76 +# stripped from the text and the result after processing the whole list, is used
1.77 +# as the annotated text. Otherwise, the brief description is used as-is. If left
1.78 +# blank, the following values are used ("$name" is automatically replaced with the
1.79 +# name of the entity): "The $name class" "The $name widget" "The $name file"
1.80 +# "is" "provides" "specifies" "contains" "represents" "a" "an" "the"
1.81 +
1.82 +ABBREVIATE_BRIEF =
1.83 +
1.84 +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
1.85 +# Doxygen will generate a detailed section even if there is only a brief
1.86 +# description.
1.87 +
1.88 +ALWAYS_DETAILED_SEC = NO
1.89 +
1.90 +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited
1.91 +# members of a class in the documentation of that class as if those members were
1.92 +# ordinary class members. Constructors, destructors and assignment operators of
1.93 +# the base classes will not be shown.
1.94 +
1.95 +INLINE_INHERITED_MEMB = NO
1.96 +
1.97 +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
1.98 +# path before files name in the file list and in the header files. If set
1.99 +# to NO the shortest path that makes the file name unique will be used.
1.100 +
1.101 +FULL_PATH_NAMES = NO
1.102 +
1.103 +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
1.104 +# can be used to strip a user-defined part of the path. Stripping is
1.105 +# only done if one of the specified strings matches the left-hand part of
1.106 +# the path. It is allowed to use relative paths in the argument list.
1.107 +# If left blank the directory from which doxygen is run is used as the
1.108 +# path to strip.
1.109 +
1.110 +STRIP_FROM_PATH =
1.111 +
1.112 +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
1.113 +# (but less readable) file names. This can be useful is your file systems
1.114 +# doesn't support long names like on DOS, Mac, or CD-ROM.
1.115 +
1.116 +SHORT_NAMES = NO
1.117 +
1.118 +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
1.119 +# will interpret the first line (until the first dot) of a JavaDoc-style
1.120 +# comment as the brief description. If set to NO, the JavaDoc
1.121 +# comments will behave just like the Qt-style comments (thus requiring an
1.122 +# explicit @brief command for a brief description.
1.123 +
1.124 +JAVADOC_AUTOBRIEF = NO
1.125 +
1.126 +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
1.127 +# treat a multi-line C++ special comment block (i.e. a block of //! or ///
1.128 +# comments) as a brief description. This used to be the default behaviour.
1.129 +# The new default is to treat a multi-line C++ comment block as a detailed
1.130 +# description. Set this tag to YES if you prefer the old behaviour instead.
1.131 +
1.132 +MULTILINE_CPP_IS_BRIEF = NO
1.133 +
1.134 +# If the DETAILS_AT_TOP tag is set to YES then Doxygen
1.135 +# will output the detailed description near the top, like JavaDoc.
1.136 +# If set to NO, the detailed description appears after the member
1.137 +# documentation.
1.138 +
1.139 +DETAILS_AT_TOP = YES
1.140 +
1.141 +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
1.142 +# member inherits the documentation from any documented member that it
1.143 +# re-implements.
1.144 +
1.145 +INHERIT_DOCS = NO
1.146 +
1.147 +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
1.148 +# tag is set to YES, then doxygen will reuse the documentation of the first
1.149 +# member in the group (if any) for the other members of the group. By default
1.150 +# all members of a group must be documented explicitly.
1.151 +
1.152 +DISTRIBUTE_GROUP_DOC = NO
1.153 +
1.154 +# The TAB_SIZE tag can be used to set the number of spaces in a tab.
1.155 +# Doxygen uses this value to replace tabs by spaces in code fragments.
1.156 +
1.157 +TAB_SIZE = 8
1.158 +
1.159 +# This tag can be used to specify a number of aliases that acts
1.160 +# as commands in the documentation. An alias has the form "name=value".
1.161 +# For example adding "sideeffect=\par Side Effects:\n" will allow you to
1.162 +# put the command \sideeffect (or @sideeffect) in the documentation, which
1.163 +# will result in a user-defined paragraph with heading "Side Effects:".
1.164 +# You can put \n's in the value part of an alias to insert newlines.
1.165 +
1.166 +ALIASES =
1.167 +
1.168 +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
1.169 +# only. Doxygen will then generate output that is more tailored for C.
1.170 +# For instance, some of the names that are used will be different. The list
1.171 +# of all members will be omitted, etc.
1.172 +
1.173 +OPTIMIZE_OUTPUT_FOR_C = NO
1.174 +
1.175 +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
1.176 +# only. Doxygen will then generate output that is more tailored for Java.
1.177 +# For instance, namespaces will be presented as packages, qualified scopes
1.178 +# will look different, etc.
1.179 +
1.180 +OPTIMIZE_OUTPUT_JAVA = NO
1.181 +
1.182 +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
1.183 +# the same type (for instance a group of public functions) to be put as a
1.184 +# subgroup of that type (e.g. under the Public Functions section). Set it to
1.185 +# NO to prevent subgrouping. Alternatively, this can be done per class using
1.186 +# the \nosubgrouping command.
1.187 +
1.188 +SUBGROUPING = YES
1.189 +
1.190 +#---------------------------------------------------------------------------
1.191 +# Build related configuration options
1.192 +#---------------------------------------------------------------------------
1.193 +
1.194 +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
1.195 +# documentation are documented, even if no documentation was available.
1.196 +# Private class members and static file members will be hidden unless
1.197 +# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
1.198 +
1.199 +EXTRACT_ALL = NO
1.200 +
1.201 +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
1.202 +# will be included in the documentation.
1.203 +
1.204 +EXTRACT_PRIVATE = NO
1.205 +
1.206 +# If the EXTRACT_STATIC tag is set to YES all static members of a file
1.207 +# will be included in the documentation.
1.208 +
1.209 +EXTRACT_STATIC = NO
1.210 +
1.211 +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
1.212 +# defined locally in source files will be included in the documentation.
1.213 +# If set to NO only classes defined in header files are included.
1.214 +
1.215 +EXTRACT_LOCAL_CLASSES = YES
1.216 +
1.217 +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
1.218 +# undocumented members of documented classes, files or namespaces.
1.219 +# If set to NO (the default) these members will be included in the
1.220 +# various overviews, but no documentation section is generated.
1.221 +# This option has no effect if EXTRACT_ALL is enabled.
1.222 +
1.223 +HIDE_UNDOC_MEMBERS = YES
1.224 +
1.225 +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
1.226 +# undocumented classes that are normally visible in the class hierarchy.
1.227 +# If set to NO (the default) these classes will be included in the various
1.228 +# overviews. This option has no effect if EXTRACT_ALL is enabled.
1.229 +
1.230 +HIDE_UNDOC_CLASSES = YES
1.231 +
1.232 +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
1.233 +# friend (class|struct|union) declarations.
1.234 +# If set to NO (the default) these declarations will be included in the
1.235 +# documentation.
1.236 +
1.237 +HIDE_FRIEND_COMPOUNDS = NO
1.238 +
1.239 +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
1.240 +# documentation blocks found inside the body of a function.
1.241 +# If set to NO (the default) these blocks will be appended to the
1.242 +# function's detailed documentation block.
1.243 +
1.244 +HIDE_IN_BODY_DOCS = NO
1.245 +
1.246 +# The INTERNAL_DOCS tag determines if documentation
1.247 +# that is typed after a \internal command is included. If the tag is set
1.248 +# to NO (the default) then the documentation will be excluded.
1.249 +# Set it to YES to include the internal documentation.
1.250 +
1.251 +INTERNAL_DOCS = NO
1.252 +
1.253 +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
1.254 +# file names in lower-case letters. If set to YES upper-case letters are also
1.255 +# allowed. This is useful if you have classes or files whose names only differ
1.256 +# in case and if your file system supports case sensitive file names. Windows
1.257 +# users are advised to set this option to NO.
1.258 +
1.259 +CASE_SENSE_NAMES = YES
1.260 +
1.261 +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
1.262 +# will show members with their full class and namespace scopes in the
1.263 +# documentation. If set to YES the scope will be hidden.
1.264 +
1.265 +HIDE_SCOPE_NAMES = YES
1.266 +
1.267 +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
1.268 +# will put a list of the files that are included by a file in the documentation
1.269 +# of that file.
1.270 +
1.271 +SHOW_INCLUDE_FILES = YES
1.272 +
1.273 +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
1.274 +# is inserted in the documentation for inline members.
1.275 +
1.276 +INLINE_INFO = YES
1.277 +
1.278 +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
1.279 +# will sort the (detailed) documentation of file and class members
1.280 +# alphabetically by member name. If set to NO the members will appear in
1.281 +# declaration order.
1.282 +
1.283 +SORT_MEMBER_DOCS = NO
1.284 +
1.285 +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
1.286 +# brief documentation of file, namespace and class members alphabetically
1.287 +# by member name. If set to NO (the default) the members will appear in
1.288 +# declaration order.
1.289 +
1.290 +SORT_BRIEF_DOCS = NO
1.291 +
1.292 +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
1.293 +# sorted by fully-qualified names, including namespaces. If set to
1.294 +# NO (the default), the class list will be sorted only by class name,
1.295 +# not including the namespace part.
1.296 +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
1.297 +# Note: This option applies only to the class list, not to the
1.298 +# alphabetical list.
1.299 +
1.300 +SORT_BY_SCOPE_NAME = NO
1.301 +
1.302 +# The GENERATE_TODOLIST tag can be used to enable (YES) or
1.303 +# disable (NO) the todo list. This list is created by putting \todo
1.304 +# commands in the documentation.
1.305 +
1.306 +GENERATE_TODOLIST = YES
1.307 +
1.308 +# The GENERATE_TESTLIST tag can be used to enable (YES) or
1.309 +# disable (NO) the test list. This list is created by putting \test
1.310 +# commands in the documentation.
1.311 +
1.312 +GENERATE_TESTLIST = YES
1.313 +
1.314 +# The GENERATE_BUGLIST tag can be used to enable (YES) or
1.315 +# disable (NO) the bug list. This list is created by putting \bug
1.316 +# commands in the documentation.
1.317 +
1.318 +GENERATE_BUGLIST = YES
1.319 +
1.320 +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
1.321 +# disable (NO) the deprecated list. This list is created by putting
1.322 +# \deprecated commands in the documentation.
1.323 +
1.324 +GENERATE_DEPRECATEDLIST= YES
1.325 +
1.326 +# The ENABLED_SECTIONS tag can be used to enable conditional
1.327 +# documentation sections, marked by \if sectionname ... \endif.
1.328 +
1.329 +ENABLED_SECTIONS =
1.330 +
1.331 +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
1.332 +# the initial value of a variable or define consists of for it to appear in
1.333 +# the documentation. If the initializer consists of more lines than specified
1.334 +# here it will be hidden. Use a value of 0 to hide initializers completely.
1.335 +# The appearance of the initializer of individual variables and defines in the
1.336 +# documentation can be controlled using \showinitializer or \hideinitializer
1.337 +# command in the documentation regardless of this setting.
1.338 +
1.339 +MAX_INITIALIZER_LINES = 30
1.340 +
1.341 +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
1.342 +# at the bottom of the documentation of classes and structs. If set to YES the
1.343 +# list will mention the files that were used to generate the documentation.
1.344 +
1.345 +SHOW_USED_FILES = YES
1.346 +
1.347 +#---------------------------------------------------------------------------
1.348 +# configuration options related to warning and progress messages
1.349 +#---------------------------------------------------------------------------
1.350 +
1.351 +# The QUIET tag can be used to turn on/off the messages that are generated
1.352 +# by doxygen. Possible values are YES and NO. If left blank NO is used.
1.353 +
1.354 +QUIET = NO
1.355 +
1.356 +# The WARNINGS tag can be used to turn on/off the warning messages that are
1.357 +# generated by doxygen. Possible values are YES and NO. If left blank
1.358 +# NO is used.
1.359 +
1.360 +WARNINGS = YES
1.361 +
1.362 +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
1.363 +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
1.364 +# automatically be disabled.
1.365 +
1.366 +WARN_IF_UNDOCUMENTED = YES
1.367 +
1.368 +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
1.369 +# potential errors in the documentation, such as not documenting some
1.370 +# parameters in a documented function, or documenting parameters that
1.371 +# don't exist or using markup commands wrongly.
1.372 +
1.373 +WARN_IF_DOC_ERROR = YES
1.374 +
1.375 +# The WARN_FORMAT tag determines the format of the warning messages that
1.376 +# doxygen can produce. The string should contain the $file, $line, and $text
1.377 +# tags, which will be replaced by the file and line number from which the
1.378 +# warning originated and the warning text.
1.379 +
1.380 +WARN_FORMAT = "$file:$line: $text"
1.381 +
1.382 +# The WARN_LOGFILE tag can be used to specify a file to which warning
1.383 +# and error messages should be written. If left blank the output is written
1.384 +# to stderr.
1.385 +
1.386 +WARN_LOGFILE = doxygen.log
1.387 +
1.388 +#---------------------------------------------------------------------------
1.389 +# configuration options related to the input files
1.390 +#---------------------------------------------------------------------------
1.391 +
1.392 +# The INPUT tag can be used to specify the files and/or directories that contain
1.393 +# documented source files. You may enter file names like "myfile.cpp" or
1.394 +# directories like "/usr/src/myproject". Separate the files or directories
1.395 +# with spaces.
1.396 +
1.397 +INPUT = ../hugo \
1.398 + ../hugo/skeletons \
1.399 + ../test/test_tools.h \
1.400 + athos/minlengthpaths.h \
1.401 + klao/path.h \
1.402 + jacint/max_flow.h \
1.403 + jacint/max_matching.h
1.404 +
1.405 +# If the value of the INPUT tag contains directories, you can use the
1.406 +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
1.407 +# and *.h) to filter out the source-files in the directories. If left
1.408 +# blank the following patterns are tested:
1.409 +# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
1.410 +# *.h++ *.idl *.odl *.cs *.php *.php3 *.inc
1.411 +
1.412 +FILE_PATTERNS =
1.413 +
1.414 +# The RECURSIVE tag can be used to turn specify whether or not subdirectories
1.415 +# should be searched for input files as well. Possible values are YES and NO.
1.416 +# If left blank NO is used.
1.417 +
1.418 +RECURSIVE = NO
1.419 +
1.420 +# The EXCLUDE tag can be used to specify files and/or directories that should
1.421 +# excluded from the INPUT source files. This way you can easily exclude a
1.422 +# subdirectory from a directory tree whose root is specified with the INPUT tag.
1.423 +
1.424 +EXCLUDE =
1.425 +
1.426 +# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
1.427 +# that are symbolic links (a Unix filesystem feature) are excluded from the input.
1.428 +
1.429 +EXCLUDE_SYMLINKS = NO
1.430 +
1.431 +# If the value of the INPUT tag contains directories, you can use the
1.432 +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
1.433 +# certain files from those directories.
1.434 +
1.435 +EXCLUDE_PATTERNS =
1.436 +
1.437 +# The EXAMPLE_PATH tag can be used to specify one or more files or
1.438 +# directories that contain example code fragments that are included (see
1.439 +# the \include command).
1.440 +
1.441 +EXAMPLE_PATH =
1.442 +
1.443 +# If the value of the EXAMPLE_PATH tag contains directories, you can use the
1.444 +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
1.445 +# and *.h) to filter out the source-files in the directories. If left
1.446 +# blank all files are included.
1.447 +
1.448 +EXAMPLE_PATTERNS =
1.449 +
1.450 +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
1.451 +# searched for input files to be used with the \include or \dontinclude
1.452 +# commands irrespective of the value of the RECURSIVE tag.
1.453 +# Possible values are YES and NO. If left blank NO is used.
1.454 +
1.455 +EXAMPLE_RECURSIVE = NO
1.456 +
1.457 +# The IMAGE_PATH tag can be used to specify one or more files or
1.458 +# directories that contain image that are included in the documentation (see
1.459 +# the \image command).
1.460 +
1.461 +IMAGE_PATH =
1.462 +
1.463 +# The INPUT_FILTER tag can be used to specify a program that doxygen should
1.464 +# invoke to filter for each input file. Doxygen will invoke the filter program
1.465 +# by executing (via popen()) the command <filter> <input-file>, where <filter>
1.466 +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
1.467 +# input file. Doxygen will then use the output that the filter program writes
1.468 +# to standard output.
1.469 +
1.470 +INPUT_FILTER =
1.471 +
1.472 +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
1.473 +# INPUT_FILTER) will be used to filter the input files when producing source
1.474 +# files to browse (i.e. when SOURCE_BROWSER is set to YES).
1.475 +
1.476 +FILTER_SOURCE_FILES = NO
1.477 +
1.478 +#---------------------------------------------------------------------------
1.479 +# configuration options related to source browsing
1.480 +#---------------------------------------------------------------------------
1.481 +
1.482 +# If the SOURCE_BROWSER tag is set to YES then a list of source files will
1.483 +# be generated. Documented entities will be cross-referenced with these sources.
1.484 +# Note: To get rid of all source code in the generated output, make sure also
1.485 +# VERBATIM_HEADERS is set to NO.
1.486 +
1.487 +SOURCE_BROWSER = YES
1.488 +
1.489 +# Setting the INLINE_SOURCES tag to YES will include the body
1.490 +# of functions and classes directly in the documentation.
1.491 +
1.492 +INLINE_SOURCES = NO
1.493 +
1.494 +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
1.495 +# doxygen to hide any special comment blocks from generated source code
1.496 +# fragments. Normal C and C++ comments will always remain visible.
1.497 +
1.498 +STRIP_CODE_COMMENTS = YES
1.499 +
1.500 +# If the REFERENCED_BY_RELATION tag is set to YES (the default)
1.501 +# then for each documented function all documented
1.502 +# functions referencing it will be listed.
1.503 +
1.504 +REFERENCED_BY_RELATION = YES
1.505 +
1.506 +# If the REFERENCES_RELATION tag is set to YES (the default)
1.507 +# then for each documented function all documented entities
1.508 +# called/used by that function will be listed.
1.509 +
1.510 +REFERENCES_RELATION = YES
1.511 +
1.512 +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
1.513 +# will generate a verbatim copy of the header file for each class for
1.514 +# which an include is specified. Set to NO to disable this.
1.515 +
1.516 +VERBATIM_HEADERS = YES
1.517 +
1.518 +#---------------------------------------------------------------------------
1.519 +# configuration options related to the alphabetical class index
1.520 +#---------------------------------------------------------------------------
1.521 +
1.522 +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
1.523 +# of all compounds will be generated. Enable this if the project
1.524 +# contains a lot of classes, structs, unions or interfaces.
1.525 +
1.526 +ALPHABETICAL_INDEX = YES
1.527 +
1.528 +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
1.529 +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
1.530 +# in which this list will be split (can be a number in the range [1..20])
1.531 +
1.532 +COLS_IN_ALPHA_INDEX = 2
1.533 +
1.534 +# In case all classes in a project start with a common prefix, all
1.535 +# classes will be put under the same header in the alphabetical index.
1.536 +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
1.537 +# should be ignored while generating the index headers.
1.538 +
1.539 +IGNORE_PREFIX =
1.540 +
1.541 +#---------------------------------------------------------------------------
1.542 +# configuration options related to the HTML output
1.543 +#---------------------------------------------------------------------------
1.544 +
1.545 +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
1.546 +# generate HTML output.
1.547 +
1.548 +GENERATE_HTML = YES
1.549 +
1.550 +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
1.551 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.552 +# put in front of it. If left blank `html' will be used as the default path.
1.553 +
1.554 +HTML_OUTPUT = html
1.555 +
1.556 +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
1.557 +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
1.558 +# doxygen will generate files with .html extension.
1.559 +
1.560 +HTML_FILE_EXTENSION = .html
1.561 +
1.562 +# The HTML_HEADER tag can be used to specify a personal HTML header for
1.563 +# each generated HTML page. If it is left blank doxygen will generate a
1.564 +# standard header.
1.565 +
1.566 +HTML_HEADER =
1.567 +
1.568 +# The HTML_FOOTER tag can be used to specify a personal HTML footer for
1.569 +# each generated HTML page. If it is left blank doxygen will generate a
1.570 +# standard footer.
1.571 +
1.572 +HTML_FOOTER =
1.573 +
1.574 +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
1.575 +# style sheet that is used by each HTML page. It can be used to
1.576 +# fine-tune the look of the HTML output. If the tag is left blank doxygen
1.577 +# will generate a default style sheet. Note that doxygen will try to copy
1.578 +# the style sheet file to the HTML output directory, so don't put your own
1.579 +# stylesheet in the HTML output directory as well, or it will be erased!
1.580 +
1.581 +HTML_STYLESHEET =
1.582 +
1.583 +# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
1.584 +# files or namespaces will be aligned in HTML using tables. If set to
1.585 +# NO a bullet list will be used.
1.586 +
1.587 +HTML_ALIGN_MEMBERS = YES
1.588 +
1.589 +# If the GENERATE_HTMLHELP tag is set to YES, additional index files
1.590 +# will be generated that can be used as input for tools like the
1.591 +# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
1.592 +# of the generated HTML documentation.
1.593 +
1.594 +GENERATE_HTMLHELP = NO
1.595 +
1.596 +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
1.597 +# be used to specify the file name of the resulting .chm file. You
1.598 +# can add a path in front of the file if the result should not be
1.599 +# written to the html output directory.
1.600 +
1.601 +CHM_FILE =
1.602 +
1.603 +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
1.604 +# be used to specify the location (absolute path including file name) of
1.605 +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
1.606 +# the HTML help compiler on the generated index.hhp.
1.607 +
1.608 +HHC_LOCATION =
1.609 +
1.610 +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
1.611 +# controls if a separate .chi index file is generated (YES) or that
1.612 +# it should be included in the master .chm file (NO).
1.613 +
1.614 +GENERATE_CHI = NO
1.615 +
1.616 +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
1.617 +# controls whether a binary table of contents is generated (YES) or a
1.618 +# normal table of contents (NO) in the .chm file.
1.619 +
1.620 +BINARY_TOC = NO
1.621 +
1.622 +# The TOC_EXPAND flag can be set to YES to add extra items for group members
1.623 +# to the contents of the HTML help documentation and to the tree view.
1.624 +
1.625 +TOC_EXPAND = NO
1.626 +
1.627 +# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
1.628 +# top of each HTML page. The value NO (the default) enables the index and
1.629 +# the value YES disables it.
1.630 +
1.631 +DISABLE_INDEX = NO
1.632 +
1.633 +# This tag can be used to set the number of enum values (range [1..20])
1.634 +# that doxygen will group on one line in the generated HTML documentation.
1.635 +
1.636 +ENUM_VALUES_PER_LINE = 4
1.637 +
1.638 +# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
1.639 +# generated containing a tree-like index structure (just like the one that
1.640 +# is generated for HTML Help). For this to work a browser that supports
1.641 +# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
1.642 +# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
1.643 +# probably better off using the HTML help feature.
1.644 +
1.645 +GENERATE_TREEVIEW = YES
1.646 +
1.647 +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
1.648 +# used to set the initial width (in pixels) of the frame in which the tree
1.649 +# is shown.
1.650 +
1.651 +TREEVIEW_WIDTH = 250
1.652 +
1.653 +#---------------------------------------------------------------------------
1.654 +# configuration options related to the LaTeX output
1.655 +#---------------------------------------------------------------------------
1.656 +
1.657 +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1.658 +# generate Latex output.
1.659 +
1.660 +GENERATE_LATEX = NO
1.661 +
1.662 +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1.663 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.664 +# put in front of it. If left blank `latex' will be used as the default path.
1.665 +
1.666 +LATEX_OUTPUT = latex
1.667 +
1.668 +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1.669 +# invoked. If left blank `latex' will be used as the default command name.
1.670 +
1.671 +LATEX_CMD_NAME = latex
1.672 +
1.673 +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1.674 +# generate index for LaTeX. If left blank `makeindex' will be used as the
1.675 +# default command name.
1.676 +
1.677 +MAKEINDEX_CMD_NAME = makeindex
1.678 +
1.679 +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1.680 +# LaTeX documents. This may be useful for small projects and may help to
1.681 +# save some trees in general.
1.682 +
1.683 +COMPACT_LATEX = YES
1.684 +
1.685 +# The PAPER_TYPE tag can be used to set the paper type that is used
1.686 +# by the printer. Possible values are: a4, a4wide, letter, legal and
1.687 +# executive. If left blank a4wide will be used.
1.688 +
1.689 +PAPER_TYPE = a4wide
1.690 +
1.691 +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1.692 +# packages that should be included in the LaTeX output.
1.693 +
1.694 +EXTRA_PACKAGES =
1.695 +
1.696 +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1.697 +# the generated latex document. The header should contain everything until
1.698 +# the first chapter. If it is left blank doxygen will generate a
1.699 +# standard header. Notice: only use this tag if you know what you are doing!
1.700 +
1.701 +LATEX_HEADER =
1.702 +
1.703 +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1.704 +# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1.705 +# contain links (just like the HTML output) instead of page references
1.706 +# This makes the output suitable for online browsing using a pdf viewer.
1.707 +
1.708 +PDF_HYPERLINKS = YES
1.709 +
1.710 +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1.711 +# plain latex in the generated Makefile. Set this option to YES to get a
1.712 +# higher quality PDF documentation.
1.713 +
1.714 +USE_PDFLATEX = YES
1.715 +
1.716 +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1.717 +# command to the generated LaTeX files. This will instruct LaTeX to keep
1.718 +# running if errors occur, instead of asking the user for help.
1.719 +# This option is also used when generating formulas in HTML.
1.720 +
1.721 +LATEX_BATCHMODE = NO
1.722 +
1.723 +# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1.724 +# include the index chapters (such as File Index, Compound Index, etc.)
1.725 +# in the output.
1.726 +
1.727 +LATEX_HIDE_INDICES = NO
1.728 +
1.729 +#---------------------------------------------------------------------------
1.730 +# configuration options related to the RTF output
1.731 +#---------------------------------------------------------------------------
1.732 +
1.733 +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1.734 +# The RTF output is optimized for Word 97 and may not look very pretty with
1.735 +# other RTF readers or editors.
1.736 +
1.737 +GENERATE_RTF = NO
1.738 +
1.739 +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1.740 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.741 +# put in front of it. If left blank `rtf' will be used as the default path.
1.742 +
1.743 +RTF_OUTPUT = rtf
1.744 +
1.745 +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1.746 +# RTF documents. This may be useful for small projects and may help to
1.747 +# save some trees in general.
1.748 +
1.749 +COMPACT_RTF = NO
1.750 +
1.751 +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1.752 +# will contain hyperlink fields. The RTF file will
1.753 +# contain links (just like the HTML output) instead of page references.
1.754 +# This makes the output suitable for online browsing using WORD or other
1.755 +# programs which support those fields.
1.756 +# Note: wordpad (write) and others do not support links.
1.757 +
1.758 +RTF_HYPERLINKS = NO
1.759 +
1.760 +# Load stylesheet definitions from file. Syntax is similar to doxygen's
1.761 +# config file, i.e. a series of assignments. You only have to provide
1.762 +# replacements, missing definitions are set to their default value.
1.763 +
1.764 +RTF_STYLESHEET_FILE =
1.765 +
1.766 +# Set optional variables used in the generation of an rtf document.
1.767 +# Syntax is similar to doxygen's config file.
1.768 +
1.769 +RTF_EXTENSIONS_FILE =
1.770 +
1.771 +#---------------------------------------------------------------------------
1.772 +# configuration options related to the man page output
1.773 +#---------------------------------------------------------------------------
1.774 +
1.775 +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1.776 +# generate man pages
1.777 +
1.778 +GENERATE_MAN = NO
1.779 +
1.780 +# The MAN_OUTPUT tag is used to specify where the man pages will be put.
1.781 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.782 +# put in front of it. If left blank `man' will be used as the default path.
1.783 +
1.784 +MAN_OUTPUT = man
1.785 +
1.786 +# The MAN_EXTENSION tag determines the extension that is added to
1.787 +# the generated man pages (default is the subroutine's section .3)
1.788 +
1.789 +MAN_EXTENSION = .3
1.790 +
1.791 +# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1.792 +# then it will generate one additional man file for each entity
1.793 +# documented in the real man page(s). These additional files
1.794 +# only source the real man page, but without them the man command
1.795 +# would be unable to find the correct page. The default is NO.
1.796 +
1.797 +MAN_LINKS = NO
1.798 +
1.799 +#---------------------------------------------------------------------------
1.800 +# configuration options related to the XML output
1.801 +#---------------------------------------------------------------------------
1.802 +
1.803 +# If the GENERATE_XML tag is set to YES Doxygen will
1.804 +# generate an XML file that captures the structure of
1.805 +# the code including all documentation.
1.806 +
1.807 +GENERATE_XML = NO
1.808 +
1.809 +# The XML_OUTPUT tag is used to specify where the XML pages will be put.
1.810 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.811 +# put in front of it. If left blank `xml' will be used as the default path.
1.812 +
1.813 +XML_OUTPUT = xml
1.814 +
1.815 +# The XML_SCHEMA tag can be used to specify an XML schema,
1.816 +# which can be used by a validating XML parser to check the
1.817 +# syntax of the XML files.
1.818 +
1.819 +XML_SCHEMA =
1.820 +
1.821 +# The XML_DTD tag can be used to specify an XML DTD,
1.822 +# which can be used by a validating XML parser to check the
1.823 +# syntax of the XML files.
1.824 +
1.825 +XML_DTD =
1.826 +
1.827 +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1.828 +# dump the program listings (including syntax highlighting
1.829 +# and cross-referencing information) to the XML output. Note that
1.830 +# enabling this will significantly increase the size of the XML output.
1.831 +
1.832 +XML_PROGRAMLISTING = YES
1.833 +
1.834 +#---------------------------------------------------------------------------
1.835 +# configuration options for the AutoGen Definitions output
1.836 +#---------------------------------------------------------------------------
1.837 +
1.838 +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1.839 +# generate an AutoGen Definitions (see autogen.sf.net) file
1.840 +# that captures the structure of the code including all
1.841 +# documentation. Note that this feature is still experimental
1.842 +# and incomplete at the moment.
1.843 +
1.844 +GENERATE_AUTOGEN_DEF = NO
1.845 +
1.846 +#---------------------------------------------------------------------------
1.847 +# configuration options related to the Perl module output
1.848 +#---------------------------------------------------------------------------
1.849 +
1.850 +# If the GENERATE_PERLMOD tag is set to YES Doxygen will
1.851 +# generate a Perl module file that captures the structure of
1.852 +# the code including all documentation. Note that this
1.853 +# feature is still experimental and incomplete at the
1.854 +# moment.
1.855 +
1.856 +GENERATE_PERLMOD = NO
1.857 +
1.858 +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1.859 +# the necessary Makefile rules, Perl scripts and LaTeX code to be able
1.860 +# to generate PDF and DVI output from the Perl module output.
1.861 +
1.862 +PERLMOD_LATEX = NO
1.863 +
1.864 +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1.865 +# nicely formatted so it can be parsed by a human reader. This is useful
1.866 +# if you want to understand what is going on. On the other hand, if this
1.867 +# tag is set to NO the size of the Perl module output will be much smaller
1.868 +# and Perl will parse it just the same.
1.869 +
1.870 +PERLMOD_PRETTY = YES
1.871 +
1.872 +# The names of the make variables in the generated doxyrules.make file
1.873 +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1.874 +# This is useful so different doxyrules.make files included by the same
1.875 +# Makefile don't overwrite each other's variables.
1.876 +
1.877 +PERLMOD_MAKEVAR_PREFIX =
1.878 +
1.879 +#---------------------------------------------------------------------------
1.880 +# Configuration options related to the preprocessor
1.881 +#---------------------------------------------------------------------------
1.882 +
1.883 +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1.884 +# evaluate all C-preprocessor directives found in the sources and include
1.885 +# files.
1.886 +
1.887 +ENABLE_PREPROCESSING = YES
1.888 +
1.889 +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1.890 +# names in the source code. If set to NO (the default) only conditional
1.891 +# compilation will be performed. Macro expansion can be done in a controlled
1.892 +# way by setting EXPAND_ONLY_PREDEF to YES.
1.893 +
1.894 +MACRO_EXPANSION = NO
1.895 +
1.896 +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1.897 +# then the macro expansion is limited to the macros specified with the
1.898 +# PREDEFINED and EXPAND_AS_PREDEFINED tags.
1.899 +
1.900 +EXPAND_ONLY_PREDEF = NO
1.901 +
1.902 +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1.903 +# in the INCLUDE_PATH (see below) will be search if a #include is found.
1.904 +
1.905 +SEARCH_INCLUDES = YES
1.906 +
1.907 +# The INCLUDE_PATH tag can be used to specify one or more directories that
1.908 +# contain include files that are not input files but should be processed by
1.909 +# the preprocessor.
1.910 +
1.911 +INCLUDE_PATH =
1.912 +
1.913 +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1.914 +# patterns (like *.h and *.hpp) to filter out the header-files in the
1.915 +# directories. If left blank, the patterns specified with FILE_PATTERNS will
1.916 +# be used.
1.917 +
1.918 +INCLUDE_FILE_PATTERNS =
1.919 +
1.920 +# The PREDEFINED tag can be used to specify one or more macro names that
1.921 +# are defined before the preprocessor is started (similar to the -D option of
1.922 +# gcc). The argument of the tag is a list of macros of the form: name
1.923 +# or name=definition (no spaces). If the definition and the = are
1.924 +# omitted =1 is assumed.
1.925 +
1.926 +PREDEFINED = DOXYGEN
1.927 +
1.928 +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1.929 +# this tag can be used to specify a list of macro names that should be expanded.
1.930 +# The macro definition that is found in the sources will be used.
1.931 +# Use the PREDEFINED tag if you want to use a different macro definition.
1.932 +
1.933 +EXPAND_AS_DEFINED =
1.934 +
1.935 +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1.936 +# doxygen's preprocessor will remove all function-like macros that are alone
1.937 +# on a line, have an all uppercase name, and do not end with a semicolon. Such
1.938 +# function macros are typically used for boiler-plate code, and will confuse the
1.939 +# parser if not removed.
1.940 +
1.941 +SKIP_FUNCTION_MACROS = YES
1.942 +
1.943 +#---------------------------------------------------------------------------
1.944 +# Configuration::additions related to external references
1.945 +#---------------------------------------------------------------------------
1.946 +
1.947 +# The TAGFILES option can be used to specify one or more tagfiles.
1.948 +# Optionally an initial location of the external documentation
1.949 +# can be added for each tagfile. The format of a tag file without
1.950 +# this location is as follows:
1.951 +# TAGFILES = file1 file2 ...
1.952 +# Adding location for the tag files is done as follows:
1.953 +# TAGFILES = file1=loc1 "file2 = loc2" ...
1.954 +# where "loc1" and "loc2" can be relative or absolute paths or
1.955 +# URLs. If a location is present for each tag, the installdox tool
1.956 +# does not have to be run to correct the links.
1.957 +# Note that each tag file must have a unique name
1.958 +# (where the name does NOT include the path)
1.959 +# If a tag file is not located in the directory in which doxygen
1.960 +# is run, you must also specify the path to the tagfile here.
1.961 +
1.962 +TAGFILES =
1.963 +
1.964 +# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1.965 +# a tag file that is based on the input files it reads.
1.966 +
1.967 +GENERATE_TAGFILE =
1.968 +
1.969 +# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1.970 +# in the class index. If set to NO only the inherited external classes
1.971 +# will be listed.
1.972 +
1.973 +ALLEXTERNALS = NO
1.974 +
1.975 +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1.976 +# in the modules index. If set to NO, only the current project's groups will
1.977 +# be listed.
1.978 +
1.979 +EXTERNAL_GROUPS = YES
1.980 +
1.981 +# The PERL_PATH should be the absolute path and name of the perl script
1.982 +# interpreter (i.e. the result of `which perl').
1.983 +
1.984 +PERL_PATH = /usr/bin/perl
1.985 +
1.986 +#---------------------------------------------------------------------------
1.987 +# Configuration options related to the dot tool
1.988 +#---------------------------------------------------------------------------
1.989 +
1.990 +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1.991 +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or
1.992 +# super classes. Setting the tag to NO turns the diagrams off. Note that this
1.993 +# option is superseded by the HAVE_DOT option below. This is only a fallback. It is
1.994 +# recommended to install and use dot, since it yields more powerful graphs.
1.995 +
1.996 +CLASS_DIAGRAMS = YES
1.997 +
1.998 +# If set to YES, the inheritance and collaboration graphs will hide
1.999 +# inheritance and usage relations if the target is undocumented
1.1000 +# or is not a class.
1.1001 +
1.1002 +HIDE_UNDOC_RELATIONS = NO
1.1003 +
1.1004 +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1.1005 +# available from the path. This tool is part of Graphviz, a graph visualization
1.1006 +# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1.1007 +# have no effect if this option is set to NO (the default)
1.1008 +
1.1009 +HAVE_DOT = YES
1.1010 +
1.1011 +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1.1012 +# will generate a graph for each documented class showing the direct and
1.1013 +# indirect inheritance relations. Setting this tag to YES will force the
1.1014 +# the CLASS_DIAGRAMS tag to NO.
1.1015 +
1.1016 +CLASS_GRAPH = YES
1.1017 +
1.1018 +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1.1019 +# will generate a graph for each documented class showing the direct and
1.1020 +# indirect implementation dependencies (inheritance, containment, and
1.1021 +# class references variables) of the class with other documented classes.
1.1022 +
1.1023 +COLLABORATION_GRAPH = YES
1.1024 +
1.1025 +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1.1026 +# collaboration diagrams in a style similar to the OMG's Unified Modeling
1.1027 +# Language.
1.1028 +
1.1029 +UML_LOOK = NO
1.1030 +
1.1031 +# If set to YES, the inheritance and collaboration graphs will show the
1.1032 +# relations between templates and their instances.
1.1033 +
1.1034 +TEMPLATE_RELATIONS = YES
1.1035 +
1.1036 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1.1037 +# tags are set to YES then doxygen will generate a graph for each documented
1.1038 +# file showing the direct and indirect include dependencies of the file with
1.1039 +# other documented files.
1.1040 +
1.1041 +INCLUDE_GRAPH = YES
1.1042 +
1.1043 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1.1044 +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1.1045 +# documented header file showing the documented files that directly or
1.1046 +# indirectly include this file.
1.1047 +
1.1048 +INCLUDED_BY_GRAPH = YES
1.1049 +
1.1050 +# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1.1051 +# generate a call dependency graph for every global function or class method.
1.1052 +# Note that enabling this option will significantly increase the time of a run.
1.1053 +# So in most cases it will be better to enable call graphs for selected
1.1054 +# functions only using the \callgraph command.
1.1055 +
1.1056 +CALL_GRAPH = YES
1.1057 +
1.1058 +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1.1059 +# will graphical hierarchy of all classes instead of a textual one.
1.1060 +
1.1061 +GRAPHICAL_HIERARCHY = YES
1.1062 +
1.1063 +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1.1064 +# generated by dot. Possible values are png, jpg, or gif
1.1065 +# If left blank png will be used.
1.1066 +
1.1067 +DOT_IMAGE_FORMAT = png
1.1068 +
1.1069 +# The tag DOT_PATH can be used to specify the path where the dot tool can be
1.1070 +# found. If left blank, it is assumed the dot tool can be found on the path.
1.1071 +
1.1072 +DOT_PATH =
1.1073 +
1.1074 +# The DOTFILE_DIRS tag can be used to specify one or more directories that
1.1075 +# contain dot files that are included in the documentation (see the
1.1076 +# \dotfile command).
1.1077 +
1.1078 +DOTFILE_DIRS =
1.1079 +
1.1080 +# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1.1081 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than
1.1082 +# this value, doxygen will try to truncate the graph, so that it fits within
1.1083 +# the specified constraint. Beware that most browsers cannot cope with very
1.1084 +# large images.
1.1085 +
1.1086 +MAX_DOT_GRAPH_WIDTH = 1024
1.1087 +
1.1088 +# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1.1089 +# (in pixels) of the graphs generated by dot. If a graph becomes larger than
1.1090 +# this value, doxygen will try to truncate the graph, so that it fits within
1.1091 +# the specified constraint. Beware that most browsers cannot cope with very
1.1092 +# large images.
1.1093 +
1.1094 +MAX_DOT_GRAPH_HEIGHT = 1024
1.1095 +
1.1096 +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1.1097 +# graphs generated by dot. A depth value of 3 means that only nodes reachable
1.1098 +# from the root by following a path via at most 3 edges will be shown. Nodes that
1.1099 +# lay further from the root node will be omitted. Note that setting this option to
1.1100 +# 1 or 2 may greatly reduce the computation time needed for large code bases. Also
1.1101 +# note that a graph may be further truncated if the graph's image dimensions are
1.1102 +# not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT).
1.1103 +# If 0 is used for the depth value (the default), the graph is not depth-constrained.
1.1104 +
1.1105 +MAX_DOT_GRAPH_DEPTH = 0
1.1106 +
1.1107 +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1.1108 +# generate a legend page explaining the meaning of the various boxes and
1.1109 +# arrows in the dot generated graphs.
1.1110 +
1.1111 +GENERATE_LEGEND = YES
1.1112 +
1.1113 +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1.1114 +# remove the intermediate dot files that are used to generate
1.1115 +# the various graphs.
1.1116 +
1.1117 +DOT_CLEANUP = YES
1.1118 +
1.1119 +#---------------------------------------------------------------------------
1.1120 +# Configuration::additions related to the search engine
1.1121 +#---------------------------------------------------------------------------
1.1122 +
1.1123 +# The SEARCHENGINE tag specifies whether or not a search engine should be
1.1124 +# used. If set to NO the values of all tags below this one will be ignored.
1.1125 +
1.1126 +SEARCHENGINE = YES