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