PageRenderTime 23ms CodeModel.GetById 5ms app.highlight 6ms RepoModel.GetById 3ms app.codeStats 0ms

/Doxyfile

https://code.google.com/p/dwarftherapist/
#! | 1544 lines | 1118 code | 426 blank | 0 comment | 0 complexity | ab3fe88f8899e2d621974984c993f9d9 MD5 | raw file

Large files files are truncated, but you can click here to view the full file

   1# Doxyfile 1.5.9
   2
   3# This file describes the settings to be used by the documentation system
   4# doxygen (www.doxygen.org) for a project
   5#
   6# All text after a hash (#) is considered a comment and will be ignored
   7# The format is:
   8#       TAG = value [value, ...]
   9# For lists items can also be appended using:
  10#       TAG += value [value, ...]
  11# Values that contain spaces should be placed between quotes (" ")
  12
  13#---------------------------------------------------------------------------
  14# Project related configuration options
  15#---------------------------------------------------------------------------
  16
  17# This tag specifies the encoding used for all characters in the config file 
  18# that follow. The default is UTF-8 which is also the encoding used for all 
  19# text before the first occurrence of this tag. Doxygen uses libiconv (or the 
  20# iconv built into libc) for the transcoding. See 
  21# http://www.gnu.org/software/libiconv for the list of possible encodings.
  22
  23DOXYFILE_ENCODING      = UTF-8
  24
  25# The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
  26# by quotes) that should identify the project.
  27
  28PROJECT_NAME           = "Dwarf Therapist"
  29
  30# The PROJECT_NUMBER tag can be used to enter a project or revision number. 
  31# This could be handy for archiving the generated documentation or 
  32# if some version control system is used.
  33
  34PROJECT_NUMBER         = 0.4.0
  35
  36# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
  37# base path where the generated documentation will be put. 
  38# If a relative path is entered, it will be relative to the location 
  39# where doxygen was started. If left blank the current directory will be used.
  40
  41OUTPUT_DIRECTORY       = G:/CODE/dwarftherapist/doc
  42
  43# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 
  44# 4096 sub-directories (in 2 levels) under the output directory of each output 
  45# format and will distribute the generated files over these directories. 
  46# Enabling this option can be useful when feeding doxygen a huge amount of 
  47# source files, where putting all generated files in the same directory would 
  48# otherwise cause performance problems for the file system.
  49
  50CREATE_SUBDIRS         = NO
  51
  52# The OUTPUT_LANGUAGE tag is used to specify the language in which all 
  53# documentation generated by doxygen is written. Doxygen will use this 
  54# information to generate all constant output in the proper language. 
  55# The default language is English, other supported languages are: 
  56# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 
  57# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 
  58# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 
  59# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, 
  60# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, 
  61# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
  62
  63OUTPUT_LANGUAGE        = English
  64
  65# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
  66# include brief member descriptions after the members that are listed in 
  67# the file and class documentation (similar to JavaDoc). 
  68# Set to NO to disable this.
  69
  70BRIEF_MEMBER_DESC      = YES
  71
  72# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
  73# the brief description of a member or function before the detailed description. 
  74# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
  75# brief descriptions will be completely suppressed.
  76
  77REPEAT_BRIEF           = YES
  78
  79# This tag implements a quasi-intelligent brief description abbreviator 
  80# that is used to form the text in various listings. Each string 
  81# in this list, if found as the leading text of the brief description, will be 
  82# stripped from the text and the result after processing the whole list, is 
  83# used as the annotated text. Otherwise, the brief description is used as-is. 
  84# If left blank, the following values are used ("$name" is automatically 
  85# replaced with the name of the entity): "The $name class" "The $name widget" 
  86# "The $name file" "is" "provides" "specifies" "contains" 
  87# "represents" "a" "an" "the"
  88
  89ABBREVIATE_BRIEF       = "The $name class" \
  90                         "The $name widget" \
  91                         "The $name file" \
  92                         is \
  93                         provides \
  94                         specifies \
  95                         contains \
  96                         represents \
  97                         a \
  98                         an \
  99                         the
 100
 101# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
 102# Doxygen will generate a detailed section even if there is only a brief 
 103# description.
 104
 105ALWAYS_DETAILED_SEC    = NO
 106
 107# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 
 108# inherited members of a class in the documentation of that class as if those 
 109# members were ordinary class members. Constructors, destructors and assignment 
 110# operators of the base classes will not be shown.
 111
 112INLINE_INHERITED_MEMB  = NO
 113
 114# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
 115# path before files name in the file list and in the header files. If set 
 116# to NO the shortest path that makes the file name unique will be used.
 117
 118FULL_PATH_NAMES        = YES
 119
 120# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
 121# can be used to strip a user-defined part of the path. Stripping is 
 122# only done if one of the specified strings matches the left-hand part of 
 123# the path. The tag can be used to show relative paths in the file list. 
 124# If left blank the directory from which doxygen is run is used as the 
 125# path to strip.
 126
 127STRIP_FROM_PATH        = G:\Code\dwarftherapist
 128
 129# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 
 130# the path mentioned in the documentation of a class, which tells 
 131# the reader which header file to include in order to use a class. 
 132# If left blank only the name of the header file containing the class 
 133# definition is used. Otherwise one should specify the include paths that 
 134# are normally passed to the compiler using the -I flag.
 135
 136STRIP_FROM_INC_PATH    = 
 137
 138# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
 139# (but less readable) file names. This can be useful is your file systems 
 140# doesn't support long names like on DOS, Mac, or CD-ROM.
 141
 142SHORT_NAMES            = NO
 143
 144# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
 145# will interpret the first line (until the first dot) of a JavaDoc-style 
 146# comment as the brief description. If set to NO, the JavaDoc 
 147# comments will behave just like regular Qt-style comments 
 148# (thus requiring an explicit @brief command for a brief description.)
 149
 150JAVADOC_AUTOBRIEF      = NO
 151
 152# If the QT_AUTOBRIEF tag is set to YES then Doxygen will 
 153# interpret the first line (until the first dot) of a Qt-style 
 154# comment as the brief description. If set to NO, the comments 
 155# will behave just like regular Qt-style comments (thus requiring 
 156# an explicit \brief command for a brief description.)
 157
 158QT_AUTOBRIEF           = YES
 159
 160# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
 161# treat a multi-line C++ special comment block (i.e. a block of //! or /// 
 162# comments) as a brief description. This used to be the default behaviour. 
 163# The new default is to treat a multi-line C++ comment block as a detailed 
 164# description. Set this tag to YES if you prefer the old behaviour instead.
 165
 166MULTILINE_CPP_IS_BRIEF = NO
 167
 168# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
 169# member inherits the documentation from any documented member that it 
 170# re-implements.
 171
 172INHERIT_DOCS           = YES
 173
 174# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 
 175# a new page for each member. If set to NO, the documentation of a member will 
 176# be part of the file/class/namespace that contains it.
 177
 178SEPARATE_MEMBER_PAGES  = NO
 179
 180# The TAB_SIZE tag can be used to set the number of spaces in a tab. 
 181# Doxygen uses this value to replace tabs by spaces in code fragments.
 182
 183TAB_SIZE               = 4
 184
 185# This tag can be used to specify a number of aliases that acts 
 186# as commands in the documentation. An alias has the form "name=value". 
 187# For example adding "sideeffect=\par Side Effects:\n" will allow you to 
 188# put the command \sideeffect (or @sideeffect) in the documentation, which 
 189# will result in a user-defined paragraph with heading "Side Effects:". 
 190# You can put \n's in the value part of an alias to insert newlines.
 191
 192ALIASES                = 
 193
 194# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 
 195# sources only. Doxygen will then generate output that is more tailored for C. 
 196# For instance, some of the names that are used will be different. The list 
 197# of all members will be omitted, etc.
 198
 199OPTIMIZE_OUTPUT_FOR_C  = NO
 200
 201# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 
 202# sources only. Doxygen will then generate output that is more tailored for 
 203# Java. For instance, namespaces will be presented as packages, qualified 
 204# scopes will look different, etc.
 205
 206OPTIMIZE_OUTPUT_JAVA   = NO
 207
 208# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 
 209# sources only. Doxygen will then generate output that is more tailored for 
 210# Fortran.
 211
 212OPTIMIZE_FOR_FORTRAN   = NO
 213
 214# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 
 215# sources. Doxygen will then generate output that is tailored for 
 216# VHDL.
 217
 218OPTIMIZE_OUTPUT_VHDL   = NO
 219
 220# Doxygen selects the parser to use depending on the extension of the files it parses. 
 221# With this tag you can assign which parser to use for a given extension. 
 222# Doxygen has a built-in mapping, but you can override or extend it using this tag. 
 223# The format is ext=language, where ext is a file extension, and language is one of 
 224# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP, 
 225# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat 
 226# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), 
 227# use: inc=Fortran f=C. Note that for custom extensions you also need to set
 228# FILE_PATTERNS otherwise the files are not read by doxygen.
 229
 230EXTENSION_MAPPING      = 
 231
 232# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 
 233# to include (a tag file for) the STL sources as input, then you should 
 234# set this tag to YES in order to let doxygen match functions declarations and 
 235# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 
 236# func(std::string) {}). This also make the inheritance and collaboration 
 237# diagrams that involve STL classes more complete and accurate.
 238
 239BUILTIN_STL_SUPPORT    = NO
 240
 241# If you use Microsoft's C++/CLI language, you should set this option to YES to 
 242# enable parsing support.
 243
 244CPP_CLI_SUPPORT        = NO
 245
 246# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 
 247# Doxygen will parse them like normal C++ but will assume all classes use public 
 248# instead of private inheritance when no explicit protection keyword is present.
 249
 250SIP_SUPPORT            = NO
 251
 252# For Microsoft's IDL there are propget and propput attributes to indicate getter 
 253# and setter methods for a property. Setting this option to YES (the default) 
 254# will make doxygen to replace the get and set methods by a property in the 
 255# documentation. This will only work if the methods are indeed getting or 
 256# setting a simple type. If this is not the case, or you want to show the 
 257# methods anyway, you should set this option to NO.
 258
 259IDL_PROPERTY_SUPPORT   = YES
 260
 261# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
 262# tag is set to YES, then doxygen will reuse the documentation of the first 
 263# member in the group (if any) for the other members of the group. By default 
 264# all members of a group must be documented explicitly.
 265
 266DISTRIBUTE_GROUP_DOC   = NO
 267
 268# Set the SUBGROUPING tag to YES (the default) to allow class member groups of 
 269# the same type (for instance a group of public functions) to be put as a 
 270# subgroup of that type (e.g. under the Public Functions section). Set it to 
 271# NO to prevent subgrouping. Alternatively, this can be done per class using 
 272# the \nosubgrouping command.
 273
 274SUBGROUPING            = YES
 275
 276# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 
 277# is documented as struct, union, or enum with the name of the typedef. So 
 278# typedef struct TypeS {} TypeT, will appear in the documentation as a struct 
 279# with name TypeT. When disabled the typedef will appear as a member of a file, 
 280# namespace, or class. And the struct will be named TypeS. This can typically 
 281# be useful for C code in case the coding convention dictates that all compound 
 282# types are typedef'ed and only the typedef is referenced, never the tag name.
 283
 284TYPEDEF_HIDES_STRUCT   = NO
 285
 286# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 
 287# determine which symbols to keep in memory and which to flush to disk. 
 288# When the cache is full, less often used symbols will be written to disk. 
 289# For small to medium size projects (<1000 input files) the default value is 
 290# probably good enough. For larger projects a too small cache size can cause 
 291# doxygen to be busy swapping symbols to and from disk most of the time 
 292# causing a significant performance penality. 
 293# If the system has enough physical memory increasing the cache will improve the 
 294# performance by keeping more symbols in memory. Note that the value works on 
 295# a logarithmic scale so increasing the size by one will rougly double the 
 296# memory usage. The cache size is given by this formula: 
 297# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, 
 298# corresponding to a cache size of 2^16 = 65536 symbols
 299
 300SYMBOL_CACHE_SIZE      = 0
 301
 302#---------------------------------------------------------------------------
 303# Build related configuration options
 304#---------------------------------------------------------------------------
 305
 306# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
 307# documentation are documented, even if no documentation was available. 
 308# Private class members and static file members will be hidden unless 
 309# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
 310
 311EXTRACT_ALL            = YES
 312
 313# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
 314# will be included in the documentation.
 315
 316EXTRACT_PRIVATE        = YES
 317
 318# If the EXTRACT_STATIC tag is set to YES all static members of a file 
 319# will be included in the documentation.
 320
 321EXTRACT_STATIC         = YES
 322
 323# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
 324# defined locally in source files will be included in the documentation. 
 325# If set to NO only classes defined in header files are included.
 326
 327EXTRACT_LOCAL_CLASSES  = YES
 328
 329# This flag is only useful for Objective-C code. When set to YES local 
 330# methods, which are defined in the implementation section but not in 
 331# the interface are included in the documentation. 
 332# If set to NO (the default) only methods in the interface are included.
 333
 334EXTRACT_LOCAL_METHODS  = NO
 335
 336# If this flag is set to YES, the members of anonymous namespaces will be 
 337# extracted and appear in the documentation as a namespace called 
 338# 'anonymous_namespace{file}', where file will be replaced with the base 
 339# name of the file that contains the anonymous namespace. By default 
 340# anonymous namespace are hidden.
 341
 342EXTRACT_ANON_NSPACES   = NO
 343
 344# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
 345# undocumented members of documented classes, files or namespaces. 
 346# If set to NO (the default) these members will be included in the 
 347# various overviews, but no documentation section is generated. 
 348# This option has no effect if EXTRACT_ALL is enabled.
 349
 350HIDE_UNDOC_MEMBERS     = NO
 351
 352# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
 353# undocumented classes that are normally visible in the class hierarchy. 
 354# If set to NO (the default) these classes will be included in the various 
 355# overviews. This option has no effect if EXTRACT_ALL is enabled.
 356
 357HIDE_UNDOC_CLASSES     = NO
 358
 359# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
 360# friend (class|struct|union) declarations. 
 361# If set to NO (the default) these declarations will be included in the 
 362# documentation.
 363
 364HIDE_FRIEND_COMPOUNDS  = NO
 365
 366# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 
 367# documentation blocks found inside the body of a function. 
 368# If set to NO (the default) these blocks will be appended to the 
 369# function's detailed documentation block.
 370
 371HIDE_IN_BODY_DOCS      = NO
 372
 373# The INTERNAL_DOCS tag determines if documentation 
 374# that is typed after a \internal command is included. If the tag is set 
 375# to NO (the default) then the documentation will be excluded. 
 376# Set it to YES to include the internal documentation.
 377
 378INTERNAL_DOCS          = NO
 379
 380# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
 381# file names in lower-case letters. If set to YES upper-case letters are also 
 382# allowed. This is useful if you have classes or files whose names only differ 
 383# in case and if your file system supports case sensitive file names. Windows 
 384# and Mac users are advised to set this option to NO.
 385
 386CASE_SENSE_NAMES       = NO
 387
 388# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
 389# will show members with their full class and namespace scopes in the 
 390# documentation. If set to YES the scope will be hidden.
 391
 392HIDE_SCOPE_NAMES       = NO
 393
 394# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
 395# will put a list of the files that are included by a file in the documentation 
 396# of that file.
 397
 398SHOW_INCLUDE_FILES     = YES
 399
 400# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
 401# is inserted in the documentation for inline members.
 402
 403INLINE_INFO            = YES
 404
 405# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
 406# will sort the (detailed) documentation of file and class members 
 407# alphabetically by member name. If set to NO the members will appear in 
 408# declaration order.
 409
 410SORT_MEMBER_DOCS       = YES
 411
 412# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 
 413# brief documentation of file, namespace and class members alphabetically 
 414# by member name. If set to NO (the default) the members will appear in 
 415# declaration order.
 416
 417SORT_BRIEF_DOCS        = NO
 418
 419# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 
 420# hierarchy of group names into alphabetical order. If set to NO (the default) 
 421# the group names will appear in their defined order.
 422
 423SORT_GROUP_NAMES       = NO
 424
 425# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 
 426# sorted by fully-qualified names, including namespaces. If set to 
 427# NO (the default), the class list will be sorted only by class name, 
 428# not including the namespace part. 
 429# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 
 430# Note: This option applies only to the class list, not to the 
 431# alphabetical list.
 432
 433SORT_BY_SCOPE_NAME     = NO
 434
 435# The GENERATE_TODOLIST tag can be used to enable (YES) or 
 436# disable (NO) the todo list. This list is created by putting \todo 
 437# commands in the documentation.
 438
 439GENERATE_TODOLIST      = YES
 440
 441# The GENERATE_TESTLIST tag can be used to enable (YES) or 
 442# disable (NO) the test list. This list is created by putting \test 
 443# commands in the documentation.
 444
 445GENERATE_TESTLIST      = YES
 446
 447# The GENERATE_BUGLIST tag can be used to enable (YES) or 
 448# disable (NO) the bug list. This list is created by putting \bug 
 449# commands in the documentation.
 450
 451GENERATE_BUGLIST       = YES
 452
 453# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
 454# disable (NO) the deprecated list. This list is created by putting 
 455# \deprecated commands in the documentation.
 456
 457GENERATE_DEPRECATEDLIST= YES
 458
 459# The ENABLED_SECTIONS tag can be used to enable conditional 
 460# documentation sections, marked by \if sectionname ... \endif.
 461
 462ENABLED_SECTIONS       = 
 463
 464# The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
 465# the initial value of a variable or define consists of for it to appear in 
 466# the documentation. If the initializer consists of more lines than specified 
 467# here it will be hidden. Use a value of 0 to hide initializers completely. 
 468# The appearance of the initializer of individual variables and defines in the 
 469# documentation can be controlled using \showinitializer or \hideinitializer 
 470# command in the documentation regardless of this setting.
 471
 472MAX_INITIALIZER_LINES  = 30
 473
 474# If the sources in your project are distributed over multiple directories 
 475# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 
 476# in the documentation. The default is NO.
 477
 478SHOW_DIRECTORIES       = NO
 479
 480# Set the SHOW_FILES tag to NO to disable the generation of the Files page. 
 481# This will remove the Files entry from the Quick Index and from the 
 482# Folder Tree View (if specified). The default is YES.
 483
 484SHOW_FILES             = YES
 485
 486# Set the SHOW_NAMESPACES tag to NO to disable the generation of the 
 487# Namespaces page.  This will remove the Namespaces entry from the Quick Index 
 488# and from the Folder Tree View (if specified). The default is YES.
 489
 490SHOW_NAMESPACES        = YES
 491
 492# The FILE_VERSION_FILTER tag can be used to specify a program or script that 
 493# doxygen should invoke to get the current version for each file (typically from 
 494# the version control system). Doxygen will invoke the program by executing (via 
 495# popen()) the command <command> <input-file>, where <command> is the value of 
 496# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 
 497# provided by doxygen. Whatever the program writes to standard output 
 498# is used as the file version. See the manual for examples.
 499
 500FILE_VERSION_FILTER    = 
 501
 502# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by 
 503# doxygen. The layout file controls the global structure of the generated output files 
 504# in an output format independent way. The create the layout file that represents 
 505# doxygen's defaults, run doxygen with the -l option. You can optionally specify a 
 506# file name after the option, if omitted DoxygenLayout.xml will be used as the name 
 507# of the layout file.
 508
 509LAYOUT_FILE            = 
 510
 511#---------------------------------------------------------------------------
 512# configuration options related to warning and progress messages
 513#---------------------------------------------------------------------------
 514
 515# The QUIET tag can be used to turn on/off the messages that are generated 
 516# by doxygen. Possible values are YES and NO. If left blank NO is used.
 517
 518QUIET                  = NO
 519
 520# The WARNINGS tag can be used to turn on/off the warning messages that are 
 521# generated by doxygen. Possible values are YES and NO. If left blank 
 522# NO is used.
 523
 524WARNINGS               = YES
 525
 526# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
 527# for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
 528# automatically be disabled.
 529
 530WARN_IF_UNDOCUMENTED   = YES
 531
 532# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 
 533# potential errors in the documentation, such as not documenting some 
 534# parameters in a documented function, or documenting parameters that 
 535# don't exist or using markup commands wrongly.
 536
 537WARN_IF_DOC_ERROR      = YES
 538
 539# This WARN_NO_PARAMDOC option can be abled to get warnings for 
 540# functions that are documented, but have no documentation for their parameters 
 541# or return value. If set to NO (the default) doxygen will only warn about 
 542# wrong or incomplete parameter documentation, but not about the absence of 
 543# documentation.
 544
 545WARN_NO_PARAMDOC       = NO
 546
 547# The WARN_FORMAT tag determines the format of the warning messages that 
 548# doxygen can produce. The string should contain the $file, $line, and $text 
 549# tags, which will be replaced by the file and line number from which the 
 550# warning originated and the warning text. Optionally the format may contain 
 551# $version, which will be replaced by the version of the file (if it could 
 552# be obtained via FILE_VERSION_FILTER)
 553
 554WARN_FORMAT            = "$file:$line: $text"
 555
 556# The WARN_LOGFILE tag can be used to specify a file to which warning 
 557# and error messages should be written. If left blank the output is written 
 558# to stderr.
 559
 560WARN_LOGFILE           = 
 561
 562#---------------------------------------------------------------------------
 563# configuration options related to the input files
 564#---------------------------------------------------------------------------
 565
 566# The INPUT tag can be used to specify the files and/or directories that contain 
 567# documented source files. You may enter file names like "myfile.cpp" or 
 568# directories like "/usr/src/myproject". Separate the files or directories 
 569# with spaces.
 570
 571INPUT                  = G:/CODE/dwarftherapist/src \
 572                         G:/CODE/dwarftherapist/inc
 573
 574# This tag can be used to specify the character encoding of the source files 
 575# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is 
 576# also the default input encoding. Doxygen uses libiconv (or the iconv built 
 577# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for 
 578# the list of possible encodings.
 579
 580INPUT_ENCODING         = UTF-8
 581
 582# If the value of the INPUT tag contains directories, you can use the 
 583# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
 584# and *.h) to filter out the source-files in the directories. If left 
 585# blank the following patterns are tested: 
 586# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx 
 587# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
 588
 589FILE_PATTERNS          = *.c \
 590                         *.cc \
 591                         *.cxx \
 592                         *.cpp \
 593                         *.c++ \
 594                         *.d \
 595                         *.java \
 596                         *.ii \
 597                         *.ixx \
 598                         *.ipp \
 599                         *.i++ \
 600                         *.inl \
 601                         *.h \
 602                         *.hh \
 603                         *.hxx \
 604                         *.hpp \
 605                         *.h++ \
 606                         *.idl \
 607                         *.odl \
 608                         *.cs \
 609                         *.php \
 610                         *.php3 \
 611                         *.inc \
 612                         *.m \
 613                         *.mm \
 614                         *.dox \
 615                         *.py \
 616                         *.f90 \
 617                         *.f \
 618                         *.vhd \
 619                         *.vhdl
 620
 621# The RECURSIVE tag can be used to turn specify whether or not subdirectories 
 622# should be searched for input files as well. Possible values are YES and NO. 
 623# If left blank NO is used.
 624
 625RECURSIVE              = YES
 626
 627# The EXCLUDE tag can be used to specify files and/or directories that should 
 628# excluded from the INPUT source files. This way you can easily exclude a 
 629# subdirectory from a directory tree whose root is specified with the INPUT tag.
 630
 631EXCLUDE                = thirdparty
 632
 633# The EXCLUDE_SYMLINKS tag can be used select whether or not files or 
 634# directories that are symbolic links (a Unix filesystem feature) are excluded 
 635# from the input.
 636
 637EXCLUDE_SYMLINKS       = NO
 638
 639# If the value of the INPUT tag contains directories, you can use the 
 640# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
 641# certain files from those directories. Note that the wildcards are matched 
 642# against the file with absolute path, so to exclude all test directories 
 643# for example use the pattern */test/*
 644
 645EXCLUDE_PATTERNS       = 
 646
 647# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 
 648# (namespaces, classes, functions, etc.) that should be excluded from the 
 649# output. The symbol name can be a fully qualified name, a word, or if the 
 650# wildcard * is used, a substring. Examples: ANamespace, AClass, 
 651# AClass::ANamespace, ANamespace::*Test
 652
 653EXCLUDE_SYMBOLS        = 
 654
 655# The EXAMPLE_PATH tag can be used to specify one or more files or 
 656# directories that contain example code fragments that are included (see 
 657# the \include command).
 658
 659EXAMPLE_PATH           = 
 660
 661# If the value of the EXAMPLE_PATH tag contains directories, you can use the 
 662# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
 663# and *.h) to filter out the source-files in the directories. If left 
 664# blank all files are included.
 665
 666EXAMPLE_PATTERNS       = *
 667
 668# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
 669# searched for input files to be used with the \include or \dontinclude 
 670# commands irrespective of the value of the RECURSIVE tag. 
 671# Possible values are YES and NO. If left blank NO is used.
 672
 673EXAMPLE_RECURSIVE      = NO
 674
 675# The IMAGE_PATH tag can be used to specify one or more files or 
 676# directories that contain image that are included in the documentation (see 
 677# the \image command).
 678
 679IMAGE_PATH             = 
 680
 681# The INPUT_FILTER tag can be used to specify a program that doxygen should 
 682# invoke to filter for each input file. Doxygen will invoke the filter program 
 683# by executing (via popen()) the command <filter> <input-file>, where <filter> 
 684# is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
 685# input file. Doxygen will then use the output that the filter program writes 
 686# to standard output.  If FILTER_PATTERNS is specified, this tag will be 
 687# ignored.
 688
 689INPUT_FILTER           = 
 690
 691# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 
 692# basis.  Doxygen will compare the file name with each pattern and apply the 
 693# filter if there is a match.  The filters are a list of the form: 
 694# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 
 695# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER 
 696# is applied to all files.
 697
 698FILTER_PATTERNS        = 
 699
 700# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
 701# INPUT_FILTER) will be used to filter the input files when producing source 
 702# files to browse (i.e. when SOURCE_BROWSER is set to YES).
 703
 704FILTER_SOURCE_FILES    = NO
 705
 706#---------------------------------------------------------------------------
 707# configuration options related to source browsing
 708#---------------------------------------------------------------------------
 709
 710# If the SOURCE_BROWSER tag is set to YES then a list of source files will 
 711# be generated. Documented entities will be cross-referenced with these sources. 
 712# Note: To get rid of all source code in the generated output, make sure also 
 713# VERBATIM_HEADERS is set to NO.
 714
 715SOURCE_BROWSER         = NO
 716
 717# Setting the INLINE_SOURCES tag to YES will include the body 
 718# of functions and classes directly in the documentation.
 719
 720INLINE_SOURCES         = NO
 721
 722# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
 723# doxygen to hide any special comment blocks from generated source code 
 724# fragments. Normal C and C++ comments will always remain visible.
 725
 726STRIP_CODE_COMMENTS    = YES
 727
 728# If the REFERENCED_BY_RELATION tag is set to YES 
 729# then for each documented function all documented 
 730# functions referencing it will be listed.
 731
 732REFERENCED_BY_RELATION = NO
 733
 734# If the REFERENCES_RELATION tag is set to YES 
 735# then for each documented function all documented entities 
 736# called/used by that function will be listed.
 737
 738REFERENCES_RELATION    = NO
 739
 740# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 
 741# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 
 742# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 
 743# link to the source code.  Otherwise they will link to the documentation.
 744
 745REFERENCES_LINK_SOURCE = YES
 746
 747# If the USE_HTAGS tag is set to YES then the references to source code 
 748# will point to the HTML generated by the htags(1) tool instead of doxygen 
 749# built-in source browser. The htags tool is part of GNU's global source 
 750# tagging system (see http://www.gnu.org/software/global/global.html). You 
 751# will need version 4.8.6 or higher.
 752
 753USE_HTAGS              = NO
 754
 755# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
 756# will generate a verbatim copy of the header file for each class for 
 757# which an include is specified. Set to NO to disable this.
 758
 759VERBATIM_HEADERS       = YES
 760
 761#---------------------------------------------------------------------------
 762# configuration options related to the alphabetical class index
 763#---------------------------------------------------------------------------
 764
 765# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
 766# of all compounds will be generated. Enable this if the project 
 767# contains a lot of classes, structs, unions or interfaces.
 768
 769ALPHABETICAL_INDEX     = YES
 770
 771# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
 772# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
 773# in which this list will be split (can be a number in the range [1..20])
 774
 775COLS_IN_ALPHA_INDEX    = 5
 776
 777# In case all classes in a project start with a common prefix, all 
 778# classes will be put under the same header in the alphabetical index. 
 779# The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
 780# should be ignored while generating the index headers.
 781
 782IGNORE_PREFIX          = 
 783
 784#---------------------------------------------------------------------------
 785# configuration options related to the HTML output
 786#---------------------------------------------------------------------------
 787
 788# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
 789# generate HTML output.
 790
 791GENERATE_HTML          = YES
 792
 793# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
 794# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
 795# put in front of it. If left blank `html' will be used as the default path.
 796
 797HTML_OUTPUT            = html
 798
 799# The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
 800# each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
 801# doxygen will generate files with .html extension.
 802
 803HTML_FILE_EXTENSION    = .html
 804
 805# The HTML_HEADER tag can be used to specify a personal HTML header for 
 806# each generated HTML page. If it is left blank doxygen will generate a 
 807# standard header.
 808
 809HTML_HEADER            = 
 810
 811# The HTML_FOOTER tag can be used to specify a personal HTML footer for 
 812# each generated HTML page. If it is left blank doxygen will generate a 
 813# standard footer.
 814
 815HTML_FOOTER            = 
 816
 817# The HTML_STYLESHEET tag can be used to specify a user-defined cascading 
 818# style sheet that is used by each HTML page. It can be used to 
 819# fine-tune the look of the HTML output. If the tag is left blank doxygen 
 820# will generate a default style sheet. Note that doxygen will try to copy 
 821# the style sheet file to the HTML output directory, so don't put your own 
 822# stylesheet in the HTML output directory as well, or it will be erased!
 823
 824HTML_STYLESHEET        = 
 825
 826# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 
 827# files or namespaces will be aligned in HTML using tables. If set to 
 828# NO a bullet list will be used.
 829
 830HTML_ALIGN_MEMBERS     = YES
 831
 832# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 
 833# documentation will contain sections that can be hidden and shown after the 
 834# page has loaded. For this to work a browser that supports 
 835# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox 
 836# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
 837
 838HTML_DYNAMIC_SECTIONS  = YES
 839
 840# If the GENERATE_DOCSET tag is set to YES, additional index files 
 841# will be generated that can be used as input for Apple's Xcode 3 
 842# integrated development environment, introduced with OSX 10.5 (Leopard). 
 843# To create a documentation set, doxygen will generate a Makefile in the 
 844# HTML output directory. Running make will produce the docset in that 
 845# directory and running "make install" will install the docset in 
 846# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 
 847# it at startup. 
 848# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.
 849
 850GENERATE_DOCSET        = NO
 851
 852# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 
 853# feed. A documentation feed provides an umbrella under which multiple 
 854# documentation sets from a single provider (such as a company or product suite) 
 855# can be grouped.
 856
 857DOCSET_FEEDNAME        = "Doxygen generated docs"
 858
 859# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 
 860# should uniquely identify the documentation set bundle. This should be a 
 861# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 
 862# will append .docset to the name.
 863
 864DOCSET_BUNDLE_ID       = org.doxygen.Project
 865
 866# If the GENERATE_HTMLHELP tag is set to YES, additional index files 
 867# will be generated that can be used as input for tools like the 
 868# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 
 869# of the generated HTML documentation.
 870
 871GENERATE_HTMLHELP      = NO
 872
 873# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
 874# be used to specify the file name of the resulting .chm file. You 
 875# can add a path in front of the file if the result should not be 
 876# written to the html output directory.
 877
 878CHM_FILE               = 
 879
 880# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
 881# be used to specify the location (absolute path including file name) of 
 882# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 
 883# the HTML help compiler on the generated index.hhp.
 884
 885HHC_LOCATION           = 
 886
 887# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
 888# controls if a separate .chi index file is generated (YES) or that 
 889# it should be included in the master .chm file (NO).
 890
 891GENERATE_CHI           = NO
 892
 893# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 
 894# is used to encode HtmlHelp index (hhk), content (hhc) and project file 
 895# content.
 896
 897CHM_INDEX_ENCODING     = 
 898
 899# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
 900# controls whether a binary table of contents is generated (YES) or a 
 901# normal table of contents (NO) in the .chm file.
 902
 903BINARY_TOC             = NO
 904
 905# The TOC_EXPAND flag can be set to YES to add extra items for group members 
 906# to the contents of the HTML help documentation and to the tree view.
 907
 908TOC_EXPAND             = NO
 909
 910# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER 
 911# are set, an additional index file will be generated that can be used as input for 
 912# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated 
 913# HTML documentation.
 914
 915GENERATE_QHP           = YES
 916
 917# If the QHG_LOCATION tag is specified, the QCH_FILE tag can 
 918# be used to specify the file name of the resulting .qch file. 
 919# The path specified is relative to the HTML output folder.
 920
 921QCH_FILE               = ../api.qch
 922
 923# The QHP_NAMESPACE tag specifies the namespace to use when generating 
 924# Qt Help Project output. For more information please see 
 925# http://doc.trolltech.com/qthelpproject.html#namespace
 926
 927QHP_NAMESPACE          = udpviper.com.dwarftherapist_api.0_4_0
 928
 929# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 
 930# Qt Help Project output. For more information please see 
 931# http://doc.trolltech.com/qthelpproject.html#virtual-folders
 932
 933QHP_VIRTUAL_FOLDER     = api
 934
 935# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. 
 936# For more information please see 
 937# http://doc.trolltech.com/qthelpproject.html#custom-filters
 938
 939QHP_CUST_FILTER_NAME   = 
 940
 941# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see 
 942# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.
 943
 944QHP_CUST_FILTER_ATTRS  = 
 945
 946# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's 
 947# filter section matches. 
 948# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.
 949
 950QHP_SECT_FILTER_ATTRS  = 
 951
 952# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 
 953# be used to specify the location of Qt's qhelpgenerator. 
 954# If non-empty doxygen will try to run qhelpgenerator on the generated 
 955# .qhp file.
 956
 957QHG_LOCATION           = C:/Qt/4.5.0/bin/qhelpgenerator.exe
 958
 959# The DISABLE_INDEX tag can be used to turn on/off the condensed index at 
 960# top of each HTML page. The value NO (the default) enables the index and 
 961# the value YES disables it.
 962
 963DISABLE_INDEX          = NO
 964
 965# This tag can be used to set the number of enum values (range [1..20]) 
 966# that doxygen will group on one line in the generated HTML documentation.
 967
 968ENUM_VALUES_PER_LINE   = 4
 969
 970# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 
 971# structure should be generated to display hierarchical information. 
 972# If the tag value is set to FRAME, a side panel will be generated 
 973# containing a tree-like index structure (just like the one that 
 974# is generated for HTML Help). For this to work a browser that supports 
 975# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+, 
 976# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are 
 977# probably better off using the HTML help feature. Other possible values 
 978# for this tag are: HIERARCHIES, which will generate the Groups, Directories, 
 979# and Class Hierarchy pages using a tree view instead of an ordered list; 
 980# ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which 
 981# disables this behavior completely. For backwards compatibility with previous 
 982# releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE 
 983# respectively.
 984
 985GENERATE_TREEVIEW      = NONE
 986
 987# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
 988# used to set the initial width (in pixels) of the frame in which the tree 
 989# is shown.
 990
 991TREEVIEW_WIDTH         = 250
 992
 993# Use this tag to change the font size of Latex formulas included 
 994# as images in the HTML documentation. The default is 10. Note that 
 995# when you change the font size after a successful doxygen run you need 
 996# to manually remove any form_*.png images from the HTML output directory 
 997# to force them to be regenerated.
 998
 999FORMULA_FONTSIZE       = 10
