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