cmake_infile.doxygen

Sun, 14 Feb 2021 15:37:12 +0100

author
Mike Becker <universe@uap-core.de>
date
Sun, 14 Feb 2021 15:37:12 +0100
changeset 413
0f4aa9fc75d9
parent 390
d345541018fa
child 462
1bcf7c8d4b47
permissions
-rw-r--r--

perform array and list tests in the same test binary (use the same assertions, later)

universe@372 1 # Doxyfile 1.8.7
universe@372 2
universe@372 3 # This file describes the settings to be used by the documentation system
universe@372 4 # doxygen (www.doxygen.org) for a project.
universe@372 5 #
universe@372 6 # All text after a double hash (##) is considered a comment and is placed in
universe@372 7 # front of the TAG it is preceding.
universe@372 8 #
universe@372 9 # All text after a single hash (#) is considered a comment and will be ignored.
universe@372 10 # The format is:
universe@372 11 # TAG = value [value, ...]
universe@372 12 # For lists, items can also be appended using:
universe@372 13 # TAG += value [value, ...]
universe@372 14 # Values that contain spaces should be placed between quotes (\" \").
universe@372 15
universe@372 16 #---------------------------------------------------------------------------
universe@372 17 # Project related configuration options
universe@372 18 #---------------------------------------------------------------------------
universe@372 19
universe@372 20 # This tag specifies the encoding used for all characters in the config file
universe@372 21 # that follow. The default is UTF-8 which is also the encoding used for all text
universe@372 22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
universe@372 23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
universe@372 24 # for the list of possible encodings.
universe@372 25 # The default value is: UTF-8.
universe@372 26
universe@372 27 DOXYFILE_ENCODING = UTF-8
universe@372 28
universe@372 29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
universe@372 30 # double-quotes, unless you are using Doxywizard) that should identify the
universe@372 31 # project for which the documentation is generated. This name is used in the
universe@372 32 # title of most generated pages and in a few other places.
universe@372 33 # The default value is: My Project.
universe@372 34
universe@372 35 PROJECT_NAME = "ucx"
universe@372 36
universe@372 37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
universe@372 38 # could be handy for archiving the generated documentation or if some version
universe@372 39 # control system is used.
universe@372 40
universe@372 41 PROJECT_NUMBER =
universe@372 42
universe@372 43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
universe@372 44 # for a project that appears at the top of each page and should give viewer a
universe@372 45 # quick idea about the purpose of the project. Keep the description short.
universe@372 46
universe@372 47 PROJECT_BRIEF = "UAP Common Extensions"
universe@372 48
universe@372 49 # With the PROJECT_LOGO tag one can specify an logo or icon that is included in
universe@372 50 # the documentation. The maximum height of the logo should not exceed 55 pixels
universe@372 51 # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo
universe@372 52 # to the output directory.
universe@372 53
universe@372 54 PROJECT_LOGO = @DOXY_PROJECT_LOGO@
universe@372 55
universe@372 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
universe@372 57 # into which the generated documentation will be written. If a relative path is
universe@372 58 # entered, it will be relative to the location where doxygen was started. If
universe@372 59 # left blank the current directory will be used.
universe@372 60
universe@372 61 OUTPUT_DIRECTORY = @DOXY_OUTPUT_DIRECTORY@
universe@372 62
universe@372 63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
universe@372 64 # directories (in 2 levels) under the output directory of each output format and
universe@372 65 # will distribute the generated files over these directories. Enabling this
universe@372 66 # option can be useful when feeding doxygen a huge amount of source files, where
universe@372 67 # putting all generated files in the same directory would otherwise causes
universe@372 68 # performance problems for the file system.
universe@372 69 # The default value is: NO.
universe@372 70
universe@372 71 CREATE_SUBDIRS = NO
universe@372 72
universe@372 73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
universe@372 74 # characters to appear in the names of generated files. If set to NO, non-ASCII
universe@372 75 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
universe@372 76 # U+3044.
universe@372 77 # The default value is: NO.
universe@372 78
universe@372 79 ALLOW_UNICODE_NAMES = NO
universe@372 80
universe@372 81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
universe@372 82 # documentation generated by doxygen is written. Doxygen will use this
universe@372 83 # information to generate all constant output in the proper language.
universe@372 84 # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
universe@372 85 # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
universe@372 86 # Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,
universe@372 87 # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
universe@372 88 # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
universe@372 89 # Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,
universe@372 90 # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
universe@372 91 # Ukrainian and Vietnamese.
universe@372 92 # The default value is: English.
universe@372 93
universe@372 94 OUTPUT_LANGUAGE = English
universe@372 95
universe@372 96 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member
universe@372 97 # descriptions after the members that are listed in the file and class
universe@372 98 # documentation (similar to Javadoc). Set to NO to disable this.
universe@372 99 # The default value is: YES.
universe@372 100
universe@372 101 BRIEF_MEMBER_DESC = YES
universe@372 102
universe@372 103 # If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief
universe@372 104 # description of a member or function before the detailed description
universe@372 105 #
universe@372 106 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
universe@372 107 # brief descriptions will be completely suppressed.
universe@372 108 # The default value is: YES.
universe@372 109
universe@372 110 REPEAT_BRIEF = YES
universe@372 111
universe@372 112 # This tag implements a quasi-intelligent brief description abbreviator that is
universe@372 113 # used to form the text in various listings. Each string in this list, if found
universe@372 114 # as the leading text of the brief description, will be stripped from the text
universe@372 115 # and the result, after processing the whole list, is used as the annotated
universe@372 116 # text. Otherwise, the brief description is used as-is. If left blank, the
universe@372 117 # following values are used ($name is automatically replaced with the name of
universe@372 118 # the entity):The $name class, The $name widget, The $name file, is, provides,
universe@372 119 # specifies, contains, represents, a, an and the.
universe@372 120
universe@372 121 ABBREVIATE_BRIEF =
universe@372 122
universe@372 123 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
universe@372 124 # doxygen will generate a detailed section even if there is only a brief
universe@372 125 # description.
universe@372 126 # The default value is: NO.
universe@372 127
universe@372 128 ALWAYS_DETAILED_SEC = NO
universe@372 129
universe@372 130 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
universe@372 131 # inherited members of a class in the documentation of that class as if those
universe@372 132 # members were ordinary class members. Constructors, destructors and assignment
universe@372 133 # operators of the base classes will not be shown.
universe@372 134 # The default value is: NO.
universe@372 135
universe@372 136 INLINE_INHERITED_MEMB = NO
universe@372 137
universe@372 138 # If the FULL_PATH_NAMES tag is set to YES doxygen will prepend the full path
universe@372 139 # before files name in the file list and in the header files. If set to NO the
universe@372 140 # shortest path that makes the file name unique will be used
universe@372 141 # The default value is: YES.
universe@372 142
universe@372 143 FULL_PATH_NAMES = YES
universe@372 144
universe@372 145 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
universe@372 146 # Stripping is only done if one of the specified strings matches the left-hand
universe@372 147 # part of the path. The tag can be used to show relative paths in the file list.
universe@372 148 # If left blank the directory from which doxygen is run is used as the path to
universe@372 149 # strip.
universe@372 150 #
universe@372 151 # Note that you can specify absolute paths here, but also relative paths, which
universe@372 152 # will be relative from the directory where doxygen is started.
universe@372 153 # This tag requires that the tag FULL_PATH_NAMES is set to YES.
universe@372 154
universe@372 155 STRIP_FROM_PATH =
universe@372 156
universe@372 157 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
universe@372 158 # path mentioned in the documentation of a class, which tells the reader which
universe@372 159 # header file to include in order to use a class. If left blank only the name of
universe@372 160 # the header file containing the class definition is used. Otherwise one should
universe@372 161 # specify the list of include paths that are normally passed to the compiler
universe@372 162 # using the -I flag.
universe@372 163
universe@372 164 STRIP_FROM_INC_PATH =
universe@372 165
universe@372 166 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
universe@372 167 # less readable) file names. This can be useful is your file systems doesn't
universe@372 168 # support long names like on DOS, Mac, or CD-ROM.
universe@372 169 # The default value is: NO.
universe@372 170
universe@372 171 SHORT_NAMES = NO
universe@372 172
universe@372 173 # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
universe@372 174 # first line (until the first dot) of a Javadoc-style comment as the brief
universe@372 175 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
universe@372 176 # style comments (thus requiring an explicit @brief command for a brief
universe@372 177 # description.)
universe@372 178 # The default value is: NO.
universe@372 179
universe@372 180 JAVADOC_AUTOBRIEF = YES
universe@372 181
universe@372 182 # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
universe@372 183 # line (until the first dot) of a Qt-style comment as the brief description. If
universe@372 184 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
universe@372 185 # requiring an explicit \brief command for a brief description.)
universe@372 186 # The default value is: NO.
universe@372 187
universe@372 188 QT_AUTOBRIEF = NO
universe@372 189
universe@372 190 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
universe@372 191 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
universe@372 192 # a brief description. This used to be the default behavior. The new default is
universe@372 193 # to treat a multi-line C++ comment block as a detailed description. Set this
universe@372 194 # tag to YES if you prefer the old behavior instead.
universe@372 195 #
universe@372 196 # Note that setting this tag to YES also means that rational rose comments are
universe@372 197 # not recognized any more.
universe@372 198 # The default value is: NO.
universe@372 199
universe@372 200 MULTILINE_CPP_IS_BRIEF = NO
universe@372 201
universe@372 202 # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
universe@372 203 # documentation from any documented member that it re-implements.
universe@372 204 # The default value is: YES.
universe@372 205
universe@372 206 INHERIT_DOCS = YES
universe@372 207
universe@372 208 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce a
universe@372 209 # new page for each member. If set to NO, the documentation of a member will be
universe@372 210 # part of the file/class/namespace that contains it.
universe@372 211 # The default value is: NO.
universe@372 212
universe@372 213 SEPARATE_MEMBER_PAGES = NO
universe@372 214
universe@372 215 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
universe@372 216 # uses this value to replace tabs by spaces in code fragments.
universe@372 217 # Minimum value: 1, maximum value: 16, default value: 4.
universe@372 218
universe@372 219 TAB_SIZE = 4
universe@372 220
universe@372 221 # This tag can be used to specify a number of aliases that act as commands in
universe@372 222 # the documentation. An alias has the form:
universe@372 223 # name=value
universe@372 224 # For example adding
universe@372 225 # "sideeffect=@par Side Effects:\n"
universe@372 226 # will allow you to put the command \sideeffect (or @sideeffect) in the
universe@372 227 # documentation, which will result in a user-defined paragraph with heading
universe@372 228 # "Side Effects:". You can put \n's in the value part of an alias to insert
universe@372 229 # newlines.
universe@372 230
universe@372 231 ALIASES =
universe@372 232
universe@372 233 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
universe@372 234 # only. Doxygen will then generate output that is more tailored for C. For
universe@372 235 # instance, some of the names that are used will be different. The list of all
universe@372 236 # members will be omitted, etc.
universe@372 237 # The default value is: NO.
universe@372 238
universe@372 239 OPTIMIZE_OUTPUT_FOR_C = YES
universe@372 240
universe@372 241 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
universe@372 242 # Python sources only. Doxygen will then generate output that is more tailored
universe@372 243 # for that language. For instance, namespaces will be presented as packages,
universe@372 244 # qualified scopes will look different, etc.
universe@372 245 # The default value is: NO.
universe@372 246
universe@372 247 OPTIMIZE_OUTPUT_JAVA = NO
universe@372 248
universe@372 249 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
universe@372 250 # sources. Doxygen will then generate output that is tailored for Fortran.
universe@372 251 # The default value is: NO.
universe@372 252
universe@372 253 OPTIMIZE_FOR_FORTRAN = NO
universe@372 254
universe@372 255 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
universe@372 256 # sources. Doxygen will then generate output that is tailored for VHDL.
universe@372 257 # The default value is: NO.
universe@372 258
universe@372 259 OPTIMIZE_OUTPUT_VHDL = NO
universe@372 260
universe@372 261 # Doxygen selects the parser to use depending on the extension of the files it
universe@372 262 # parses. With this tag you can assign which parser to use for a given
universe@372 263 # extension. Doxygen has a built-in mapping, but you can override or extend it
universe@372 264 # using this tag. The format is ext=language, where ext is a file extension, and
universe@372 265 # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
universe@372 266 # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
universe@372 267 # FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:
universe@372 268 # Fortran. In the later case the parser tries to guess whether the code is fixed
universe@372 269 # or free formatted code, this is the default for Fortran type files), VHDL. For
universe@372 270 # instance to make doxygen treat .inc files as Fortran files (default is PHP),
universe@372 271 # and .f files as C (default is Fortran), use: inc=Fortran f=C.
universe@372 272 #
universe@372 273 # Note For files without extension you can use no_extension as a placeholder.
universe@372 274 #
universe@372 275 # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
universe@372 276 # the files are not read by doxygen.
universe@372 277
universe@372 278 EXTENSION_MAPPING =
universe@372 279
universe@372 280 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
universe@372 281 # according to the Markdown format, which allows for more readable
universe@372 282 # documentation. See http://daringfireball.net/projects/markdown/ for details.
universe@372 283 # The output of markdown processing is further processed by doxygen, so you can
universe@372 284 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
universe@372 285 # case of backward compatibilities issues.
universe@372 286 # The default value is: YES.
universe@372 287
universe@372 288 MARKDOWN_SUPPORT = YES
universe@372 289
universe@372 290 # When enabled doxygen tries to link words that correspond to documented
universe@372 291 # classes, or namespaces to their corresponding documentation. Such a link can
universe@372 292 # be prevented in individual cases by by putting a % sign in front of the word
universe@372 293 # or globally by setting AUTOLINK_SUPPORT to NO.
universe@372 294 # The default value is: YES.
universe@372 295
universe@372 296 AUTOLINK_SUPPORT = YES
universe@372 297
universe@372 298 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
universe@372 299 # to include (a tag file for) the STL sources as input, then you should set this
universe@372 300 # tag to YES in order to let doxygen match functions declarations and
universe@372 301 # definitions whose arguments contain STL classes (e.g. func(std::string);
universe@372 302 # versus func(std::string) {}). This also make the inheritance and collaboration
universe@372 303 # diagrams that involve STL classes more complete and accurate.
universe@372 304 # The default value is: NO.
universe@372 305
universe@372 306 BUILTIN_STL_SUPPORT = NO
universe@372 307
universe@372 308 # If you use Microsoft's C++/CLI language, you should set this option to YES to
universe@372 309 # enable parsing support.
universe@372 310 # The default value is: NO.
universe@372 311
universe@372 312 CPP_CLI_SUPPORT = NO
universe@372 313
universe@372 314 # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
universe@372 315 # http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen
universe@372 316 # will parse them like normal C++ but will assume all classes use public instead
universe@372 317 # of private inheritance when no explicit protection keyword is present.
universe@372 318 # The default value is: NO.
universe@372 319
universe@372 320 SIP_SUPPORT = NO
universe@372 321
universe@372 322 # For Microsoft's IDL there are propget and propput attributes to indicate
universe@372 323 # getter and setter methods for a property. Setting this option to YES will make
universe@372 324 # doxygen to replace the get and set methods by a property in the documentation.
universe@372 325 # This will only work if the methods are indeed getting or setting a simple
universe@372 326 # type. If this is not the case, or you want to show the methods anyway, you
universe@372 327 # should set this option to NO.
universe@372 328 # The default value is: YES.
universe@372 329
universe@372 330 IDL_PROPERTY_SUPPORT = YES
universe@372 331
universe@372 332 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
universe@372 333 # tag is set to YES, then doxygen will reuse the documentation of the first
universe@372 334 # member in the group (if any) for the other members of the group. By default
universe@372 335 # all members of a group must be documented explicitly.
universe@372 336 # The default value is: NO.
universe@372 337
universe@372 338 DISTRIBUTE_GROUP_DOC = NO
universe@372 339
universe@372 340 # Set the SUBGROUPING tag to YES to allow class member groups of the same type
universe@372 341 # (for instance a group of public functions) to be put as a subgroup of that
universe@372 342 # type (e.g. under the Public Functions section). Set it to NO to prevent
universe@372 343 # subgrouping. Alternatively, this can be done per class using the
universe@372 344 # \nosubgrouping command.
universe@372 345 # The default value is: YES.
universe@372 346
universe@372 347 SUBGROUPING = YES
universe@372 348
universe@372 349 # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
universe@372 350 # are shown inside the group in which they are included (e.g. using \ingroup)
universe@372 351 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
universe@372 352 # and RTF).
universe@372 353 #
universe@372 354 # Note that this feature does not work in combination with
universe@372 355 # SEPARATE_MEMBER_PAGES.
universe@372 356 # The default value is: NO.
universe@372 357
universe@372 358 INLINE_GROUPED_CLASSES = NO
universe@372 359
universe@372 360 # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
universe@372 361 # with only public data fields or simple typedef fields will be shown inline in
universe@372 362 # the documentation of the scope in which they are defined (i.e. file,
universe@372 363 # namespace, or group documentation), provided this scope is documented. If set
universe@372 364 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
universe@372 365 # Man pages) or section (for LaTeX and RTF).
universe@372 366 # The default value is: NO.
universe@372 367
universe@372 368 INLINE_SIMPLE_STRUCTS = NO
universe@372 369
universe@372 370 # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
universe@372 371 # enum is documented as struct, union, or enum with the name of the typedef. So
universe@372 372 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
universe@372 373 # with name TypeT. When disabled the typedef will appear as a member of a file,
universe@372 374 # namespace, or class. And the struct will be named TypeS. This can typically be
universe@372 375 # useful for C code in case the coding convention dictates that all compound
universe@372 376 # types are typedef'ed and only the typedef is referenced, never the tag name.
universe@372 377 # The default value is: NO.
universe@372 378
universe@372 379 TYPEDEF_HIDES_STRUCT = NO
universe@372 380
universe@372 381 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
universe@372 382 # cache is used to resolve symbols given their name and scope. Since this can be
universe@372 383 # an expensive process and often the same symbol appears multiple times in the
universe@372 384 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
universe@372 385 # doxygen will become slower. If the cache is too large, memory is wasted. The
universe@372 386 # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
universe@372 387 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
universe@372 388 # symbols. At the end of a run doxygen will report the cache usage and suggest
universe@372 389 # the optimal cache size from a speed point of view.
universe@372 390 # Minimum value: 0, maximum value: 9, default value: 0.
universe@372 391
universe@372 392 LOOKUP_CACHE_SIZE = 0
universe@372 393
universe@372 394 #---------------------------------------------------------------------------
universe@372 395 # Build related configuration options
universe@372 396 #---------------------------------------------------------------------------
universe@372 397
universe@372 398 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
universe@372 399 # documentation are documented, even if no documentation was available. Private
universe@372 400 # class members and static file members will be hidden unless the
universe@372 401 # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
universe@372 402 # Note: This will also disable the warnings about undocumented members that are
universe@372 403 # normally produced when WARNINGS is set to YES.
universe@372 404 # The default value is: NO.
universe@372 405
universe@372 406 EXTRACT_ALL = NO
universe@372 407
universe@372 408 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class will
universe@372 409 # be included in the documentation.
universe@372 410 # The default value is: NO.
universe@372 411
universe@372 412 EXTRACT_PRIVATE = NO
universe@372 413
universe@372 414 # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
universe@372 415 # scope will be included in the documentation.
universe@372 416 # The default value is: NO.
universe@372 417
universe@372 418 EXTRACT_PACKAGE = NO
universe@372 419
universe@372 420 # If the EXTRACT_STATIC tag is set to YES all static members of a file will be
universe@372 421 # included in the documentation.
universe@372 422 # The default value is: NO.
universe@372 423
universe@372 424 EXTRACT_STATIC = NO
universe@372 425
universe@372 426 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) defined
universe@372 427 # locally in source files will be included in the documentation. If set to NO
universe@372 428 # only classes defined in header files are included. Does not have any effect
universe@372 429 # for Java sources.
universe@372 430 # The default value is: YES.
universe@372 431
universe@372 432 EXTRACT_LOCAL_CLASSES = YES
universe@372 433
universe@372 434 # This flag is only useful for Objective-C code. When set to YES local methods,
universe@372 435 # which are defined in the implementation section but not in the interface are
universe@372 436 # included in the documentation. If set to NO only methods in the interface are
universe@372 437 # included.
universe@372 438 # The default value is: NO.
universe@372 439
universe@372 440 EXTRACT_LOCAL_METHODS = NO
universe@372 441
universe@372 442 # If this flag is set to YES, the members of anonymous namespaces will be
universe@372 443 # extracted and appear in the documentation as a namespace called
universe@372 444 # 'anonymous_namespace{file}', where file will be replaced with the base name of
universe@372 445 # the file that contains the anonymous namespace. By default anonymous namespace
universe@372 446 # are hidden.
universe@372 447 # The default value is: NO.
universe@372 448
universe@372 449 EXTRACT_ANON_NSPACES = NO
universe@372 450
universe@372 451 # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
universe@372 452 # undocumented members inside documented classes or files. If set to NO these
universe@372 453 # members will be included in the various overviews, but no documentation
universe@372 454 # section is generated. This option has no effect if EXTRACT_ALL is enabled.
universe@372 455 # The default value is: NO.
universe@372 456
universe@372 457 HIDE_UNDOC_MEMBERS = NO
universe@372 458
universe@372 459 # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
universe@372 460 # undocumented classes that are normally visible in the class hierarchy. If set
universe@372 461 # to NO these classes will be included in the various overviews. This option has
universe@372 462 # no effect if EXTRACT_ALL is enabled.
universe@372 463 # The default value is: NO.
universe@372 464
universe@372 465 HIDE_UNDOC_CLASSES = NO
universe@372 466
universe@372 467 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
universe@372 468 # (class|struct|union) declarations. If set to NO these declarations will be
universe@372 469 # included in the documentation.
universe@372 470 # The default value is: NO.
universe@372 471
universe@372 472 HIDE_FRIEND_COMPOUNDS = NO
universe@372 473
universe@372 474 # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
universe@372 475 # documentation blocks found inside the body of a function. If set to NO these
universe@372 476 # blocks will be appended to the function's detailed documentation block.
universe@372 477 # The default value is: NO.
universe@372 478
universe@372 479 HIDE_IN_BODY_DOCS = NO
universe@372 480
universe@372 481 # The INTERNAL_DOCS tag determines if documentation that is typed after a
universe@372 482 # \internal command is included. If the tag is set to NO then the documentation
universe@372 483 # will be excluded. Set it to YES to include the internal documentation.
universe@372 484 # The default value is: NO.
universe@372 485
universe@372 486 INTERNAL_DOCS = NO
universe@372 487
universe@372 488 # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
universe@372 489 # names in lower-case letters. If set to YES upper-case letters are also
universe@372 490 # allowed. This is useful if you have classes or files whose names only differ
universe@372 491 # in case and if your file system supports case sensitive file names. Windows
universe@372 492 # and Mac users are advised to set this option to NO.
universe@372 493 # The default value is: system dependent.
universe@372 494
universe@372 495 CASE_SENSE_NAMES = YES
universe@372 496
universe@372 497 # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
universe@372 498 # their full class and namespace scopes in the documentation. If set to YES the
universe@372 499 # scope will be hidden.
universe@372 500 # The default value is: NO.
universe@372 501
universe@372 502 HIDE_SCOPE_NAMES = NO
universe@372 503
universe@372 504 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
universe@372 505 # the files that are included by a file in the documentation of that file.
universe@372 506 # The default value is: YES.
universe@372 507
universe@372 508 SHOW_INCLUDE_FILES = YES
universe@372 509
universe@372 510 # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
universe@372 511 # grouped member an include statement to the documentation, telling the reader
universe@372 512 # which file to include in order to use the member.
universe@372 513 # The default value is: NO.
universe@372 514
universe@372 515 SHOW_GROUPED_MEMB_INC = NO
universe@372 516
universe@372 517 # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
universe@372 518 # files with double quotes in the documentation rather than with sharp brackets.
universe@372 519 # The default value is: NO.
universe@372 520
universe@372 521 FORCE_LOCAL_INCLUDES = NO
universe@372 522
universe@372 523 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
universe@372 524 # documentation for inline members.
universe@372 525 # The default value is: YES.
universe@372 526
universe@372 527 INLINE_INFO = YES
universe@372 528
universe@372 529 # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
universe@372 530 # (detailed) documentation of file and class members alphabetically by member
universe@372 531 # name. If set to NO the members will appear in declaration order.
universe@372 532 # The default value is: YES.
universe@372 533
universe@372 534 SORT_MEMBER_DOCS = YES
universe@372 535
universe@372 536 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
universe@372 537 # descriptions of file, namespace and class members alphabetically by member
universe@372 538 # name. If set to NO the members will appear in declaration order. Note that
universe@372 539 # this will also influence the order of the classes in the class list.
universe@372 540 # The default value is: NO.
universe@372 541
universe@372 542 SORT_BRIEF_DOCS = NO
universe@372 543
universe@372 544 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
universe@372 545 # (brief and detailed) documentation of class members so that constructors and
universe@372 546 # destructors are listed first. If set to NO the constructors will appear in the
universe@372 547 # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
universe@372 548 # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
universe@372 549 # member documentation.
universe@372 550 # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
universe@372 551 # detailed member documentation.
universe@372 552 # The default value is: NO.
universe@372 553
universe@372 554 SORT_MEMBERS_CTORS_1ST = NO
universe@372 555
universe@372 556 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
universe@372 557 # of group names into alphabetical order. If set to NO the group names will
universe@372 558 # appear in their defined order.
universe@372 559 # The default value is: NO.
universe@372 560
universe@372 561 SORT_GROUP_NAMES = NO
universe@372 562
universe@372 563 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
universe@372 564 # fully-qualified names, including namespaces. If set to NO, the class list will
universe@372 565 # be sorted only by class name, not including the namespace part.
universe@372 566 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
universe@372 567 # Note: This option applies only to the class list, not to the alphabetical
universe@372 568 # list.
universe@372 569 # The default value is: NO.
universe@372 570
universe@372 571 SORT_BY_SCOPE_NAME = NO
universe@372 572
universe@372 573 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
universe@372 574 # type resolution of all parameters of a function it will reject a match between
universe@372 575 # the prototype and the implementation of a member function even if there is
universe@372 576 # only one candidate or it is obvious which candidate to choose by doing a
universe@372 577 # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
universe@372 578 # accept a match between prototype and implementation in such cases.
universe@372 579 # The default value is: NO.
universe@372 580
universe@372 581 STRICT_PROTO_MATCHING = NO
universe@372 582
universe@372 583 # The GENERATE_TODOLIST tag can be used to enable ( YES) or disable ( NO) the
universe@372 584 # todo list. This list is created by putting \todo commands in the
universe@372 585 # documentation.
universe@372 586 # The default value is: YES.
universe@372 587
universe@372 588 GENERATE_TODOLIST = YES
universe@372 589
universe@372 590 # The GENERATE_TESTLIST tag can be used to enable ( YES) or disable ( NO) the
universe@372 591 # test list. This list is created by putting \test commands in the
universe@372 592 # documentation.
universe@372 593 # The default value is: YES.
universe@372 594
universe@372 595 GENERATE_TESTLIST = YES
universe@372 596
universe@372 597 # The GENERATE_BUGLIST tag can be used to enable ( YES) or disable ( NO) the bug
universe@372 598 # list. This list is created by putting \bug commands in the documentation.
universe@372 599 # The default value is: YES.
universe@372 600
universe@372 601 GENERATE_BUGLIST = YES
universe@372 602
universe@372 603 # The GENERATE_DEPRECATEDLIST tag can be used to enable ( YES) or disable ( NO)
universe@372 604 # the deprecated list. This list is created by putting \deprecated commands in
universe@372 605 # the documentation.
universe@372 606 # The default value is: YES.
universe@372 607
universe@372 608 GENERATE_DEPRECATEDLIST= YES
universe@372 609
universe@372 610 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
universe@372 611 # sections, marked by \if <section_label> ... \endif and \cond <section_label>
universe@372 612 # ... \endcond blocks.
universe@372 613
universe@372 614 ENABLED_SECTIONS =
universe@372 615
universe@372 616 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
universe@372 617 # initial value of a variable or macro / define can have for it to appear in the
universe@372 618 # documentation. If the initializer consists of more lines than specified here
universe@372 619 # it will be hidden. Use a value of 0 to hide initializers completely. The
universe@372 620 # appearance of the value of individual variables and macros / defines can be
universe@372 621 # controlled using \showinitializer or \hideinitializer command in the
universe@372 622 # documentation regardless of this setting.
universe@372 623 # Minimum value: 0, maximum value: 10000, default value: 30.
universe@372 624
universe@372 625 MAX_INITIALIZER_LINES = 30
universe@372 626
universe@372 627 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
universe@372 628 # the bottom of the documentation of classes and structs. If set to YES the list
universe@372 629 # will mention the files that were used to generate the documentation.
universe@372 630 # The default value is: YES.
universe@372 631
universe@372 632 SHOW_USED_FILES = YES
universe@372 633
universe@372 634 # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
universe@372 635 # will remove the Files entry from the Quick Index and from the Folder Tree View
universe@372 636 # (if specified).
universe@372 637 # The default value is: YES.
universe@372 638
universe@372 639 SHOW_FILES = YES
universe@372 640
universe@372 641 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
universe@372 642 # page. This will remove the Namespaces entry from the Quick Index and from the
universe@372 643 # Folder Tree View (if specified).
universe@372 644 # The default value is: YES.
universe@372 645
universe@372 646 SHOW_NAMESPACES = YES
universe@372 647
universe@372 648 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
universe@372 649 # doxygen should invoke to get the current version for each file (typically from
universe@372 650 # the version control system). Doxygen will invoke the program by executing (via
universe@372 651 # popen()) the command command input-file, where command is the value of the
universe@372 652 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
universe@372 653 # by doxygen. Whatever the program writes to standard output is used as the file
universe@372 654 # version. For an example see the documentation.
universe@372 655
universe@372 656 FILE_VERSION_FILTER =
universe@372 657
universe@372 658 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
universe@372 659 # by doxygen. The layout file controls the global structure of the generated
universe@372 660 # output files in an output format independent way. To create the layout file
universe@372 661 # that represents doxygen's defaults, run doxygen with the -l option. You can
universe@372 662 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
universe@372 663 # will be used as the name of the layout file.
universe@372 664 #
universe@372 665 # Note that if you run doxygen from a directory containing a file called
universe@372 666 # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
universe@372 667 # tag is left empty.
universe@372 668
universe@372 669 LAYOUT_FILE =
universe@372 670
universe@372 671 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
universe@372 672 # the reference definitions. This must be a list of .bib files. The .bib
universe@372 673 # extension is automatically appended if omitted. This requires the bibtex tool
universe@372 674 # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
universe@372 675 # For LaTeX the style of the bibliography can be controlled using
universe@372 676 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
universe@372 677 # search path. Do not use file names with spaces, bibtex cannot handle them. See
universe@372 678 # also \cite for info how to create references.
universe@372 679
universe@372 680 CITE_BIB_FILES =
universe@372 681
universe@372 682 #---------------------------------------------------------------------------
universe@372 683 # Configuration options related to warning and progress messages
universe@372 684 #---------------------------------------------------------------------------
universe@372 685
universe@372 686 # The QUIET tag can be used to turn on/off the messages that are generated to
universe@372 687 # standard output by doxygen. If QUIET is set to YES this implies that the
universe@372 688 # messages are off.
universe@372 689 # The default value is: NO.
universe@372 690
universe@372 691 QUIET = YES
universe@372 692
universe@372 693 # The WARNINGS tag can be used to turn on/off the warning messages that are
universe@372 694 # generated to standard error ( stderr) by doxygen. If WARNINGS is set to YES
universe@372 695 # this implies that the warnings are on.
universe@372 696 #
universe@372 697 # Tip: Turn warnings on while writing the documentation.
universe@372 698 # The default value is: YES.
universe@372 699
universe@372 700 WARNINGS = YES
universe@372 701
universe@372 702 # If the WARN_IF_UNDOCUMENTED tag is set to YES, then doxygen will generate
universe@372 703 # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
universe@372 704 # will automatically be disabled.
universe@372 705 # The default value is: YES.
universe@372 706
universe@372 707 WARN_IF_UNDOCUMENTED = YES
universe@372 708
universe@372 709 # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
universe@372 710 # potential errors in the documentation, such as not documenting some parameters
universe@372 711 # in a documented function, or documenting parameters that don't exist or using
universe@372 712 # markup commands wrongly.
universe@372 713 # The default value is: YES.
universe@372 714
universe@372 715 WARN_IF_DOC_ERROR = YES
universe@372 716
universe@372 717 # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
universe@372 718 # are documented, but have no documentation for their parameters or return
universe@372 719 # value. If set to NO doxygen will only warn about wrong or incomplete parameter
universe@372 720 # documentation, but not about the absence of documentation.
universe@372 721 # The default value is: NO.
universe@372 722
universe@372 723 WARN_NO_PARAMDOC = YES
universe@372 724
universe@372 725 # The WARN_FORMAT tag determines the format of the warning messages that doxygen
universe@372 726 # can produce. The string should contain the $file, $line, and $text tags, which
universe@372 727 # will be replaced by the file and line number from which the warning originated
universe@372 728 # and the warning text. Optionally the format may contain $version, which will
universe@372 729 # be replaced by the version of the file (if it could be obtained via
universe@372 730 # FILE_VERSION_FILTER)
universe@372 731 # The default value is: $file:$line: $text.
universe@372 732
universe@372 733 WARN_FORMAT = "$file:$line: $text"
universe@372 734
universe@372 735 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
universe@372 736 # messages should be written. If left blank the output is written to standard
universe@372 737 # error (stderr).
universe@372 738
universe@372 739 WARN_LOGFILE =
universe@372 740
universe@372 741 #---------------------------------------------------------------------------
universe@372 742 # Configuration options related to the input files
universe@372 743 #---------------------------------------------------------------------------
universe@372 744
universe@372 745 # The INPUT tag is used to specify the files and/or directories that contain
universe@372 746 # documented source files. You may enter file names like myfile.cpp or
universe@372 747 # directories like /usr/src/myproject. Separate the files or directories with
universe@372 748 # spaces.
universe@372 749 # Note: If this tag is empty the current directory is searched.
universe@372 750
universe@372 751 INPUT = @DOXY_INPUT@
universe@372 752
universe@372 753 # This tag can be used to specify the character encoding of the source files
universe@372 754 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
universe@372 755 # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
universe@372 756 # documentation (see: http://www.gnu.org/software/libiconv) for the list of
universe@372 757 # possible encodings.
universe@372 758 # The default value is: UTF-8.
universe@372 759
universe@372 760 INPUT_ENCODING = UTF-8
universe@372 761
universe@372 762 # If the value of the INPUT tag contains directories, you can use the
universe@372 763 # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
universe@372 764 # *.h) to filter out the source-files in the directories. If left blank the
universe@372 765 # following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii,
universe@372 766 # *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp,
universe@372 767 # *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown,
universe@372 768 # *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf,
universe@372 769 # *.qsf, *.as and *.js.
universe@372 770
universe@372 771 FILE_PATTERNS =
universe@372 772
universe@372 773 # The RECURSIVE tag can be used to specify whether or not subdirectories should
universe@372 774 # be searched for input files as well.
universe@372 775 # The default value is: NO.
universe@372 776
universe@372 777 RECURSIVE = YES
universe@372 778
universe@372 779 # The EXCLUDE tag can be used to specify files and/or directories that should be
universe@372 780 # excluded from the INPUT source files. This way you can easily exclude a
universe@372 781 # subdirectory from a directory tree whose root is specified with the INPUT tag.
universe@372 782 #
universe@372 783 # Note that relative paths are relative to the directory from which doxygen is
universe@372 784 # run.
universe@372 785
universe@372 786 EXCLUDE =
universe@372 787
universe@372 788 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
universe@372 789 # directories that are symbolic links (a Unix file system feature) are excluded
universe@372 790 # from the input.
universe@372 791 # The default value is: NO.
universe@372 792
universe@372 793 EXCLUDE_SYMLINKS = NO
universe@372 794
universe@372 795 # If the value of the INPUT tag contains directories, you can use the
universe@372 796 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
universe@372 797 # certain files from those directories.
universe@372 798 #
universe@372 799 # Note that the wildcards are matched against the file with absolute path, so to
universe@372 800 # exclude all test directories for example use the pattern */test/*
universe@372 801
universe@372 802 EXCLUDE_PATTERNS =
universe@372 803
universe@372 804 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
universe@372 805 # (namespaces, classes, functions, etc.) that should be excluded from the
universe@372 806 # output. The symbol name can be a fully qualified name, a word, or if the
universe@372 807 # wildcard * is used, a substring. Examples: ANamespace, AClass,
universe@372 808 # AClass::ANamespace, ANamespace::*Test
universe@372 809 #
universe@372 810 # Note that the wildcards are matched against the file with absolute path, so to
universe@372 811 # exclude all test directories use the pattern */test/*
universe@372 812
universe@372 813 EXCLUDE_SYMBOLS =
universe@372 814
universe@372 815 # The EXAMPLE_PATH tag can be used to specify one or more files or directories
universe@372 816 # that contain example code fragments that are included (see the \include
universe@372 817 # command).
universe@372 818
universe@372 819 EXAMPLE_PATH =
universe@372 820
universe@372 821 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
universe@372 822 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
universe@372 823 # *.h) to filter out the source-files in the directories. If left blank all
universe@372 824 # files are included.
universe@372 825
universe@372 826 EXAMPLE_PATTERNS =
universe@372 827
universe@372 828 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
universe@372 829 # searched for input files to be used with the \include or \dontinclude commands
universe@372 830 # irrespective of the value of the RECURSIVE tag.
universe@372 831 # The default value is: NO.
universe@372 832
universe@372 833 EXAMPLE_RECURSIVE = NO
universe@372 834
universe@372 835 # The IMAGE_PATH tag can be used to specify one or more files or directories
universe@372 836 # that contain images that are to be included in the documentation (see the
universe@372 837 # \image command).
universe@372 838
universe@372 839 IMAGE_PATH =
universe@372 840
universe@372 841 # The INPUT_FILTER tag can be used to specify a program that doxygen should
universe@372 842 # invoke to filter for each input file. Doxygen will invoke the filter program
universe@372 843 # by executing (via popen()) the command:
universe@372 844 #
universe@372 845 # <filter> <input-file>
universe@372 846 #
universe@372 847 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
universe@372 848 # name of an input file. Doxygen will then use the output that the filter
universe@372 849 # program writes to standard output. If FILTER_PATTERNS is specified, this tag
universe@372 850 # will be ignored.
universe@372 851 #
universe@372 852 # Note that the filter must not add or remove lines; it is applied before the
universe@372 853 # code is scanned, but not when the output code is generated. If lines are added
universe@372 854 # or removed, the anchors will not be placed correctly.
universe@372 855
universe@372 856 INPUT_FILTER =
universe@372 857
universe@372 858 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
universe@372 859 # basis. Doxygen will compare the file name with each pattern and apply the
universe@372 860 # filter if there is a match. The filters are a list of the form: pattern=filter
universe@372 861 # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
universe@372 862 # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
universe@372 863 # patterns match the file name, INPUT_FILTER is applied.
universe@372 864
universe@372 865 FILTER_PATTERNS =
universe@372 866
universe@372 867 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
universe@372 868 # INPUT_FILTER ) will also be used to filter the input files that are used for
universe@372 869 # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
universe@372 870 # The default value is: NO.
universe@372 871
universe@372 872 FILTER_SOURCE_FILES = NO
universe@372 873
universe@372 874 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
universe@372 875 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
universe@372 876 # it is also possible to disable source filtering for a specific pattern using
universe@372 877 # *.ext= (so without naming a filter).
universe@372 878 # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
universe@372 879
universe@372 880 FILTER_SOURCE_PATTERNS =
universe@372 881
universe@372 882 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
universe@372 883 # is part of the input, its contents will be placed on the main page
universe@372 884 # (index.html). This can be useful if you have a project on for instance GitHub
universe@372 885 # and want to reuse the introduction page also for the doxygen output.
universe@372 886
universe@372 887 USE_MDFILE_AS_MAINPAGE =
universe@372 888
universe@372 889 #---------------------------------------------------------------------------
universe@372 890 # Configuration options related to source browsing
universe@372 891 #---------------------------------------------------------------------------
universe@372 892
universe@372 893 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
universe@372 894 # generated. Documented entities will be cross-referenced with these sources.
universe@372 895 #
universe@372 896 # Note: To get rid of all source code in the generated output, make sure that
universe@372 897 # also VERBATIM_HEADERS is set to NO.
universe@372 898 # The default value is: NO.
universe@372 899
universe@372 900 SOURCE_BROWSER = NO
universe@372 901
universe@372 902 # Setting the INLINE_SOURCES tag to YES will include the body of functions,
universe@372 903 # classes and enums directly into the documentation.
universe@372 904 # The default value is: NO.
universe@372 905
universe@372 906 INLINE_SOURCES = NO
universe@372 907
universe@372 908 # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
universe@372 909 # special comment blocks from generated source code fragments. Normal C, C++ and
universe@372 910 # Fortran comments will always remain visible.
universe@372 911 # The default value is: YES.
universe@372 912
universe@372 913 STRIP_CODE_COMMENTS = YES
universe@372 914
universe@372 915 # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
universe@372 916 # function all documented functions referencing it will be listed.
universe@372 917 # The default value is: NO.
universe@372 918
universe@372 919 REFERENCED_BY_RELATION = NO
universe@372 920
universe@372 921 # If the REFERENCES_RELATION tag is set to YES then for each documented function
universe@372 922 # all documented entities called/used by that function will be listed.
universe@372 923 # The default value is: NO.
universe@372 924
universe@372 925 REFERENCES_RELATION = NO
universe@372 926
universe@372 927 # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
universe@372 928 # to YES, then the hyperlinks from functions in REFERENCES_RELATION and
universe@372 929 # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
universe@372 930 # link to the documentation.
universe@372 931 # The default value is: YES.
universe@372 932
universe@372 933 REFERENCES_LINK_SOURCE = YES
universe@372 934
universe@372 935 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
universe@372 936 # source code will show a tooltip with additional information such as prototype,
universe@372 937 # brief description and links to the definition and documentation. Since this
universe@372 938 # will make the HTML file larger and loading of large files a bit slower, you
universe@372 939 # can opt to disable this feature.
universe@372 940 # The default value is: YES.
universe@372 941 # This tag requires that the tag SOURCE_BROWSER is set to YES.
universe@372 942
universe@372 943 SOURCE_TOOLTIPS = YES
universe@372 944
universe@372 945 # If the USE_HTAGS tag is set to YES then the references to source code will
universe@372 946 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
universe@372 947 # source browser. The htags tool is part of GNU's global source tagging system
universe@372 948 # (see http://www.gnu.org/software/global/global.html). You will need version
universe@372 949 # 4.8.6 or higher.
universe@372 950 #
universe@372 951 # To use it do the following:
universe@372 952 # - Install the latest version of global
universe@372 953 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
universe@372 954 # - Make sure the INPUT points to the root of the source tree
universe@372 955 # - Run doxygen as normal
universe@372 956 #
universe@372 957 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
universe@372 958 # tools must be available from the command line (i.e. in the search path).
universe@372 959 #
universe@372 960 # The result: instead of the source browser generated by doxygen, the links to
universe@372 961 # source code will now point to the output of htags.
universe@372 962 # The default value is: NO.
universe@372 963 # This tag requires that the tag SOURCE_BROWSER is set to YES.
universe@372 964
universe@372 965 USE_HTAGS = NO
universe@372 966
universe@372 967 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
universe@372 968 # verbatim copy of the header file for each class for which an include is
universe@372 969 # specified. Set to NO to disable this.
universe@372 970 # See also: Section \class.
universe@372 971 # The default value is: YES.
universe@372 972
universe@372 973 VERBATIM_HEADERS = YES
universe@372 974
universe@372 975 #---------------------------------------------------------------------------
universe@372 976 # Configuration options related to the alphabetical class index
universe@372 977 #---------------------------------------------------------------------------
universe@372 978
universe@372 979 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
universe@372 980 # compounds will be generated. Enable this if the project contains a lot of
universe@372 981 # classes, structs, unions or interfaces.
universe@372 982 # The default value is: YES.
universe@372 983
universe@372 984 ALPHABETICAL_INDEX = YES
universe@372 985
universe@372 986 # In case all classes in a project start with a common prefix, all classes will
universe@372 987 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
universe@372 988 # can be used to specify a prefix (or a list of prefixes) that should be ignored
universe@372 989 # while generating the index headers.
universe@372 990 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
universe@372 991
universe@372 992 IGNORE_PREFIX =
universe@372 993
universe@372 994 #---------------------------------------------------------------------------
universe@372 995 # Configuration options related to the HTML output
universe@372 996 #---------------------------------------------------------------------------
universe@372 997
universe@372 998 # If the GENERATE_HTML tag is set to YES doxygen will generate HTML output
universe@372 999 # The default value is: YES.
universe@372 1000
universe@372 1001 GENERATE_HTML = YES
universe@372 1002
universe@372 1003 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
universe@372 1004 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
universe@372 1005 # it.
universe@372 1006 # The default directory is: html.
universe@372 1007 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1008
universe@372 1009 HTML_OUTPUT = web/api
universe@372 1010
universe@372 1011 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
universe@372 1012 # generated HTML page (for example: .htm, .php, .asp).
universe@372 1013 # The default value is: .html.
universe@372 1014 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1015
universe@372 1016 HTML_FILE_EXTENSION = .html
universe@372 1017
universe@372 1018 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
universe@372 1019 # each generated HTML page. If the tag is left blank doxygen will generate a
universe@372 1020 # standard header.
universe@372 1021 #
universe@372 1022 # To get valid HTML the header file that includes any scripts and style sheets
universe@372 1023 # that doxygen needs, which is dependent on the configuration options used (e.g.
universe@372 1024 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
universe@372 1025 # default header using
universe@372 1026 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
universe@372 1027 # YourConfigFile
universe@372 1028 # and then modify the file new_header.html. See also section "Doxygen usage"
universe@372 1029 # for information on how to generate the default header that doxygen normally
universe@372 1030 # uses.
universe@372 1031 # Note: The header is subject to change so you typically have to regenerate the
universe@372 1032 # default header when upgrading to a newer version of doxygen. For a description
universe@372 1033 # of the possible markers and block names see the documentation.
universe@372 1034 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1035
universe@372 1036 HTML_HEADER =
universe@372 1037
universe@372 1038 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
universe@372 1039 # generated HTML page. If the tag is left blank doxygen will generate a standard
universe@372 1040 # footer. See HTML_HEADER for more information on how to generate a default
universe@372 1041 # footer and what special commands can be used inside the footer. See also
universe@372 1042 # section "Doxygen usage" for information on how to generate the default footer
universe@372 1043 # that doxygen normally uses.
universe@372 1044 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1045
universe@372 1046 HTML_FOOTER =
universe@372 1047
universe@372 1048 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
universe@372 1049 # sheet that is used by each HTML page. It can be used to fine-tune the look of
universe@372 1050 # the HTML output. If left blank doxygen will generate a default style sheet.
universe@372 1051 # See also section "Doxygen usage" for information on how to generate the style
universe@372 1052 # sheet that doxygen normally uses.
universe@372 1053 # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
universe@372 1054 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
universe@372 1055 # obsolete.
universe@372 1056 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1057
universe@372 1058 HTML_STYLESHEET =
universe@372 1059
universe@372 1060 # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
universe@372 1061 # defined cascading style sheet that is included after the standard style sheets
universe@372 1062 # created by doxygen. Using this option one can overrule certain style aspects.
universe@372 1063 # This is preferred over using HTML_STYLESHEET since it does not replace the
universe@372 1064 # standard style sheet and is therefor more robust against future updates.
universe@372 1065 # Doxygen will copy the style sheet file to the output directory. For an example
universe@372 1066 # see the documentation.
universe@372 1067 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1068
universe@372 1069 HTML_EXTRA_STYLESHEET =
universe@372 1070
universe@372 1071 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
universe@372 1072 # other source files which should be copied to the HTML output directory. Note
universe@372 1073 # that these files will be copied to the base HTML output directory. Use the
universe@372 1074 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
universe@372 1075 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
universe@372 1076 # files will be copied as-is; there are no commands or markers available.
universe@372 1077 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1078
universe@372 1079 HTML_EXTRA_FILES =
universe@372 1080
universe@372 1081 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
universe@372 1082 # will adjust the colors in the stylesheet and background images according to
universe@372 1083 # this color. Hue is specified as an angle on a colorwheel, see
universe@372 1084 # http://en.wikipedia.org/wiki/Hue for more information. For instance the value
universe@372 1085 # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
universe@372 1086 # purple, and 360 is red again.
universe@372 1087 # Minimum value: 0, maximum value: 359, default value: 220.
universe@372 1088 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1089
universe@372 1090 HTML_COLORSTYLE_HUE = 220
universe@372 1091
universe@372 1092 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
universe@372 1093 # in the HTML output. For a value of 0 the output will use grayscales only. A
universe@372 1094 # value of 255 will produce the most vivid colors.
universe@372 1095 # Minimum value: 0, maximum value: 255, default value: 100.
universe@372 1096 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1097
universe@372 1098 HTML_COLORSTYLE_SAT = 100
universe@372 1099
universe@372 1100 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
universe@372 1101 # luminance component of the colors in the HTML output. Values below 100
universe@372 1102 # gradually make the output lighter, whereas values above 100 make the output
universe@372 1103 # darker. The value divided by 100 is the actual gamma applied, so 80 represents
universe@372 1104 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
universe@372 1105 # change the gamma.
universe@372 1106 # Minimum value: 40, maximum value: 240, default value: 80.
universe@372 1107 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1108
universe@372 1109 HTML_COLORSTYLE_GAMMA = 80
universe@372 1110
universe@372 1111 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
universe@372 1112 # page will contain the date and time when the page was generated. Setting this
universe@372 1113 # to NO can help when comparing the output of multiple runs.
universe@372 1114 # The default value is: YES.
universe@372 1115 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1116
universe@372 1117 HTML_TIMESTAMP = YES
universe@372 1118
universe@372 1119 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
universe@372 1120 # documentation will contain sections that can be hidden and shown after the
universe@372 1121 # page has loaded.
universe@372 1122 # The default value is: NO.
universe@372 1123 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1124
universe@372 1125 HTML_DYNAMIC_SECTIONS = NO
universe@372 1126
universe@372 1127 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
universe@372 1128 # shown in the various tree structured indices initially; the user can expand
universe@372 1129 # and collapse entries dynamically later on. Doxygen will expand the tree to
universe@372 1130 # such a level that at most the specified number of entries are visible (unless
universe@372 1131 # a fully collapsed tree already exceeds this amount). So setting the number of
universe@372 1132 # entries 1 will produce a full collapsed tree by default. 0 is a special value
universe@372 1133 # representing an infinite number of entries and will result in a full expanded
universe@372 1134 # tree by default.
universe@372 1135 # Minimum value: 0, maximum value: 9999, default value: 100.
universe@372 1136 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1137
universe@372 1138 HTML_INDEX_NUM_ENTRIES = 100
universe@372 1139
universe@372 1140 # If the GENERATE_DOCSET tag is set to YES, additional index files will be
universe@372 1141 # generated that can be used as input for Apple's Xcode 3 integrated development
universe@372 1142 # environment (see: http://developer.apple.com/tools/xcode/), introduced with
universe@372 1143 # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
universe@372 1144 # Makefile in the HTML output directory. Running make will produce the docset in
universe@372 1145 # that directory and running make install will install the docset in
universe@372 1146 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
universe@372 1147 # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
universe@372 1148 # for more information.
universe@372 1149 # The default value is: NO.
universe@372 1150 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1151
universe@372 1152 GENERATE_DOCSET = NO
universe@372 1153
universe@372 1154 # This tag determines the name of the docset feed. A documentation feed provides
universe@372 1155 # an umbrella under which multiple documentation sets from a single provider
universe@372 1156 # (such as a company or product suite) can be grouped.
universe@372 1157 # The default value is: Doxygen generated docs.
universe@372 1158 # This tag requires that the tag GENERATE_DOCSET is set to YES.
universe@372 1159
universe@372 1160 DOCSET_FEEDNAME = "Doxygen generated docs"
universe@372 1161
universe@372 1162 # This tag specifies a string that should uniquely identify the documentation
universe@372 1163 # set bundle. This should be a reverse domain-name style string, e.g.
universe@372 1164 # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
universe@372 1165 # The default value is: org.doxygen.Project.
universe@372 1166 # This tag requires that the tag GENERATE_DOCSET is set to YES.
universe@372 1167
universe@372 1168 DOCSET_BUNDLE_ID = org.doxygen.Project
universe@372 1169
universe@372 1170 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
universe@372 1171 # the documentation publisher. This should be a reverse domain-name style
universe@372 1172 # string, e.g. com.mycompany.MyDocSet.documentation.
universe@372 1173 # The default value is: org.doxygen.Publisher.
universe@372 1174 # This tag requires that the tag GENERATE_DOCSET is set to YES.
universe@372 1175
universe@372 1176 DOCSET_PUBLISHER_ID = org.doxygen.Publisher
universe@372 1177
universe@372 1178 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
universe@372 1179 # The default value is: Publisher.
universe@372 1180 # This tag requires that the tag GENERATE_DOCSET is set to YES.
universe@372 1181
universe@372 1182 DOCSET_PUBLISHER_NAME = Publisher
universe@372 1183
universe@372 1184 # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
universe@372 1185 # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
universe@372 1186 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
universe@372 1187 # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
universe@372 1188 # Windows.
universe@372 1189 #
universe@372 1190 # The HTML Help Workshop contains a compiler that can convert all HTML output
universe@372 1191 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
universe@372 1192 # files are now used as the Windows 98 help format, and will replace the old
universe@372 1193 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
universe@372 1194 # HTML files also contain an index, a table of contents, and you can search for
universe@372 1195 # words in the documentation. The HTML workshop also contains a viewer for
universe@372 1196 # compressed HTML files.
universe@372 1197 # The default value is: NO.
universe@372 1198 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1199
universe@372 1200 GENERATE_HTMLHELP = NO
universe@372 1201
universe@372 1202 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
universe@372 1203 # file. You can add a path in front of the file if the result should not be
universe@372 1204 # written to the html output directory.
universe@372 1205 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
universe@372 1206
universe@372 1207 CHM_FILE =
universe@372 1208
universe@372 1209 # The HHC_LOCATION tag can be used to specify the location (absolute path
universe@372 1210 # including file name) of the HTML help compiler ( hhc.exe). If non-empty
universe@372 1211 # doxygen will try to run the HTML help compiler on the generated index.hhp.
universe@372 1212 # The file has to be specified with full path.
universe@372 1213 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
universe@372 1214
universe@372 1215 HHC_LOCATION =
universe@372 1216
universe@372 1217 # The GENERATE_CHI flag controls if a separate .chi index file is generated (
universe@372 1218 # YES) or that it should be included in the master .chm file ( NO).
universe@372 1219 # The default value is: NO.
universe@372 1220 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
universe@372 1221
universe@372 1222 GENERATE_CHI = NO
universe@372 1223
universe@372 1224 # The CHM_INDEX_ENCODING is used to encode HtmlHelp index ( hhk), content ( hhc)
universe@372 1225 # and project file content.
universe@372 1226 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
universe@372 1227
universe@372 1228 CHM_INDEX_ENCODING =
universe@372 1229
universe@372 1230 # The BINARY_TOC flag controls whether a binary table of contents is generated (
universe@372 1231 # YES) or a normal table of contents ( NO) in the .chm file. Furthermore it
universe@372 1232 # enables the Previous and Next buttons.
universe@372 1233 # The default value is: NO.
universe@372 1234 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
universe@372 1235
universe@372 1236 BINARY_TOC = NO
universe@372 1237
universe@372 1238 # The TOC_EXPAND flag can be set to YES to add extra items for group members to
universe@372 1239 # the table of contents of the HTML help documentation and to the tree view.
universe@372 1240 # The default value is: NO.
universe@372 1241 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
universe@372 1242
universe@372 1243 TOC_EXPAND = NO
universe@372 1244
universe@372 1245 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
universe@372 1246 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
universe@372 1247 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
universe@372 1248 # (.qch) of the generated HTML documentation.
universe@372 1249 # The default value is: NO.
universe@372 1250 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1251
universe@372 1252 GENERATE_QHP = NO
universe@372 1253
universe@372 1254 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
universe@372 1255 # the file name of the resulting .qch file. The path specified is relative to
universe@372 1256 # the HTML output folder.
universe@372 1257 # This tag requires that the tag GENERATE_QHP is set to YES.
universe@372 1258
universe@372 1259 QCH_FILE =
universe@372 1260
universe@372 1261 # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
universe@372 1262 # Project output. For more information please see Qt Help Project / Namespace
universe@372 1263 # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
universe@372 1264 # The default value is: org.doxygen.Project.
universe@372 1265 # This tag requires that the tag GENERATE_QHP is set to YES.
universe@372 1266
universe@372 1267 QHP_NAMESPACE = org.doxygen.Project
universe@372 1268
universe@372 1269 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
universe@372 1270 # Help Project output. For more information please see Qt Help Project / Virtual
universe@372 1271 # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
universe@372 1272 # folders).
universe@372 1273 # The default value is: doc.
universe@372 1274 # This tag requires that the tag GENERATE_QHP is set to YES.
universe@372 1275
universe@372 1276 QHP_VIRTUAL_FOLDER = doc
universe@372 1277
universe@372 1278 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
universe@372 1279 # filter to add. For more information please see Qt Help Project / Custom
universe@372 1280 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
universe@372 1281 # filters).
universe@372 1282 # This tag requires that the tag GENERATE_QHP is set to YES.
universe@372 1283
universe@372 1284 QHP_CUST_FILTER_NAME =
universe@372 1285
universe@372 1286 # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
universe@372 1287 # custom filter to add. For more information please see Qt Help Project / Custom
universe@372 1288 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
universe@372 1289 # filters).
universe@372 1290 # This tag requires that the tag GENERATE_QHP is set to YES.
universe@372 1291
universe@372 1292 QHP_CUST_FILTER_ATTRS =
universe@372 1293
universe@372 1294 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
universe@372 1295 # project's filter section matches. Qt Help Project / Filter Attributes (see:
universe@372 1296 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
universe@372 1297 # This tag requires that the tag GENERATE_QHP is set to YES.
universe@372 1298
universe@372 1299 QHP_SECT_FILTER_ATTRS =
universe@372 1300
universe@372 1301 # The QHG_LOCATION tag can be used to specify the location of Qt's
universe@372 1302 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
universe@372 1303 # generated .qhp file.
universe@372 1304 # This tag requires that the tag GENERATE_QHP is set to YES.
universe@372 1305
universe@372 1306 QHG_LOCATION =
universe@372 1307
universe@372 1308 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
universe@372 1309 # generated, together with the HTML files, they form an Eclipse help plugin. To
universe@372 1310 # install this plugin and make it available under the help contents menu in
universe@372 1311 # Eclipse, the contents of the directory containing the HTML and XML files needs
universe@372 1312 # to be copied into the plugins directory of eclipse. The name of the directory
universe@372 1313 # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
universe@372 1314 # After copying Eclipse needs to be restarted before the help appears.
universe@372 1315 # The default value is: NO.
universe@372 1316 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1317
universe@372 1318 GENERATE_ECLIPSEHELP = NO
universe@372 1319
universe@372 1320 # A unique identifier for the Eclipse help plugin. When installing the plugin
universe@372 1321 # the directory name containing the HTML and XML files should also have this
universe@372 1322 # name. Each documentation set should have its own identifier.
universe@372 1323 # The default value is: org.doxygen.Project.
universe@372 1324 # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
universe@372 1325
universe@372 1326 ECLIPSE_DOC_ID = org.doxygen.Project
universe@372 1327
universe@372 1328 # If you want full control over the layout of the generated HTML pages it might
universe@372 1329 # be necessary to disable the index and replace it with your own. The
universe@372 1330 # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
universe@372 1331 # of each HTML page. A value of NO enables the index and the value YES disables
universe@372 1332 # it. Since the tabs in the index contain the same information as the navigation
universe@372 1333 # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
universe@372 1334 # The default value is: NO.
universe@372 1335 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1336
universe@372 1337 DISABLE_INDEX = NO
universe@372 1338
universe@372 1339 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
universe@372 1340 # structure should be generated to display hierarchical information. If the tag
universe@372 1341 # value is set to YES, a side panel will be generated containing a tree-like
universe@372 1342 # index structure (just like the one that is generated for HTML Help). For this
universe@372 1343 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
universe@372 1344 # (i.e. any modern browser). Windows users are probably better off using the
universe@372 1345 # HTML help feature. Via custom stylesheets (see HTML_EXTRA_STYLESHEET) one can
universe@372 1346 # further fine-tune the look of the index. As an example, the default style
universe@372 1347 # sheet generated by doxygen has an example that shows how to put an image at
universe@372 1348 # the root of the tree instead of the PROJECT_NAME. Since the tree basically has
universe@372 1349 # the same information as the tab index, you could consider setting
universe@372 1350 # DISABLE_INDEX to YES when enabling this option.
universe@372 1351 # The default value is: NO.
universe@372 1352 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1353
universe@372 1354 GENERATE_TREEVIEW = NO
universe@372 1355
universe@372 1356 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
universe@372 1357 # doxygen will group on one line in the generated HTML documentation.
universe@372 1358 #
universe@372 1359 # Note that a value of 0 will completely suppress the enum values from appearing
universe@372 1360 # in the overview section.
universe@372 1361 # Minimum value: 0, maximum value: 20, default value: 4.
universe@372 1362 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1363
universe@372 1364 ENUM_VALUES_PER_LINE = 4
universe@372 1365
universe@372 1366 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
universe@372 1367 # to set the initial width (in pixels) of the frame in which the tree is shown.
universe@372 1368 # Minimum value: 0, maximum value: 1500, default value: 250.
universe@372 1369 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1370
universe@372 1371 TREEVIEW_WIDTH = 250
universe@372 1372
universe@372 1373 # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open links to
universe@372 1374 # external symbols imported via tag files in a separate window.
universe@372 1375 # The default value is: NO.
universe@372 1376 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1377
universe@372 1378 EXT_LINKS_IN_WINDOW = NO
universe@372 1379
universe@372 1380 # Use this tag to change the font size of LaTeX formulas included as images in
universe@372 1381 # the HTML documentation. When you change the font size after a successful
universe@372 1382 # doxygen run you need to manually remove any form_*.png images from the HTML
universe@372 1383 # output directory to force them to be regenerated.
universe@372 1384 # Minimum value: 8, maximum value: 50, default value: 10.
universe@372 1385 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1386
universe@372 1387 FORMULA_FONTSIZE = 10
universe@372 1388
universe@372 1389 # Use the FORMULA_TRANPARENT tag to determine whether or not the images
universe@372 1390 # generated for formulas are transparent PNGs. Transparent PNGs are not
universe@372 1391 # supported properly for IE 6.0, but are supported on all modern browsers.
universe@372 1392 #
universe@372 1393 # Note that when changing this option you need to delete any form_*.png files in
universe@372 1394 # the HTML output directory before the changes have effect.
universe@372 1395 # The default value is: YES.
universe@372 1396 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1397
universe@372 1398 FORMULA_TRANSPARENT = YES
universe@372 1399
universe@372 1400 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
universe@372 1401 # http://www.mathjax.org) which uses client side Javascript for the rendering
universe@372 1402 # instead of using prerendered bitmaps. Use this if you do not have LaTeX
universe@372 1403 # installed or if you want to formulas look prettier in the HTML output. When
universe@372 1404 # enabled you may also need to install MathJax separately and configure the path
universe@372 1405 # to it using the MATHJAX_RELPATH option.
universe@372 1406 # The default value is: NO.
universe@372 1407 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1408
universe@372 1409 USE_MATHJAX = NO
universe@372 1410
universe@372 1411 # When MathJax is enabled you can set the default output format to be used for
universe@372 1412 # the MathJax output. See the MathJax site (see:
universe@372 1413 # http://docs.mathjax.org/en/latest/output.html) for more details.
universe@372 1414 # Possible values are: HTML-CSS (which is slower, but has the best
universe@372 1415 # compatibility), NativeMML (i.e. MathML) and SVG.
universe@372 1416 # The default value is: HTML-CSS.
universe@372 1417 # This tag requires that the tag USE_MATHJAX is set to YES.
universe@372 1418
universe@372 1419 MATHJAX_FORMAT = HTML-CSS
universe@372 1420
universe@372 1421 # When MathJax is enabled you need to specify the location relative to the HTML
universe@372 1422 # output directory using the MATHJAX_RELPATH option. The destination directory
universe@372 1423 # should contain the MathJax.js script. For instance, if the mathjax directory
universe@372 1424 # is located at the same level as the HTML output directory, then
universe@372 1425 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
universe@372 1426 # Content Delivery Network so you can quickly see the result without installing
universe@372 1427 # MathJax. However, it is strongly recommended to install a local copy of
universe@372 1428 # MathJax from http://www.mathjax.org before deployment.
universe@372 1429 # The default value is: http://cdn.mathjax.org/mathjax/latest.
universe@372 1430 # This tag requires that the tag USE_MATHJAX is set to YES.
universe@372 1431
universe@372 1432 MATHJAX_RELPATH = http://www.mathjax.org/mathjax
universe@372 1433
universe@372 1434 # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
universe@372 1435 # extension names that should be enabled during MathJax rendering. For example
universe@372 1436 # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
universe@372 1437 # This tag requires that the tag USE_MATHJAX is set to YES.
universe@372 1438
universe@372 1439 MATHJAX_EXTENSIONS =
universe@372 1440
universe@372 1441 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
universe@372 1442 # of code that will be used on startup of the MathJax code. See the MathJax site
universe@372 1443 # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
universe@372 1444 # example see the documentation.
universe@372 1445 # This tag requires that the tag USE_MATHJAX is set to YES.
universe@372 1446
universe@372 1447 MATHJAX_CODEFILE =
universe@372 1448
universe@372 1449 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
universe@372 1450 # the HTML output. The underlying search engine uses javascript and DHTML and
universe@372 1451 # should work on any modern browser. Note that when using HTML help
universe@372 1452 # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
universe@372 1453 # there is already a search function so this one should typically be disabled.
universe@372 1454 # For large projects the javascript based search engine can be slow, then
universe@372 1455 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
universe@372 1456 # search using the keyboard; to jump to the search box use <access key> + S
universe@372 1457 # (what the <access key> is depends on the OS and browser, but it is typically
universe@372 1458 # <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
universe@372 1459 # key> to jump into the search results window, the results can be navigated
universe@372 1460 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
universe@372 1461 # the search. The filter options can be selected when the cursor is inside the
universe@372 1462 # search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
universe@372 1463 # to select a filter and <Enter> or <escape> to activate or cancel the filter
universe@372 1464 # option.
universe@372 1465 # The default value is: YES.
universe@372 1466 # This tag requires that the tag GENERATE_HTML is set to YES.
universe@372 1467
universe@372 1468 SEARCHENGINE = YES
universe@372 1469
universe@372 1470 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
universe@372 1471 # implemented using a web server instead of a web client using Javascript. There
universe@372 1472 # are two flavors of web server based searching depending on the EXTERNAL_SEARCH
universe@372 1473 # setting. When disabled, doxygen will generate a PHP script for searching and
universe@372 1474 # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
universe@372 1475 # and searching needs to be provided by external tools. See the section
universe@372 1476 # "External Indexing and Searching" for details.
universe@372 1477 # The default value is: NO.
universe@372 1478 # This tag requires that the tag SEARCHENGINE is set to YES.
universe@372 1479
universe@372 1480 SERVER_BASED_SEARCH = NO
universe@372 1481
universe@372 1482 # When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
universe@372 1483 # script for searching. Instead the search results are written to an XML file
universe@372 1484 # which needs to be processed by an external indexer. Doxygen will invoke an
universe@372 1485 # external search engine pointed to by the SEARCHENGINE_URL option to obtain the
universe@372 1486 # search results.
universe@372 1487 #
universe@372 1488 # Doxygen ships with an example indexer ( doxyindexer) and search engine
universe@372 1489 # (doxysearch.cgi) which are based on the open source search engine library
universe@372 1490 # Xapian (see: http://xapian.org/).
universe@372 1491 #
universe@372 1492 # See the section "External Indexing and Searching" for details.
universe@372 1493 # The default value is: NO.
universe@372 1494 # This tag requires that the tag SEARCHENGINE is set to YES.
universe@372 1495
universe@372 1496 EXTERNAL_SEARCH = NO
universe@372 1497
universe@372 1498 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
universe@372 1499 # which will return the search results when EXTERNAL_SEARCH is enabled.
universe@372 1500 #
universe@372 1501 # Doxygen ships with an example indexer ( doxyindexer) and search engine
universe@372 1502 # (doxysearch.cgi) which are based on the open source search engine library
universe@372 1503 # Xapian (see: http://xapian.org/). See the section "External Indexing and
universe@372 1504 # Searching" for details.
universe@372 1505 # This tag requires that the tag SEARCHENGINE is set to YES.
universe@372 1506
universe@372 1507 SEARCHENGINE_URL =
universe@372 1508
universe@372 1509 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
universe@372 1510 # search data is written to a file for indexing by an external tool. With the
universe@372 1511 # SEARCHDATA_FILE tag the name of this file can be specified.
universe@372 1512 # The default file is: searchdata.xml.
universe@372 1513 # This tag requires that the tag SEARCHENGINE is set to YES.
universe@372 1514
universe@372 1515 SEARCHDATA_FILE = searchdata.xml
universe@372 1516
universe@372 1517 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
universe@372 1518 # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
universe@372 1519 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
universe@372 1520 # projects and redirect the results back to the right project.
universe@372 1521 # This tag requires that the tag SEARCHENGINE is set to YES.
universe@372 1522
universe@372 1523 EXTERNAL_SEARCH_ID =
universe@372 1524
universe@372 1525 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
universe@372 1526 # projects other than the one defined by this configuration file, but that are
universe@372 1527 # all added to the same external search index. Each project needs to have a
universe@372 1528 # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
universe@372 1529 # to a relative location where the documentation can be found. The format is:
universe@372 1530 # EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
universe@372 1531 # This tag requires that the tag SEARCHENGINE is set to YES.
universe@372 1532
universe@372 1533 EXTRA_SEARCH_MAPPINGS =
universe@372 1534
universe@372 1535 #---------------------------------------------------------------------------
universe@372 1536 # Configuration options related to the LaTeX output
universe@372 1537 #---------------------------------------------------------------------------
universe@372 1538
universe@372 1539 # If the GENERATE_LATEX tag is set to YES doxygen will generate LaTeX output.
universe@372 1540 # The default value is: YES.
universe@372 1541
universe@372 1542 GENERATE_LATEX = NO
universe@372 1543
universe@372 1544 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
universe@372 1545 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
universe@372 1546 # it.
universe@372 1547 # The default directory is: latex.
universe@372 1548 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1549
universe@372 1550 LATEX_OUTPUT = latex
universe@372 1551
universe@372 1552 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
universe@372 1553 # invoked.
universe@372 1554 #
universe@372 1555 # Note that when enabling USE_PDFLATEX this option is only used for generating
universe@372 1556 # bitmaps for formulas in the HTML output, but not in the Makefile that is
universe@372 1557 # written to the output directory.
universe@372 1558 # The default file is: latex.
universe@372 1559 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1560
universe@372 1561 LATEX_CMD_NAME = latex
universe@372 1562
universe@372 1563 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
universe@372 1564 # index for LaTeX.
universe@372 1565 # The default file is: makeindex.
universe@372 1566 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1567
universe@372 1568 MAKEINDEX_CMD_NAME = makeindex
universe@372 1569
universe@372 1570 # If the COMPACT_LATEX tag is set to YES doxygen generates more compact LaTeX
universe@372 1571 # documents. This may be useful for small projects and may help to save some
universe@372 1572 # trees in general.
universe@372 1573 # The default value is: NO.
universe@372 1574 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1575
universe@372 1576 COMPACT_LATEX = NO
universe@372 1577
universe@372 1578 # The PAPER_TYPE tag can be used to set the paper type that is used by the
universe@372 1579 # printer.
universe@372 1580 # Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
universe@372 1581 # 14 inches) and executive (7.25 x 10.5 inches).
universe@372 1582 # The default value is: a4.
universe@372 1583 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1584
universe@372 1585 PAPER_TYPE = a4
universe@372 1586
universe@372 1587 # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
universe@372 1588 # that should be included in the LaTeX output. To get the times font for
universe@372 1589 # instance you can specify
universe@372 1590 # EXTRA_PACKAGES=times
universe@372 1591 # If left blank no extra packages will be included.
universe@372 1592 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1593
universe@372 1594 EXTRA_PACKAGES =
universe@372 1595
universe@372 1596 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
universe@372 1597 # generated LaTeX document. The header should contain everything until the first
universe@372 1598 # chapter. If it is left blank doxygen will generate a standard header. See
universe@372 1599 # section "Doxygen usage" for information on how to let doxygen write the
universe@372 1600 # default header to a separate file.
universe@372 1601 #
universe@372 1602 # Note: Only use a user-defined header if you know what you are doing! The
universe@372 1603 # following commands have a special meaning inside the header: $title,
universe@372 1604 # $datetime, $date, $doxygenversion, $projectname, $projectnumber. Doxygen will
universe@372 1605 # replace them by respectively the title of the page, the current date and time,
universe@372 1606 # only the current date, the version number of doxygen, the project name (see
universe@372 1607 # PROJECT_NAME), or the project number (see PROJECT_NUMBER).
universe@372 1608 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1609
universe@372 1610 LATEX_HEADER =
universe@372 1611
universe@372 1612 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
universe@372 1613 # generated LaTeX document. The footer should contain everything after the last
universe@372 1614 # chapter. If it is left blank doxygen will generate a standard footer.
universe@372 1615 #
universe@372 1616 # Note: Only use a user-defined footer if you know what you are doing!
universe@372 1617 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1618
universe@372 1619 LATEX_FOOTER =
universe@372 1620
universe@372 1621 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
universe@372 1622 # other source files which should be copied to the LATEX_OUTPUT output
universe@372 1623 # directory. Note that the files will be copied as-is; there are no commands or
universe@372 1624 # markers available.
universe@372 1625 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1626
universe@372 1627 LATEX_EXTRA_FILES =
universe@372 1628
universe@372 1629 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
universe@372 1630 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
universe@372 1631 # contain links (just like the HTML output) instead of page references. This
universe@372 1632 # makes the output suitable for online browsing using a PDF viewer.
universe@372 1633 # The default value is: YES.
universe@372 1634 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1635
universe@372 1636 PDF_HYPERLINKS = YES
universe@372 1637
universe@372 1638 # If the LATEX_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
universe@372 1639 # the PDF file directly from the LaTeX files. Set this option to YES to get a
universe@372 1640 # higher quality PDF documentation.
universe@372 1641 # The default value is: YES.
universe@372 1642 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1643
universe@372 1644 USE_PDFLATEX = YES
universe@372 1645
universe@372 1646 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
universe@372 1647 # command to the generated LaTeX files. This will instruct LaTeX to keep running
universe@372 1648 # if errors occur, instead of asking the user for help. This option is also used
universe@372 1649 # when generating formulas in HTML.
universe@372 1650 # The default value is: NO.
universe@372 1651 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1652
universe@372 1653 LATEX_BATCHMODE = NO
universe@372 1654
universe@372 1655 # If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
universe@372 1656 # index chapters (such as File Index, Compound Index, etc.) in the output.
universe@372 1657 # The default value is: NO.
universe@372 1658 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1659
universe@372 1660 LATEX_HIDE_INDICES = NO
universe@372 1661
universe@372 1662 # If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
universe@372 1663 # code with syntax highlighting in the LaTeX output.
universe@372 1664 #
universe@372 1665 # Note that which sources are shown also depends on other settings such as
universe@372 1666 # SOURCE_BROWSER.
universe@372 1667 # The default value is: NO.
universe@372 1668 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1669
universe@372 1670 LATEX_SOURCE_CODE = NO
universe@372 1671
universe@372 1672 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
universe@372 1673 # bibliography, e.g. plainnat, or ieeetr. See
universe@372 1674 # http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
universe@372 1675 # The default value is: plain.
universe@372 1676 # This tag requires that the tag GENERATE_LATEX is set to YES.
universe@372 1677
universe@372 1678 LATEX_BIB_STYLE = plain
universe@372 1679
universe@372 1680 #---------------------------------------------------------------------------
universe@372 1681 # Configuration options related to the RTF output
universe@372 1682 #---------------------------------------------------------------------------
universe@372 1683
universe@372 1684 # If the GENERATE_RTF tag is set to YES doxygen will generate RTF output. The
universe@372 1685 # RTF output is optimized for Word 97 and may not look too pretty with other RTF
universe@372 1686 # readers/editors.
universe@372 1687 # The default value is: NO.
universe@372 1688
universe@372 1689 GENERATE_RTF = NO
universe@372 1690
universe@372 1691 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
universe@372 1692 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
universe@372 1693 # it.
universe@372 1694 # The default directory is: rtf.
universe@372 1695 # This tag requires that the tag GENERATE_RTF is set to YES.
universe@372 1696
universe@372 1697 RTF_OUTPUT = rtf
universe@372 1698
universe@372 1699 # If the COMPACT_RTF tag is set to YES doxygen generates more compact RTF
universe@372 1700 # documents. This may be useful for small projects and may help to save some
universe@372 1701 # trees in general.
universe@372 1702 # The default value is: NO.
universe@372 1703 # This tag requires that the tag GENERATE_RTF is set to YES.
universe@372 1704
universe@372 1705 COMPACT_RTF = NO
universe@372 1706
universe@372 1707 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
universe@372 1708 # contain hyperlink fields. The RTF file will contain links (just like the HTML
universe@372 1709 # output) instead of page references. This makes the output suitable for online
universe@372 1710 # browsing using Word or some other Word compatible readers that support those
universe@372 1711 # fields.
universe@372 1712 #
universe@372 1713 # Note: WordPad (write) and others do not support links.
universe@372 1714 # The default value is: NO.
universe@372 1715 # This tag requires that the tag GENERATE_RTF is set to YES.
universe@372 1716
universe@372 1717 RTF_HYPERLINKS = NO
universe@372 1718
universe@372 1719 # Load stylesheet definitions from file. Syntax is similar to doxygen's config
universe@372 1720 # file, i.e. a series of assignments. You only have to provide replacements,
universe@372 1721 # missing definitions are set to their default value.
universe@372 1722 #
universe@372 1723 # See also section "Doxygen usage" for information on how to generate the
universe@372 1724 # default style sheet that doxygen normally uses.
universe@372 1725 # This tag requires that the tag GENERATE_RTF is set to YES.
universe@372 1726
universe@372 1727 RTF_STYLESHEET_FILE =
universe@372 1728
universe@372 1729 # Set optional variables used in the generation of an RTF document. Syntax is
universe@372 1730 # similar to doxygen's config file. A template extensions file can be generated
universe@372 1731 # using doxygen -e rtf extensionFile.
universe@372 1732 # This tag requires that the tag GENERATE_RTF is set to YES.
universe@372 1733
universe@372 1734 RTF_EXTENSIONS_FILE =
universe@372 1735
universe@372 1736 #---------------------------------------------------------------------------
universe@372 1737 # Configuration options related to the man page output
universe@372 1738 #---------------------------------------------------------------------------
universe@372 1739
universe@372 1740 # If the GENERATE_MAN tag is set to YES doxygen will generate man pages for
universe@372 1741 # classes and files.
universe@372 1742 # The default value is: NO.
universe@372 1743
universe@372 1744 GENERATE_MAN = NO
universe@372 1745
universe@372 1746 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
universe@372 1747 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
universe@372 1748 # it. A directory man3 will be created inside the directory specified by
universe@372 1749 # MAN_OUTPUT.
universe@372 1750 # The default directory is: man.
universe@372 1751 # This tag requires that the tag GENERATE_MAN is set to YES.
universe@372 1752
universe@372 1753 MAN_OUTPUT = man
universe@372 1754
universe@372 1755 # The MAN_EXTENSION tag determines the extension that is added to the generated
universe@372 1756 # man pages. In case the manual section does not start with a number, the number
universe@372 1757 # 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
universe@372 1758 # optional.
universe@372 1759 # The default value is: .3.
universe@372 1760 # This tag requires that the tag GENERATE_MAN is set to YES.
universe@372 1761
universe@372 1762 MAN_EXTENSION = .3
universe@372 1763
universe@372 1764 # The MAN_SUBDIR tag determines the name of the directory created within
universe@372 1765 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
universe@372 1766 # MAN_EXTENSION with the initial . removed.
universe@372 1767 # This tag requires that the tag GENERATE_MAN is set to YES.
universe@372 1768
universe@372 1769 MAN_SUBDIR =
universe@372 1770
universe@372 1771 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
universe@372 1772 # will generate one additional man file for each entity documented in the real
universe@372 1773 # man page(s). These additional files only source the real man page, but without
universe@372 1774 # them the man command would be unable to find the correct page.
universe@372 1775 # The default value is: NO.
universe@372 1776 # This tag requires that the tag GENERATE_MAN is set to YES.
universe@372 1777
universe@372 1778 MAN_LINKS = NO
universe@372 1779
universe@372 1780 #---------------------------------------------------------------------------
universe@372 1781 # Configuration options related to the XML output
universe@372 1782 #---------------------------------------------------------------------------
universe@372 1783
universe@372 1784 # If the GENERATE_XML tag is set to YES doxygen will generate an XML file that
universe@372 1785 # captures the structure of the code including all documentation.
universe@372 1786 # The default value is: NO.
universe@372 1787
universe@372 1788 GENERATE_XML = NO
universe@372 1789
universe@372 1790 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
universe@372 1791 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
universe@372 1792 # it.
universe@372 1793 # The default directory is: xml.
universe@372 1794 # This tag requires that the tag GENERATE_XML is set to YES.
universe@372 1795
universe@372 1796 XML_OUTPUT = xml
universe@372 1797
universe@372 1798 # If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program
universe@372 1799 # listings (including syntax highlighting and cross-referencing information) to
universe@372 1800 # the XML output. Note that enabling this will significantly increase the size
universe@372 1801 # of the XML output.
universe@372 1802 # The default value is: YES.
universe@372 1803 # This tag requires that the tag GENERATE_XML is set to YES.
universe@372 1804
universe@372 1805 XML_PROGRAMLISTING = YES
universe@372 1806
universe@372 1807 #---------------------------------------------------------------------------
universe@372 1808 # Configuration options related to the DOCBOOK output
universe@372 1809 #---------------------------------------------------------------------------
universe@372 1810
universe@372 1811 # If the GENERATE_DOCBOOK tag is set to YES doxygen will generate Docbook files
universe@372 1812 # that can be used to generate PDF.
universe@372 1813 # The default value is: NO.
universe@372 1814
universe@372 1815 GENERATE_DOCBOOK = NO
universe@372 1816
universe@372 1817 # The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
universe@372 1818 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
universe@372 1819 # front of it.
universe@372 1820 # The default directory is: docbook.
universe@372 1821 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
universe@372 1822
universe@372 1823 DOCBOOK_OUTPUT = docbook
universe@372 1824
universe@372 1825 #---------------------------------------------------------------------------
universe@372 1826 # Configuration options for the AutoGen Definitions output
universe@372 1827 #---------------------------------------------------------------------------
universe@372 1828
universe@372 1829 # If the GENERATE_AUTOGEN_DEF tag is set to YES doxygen will generate an AutoGen
universe@372 1830 # Definitions (see http://autogen.sf.net) file that captures the structure of
universe@372 1831 # the code including all documentation. Note that this feature is still
universe@372 1832 # experimental and incomplete at the moment.
universe@372 1833 # The default value is: NO.
universe@372 1834
universe@372 1835 GENERATE_AUTOGEN_DEF = NO
universe@372 1836
universe@372 1837 #---------------------------------------------------------------------------
universe@372 1838 # Configuration options related to the Perl module output
universe@372 1839 #---------------------------------------------------------------------------
universe@372 1840
universe@372 1841 # If the GENERATE_PERLMOD tag is set to YES doxygen will generate a Perl module
universe@372 1842 # file that captures the structure of the code including all documentation.
universe@372 1843 #
universe@372 1844 # Note that this feature is still experimental and incomplete at the moment.
universe@372 1845 # The default value is: NO.
universe@372 1846
universe@372 1847 GENERATE_PERLMOD = NO
universe@372 1848
universe@372 1849 # If the PERLMOD_LATEX tag is set to YES doxygen will generate the necessary
universe@372 1850 # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
universe@372 1851 # output from the Perl module output.
universe@372 1852 # The default value is: NO.
universe@372 1853 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
universe@372 1854
universe@372 1855 PERLMOD_LATEX = NO
universe@372 1856
universe@372 1857 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be nicely
universe@372 1858 # formatted so it can be parsed by a human reader. This is useful if you want to
universe@372 1859 # understand what is going on. On the other hand, if this tag is set to NO the
universe@372 1860 # size of the Perl module output will be much smaller and Perl will parse it
universe@372 1861 # just the same.
universe@372 1862 # The default value is: YES.
universe@372 1863 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
universe@372 1864
universe@372 1865 PERLMOD_PRETTY = YES
universe@372 1866
universe@372 1867 # The names of the make variables in the generated doxyrules.make file are
universe@372 1868 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
universe@372 1869 # so different doxyrules.make files included by the same Makefile don't
universe@372 1870 # overwrite each other's variables.
universe@372 1871 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
universe@372 1872
universe@372 1873 PERLMOD_MAKEVAR_PREFIX =
universe@372 1874
universe@372 1875 #---------------------------------------------------------------------------
universe@372 1876 # Configuration options related to the preprocessor
universe@372 1877 #---------------------------------------------------------------------------
universe@372 1878
universe@372 1879 # If the ENABLE_PREPROCESSING tag is set to YES doxygen will evaluate all
universe@372 1880 # C-preprocessor directives found in the sources and include files.
universe@372 1881 # The default value is: YES.
universe@372 1882
universe@372 1883 ENABLE_PREPROCESSING = YES
universe@372 1884
universe@372 1885 # If the MACRO_EXPANSION tag is set to YES doxygen will expand all macro names
universe@372 1886 # in the source code. If set to NO only conditional compilation will be
universe@372 1887 # performed. Macro expansion can be done in a controlled way by setting
universe@372 1888 # EXPAND_ONLY_PREDEF to YES.
universe@372 1889 # The default value is: NO.
universe@372 1890 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
universe@372 1891
universe@372 1892 MACRO_EXPANSION = NO
universe@372 1893
universe@372 1894 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
universe@372 1895 # the macro expansion is limited to the macros specified with the PREDEFINED and
universe@372 1896 # EXPAND_AS_DEFINED tags.
universe@372 1897 # The default value is: NO.
universe@372 1898 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
universe@372 1899
universe@372 1900 EXPAND_ONLY_PREDEF = NO
universe@372 1901
universe@372 1902 # If the SEARCH_INCLUDES tag is set to YES the includes files in the
universe@372 1903 # INCLUDE_PATH will be searched if a #include is found.
universe@372 1904 # The default value is: YES.
universe@372 1905 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
universe@372 1906
universe@372 1907 SEARCH_INCLUDES = YES
universe@372 1908
universe@372 1909 # The INCLUDE_PATH tag can be used to specify one or more directories that
universe@372 1910 # contain include files that are not input files but should be processed by the
universe@372 1911 # preprocessor.
universe@372 1912 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
universe@372 1913
universe@372 1914 INCLUDE_PATH =
universe@372 1915
universe@372 1916 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
universe@372 1917 # patterns (like *.h and *.hpp) to filter out the header-files in the
universe@372 1918 # directories. If left blank, the patterns specified with FILE_PATTERNS will be
universe@372 1919 # used.
universe@372 1920 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
universe@372 1921
universe@372 1922 INCLUDE_FILE_PATTERNS =
universe@372 1923
universe@372 1924 # The PREDEFINED tag can be used to specify one or more macro names that are
universe@372 1925 # defined before the preprocessor is started (similar to the -D option of e.g.
universe@372 1926 # gcc). The argument of the tag is a list of macros of the form: name or
universe@372 1927 # name=definition (no spaces). If the definition and the "=" are omitted, "=1"
universe@372 1928 # is assumed. To prevent a macro definition from being undefined via #undef or
universe@372 1929 # recursively expanded use the := operator instead of the = operator.
universe@372 1930 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
universe@372 1931
universe@372 1932 PREDEFINED =
universe@372 1933
universe@372 1934 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
universe@372 1935 # tag can be used to specify a list of macro names that should be expanded. The
universe@372 1936 # macro definition that is found in the sources will be used. Use the PREDEFINED
universe@372 1937 # tag if you want to use a different macro definition that overrules the
universe@372 1938 # definition found in the source code.
universe@372 1939 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
universe@372 1940
universe@372 1941 EXPAND_AS_DEFINED =
universe@372 1942
universe@372 1943 # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
universe@372 1944 # remove all references to function-like macros that are alone on a line, have
universe@372 1945 # an all uppercase name, and do not end with a semicolon. Such function macros
universe@372 1946 # are typically used for boiler-plate code, and will confuse the parser if not
universe@372 1947 # removed.
universe@372 1948 # The default value is: YES.
universe@372 1949 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
universe@372 1950
universe@372 1951 SKIP_FUNCTION_MACROS = YES
universe@372 1952
universe@372 1953 #---------------------------------------------------------------------------
universe@372 1954 # Configuration options related to external references
universe@372 1955 #---------------------------------------------------------------------------
universe@372 1956
universe@372 1957 # The TAGFILES tag can be used to specify one or more tag files. For each tag
universe@372 1958 # file the location of the external documentation should be added. The format of
universe@372 1959 # a tag file without this location is as follows:
universe@372 1960 # TAGFILES = file1 file2 ...
universe@372 1961 # Adding location for the tag files is done as follows:
universe@372 1962 # TAGFILES = file1=loc1 "file2 = loc2" ...
universe@372 1963 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
universe@372 1964 # section "Linking to external documentation" for more information about the use
universe@372 1965 # of tag files.
universe@372 1966 # Note: Each tag file must have a unique name (where the name does NOT include
universe@372 1967 # the path). If a tag file is not located in the directory in which doxygen is
universe@372 1968 # run, you must also specify the path to the tagfile here.
universe@372 1969
universe@372 1970 TAGFILES =
universe@372 1971
universe@372 1972 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
universe@372 1973 # tag file that is based on the input files it reads. See section "Linking to
universe@372 1974 # external documentation" for more information about the usage of tag files.
universe@372 1975
universe@372 1976 GENERATE_TAGFILE =
universe@372 1977
universe@372 1978 # If the ALLEXTERNALS tag is set to YES all external class will be listed in the
universe@372 1979 # class index. If set to NO only the inherited external classes will be listed.
universe@372 1980 # The default value is: NO.
universe@372 1981
universe@372 1982 ALLEXTERNALS = NO
universe@372 1983
universe@372 1984 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed in
universe@372 1985 # the modules index. If set to NO, only the current project's groups will be
universe@372 1986 # listed.
universe@372 1987 # The default value is: YES.
universe@372 1988
universe@372 1989 EXTERNAL_GROUPS = YES
universe@372 1990
universe@372 1991 # If the EXTERNAL_PAGES tag is set to YES all external pages will be listed in
universe@372 1992 # the related pages index. If set to NO, only the current project's pages will
universe@372 1993 # be listed.
universe@372 1994 # The default value is: YES.
universe@372 1995
universe@372 1996 EXTERNAL_PAGES = YES
universe@372 1997
universe@372 1998 #---------------------------------------------------------------------------
universe@372 1999 # Configuration options related to the dot tool
universe@372 2000 #---------------------------------------------------------------------------
universe@372 2001
universe@372 2002 # If the CLASS_DIAGRAMS tag is set to YES doxygen will generate a class diagram
universe@372 2003 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
universe@372 2004 # NO turns the diagrams off. Note that this option also works with HAVE_DOT
universe@372 2005 # disabled, but it is recommended to install and use dot, since it yields more
universe@372 2006 # powerful graphs.
universe@372 2007 # The default value is: YES.
universe@372 2008
universe@372 2009 CLASS_DIAGRAMS = YES
universe@372 2010
universe@372 2011 # You can include diagrams made with dia in doxygen documentation. Doxygen will
universe@372 2012 # then run dia to produce the diagram and insert it in the documentation. The
universe@372 2013 # DIA_PATH tag allows you to specify the directory where the dia binary resides.
universe@372 2014 # If left empty dia is assumed to be found in the default search path.
universe@372 2015
universe@372 2016 DIA_PATH =
universe@372 2017
universe@372 2018 # If set to YES, the inheritance and collaboration graphs will hide inheritance
universe@372 2019 # and usage relations if the target is undocumented or is not a class.
universe@372 2020 # The default value is: YES.
universe@372 2021
universe@372 2022 HIDE_UNDOC_RELATIONS = YES
universe@372 2023
universe@372 2024 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
universe@372 2025 # available from the path. This tool is part of Graphviz (see:
universe@372 2026 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
universe@372 2027 # Bell Labs. The other options in this section have no effect if this option is
universe@372 2028 # set to NO
universe@372 2029 # The default value is: YES.
universe@372 2030
universe@372 2031 HAVE_DOT = NO
universe@372 2032
universe@372 2033 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
universe@372 2034 # to run in parallel. When set to 0 doxygen will base this on the number of
universe@372 2035 # processors available in the system. You can set it explicitly to a value
universe@372 2036 # larger than 0 to get control over the balance between CPU load and processing
universe@372 2037 # speed.
universe@372 2038 # Minimum value: 0, maximum value: 32, default value: 0.
universe@372 2039 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2040
universe@372 2041 DOT_NUM_THREADS = 0
universe@372 2042
universe@372 2043 # When you want a differently looking font n the dot files that doxygen
universe@372 2044 # generates you can specify the font name using DOT_FONTNAME. You need to make
universe@372 2045 # sure dot is able to find the font, which can be done by putting it in a
universe@372 2046 # standard location or by setting the DOTFONTPATH environment variable or by
universe@372 2047 # setting DOT_FONTPATH to the directory containing the font.
universe@372 2048 # The default value is: Helvetica.
universe@372 2049 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2050
universe@372 2051 DOT_FONTNAME = Helvetica
universe@372 2052
universe@372 2053 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
universe@372 2054 # dot graphs.
universe@372 2055 # Minimum value: 4, maximum value: 24, default value: 10.
universe@372 2056 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2057
universe@372 2058 DOT_FONTSIZE = 10
universe@372 2059
universe@372 2060 # By default doxygen will tell dot to use the default font as specified with
universe@372 2061 # DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
universe@372 2062 # the path where dot can find it using this tag.
universe@372 2063 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2064
universe@372 2065 DOT_FONTPATH =
universe@372 2066
universe@372 2067 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
universe@372 2068 # each documented class showing the direct and indirect inheritance relations.
universe@372 2069 # Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
universe@372 2070 # The default value is: YES.
universe@372 2071 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2072
universe@372 2073 CLASS_GRAPH = YES
universe@372 2074
universe@372 2075 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
universe@372 2076 # graph for each documented class showing the direct and indirect implementation
universe@372 2077 # dependencies (inheritance, containment, and class references variables) of the
universe@372 2078 # class with other documented classes.
universe@372 2079 # The default value is: YES.
universe@372 2080 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2081
universe@372 2082 COLLABORATION_GRAPH = YES
universe@372 2083
universe@372 2084 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
universe@372 2085 # groups, showing the direct groups dependencies.
universe@372 2086 # The default value is: YES.
universe@372 2087 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2088
universe@372 2089 GROUP_GRAPHS = YES
universe@372 2090
universe@372 2091 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
universe@372 2092 # collaboration diagrams in a style similar to the OMG's Unified Modeling
universe@372 2093 # Language.
universe@372 2094 # The default value is: NO.
universe@372 2095 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2096
universe@372 2097 UML_LOOK = NO
universe@372 2098
universe@372 2099 # If the UML_LOOK tag is enabled, the fields and methods are shown inside the
universe@372 2100 # class node. If there are many fields or methods and many nodes the graph may
universe@372 2101 # become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
universe@372 2102 # number of items for each type to make the size more manageable. Set this to 0
universe@372 2103 # for no limit. Note that the threshold may be exceeded by 50% before the limit
universe@372 2104 # is enforced. So when you set the threshold to 10, up to 15 fields may appear,
universe@372 2105 # but if the number exceeds 15, the total amount of fields shown is limited to
universe@372 2106 # 10.
universe@372 2107 # Minimum value: 0, maximum value: 100, default value: 10.
universe@372 2108 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2109
universe@372 2110 UML_LIMIT_NUM_FIELDS = 10
universe@372 2111
universe@372 2112 # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
universe@372 2113 # collaboration graphs will show the relations between templates and their
universe@372 2114 # instances.
universe@372 2115 # The default value is: NO.
universe@372 2116 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2117
universe@372 2118 TEMPLATE_RELATIONS = NO
universe@372 2119
universe@372 2120 # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
universe@372 2121 # YES then doxygen will generate a graph for each documented file showing the
universe@372 2122 # direct and indirect include dependencies of the file with other documented
universe@372 2123 # files.
universe@372 2124 # The default value is: YES.
universe@372 2125 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2126
universe@372 2127 INCLUDE_GRAPH = YES
universe@372 2128
universe@372 2129 # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
universe@372 2130 # set to YES then doxygen will generate a graph for each documented file showing
universe@372 2131 # the direct and indirect include dependencies of the file with other documented
universe@372 2132 # files.
universe@372 2133 # The default value is: YES.
universe@372 2134 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2135
universe@372 2136 INCLUDED_BY_GRAPH = YES
universe@372 2137
universe@372 2138 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
universe@372 2139 # dependency graph for every global function or class method.
universe@372 2140 #
universe@372 2141 # Note that enabling this option will significantly increase the time of a run.
universe@372 2142 # So in most cases it will be better to enable call graphs for selected
universe@372 2143 # functions only using the \callgraph command.
universe@372 2144 # The default value is: NO.
universe@372 2145 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2146
universe@372 2147 CALL_GRAPH = NO
universe@372 2148
universe@372 2149 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
universe@372 2150 # dependency graph for every global function or class method.
universe@372 2151 #
universe@372 2152 # Note that enabling this option will significantly increase the time of a run.
universe@372 2153 # So in most cases it will be better to enable caller graphs for selected
universe@372 2154 # functions only using the \callergraph command.
universe@372 2155 # The default value is: NO.
universe@372 2156 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2157
universe@372 2158 CALLER_GRAPH = NO
universe@372 2159
universe@372 2160 # If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
universe@372 2161 # hierarchy of all classes instead of a textual one.
universe@372 2162 # The default value is: YES.
universe@372 2163 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2164
universe@372 2165 GRAPHICAL_HIERARCHY = YES
universe@372 2166
universe@372 2167 # If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
universe@372 2168 # dependencies a directory has on other directories in a graphical way. The
universe@372 2169 # dependency relations are determined by the #include relations between the
universe@372 2170 # files in the directories.
universe@372 2171 # The default value is: YES.
universe@372 2172 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2173
universe@372 2174 DIRECTORY_GRAPH = YES
universe@372 2175
universe@372 2176 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
universe@372 2177 # generated by dot.
universe@372 2178 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
universe@372 2179 # to make the SVG files visible in IE 9+ (other browsers do not have this
universe@372 2180 # requirement).
universe@372 2181 # Possible values are: png, png:cairo, png:cairo:cairo, png:cairo:gd, png:gd,
universe@372 2182 # png:gd:gd, jpg, jpg:cairo, jpg:cairo:gd, jpg:gd, jpg:gd:gd, gif, gif:cairo,
universe@372 2183 # gif:cairo:gd, gif:gd, gif:gd:gd and svg.
universe@372 2184 # The default value is: png.
universe@372 2185 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2186
universe@372 2187 DOT_IMAGE_FORMAT = png
universe@372 2188
universe@372 2189 # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
universe@372 2190 # enable generation of interactive SVG images that allow zooming and panning.
universe@372 2191 #
universe@372 2192 # Note that this requires a modern browser other than Internet Explorer. Tested
universe@372 2193 # and working are Firefox, Chrome, Safari, and Opera.
universe@372 2194 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
universe@372 2195 # the SVG files visible. Older versions of IE do not have SVG support.
universe@372 2196 # The default value is: NO.
universe@372 2197 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2198
universe@372 2199 INTERACTIVE_SVG = NO
universe@372 2200
universe@372 2201 # The DOT_PATH tag can be used to specify the path where the dot tool can be
universe@372 2202 # found. If left blank, it is assumed the dot tool can be found in the path.
universe@372 2203 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2204
universe@372 2205 DOT_PATH =
universe@372 2206
universe@372 2207 # The DOTFILE_DIRS tag can be used to specify one or more directories that
universe@372 2208 # contain dot files that are included in the documentation (see the \dotfile
universe@372 2209 # command).
universe@372 2210 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2211
universe@372 2212 DOTFILE_DIRS =
universe@372 2213
universe@372 2214 # The MSCFILE_DIRS tag can be used to specify one or more directories that
universe@372 2215 # contain msc files that are included in the documentation (see the \mscfile
universe@372 2216 # command).
universe@372 2217
universe@372 2218 MSCFILE_DIRS =
universe@372 2219
universe@372 2220 # The DIAFILE_DIRS tag can be used to specify one or more directories that
universe@372 2221 # contain dia files that are included in the documentation (see the \diafile
universe@372 2222 # command).
universe@372 2223
universe@372 2224 DIAFILE_DIRS =
universe@372 2225
universe@372 2226 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
universe@372 2227 # that will be shown in the graph. If the number of nodes in a graph becomes
universe@372 2228 # larger than this value, doxygen will truncate the graph, which is visualized
universe@372 2229 # by representing a node as a red box. Note that doxygen if the number of direct
universe@372 2230 # children of the root node in a graph is already larger than
universe@372 2231 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
universe@372 2232 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
universe@372 2233 # Minimum value: 0, maximum value: 10000, default value: 50.
universe@372 2234 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2235
universe@372 2236 DOT_GRAPH_MAX_NODES = 50
universe@372 2237
universe@372 2238 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
universe@372 2239 # generated by dot. A depth value of 3 means that only nodes reachable from the
universe@372 2240 # root by following a path via at most 3 edges will be shown. Nodes that lay
universe@372 2241 # further from the root node will be omitted. Note that setting this option to 1
universe@372 2242 # or 2 may greatly reduce the computation time needed for large code bases. Also
universe@372 2243 # note that the size of a graph can be further restricted by
universe@372 2244 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
universe@372 2245 # Minimum value: 0, maximum value: 1000, default value: 0.
universe@372 2246 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2247
universe@372 2248 MAX_DOT_GRAPH_DEPTH = 0
universe@372 2249
universe@372 2250 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
universe@372 2251 # background. This is disabled by default, because dot on Windows does not seem
universe@372 2252 # to support this out of the box.
universe@372 2253 #
universe@372 2254 # Warning: Depending on the platform used, enabling this option may lead to
universe@372 2255 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
universe@372 2256 # read).
universe@372 2257 # The default value is: NO.
universe@372 2258 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2259
universe@372 2260 DOT_TRANSPARENT = NO
universe@372 2261
universe@372 2262 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
universe@372 2263 # files in one run (i.e. multiple -o and -T options on the command line). This
universe@372 2264 # makes dot run faster, but since only newer versions of dot (>1.8.10) support
universe@372 2265 # this, this feature is disabled by default.
universe@372 2266 # The default value is: NO.
universe@372 2267 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2268
universe@372 2269 DOT_MULTI_TARGETS = YES
universe@372 2270
universe@372 2271 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
universe@372 2272 # explaining the meaning of the various boxes and arrows in the dot generated
universe@372 2273 # graphs.
universe@372 2274 # The default value is: YES.
universe@372 2275 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2276
universe@372 2277 GENERATE_LEGEND = YES
universe@372 2278
universe@372 2279 # If the DOT_CLEANUP tag is set to YES doxygen will remove the intermediate dot
universe@372 2280 # files that are used to generate the various graphs.
universe@372 2281 # The default value is: YES.
universe@372 2282 # This tag requires that the tag HAVE_DOT is set to YES.
universe@372 2283
universe@372 2284 DOT_CLEANUP = YES

mercurial