1000
1001#---------------------------------------------------------------------------
1002# configuration options related to the LaTeX output
1003#---------------------------------------------------------------------------
1004
1005# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
1006# generate Latex output.
1007
1008GENERATE_LATEX         = NO
1009
1010# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
1011# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
1012# put in front of it. If left blank `latex' will be used as the default path.
1013
1014LATEX_OUTPUT           = latex
1015
1016# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 
1017# invoked. If left blank `latex' will be used as the default command name.
1018
1019LATEX_CMD_NAME         = latex
1020
1021# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
1022# generate index for LaTeX. If left blank `makeindex' will be used as the 
1023# default command name.
1024
1025MAKEINDEX_CMD_NAME     = makeindex
1026
1027# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
1028# LaTeX documents. This may be useful for small projects and may help to 
1029# save some trees in general.
1030
1031COMPACT_LATEX          = NO
1032
1033# The PAPER_TYPE tag can be used to set the paper type that is used 
1034# by the printer. Possible values are: a4, a4wide, letter, legal and 
1035# executive. If left blank a4wide will be used.
1036
1037PAPER_TYPE             = a4wide
1038
1039# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
1040# packages that should be included in the LaTeX output.
1041
1042EXTRA_PACKAGES         = 
1043
1044# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
1045# the generated latex document. The header should contain everything until 
1046# the first chapter. If it is left blank doxygen will generate a 
1047# standard header. Notice: only use this tag if you know what you are doing!
1048
1049LATEX_HEADER           = 
1050
1051# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
1052# is prepared for conversion to pdf (using ps2pdf). The pdf file will 
1053# contain links (just like the HTML output) instead of page references 
1054# This makes the output suitable for online browsing using a pdf viewer.
1055
1056PDF_HYPERLINKS         = YES
1057
1058# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
1059# plain latex in the generated Makefile. Set this option to YES to get a 
1060# higher quality PDF documentation.
1061
1062USE_PDFLATEX           = YES
1063
1064# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
1065# command to the generated LaTeX files. This will instruct LaTeX to keep 
1066# running if errors occur, instead of asking the user for help. 
1067# This option is also used when generating formulas in HTML.
1068
1069LATEX_BATCHMODE        = NO
1070
1071# If LATEX_HIDE_INDICES is set to YES then doxygen will not 
1072# include the index chapters (such as File Index, Compound Index, etc.) 
1073# in the output.
1074
1075LATEX_HIDE_INDICES     = NO
1076
1077# If LATEX_SOURCE_CODE is set to YES then doxygen will include
1078# source code with syntax highlighting in the LaTeX output.
1079# Note that which sources are shown also depends on other settings
1080# such as SOURCE_BROWSER.
1081
1082LATEX_SOURCE_CODE      = NO
1083
1084#---------------------------------------------------------------------------
1085# configuration options related to the RTF output
1086#---------------------------------------------------------------------------
1087
1088# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
1089# The RTF output is optimized for Word 97 and may not look very pretty with 
1090# other RTF readers or editors.
1091
1092GENERATE_RTF           = NO
1093
1094# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
1095# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
1096# put in front of it. If left blank `rtf' will be used as the default path.
1097
1098RTF_OUTPUT             = rtf
1099
1100# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
1101# RTF documents. This may be useful for small projects and may help to 
1102# save some trees in general.
1103
1104COMPACT_RTF            = NO
1105
1106# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
1107# will contain hyperlink fields. The RTF file will 
1108# contain links (just like the HTML output) instead of page references. 
1109# This makes the output suitable for online browsing using WORD or other 
1110# programs which support those fields. 
1111# Note: wordpad (write) and others do not support links.
1112
1113RTF_HYPERLINKS         = NO
1114
1115# Load stylesheet definitions from file. Syntax is similar to doxygen's 
1116# config file, i.e. a series of assignments. You only have to provide 
1117# replacements, missing definitions are set to their default value.
1118
1119RTF_STYLESHEET_FILE    = 
1120
1121# Set optional variables used in the generation of an rtf document. 
1122# Syntax is similar to doxygen's config file.
1123
1124RTF_EXTENSIONS_FILE    = 
1125
1126#---------------------------------------------------------------------------
1127# configuration options related to the man page output
1128#---------------------------------------------------------------------------
1129
1130# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
1131# generate man pages
1132
1133GENERATE_MAN           = NO
1134
1135# The MAN_OUTPUT tag is used to specify where the man pages will be put. 
1136# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
1137# put in front of it. If left blank `man' will be used as the default path.
1138
1139MAN_OUTPUT             = man
1140
1141# The MAN_EXTENSION tag determines the extension that is added to 
1142# the generated man pages (default is the subroutine's section .3)
1143
1144MAN_EXTENSION          = .3
1145
1146# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
1147# then it will generate one additional man file for each entity 
1148# documented in the real man page(s). These additional files 
1149# only source the real man page, but without them the man command 
1150# would be unable to find the correct page. The default is NO.
1151
1152MAN_LINKS              = NO
1153
1154#---------------------------------------------------------------------------
1155# configuration options related to the XML output
1156#---------------------------------------------------------------------------
1157
1158# If the GENERATE_XML tag is set to YES Doxygen will 
1159# generate an XML file that captures the structure of 
1160# the code including all documentation.
1161
1162GENERATE_XML           = NO
1163
1164# The XML_OUTPUT tag is used to specify where the XML pages will be put. 
1165# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
1166# put in front of it. If left blank `xml' will be used as the default path.
1167
1168XML_OUTPUT             = xml
1169
1170# The XML_SCHEMA tag can be used to specify an XML schema, 
1171# which can be used by a validating XML parser to check the 
1172# syntax of the XML files.
1173
1174XML_SCHEMA             = 
1175
1176# The XML_DTD tag can be used to specify an XML DTD, 
1177# which can be used by a validating XML parser to check the 
1178# syntax of the XML files.
1179
1180XML_DTD                = 
1181
1182# If the XML_PROGRAMLISTING tag is set to YES Doxygen will 
1183# dump the program listings (including syntax highlighting 
1184# and cross-referencing information) to the XML output. Note that 
1185# enabling this will significantly increase the size of the XML output.
1186
1187XML_PROGRAMLISTING     = YES…

Large files files are truncated, but you can click here to view the full file