Xcode/XcodeDocSet/Doxyfile
author David Ludwig <dludwig@pobox.com>
Wed, 25 Dec 2013 21:39:48 -0500
changeset 8563 c0e68f3b6bbb
parent 3347 0dc3d85ce0ac
permissions -rw-r--r--
WinRT: compiled the d3d11 renderer's shaders into SDL itself

Previously, the shaders would get compiled separately, the output of which would need to be packaged into the app. This change should make SDL's dll be the only binary needed to include SDL in a WinRT app.
slouken@3331
     1
# Doxyfile 1.6.1
slouken@3331
     2
slouken@3331
     3
# This file describes the settings to be used by the documentation system
slouken@3331
     4
# doxygen (www.doxygen.org) for a project
slouken@3331
     5
#
slouken@3331
     6
# All text after a hash (#) is considered a comment and will be ignored
slouken@3331
     7
# The format is:
slouken@3331
     8
#       TAG = value [value, ...]
slouken@3331
     9
# For lists items can also be appended using:
slouken@3331
    10
#       TAG += value [value, ...]
slouken@3331
    11
# Values that contain spaces should be placed between quotes (" ")
slouken@3331
    12
slouken@3331
    13
#---------------------------------------------------------------------------
slouken@3331
    14
# Project related configuration options
slouken@3331
    15
#---------------------------------------------------------------------------
slouken@3331
    16
slouken@3331
    17
# This tag specifies the encoding used for all characters in the config file 
slouken@3331
    18
# that follow. The default is UTF-8 which is also the encoding used for all 
slouken@3331
    19
# text before the first occurrence of this tag. Doxygen uses libiconv (or the 
slouken@3331
    20
# iconv built into libc) for the transcoding. See 
slouken@3331
    21
# http://www.gnu.org/software/libiconv for the list of possible encodings.
slouken@3331
    22
slouken@3331
    23
DOXYFILE_ENCODING      = UTF-8
slouken@3331
    24
slouken@3331
    25
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded 
slouken@3331
    26
# by quotes) that should identify the project.
slouken@3331
    27
slouken@3331
    28
PROJECT_NAME           = SDL
slouken@3331
    29
slouken@3331
    30
# The PROJECT_NUMBER tag can be used to enter a project or revision number. 
slouken@3331
    31
# This could be handy for archiving the generated documentation or 
slouken@3331
    32
# if some version control system is used.
slouken@3331
    33
slouken@3331
    34
PROJECT_NUMBER         = 1.3.0
slouken@3331
    35
slouken@3331
    36
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
slouken@3331
    37
# base path where the generated documentation will be put. 
slouken@3331
    38
# If a relative path is entered, it will be relative to the location 
slouken@3331
    39
# where doxygen was started. If left blank the current directory will be used.
slouken@3331
    40
slouken@3331
    41
OUTPUT_DIRECTORY       = 
slouken@3331
    42
slouken@3331
    43
# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 
slouken@3331
    44
# 4096 sub-directories (in 2 levels) under the output directory of each output 
slouken@3331
    45
# format and will distribute the generated files over these directories. 
slouken@3331
    46
# Enabling this option can be useful when feeding doxygen a huge amount of 
slouken@3331
    47
# source files, where putting all generated files in the same directory would 
slouken@3331
    48
# otherwise cause performance problems for the file system.
slouken@3331
    49
slouken@3331
    50
CREATE_SUBDIRS         = NO
slouken@3331
    51
slouken@3331
    52
# The OUTPUT_LANGUAGE tag is used to specify the language in which all 
slouken@3331
    53
# documentation generated by doxygen is written. Doxygen will use this 
slouken@3331
    54
# information to generate all constant output in the proper language. 
slouken@3331
    55
# The default language is English, other supported languages are: 
slouken@3331
    56
# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 
slouken@3331
    57
# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 
slouken@3331
    58
# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 
slouken@3331
    59
# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, 
slouken@3331
    60
# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, 
slouken@3331
    61
# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
slouken@3331
    62
slouken@3331
    63
OUTPUT_LANGUAGE        = English
slouken@3331
    64
slouken@3331
    65
# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
slouken@3331
    66
# include brief member descriptions after the members that are listed in 
slouken@3331
    67
# the file and class documentation (similar to JavaDoc). 
slouken@3331
    68
# Set to NO to disable this.
slouken@3331
    69
slouken@3331
    70
BRIEF_MEMBER_DESC      = YES
slouken@3331
    71
slouken@3331
    72
# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
slouken@3331
    73
# the brief description of a member or function before the detailed description. 
slouken@3331
    74
# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
slouken@3331
    75
# brief descriptions will be completely suppressed.
slouken@3331
    76
slouken@3331
    77
REPEAT_BRIEF           = YES
slouken@3331
    78
slouken@3331
    79
# This tag implements a quasi-intelligent brief description abbreviator 
slouken@3331
    80
# that is used to form the text in various listings. Each string 
slouken@3331
    81
# in this list, if found as the leading text of the brief description, will be 
slouken@3331
    82
# stripped from the text and the result after processing the whole list, is 
slouken@3331
    83
# used as the annotated text. Otherwise, the brief description is used as-is. 
slouken@3331
    84
# If left blank, the following values are used ("$name" is automatically 
slouken@3331
    85
# replaced with the name of the entity): "The $name class" "The $name widget" 
slouken@3331
    86
# "The $name file" "is" "provides" "specifies" "contains" 
slouken@3331
    87
# "represents" "a" "an" "the"
slouken@3331
    88
slouken@3331
    89
ABBREVIATE_BRIEF       = "The $name class" \
slouken@3331
    90
                         "The $name widget" \
slouken@3331
    91
                         "The $name file" \
slouken@3331
    92
                         is \
slouken@3331
    93
                         provides \
slouken@3331
    94
                         specifies \
slouken@3331
    95
                         contains \
slouken@3331
    96
                         represents \
slouken@3331
    97
                         a \
slouken@3331
    98
                         an \
slouken@3331
    99
                         the
slouken@3331
   100
slouken@3331
   101
# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
slouken@3331
   102
# Doxygen will generate a detailed section even if there is only a brief 
slouken@3331
   103
# description.
slouken@3331
   104
slouken@3331
   105
ALWAYS_DETAILED_SEC    = NO
slouken@3331
   106
slouken@3331
   107
# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 
slouken@3331
   108
# inherited members of a class in the documentation of that class as if those 
slouken@3331
   109
# members were ordinary class members. Constructors, destructors and assignment 
slouken@3331
   110
# operators of the base classes will not be shown.
slouken@3331
   111
slouken@3331
   112
INLINE_INHERITED_MEMB  = NO
slouken@3331
   113
slouken@3331
   114
# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
slouken@3331
   115
# path before files name in the file list and in the header files. If set 
slouken@3331
   116
# to NO the shortest path that makes the file name unique will be used.
slouken@3331
   117
slouken@3331
   118
FULL_PATH_NAMES        = NO
slouken@3331
   119
slouken@3331
   120
# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
slouken@3331
   121
# can be used to strip a user-defined part of the path. Stripping is 
slouken@3331
   122
# only done if one of the specified strings matches the left-hand part of 
slouken@3331
   123
# the path. The tag can be used to show relative paths in the file list. 
slouken@3331
   124
# If left blank the directory from which doxygen is run is used as the 
slouken@3331
   125
# path to strip.
slouken@3331
   126
slouken@3331
   127
STRIP_FROM_PATH        = 
slouken@3331
   128
slouken@3331
   129
# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 
slouken@3331
   130
# the path mentioned in the documentation of a class, which tells 
slouken@3331
   131
# the reader which header file to include in order to use a class. 
slouken@3331
   132
# If left blank only the name of the header file containing the class 
slouken@3331
   133
# definition is used. Otherwise one should specify the include paths that 
slouken@3331
   134
# are normally passed to the compiler using the -I flag.
slouken@3331
   135
slouken@3331
   136
STRIP_FROM_INC_PATH    = 
slouken@3331
   137
slouken@3331
   138
# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
slouken@3331
   139
# (but less readable) file names. This can be useful is your file systems 
slouken@3331
   140
# doesn't support long names like on DOS, Mac, or CD-ROM.
slouken@3331
   141
slouken@3331
   142
SHORT_NAMES            = NO
slouken@3331
   143
slouken@3331
   144
# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
slouken@3331
   145
# will interpret the first line (until the first dot) of a JavaDoc-style 
slouken@3331
   146
# comment as the brief description. If set to NO, the JavaDoc 
slouken@3331
   147
# comments will behave just like regular Qt-style comments 
slouken@3331
   148
# (thus requiring an explicit @brief command for a brief description.)
slouken@3331
   149
slouken@3347
   150
JAVADOC_AUTOBRIEF      = YES
slouken@3331
   151
slouken@3331
   152
# If the QT_AUTOBRIEF tag is set to YES then Doxygen will 
slouken@3331
   153
# interpret the first line (until the first dot) of a Qt-style 
slouken@3331
   154
# comment as the brief description. If set to NO, the comments 
slouken@3331
   155
# will behave just like regular Qt-style comments (thus requiring 
slouken@3331
   156
# an explicit \brief command for a brief description.)
slouken@3331
   157
slouken@3347
   158
QT_AUTOBRIEF           = YES
slouken@3331
   159
slouken@3331
   160
# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
slouken@3331
   161
# treat a multi-line C++ special comment block (i.e. a block of //! or /// 
slouken@3331
   162
# comments) as a brief description. This used to be the default behaviour. 
slouken@3331
   163
# The new default is to treat a multi-line C++ comment block as a detailed 
slouken@3331
   164
# description. Set this tag to YES if you prefer the old behaviour instead.
slouken@3331
   165
slouken@3331
   166
MULTILINE_CPP_IS_BRIEF = NO
slouken@3331
   167
slouken@3331
   168
# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
slouken@3331
   169
# member inherits the documentation from any documented member that it 
slouken@3331
   170
# re-implements.
slouken@3331
   171
slouken@3331
   172
INHERIT_DOCS           = YES
slouken@3331
   173
slouken@3331
   174
# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 
slouken@3331
   175
# a new page for each member. If set to NO, the documentation of a member will 
slouken@3331
   176
# be part of the file/class/namespace that contains it.
slouken@3331
   177
slouken@3331
   178
SEPARATE_MEMBER_PAGES  = NO
slouken@3331
   179
slouken@3331
   180
# The TAB_SIZE tag can be used to set the number of spaces in a tab. 
slouken@3331
   181
# Doxygen uses this value to replace tabs by spaces in code fragments.
slouken@3331
   182
slouken@3331
   183
TAB_SIZE               = 4
slouken@3331
   184
slouken@3331
   185
# This tag can be used to specify a number of aliases that acts 
slouken@3331
   186
# as commands in the documentation. An alias has the form "name=value". 
slouken@3331
   187
# For example adding "sideeffect=\par Side Effects:\n" will allow you to 
slouken@3331
   188
# put the command \sideeffect (or @sideeffect) in the documentation, which 
slouken@3331
   189
# will result in a user-defined paragraph with heading "Side Effects:". 
slouken@3331
   190
# You can put \n's in the value part of an alias to insert newlines.
slouken@3331
   191
slouken@3331
   192
ALIASES                = 
slouken@3331
   193
slouken@3331
   194
# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 
slouken@3331
   195
# sources only. Doxygen will then generate output that is more tailored for C. 
slouken@3331
   196
# For instance, some of the names that are used will be different. The list 
slouken@3331
   197
# of all members will be omitted, etc.
slouken@3331
   198
slouken@3331
   199
OPTIMIZE_OUTPUT_FOR_C  = YES
slouken@3331
   200
slouken@3331
   201
# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 
slouken@3331
   202
# sources only. Doxygen will then generate output that is more tailored for 
slouken@3331
   203
# Java. For instance, namespaces will be presented as packages, qualified 
slouken@3331
   204
# scopes will look different, etc.
slouken@3331
   205
slouken@3331
   206
OPTIMIZE_OUTPUT_JAVA   = NO
slouken@3331
   207
slouken@3331
   208
# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 
slouken@3331
   209
# sources only. Doxygen will then generate output that is more tailored for 
slouken@3331
   210
# Fortran.
slouken@3331
   211
slouken@3331
   212
OPTIMIZE_FOR_FORTRAN   = NO
slouken@3331
   213
slouken@3331
   214
# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 
slouken@3331
   215
# sources. Doxygen will then generate output that is tailored for 
slouken@3331
   216
# VHDL.
slouken@3331
   217
slouken@3331
   218
OPTIMIZE_OUTPUT_VHDL   = NO
slouken@3331
   219
slouken@3331
   220
# Doxygen selects the parser to use depending on the extension of the files it parses. 
slouken@3331
   221
# With this tag you can assign which parser to use for a given extension. 
slouken@3331
   222
# Doxygen has a built-in mapping, but you can override or extend it using this tag. 
slouken@3331
   223
# The format is ext=language, where ext is a file extension, and language is one of 
slouken@3331
   224
# the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP, 
slouken@3331
   225
# Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat 
slouken@3331
   226
# .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran), 
slouken@3331
   227
# use: inc=Fortran f=C. Note that for custom extensions you also need to set
slouken@3331
   228
# FILE_PATTERNS otherwise the files are not read by doxygen.
slouken@3331
   229
slouken@3331
   230
EXTENSION_MAPPING      = 
slouken@3331
   231
slouken@3331
   232
# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 
slouken@3331
   233
# to include (a tag file for) the STL sources as input, then you should 
slouken@3331
   234
# set this tag to YES in order to let doxygen match functions declarations and 
slouken@3331
   235
# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 
slouken@3331
   236
# func(std::string) {}). This also make the inheritance and collaboration 
slouken@3331
   237
# diagrams that involve STL classes more complete and accurate.
slouken@3331
   238
slouken@3331
   239
BUILTIN_STL_SUPPORT    = NO
slouken@3331
   240
slouken@3331
   241
# If you use Microsoft's C++/CLI language, you should set this option to YES to 
slouken@3331
   242
# enable parsing support.
slouken@3331
   243
slouken@3331
   244
CPP_CLI_SUPPORT        = NO
slouken@3331
   245
slouken@3331
   246
# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 
slouken@3331
   247
# Doxygen will parse them like normal C++ but will assume all classes use public 
slouken@3331
   248
# instead of private inheritance when no explicit protection keyword is present.
slouken@3331
   249
slouken@3331
   250
SIP_SUPPORT            = NO
slouken@3331
   251
slouken@3331
   252
# For Microsoft's IDL there are propget and propput attributes to indicate getter 
slouken@3331
   253
# and setter methods for a property. Setting this option to YES (the default) 
slouken@3331
   254
# will make doxygen to replace the get and set methods by a property in the 
slouken@3331
   255
# documentation. This will only work if the methods are indeed getting or 
slouken@3331
   256
# setting a simple type. If this is not the case, or you want to show the 
slouken@3331
   257
# methods anyway, you should set this option to NO.
slouken@3331
   258
slouken@3331
   259
IDL_PROPERTY_SUPPORT   = YES
slouken@3331
   260
slouken@3331
   261
# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
slouken@3331
   262
# tag is set to YES, then doxygen will reuse the documentation of the first 
slouken@3331
   263
# member in the group (if any) for the other members of the group. By default 
slouken@3331
   264
# all members of a group must be documented explicitly.
slouken@3331
   265
slouken@3331
   266
DISTRIBUTE_GROUP_DOC   = NO
slouken@3331
   267
slouken@3331
   268
# Set the SUBGROUPING tag to YES (the default) to allow class member groups of 
slouken@3331
   269
# the same type (for instance a group of public functions) to be put as a 
slouken@3331
   270
# subgroup of that type (e.g. under the Public Functions section). Set it to 
slouken@3331
   271
# NO to prevent subgrouping. Alternatively, this can be done per class using 
slouken@3331
   272
# the \nosubgrouping command.
slouken@3331
   273
slouken@3331
   274
SUBGROUPING            = YES
slouken@3331
   275
slouken@3331
   276
# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 
slouken@3331
   277
# is documented as struct, union, or enum with the name of the typedef. So 
slouken@3331
   278
# typedef struct TypeS {} TypeT, will appear in the documentation as a struct 
slouken@3331
   279
# with name TypeT. When disabled the typedef will appear as a member of a file, 
slouken@3331
   280
# namespace, or class. And the struct will be named TypeS. This can typically 
slouken@3331
   281
# be useful for C code in case the coding convention dictates that all compound 
slouken@3331
   282
# types are typedef'ed and only the typedef is referenced, never the tag name.
slouken@3331
   283
slouken@3331
   284
TYPEDEF_HIDES_STRUCT   = YES
slouken@3331
   285
slouken@3331
   286
# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 
slouken@3331
   287
# determine which symbols to keep in memory and which to flush to disk. 
slouken@3331
   288
# When the cache is full, less often used symbols will be written to disk. 
slouken@3331
   289
# For small to medium size projects (<1000 input files) the default value is 
slouken@3331
   290
# probably good enough. For larger projects a too small cache size can cause 
slouken@3331
   291
# doxygen to be busy swapping symbols to and from disk most of the time 
slouken@3331
   292
# causing a significant performance penality. 
slouken@3331
   293
# If the system has enough physical memory increasing the cache will improve the 
slouken@3331
   294
# performance by keeping more symbols in memory. Note that the value works on 
slouken@3331
   295
# a logarithmic scale so increasing the size by one will rougly double the 
slouken@3331
   296
# memory usage. The cache size is given by this formula: 
slouken@3331
   297
# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0, 
slouken@3331
   298
# corresponding to a cache size of 2^16 = 65536 symbols
slouken@3331
   299
slouken@3331
   300
SYMBOL_CACHE_SIZE      = 0
slouken@3331
   301
slouken@3331
   302
#---------------------------------------------------------------------------
slouken@3331
   303
# Build related configuration options
slouken@3331
   304
#---------------------------------------------------------------------------
slouken@3331
   305
slouken@3331
   306
# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
slouken@3331
   307
# documentation are documented, even if no documentation was available. 
slouken@3331
   308
# Private class members and static file members will be hidden unless 
slouken@3331
   309
# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
slouken@3331
   310
slouken@3331
   311
EXTRACT_ALL            = YES
slouken@3331
   312
slouken@3331
   313
# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
slouken@3331
   314
# will be included in the documentation.
slouken@3331
   315
slouken@3331
   316
EXTRACT_PRIVATE        = NO
slouken@3331
   317
slouken@3331
   318
# If the EXTRACT_STATIC tag is set to YES all static members of a file 
slouken@3331
   319
# will be included in the documentation.
slouken@3331
   320
slouken@3331
   321
EXTRACT_STATIC         = NO
slouken@3331
   322
slouken@3331
   323
# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
slouken@3331
   324
# defined locally in source files will be included in the documentation. 
slouken@3331
   325
# If set to NO only classes defined in header files are included.
slouken@3331
   326
slouken@3331
   327
EXTRACT_LOCAL_CLASSES  = NO
slouken@3331
   328
slouken@3331
   329
# This flag is only useful for Objective-C code. When set to YES local 
slouken@3331
   330
# methods, which are defined in the implementation section but not in 
slouken@3331
   331
# the interface are included in the documentation. 
slouken@3331
   332
# If set to NO (the default) only methods in the interface are included.
slouken@3331
   333
slouken@3331
   334
EXTRACT_LOCAL_METHODS  = NO
slouken@3331
   335
slouken@3331
   336
# If this flag is set to YES, the members of anonymous namespaces will be 
slouken@3331
   337
# extracted and appear in the documentation as a namespace called 
slouken@3331
   338
# 'anonymous_namespace{file}', where file will be replaced with the base 
slouken@3331
   339
# name of the file that contains the anonymous namespace. By default 
slouken@3331
   340
# anonymous namespace are hidden.
slouken@3331
   341
slouken@3331
   342
EXTRACT_ANON_NSPACES   = NO
slouken@3331
   343
slouken@3331
   344
# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
slouken@3331
   345
# undocumented members of documented classes, files or namespaces. 
slouken@3331
   346
# If set to NO (the default) these members will be included in the 
slouken@3331
   347
# various overviews, but no documentation section is generated. 
slouken@3331
   348
# This option has no effect if EXTRACT_ALL is enabled.
slouken@3331
   349
slouken@3331
   350
HIDE_UNDOC_MEMBERS     = NO
slouken@3331
   351
slouken@3331
   352
# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
slouken@3331
   353
# undocumented classes that are normally visible in the class hierarchy. 
slouken@3331
   354
# If set to NO (the default) these classes will be included in the various 
slouken@3331
   355
# overviews. This option has no effect if EXTRACT_ALL is enabled.
slouken@3331
   356
slouken@3331
   357
HIDE_UNDOC_CLASSES     = NO
slouken@3331
   358
slouken@3331
   359
# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
slouken@3331
   360
# friend (class|struct|union) declarations. 
slouken@3331
   361
# If set to NO (the default) these declarations will be included in the 
slouken@3331
   362
# documentation.
slouken@3331
   363
slouken@3331
   364
HIDE_FRIEND_COMPOUNDS  = NO
slouken@3331
   365
slouken@3331
   366
# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 
slouken@3331
   367
# documentation blocks found inside the body of a function. 
slouken@3331
   368
# If set to NO (the default) these blocks will be appended to the 
slouken@3331
   369
# function's detailed documentation block.
slouken@3331
   370
slouken@3331
   371
HIDE_IN_BODY_DOCS      = NO
slouken@3331
   372
slouken@3331
   373
# The INTERNAL_DOCS tag determines if documentation 
slouken@3331
   374
# that is typed after a \internal command is included. If the tag is set 
slouken@3331
   375
# to NO (the default) then the documentation will be excluded. 
slouken@3331
   376
# Set it to YES to include the internal documentation.
slouken@3331
   377
slouken@3331
   378
INTERNAL_DOCS          = NO
slouken@3331
   379
slouken@3331
   380
# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
slouken@3331
   381
# file names in lower-case letters. If set to YES upper-case letters are also 
slouken@3331
   382
# allowed. This is useful if you have classes or files whose names only differ 
slouken@3331
   383
# in case and if your file system supports case sensitive file names. Windows 
slouken@3331
   384
# and Mac users are advised to set this option to NO.
slouken@3331
   385
slouken@3331
   386
CASE_SENSE_NAMES       = YES
slouken@3331
   387
slouken@3331
   388
# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
slouken@3331
   389
# will show members with their full class and namespace scopes in the 
slouken@3331
   390
# documentation. If set to YES the scope will be hidden.
slouken@3331
   391
slouken@3331
   392
HIDE_SCOPE_NAMES       = YES
slouken@3331
   393
slouken@3331
   394
# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
slouken@3331
   395
# will put a list of the files that are included by a file in the documentation 
slouken@3331
   396
# of that file.
slouken@3331
   397
slouken@3331
   398
SHOW_INCLUDE_FILES     = YES
slouken@3331
   399
slouken@3331
   400
# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
slouken@3331
   401
# is inserted in the documentation for inline members.
slouken@3331
   402
slouken@3331
   403
INLINE_INFO            = YES
slouken@3331
   404
slouken@3331
   405
# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
slouken@3331
   406
# will sort the (detailed) documentation of file and class members 
slouken@3331
   407
# alphabetically by member name. If set to NO the members will appear in 
slouken@3331
   408
# declaration order.
slouken@3331
   409
slouken@3331
   410
SORT_MEMBER_DOCS       = NO
slouken@3331
   411
slouken@3331
   412
# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 
slouken@3331
   413
# brief documentation of file, namespace and class members alphabetically 
slouken@3331
   414
# by member name. If set to NO (the default) the members will appear in 
slouken@3331
   415
# declaration order.
slouken@3331
   416
slouken@3331
   417
SORT_BRIEF_DOCS        = NO
slouken@3331
   418
slouken@3331
   419
# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
slouken@3331
   420
# will sort the (brief and detailed) documentation of class members so that
slouken@3331
   421
# constructors and destructors are listed first. If set to NO (the default)
slouken@3331
   422
# the constructors will appear in the respective orders defined by
slouken@3331
   423
# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
slouken@3331
   424
# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
slouken@3331
   425
# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
slouken@3331
   426
slouken@3331
   427
SORT_MEMBERS_CTORS_1ST = NO
slouken@3331
   428
slouken@3331
   429
# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 
slouken@3331
   430
# hierarchy of group names into alphabetical order. If set to NO (the default) 
slouken@3331
   431
# the group names will appear in their defined order.
slouken@3331
   432
slouken@3331
   433
SORT_GROUP_NAMES       = NO
slouken@3331
   434
slouken@3331
   435
# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 
slouken@3331
   436
# sorted by fully-qualified names, including namespaces. If set to 
slouken@3331
   437
# NO (the default), the class list will be sorted only by class name, 
slouken@3331
   438
# not including the namespace part. 
slouken@3331
   439
# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 
slouken@3331
   440
# Note: This option applies only to the class list, not to the 
slouken@3331
   441
# alphabetical list.
slouken@3331
   442
slouken@3331
   443
SORT_BY_SCOPE_NAME     = NO
slouken@3331
   444
slouken@3331
   445
# The GENERATE_TODOLIST tag can be used to enable (YES) or 
slouken@3331
   446
# disable (NO) the todo list. This list is created by putting \todo 
slouken@3331
   447
# commands in the documentation.
slouken@3331
   448
slouken@3331
   449
GENERATE_TODOLIST      = YES
slouken@3331
   450
slouken@3331
   451
# The GENERATE_TESTLIST tag can be used to enable (YES) or 
slouken@3331
   452
# disable (NO) the test list. This list is created by putting \test 
slouken@3331
   453
# commands in the documentation.
slouken@3331
   454
slouken@3331
   455
GENERATE_TESTLIST      = YES
slouken@3331
   456
slouken@3331
   457
# The GENERATE_BUGLIST tag can be used to enable (YES) or 
slouken@3331
   458
# disable (NO) the bug list. This list is created by putting \bug 
slouken@3331
   459
# commands in the documentation.
slouken@3331
   460
slouken@3331
   461
GENERATE_BUGLIST       = YES
slouken@3331
   462
slouken@3331
   463
# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
slouken@3331
   464
# disable (NO) the deprecated list. This list is created by putting 
slouken@3331
   465
# \deprecated commands in the documentation.
slouken@3331
   466
slouken@3331
   467
GENERATE_DEPRECATEDLIST= YES
slouken@3331
   468
slouken@3331
   469
# The ENABLED_SECTIONS tag can be used to enable conditional 
slouken@3331
   470
# documentation sections, marked by \if sectionname ... \endif.
slouken@3331
   471
slouken@3331
   472
ENABLED_SECTIONS       = 
slouken@3331
   473
slouken@3331
   474
# The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
slouken@3331
   475
# the initial value of a variable or define consists of for it to appear in 
slouken@3331
   476
# the documentation. If the initializer consists of more lines than specified 
slouken@3331
   477
# here it will be hidden. Use a value of 0 to hide initializers completely. 
slouken@3331
   478
# The appearance of the initializer of individual variables and defines in the 
slouken@3331
   479
# documentation can be controlled using \showinitializer or \hideinitializer 
slouken@3331
   480
# command in the documentation regardless of this setting.
slouken@3331
   481
slouken@3331
   482
MAX_INITIALIZER_LINES  = 30
slouken@3331
   483
slouken@3331
   484
# Set the SHOW_USED_FILES tag to NO to disable the list of files generated 
slouken@3331
   485
# at the bottom of the documentation of classes and structs. If set to YES the 
slouken@3331
   486
# list will mention the files that were used to generate the documentation.
slouken@3331
   487
slouken@3331
   488
SHOW_USED_FILES        = YES
slouken@3331
   489
slouken@3331
   490
# If the sources in your project are distributed over multiple directories 
slouken@3331
   491
# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy 
slouken@3331
   492
# in the documentation. The default is NO.
slouken@3331
   493
slouken@3331
   494
SHOW_DIRECTORIES       = NO
slouken@3331
   495
slouken@3331
   496
# Set the SHOW_FILES tag to NO to disable the generation of the Files page. 
slouken@3331
   497
# This will remove the Files entry from the Quick Index and from the 
slouken@3331
   498
# Folder Tree View (if specified). The default is YES.
slouken@3331
   499
slouken@3331
   500
SHOW_FILES             = YES
slouken@3331
   501
slouken@3331
   502
# Set the SHOW_NAMESPACES tag to NO to disable the generation of the 
slouken@3331
   503
# Namespaces page.  This will remove the Namespaces entry from the Quick Index 
slouken@3331
   504
# and from the Folder Tree View (if specified). The default is YES.
slouken@3331
   505
slouken@3331
   506
SHOW_NAMESPACES        = NO
slouken@3331
   507
slouken@3331
   508
# The FILE_VERSION_FILTER tag can be used to specify a program or script that 
slouken@3331
   509
# doxygen should invoke to get the current version for each file (typically from 
slouken@3331
   510
# the version control system). Doxygen will invoke the program by executing (via 
slouken@3331
   511
# popen()) the command <command> <input-file>, where <command> is the value of 
slouken@3331
   512
# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 
slouken@3331
   513
# provided by doxygen. Whatever the program writes to standard output 
slouken@3331
   514
# is used as the file version. See the manual for examples.
slouken@3331
   515
slouken@3331
   516
FILE_VERSION_FILTER    = 
slouken@3331
   517
slouken@3331
   518
# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by 
slouken@3331
   519
# doxygen. The layout file controls the global structure of the generated output files 
slouken@3331
   520
# in an output format independent way. The create the layout file that represents 
slouken@3331
   521
# doxygen's defaults, run doxygen with the -l option. You can optionally specify a 
slouken@3331
   522
# file name after the option, if omitted DoxygenLayout.xml will be used as the name 
slouken@3331
   523
# of the layout file.
slouken@3331
   524
slouken@3331
   525
LAYOUT_FILE            = 
slouken@3331
   526
slouken@3331
   527
#---------------------------------------------------------------------------
slouken@3331
   528
# configuration options related to warning and progress messages
slouken@3331
   529
#---------------------------------------------------------------------------
slouken@3331
   530
slouken@3331
   531
# The QUIET tag can be used to turn on/off the messages that are generated 
slouken@3331
   532
# by doxygen. Possible values are YES and NO. If left blank NO is used.
slouken@3331
   533
slouken@3331
   534
QUIET                  = YES
slouken@3331
   535
slouken@3331
   536
# The WARNINGS tag can be used to turn on/off the warning messages that are 
slouken@3331
   537
# generated by doxygen. Possible values are YES and NO. If left blank 
slouken@3331
   538
# NO is used.
slouken@3331
   539
slouken@3331
   540
WARNINGS               = YES
slouken@3331
   541
slouken@3331
   542
# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
slouken@3331
   543
# for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
slouken@3331
   544
# automatically be disabled.
slouken@3331
   545
slouken@3331
   546
WARN_IF_UNDOCUMENTED   = YES
slouken@3331
   547
slouken@3331
   548
# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 
slouken@3331
   549
# potential errors in the documentation, such as not documenting some 
slouken@3331
   550
# parameters in a documented function, or documenting parameters that 
slouken@3331
   551
# don't exist or using markup commands wrongly.
slouken@3331
   552
slouken@3331
   553
WARN_IF_DOC_ERROR      = YES
slouken@3331
   554
slouken@3331
   555
# This WARN_NO_PARAMDOC option can be abled to get warnings for 
slouken@3331
   556
# functions that are documented, but have no documentation for their parameters 
slouken@3331
   557
# or return value. If set to NO (the default) doxygen will only warn about 
slouken@3331
   558
# wrong or incomplete parameter documentation, but not about the absence of 
slouken@3331
   559
# documentation.
slouken@3331
   560
slouken@3331
   561
WARN_NO_PARAMDOC       = YES
slouken@3331
   562
slouken@3331
   563
# The WARN_FORMAT tag determines the format of the warning messages that 
slouken@3331
   564
# doxygen can produce. The string should contain the $file, $line, and $text 
slouken@3331
   565
# tags, which will be replaced by the file and line number from which the 
slouken@3331
   566
# warning originated and the warning text. Optionally the format may contain 
slouken@3331
   567
# $version, which will be replaced by the version of the file (if it could 
slouken@3331
   568
# be obtained via FILE_VERSION_FILTER)
slouken@3331
   569
slouken@3331
   570
WARN_FORMAT            = "$file:$line: $text"
slouken@3331
   571
slouken@3331
   572
# The WARN_LOGFILE tag can be used to specify a file to which warning 
slouken@3331
   573
# and error messages should be written. If left blank the output is written 
slouken@3331
   574
# to stderr.
slouken@3331
   575
slouken@3331
   576
WARN_LOGFILE           = 
slouken@3331
   577
slouken@3331
   578
#---------------------------------------------------------------------------
slouken@3331
   579
# configuration options related to the input files
slouken@3331
   580
#---------------------------------------------------------------------------
slouken@3331
   581
slouken@3331
   582
# The INPUT tag can be used to specify the files and/or directories that contain 
slouken@3331
   583
# documented source files. You may enter file names like "myfile.cpp" or 
slouken@3331
   584
# directories like "/usr/src/myproject". Separate the files or directories 
slouken@3331
   585
# with spaces.
slouken@3331
   586
slouken@3331
   587
INPUT                  = ../../include
slouken@3331
   588
slouken@3331
   589
# This tag can be used to specify the character encoding of the source files 
slouken@3331
   590
# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is 
slouken@3331
   591
# also the default input encoding. Doxygen uses libiconv (or the iconv built 
slouken@3331
   592
# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for 
slouken@3331
   593
# the list of possible encodings.
slouken@3331
   594
slouken@3331
   595
INPUT_ENCODING         = UTF-8
slouken@3331
   596
slouken@3331
   597
# If the value of the INPUT tag contains directories, you can use the 
slouken@3331
   598
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
slouken@3331
   599
# and *.h) to filter out the source-files in the directories. If left 
slouken@3331
   600
# blank the following patterns are tested: 
slouken@3331
   601
# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx 
slouken@3331
   602
# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
slouken@3331
   603
slouken@3331
   604
FILE_PATTERNS          = *.c \
slouken@3331
   605
                         *.cc \
slouken@3331
   606
                         *.cxx \
slouken@3331
   607
                         *.cpp \
slouken@3331
   608
                         *.c++ \
slouken@3331
   609
                         *.d \
slouken@3331
   610
                         *.java \
slouken@3331
   611
                         *.ii \
slouken@3331
   612
                         *.ixx \
slouken@3331
   613
                         *.ipp \
slouken@3331
   614
                         *.i++ \
slouken@3331
   615
                         *.inl \
slouken@3331
   616
                         *.h \
slouken@3331
   617
                         *.hh \
slouken@3331
   618
                         *.hxx \
slouken@3331
   619
                         *.hpp \
slouken@3331
   620
                         *.h++ \
slouken@3331
   621
                         *.idl \
slouken@3331
   622
                         *.odl \
slouken@3331
   623
                         *.cs \
slouken@3331
   624
                         *.php \
slouken@3331
   625
                         *.php3 \
slouken@3331
   626
                         *.inc \
slouken@3331
   627
                         *.m \
slouken@3331
   628
                         *.mm \
slouken@3331
   629
                         *.dox \
slouken@3331
   630
                         *.py \
slouken@3331
   631
                         *.f90 \
slouken@3331
   632
                         *.f \
slouken@3331
   633
                         *.vhd \
slouken@3331
   634
                         *.vhdl
slouken@3331
   635
slouken@3331
   636
# The RECURSIVE tag can be used to turn specify whether or not subdirectories 
slouken@3331
   637
# should be searched for input files as well. Possible values are YES and NO. 
slouken@3331
   638
# If left blank NO is used.
slouken@3331
   639
slouken@3331
   640
RECURSIVE              = NO
slouken@3331
   641
slouken@3331
   642
# The EXCLUDE tag can be used to specify files and/or directories that should 
slouken@3331
   643
# excluded from the INPUT source files. This way you can easily exclude a 
slouken@3331
   644
# subdirectory from a directory tree whose root is specified with the INPUT tag.
slouken@3331
   645
slouken@3331
   646
EXCLUDE                = 
slouken@3331
   647
slouken@3331
   648
# The EXCLUDE_SYMLINKS tag can be used select whether or not files or 
slouken@3331
   649
# directories that are symbolic links (a Unix filesystem feature) are excluded 
slouken@3331
   650
# from the input.
slouken@3331
   651
slouken@3331
   652
EXCLUDE_SYMLINKS       = NO
slouken@3331
   653
slouken@3331
   654
# If the value of the INPUT tag contains directories, you can use the 
slouken@3331
   655
# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
slouken@3331
   656
# certain files from those directories. Note that the wildcards are matched 
slouken@3331
   657
# against the file with absolute path, so to exclude all test directories 
slouken@3331
   658
# for example use the pattern */test/*
slouken@3331
   659
slouken@3331
   660
EXCLUDE_PATTERNS       = 
slouken@3331
   661
slouken@3331
   662
# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 
slouken@3331
   663
# (namespaces, classes, functions, etc.) that should be excluded from the 
slouken@3331
   664
# output. The symbol name can be a fully qualified name, a word, or if the 
slouken@3331
   665
# wildcard * is used, a substring. Examples: ANamespace, AClass, 
slouken@3331
   666
# AClass::ANamespace, ANamespace::*Test
slouken@3331
   667
slouken@3331
   668
EXCLUDE_SYMBOLS        = 
slouken@3331
   669
slouken@3331
   670
# The EXAMPLE_PATH tag can be used to specify one or more files or 
slouken@3331
   671
# directories that contain example code fragments that are included (see 
slouken@3331
   672
# the \include command).
slouken@3331
   673
slouken@3331
   674
EXAMPLE_PATH           = 
slouken@3331
   675
slouken@3331
   676
# If the value of the EXAMPLE_PATH tag contains directories, you can use the 
slouken@3331
   677
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
slouken@3331
   678
# and *.h) to filter out the source-files in the directories. If left 
slouken@3331
   679
# blank all files are included.
slouken@3331
   680
slouken@3331
   681
EXAMPLE_PATTERNS       = *
slouken@3331
   682
slouken@3331
   683
# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
slouken@3331
   684
# searched for input files to be used with the \include or \dontinclude 
slouken@3331
   685
# commands irrespective of the value of the RECURSIVE tag. 
slouken@3331
   686
# Possible values are YES and NO. If left blank NO is used.
slouken@3331
   687
slouken@3331
   688
EXAMPLE_RECURSIVE      = NO
slouken@3331
   689
slouken@3331
   690
# The IMAGE_PATH tag can be used to specify one or more files or 
slouken@3331
   691
# directories that contain image that are included in the documentation (see 
slouken@3331
   692
# the \image command).
slouken@3331
   693
slouken@3331
   694
IMAGE_PATH             = 
slouken@3331
   695
slouken@3331
   696
# The INPUT_FILTER tag can be used to specify a program that doxygen should 
slouken@3331
   697
# invoke to filter for each input file. Doxygen will invoke the filter program 
slouken@3331
   698
# by executing (via popen()) the command <filter> <input-file>, where <filter> 
slouken@3331
   699
# is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
slouken@3331
   700
# input file. Doxygen will then use the output that the filter program writes 
slouken@3331
   701
# to standard output.  If FILTER_PATTERNS is specified, this tag will be 
slouken@3331
   702
# ignored.
slouken@3331
   703
slouken@3331
   704
INPUT_FILTER           = 
slouken@3331
   705
slouken@3331
   706
# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 
slouken@3331
   707
# basis.  Doxygen will compare the file name with each pattern and apply the 
slouken@3331
   708
# filter if there is a match.  The filters are a list of the form: 
slouken@3331
   709
# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 
slouken@3331
   710
# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER 
slouken@3331
   711
# is applied to all files.
slouken@3331
   712
slouken@3331
   713
FILTER_PATTERNS        = 
slouken@3331
   714
slouken@3331
   715
# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
slouken@3331
   716
# INPUT_FILTER) will be used to filter the input files when producing source 
slouken@3331
   717
# files to browse (i.e. when SOURCE_BROWSER is set to YES).
slouken@3331
   718
slouken@3331
   719
FILTER_SOURCE_FILES    = NO
slouken@3331
   720
slouken@3331
   721
#---------------------------------------------------------------------------
slouken@3331
   722
# configuration options related to source browsing
slouken@3331
   723
#---------------------------------------------------------------------------
slouken@3331
   724
slouken@3331
   725
# If the SOURCE_BROWSER tag is set to YES then a list of source files will 
slouken@3331
   726
# be generated. Documented entities will be cross-referenced with these sources. 
slouken@3331
   727
# Note: To get rid of all source code in the generated output, make sure also 
slouken@3331
   728
# VERBATIM_HEADERS is set to NO.
slouken@3331
   729
slouken@3331
   730
SOURCE_BROWSER         = NO
slouken@3331
   731
slouken@3331
   732
# Setting the INLINE_SOURCES tag to YES will include the body 
slouken@3331
   733
# of functions and classes directly in the documentation.
slouken@3331
   734
slouken@3331
   735
INLINE_SOURCES         = NO
slouken@3331
   736
slouken@3331
   737
# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
slouken@3331
   738
# doxygen to hide any special comment blocks from generated source code 
slouken@3331
   739
# fragments. Normal C and C++ comments will always remain visible.
slouken@3331
   740
slouken@3331
   741
STRIP_CODE_COMMENTS    = YES
slouken@3331
   742
slouken@3331
   743
# If the REFERENCED_BY_RELATION tag is set to YES 
slouken@3331
   744
# then for each documented function all documented 
slouken@3331
   745
# functions referencing it will be listed.
slouken@3331
   746
slouken@3331
   747
REFERENCED_BY_RELATION = YES
slouken@3331
   748
slouken@3331
   749
# If the REFERENCES_RELATION tag is set to YES 
slouken@3331
   750
# then for each documented function all documented entities 
slouken@3331
   751
# called/used by that function will be listed.
slouken@3331
   752
slouken@3331
   753
REFERENCES_RELATION    = YES
slouken@3331
   754
slouken@3331
   755
# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 
slouken@3331
   756
# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 
slouken@3331
   757
# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 
slouken@3331
   758
# link to the source code.  Otherwise they will link to the documentation.
slouken@3331
   759
slouken@3331
   760
REFERENCES_LINK_SOURCE = YES
slouken@3331
   761
slouken@3331
   762
# If the USE_HTAGS tag is set to YES then the references to source code 
slouken@3331
   763
# will point to the HTML generated by the htags(1) tool instead of doxygen 
slouken@3331
   764
# built-in source browser. The htags tool is part of GNU's global source 
slouken@3331
   765
# tagging system (see http://www.gnu.org/software/global/global.html). You 
slouken@3331
   766
# will need version 4.8.6 or higher.
slouken@3331
   767
slouken@3331
   768
USE_HTAGS              = NO
slouken@3331
   769
slouken@3331
   770
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
slouken@3331
   771
# will generate a verbatim copy of the header file for each class for 
slouken@3331
   772
# which an include is specified. Set to NO to disable this.
slouken@3331
   773
slouken@3331
   774
VERBATIM_HEADERS       = NO
slouken@3331
   775
slouken@3331
   776
#---------------------------------------------------------------------------
slouken@3331
   777
# configuration options related to the alphabetical class index
slouken@3331
   778
#---------------------------------------------------------------------------
slouken@3331
   779
slouken@3331
   780
# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
slouken@3331
   781
# of all compounds will be generated. Enable this if the project 
slouken@3331
   782
# contains a lot of classes, structs, unions or interfaces.
slouken@3331
   783
slouken@3331
   784
ALPHABETICAL_INDEX     = YES
slouken@3331
   785
slouken@3331
   786
# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
slouken@3331
   787
# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
slouken@3331
   788
# in which this list will be split (can be a number in the range [1..20])
slouken@3331
   789
slouken@3331
   790
COLS_IN_ALPHA_INDEX    = 5
slouken@3331
   791
slouken@3331
   792
# In case all classes in a project start with a common prefix, all 
slouken@3331
   793
# classes will be put under the same header in the alphabetical index. 
slouken@3331
   794
# The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
slouken@3331
   795
# should be ignored while generating the index headers.
slouken@3331
   796
slouken@3331
   797
IGNORE_PREFIX          = 
slouken@3331
   798
slouken@3331
   799
#---------------------------------------------------------------------------
slouken@3331
   800
# configuration options related to the HTML output
slouken@3331
   801
#---------------------------------------------------------------------------
slouken@3331
   802
slouken@3331
   803
# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
slouken@3331
   804
# generate HTML output.
slouken@3331
   805
slouken@3331
   806
GENERATE_HTML          = YES
slouken@3331
   807
slouken@3331
   808
# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
slouken@3331
   809
# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
slouken@3331
   810
# put in front of it. If left blank `html' will be used as the default path.
slouken@3331
   811
slouken@3331
   812
HTML_OUTPUT            = html
slouken@3331
   813
slouken@3331
   814
# The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
slouken@3331
   815
# each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
slouken@3331
   816
# doxygen will generate files with .html extension.
slouken@3331
   817
slouken@3331
   818
HTML_FILE_EXTENSION    = .html
slouken@3331
   819
slouken@3331
   820
# The HTML_HEADER tag can be used to specify a personal HTML header for 
slouken@3331
   821
# each generated HTML page. If it is left blank doxygen will generate a 
slouken@3331
   822
# standard header.
slouken@3331
   823
slouken@3331
   824
HTML_HEADER            = 
slouken@3331
   825
slouken@3331
   826
# The HTML_FOOTER tag can be used to specify a personal HTML footer for 
slouken@3331
   827
# each generated HTML page. If it is left blank doxygen will generate a 
slouken@3331
   828
# standard footer.
slouken@3331
   829
slouken@3331
   830
HTML_FOOTER            = 
slouken@3331
   831
slouken@3331
   832
# The HTML_STYLESHEET tag can be used to specify a user-defined cascading 
slouken@3331
   833
# style sheet that is used by each HTML page. It can be used to 
slouken@3331
   834
# fine-tune the look of the HTML output. If the tag is left blank doxygen 
slouken@3331
   835
# will generate a default style sheet. Note that doxygen will try to copy 
slouken@3331
   836
# the style sheet file to the HTML output directory, so don't put your own 
slouken@3331
   837
# stylesheet in the HTML output directory as well, or it will be erased!
slouken@3331
   838
slouken@3331
   839
HTML_STYLESHEET        = 
slouken@3331
   840
slouken@3331
   841
# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, 
slouken@3331
   842
# files or namespaces will be aligned in HTML using tables. If set to 
slouken@3331
   843
# NO a bullet list will be used.
slouken@3331
   844
slouken@3331
   845
HTML_ALIGN_MEMBERS     = YES
slouken@3331
   846
slouken@3331
   847
# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 
slouken@3331
   848
# documentation will contain sections that can be hidden and shown after the 
slouken@3331
   849
# page has loaded. For this to work a browser that supports 
slouken@3331
   850
# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox 
slouken@3331
   851
# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
slouken@3331
   852
slouken@3331
   853
HTML_DYNAMIC_SECTIONS  = NO
slouken@3331
   854
slouken@3331
   855
# If the GENERATE_DOCSET tag is set to YES, additional index files 
slouken@3331
   856
# will be generated that can be used as input for Apple's Xcode 3 
slouken@3331
   857
# integrated development environment, introduced with OSX 10.5 (Leopard). 
slouken@3331
   858
# To create a documentation set, doxygen will generate a Makefile in the 
slouken@3331
   859
# HTML output directory. Running make will produce the docset in that 
slouken@3331
   860
# directory and running "make install" will install the docset in 
slouken@3331
   861
# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 
slouken@3331
   862
# it at startup. 
slouken@3331
   863
# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.
slouken@3331
   864
slouken@3331
   865
GENERATE_DOCSET        = YES
slouken@3331
   866
slouken@3331
   867
# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 
slouken@3331
   868
# feed. A documentation feed provides an umbrella under which multiple 
slouken@3331
   869
# documentation sets from a single provider (such as a company or product suite) 
slouken@3331
   870
# can be grouped.
slouken@3331
   871
slouken@3331
   872
DOCSET_FEEDNAME        = "Doxygen generated docs for SDL"
slouken@3331
   873
slouken@3331
   874
# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 
slouken@3331
   875
# should uniquely identify the documentation set bundle. This should be a 
slouken@3331
   876
# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 
slouken@3331
   877
# will append .docset to the name.
slouken@3331
   878
slouken@3331
   879
DOCSET_BUNDLE_ID       = org.libsdl.sdl
slouken@3331
   880
slouken@3331
   881
# If the GENERATE_HTMLHELP tag is set to YES, additional index files 
slouken@3331
   882
# will be generated that can be used as input for tools like the 
slouken@3331
   883
# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 
slouken@3331
   884
# of the generated HTML documentation.
slouken@3331
   885
slouken@3331
   886
GENERATE_HTMLHELP      = NO
slouken@3331
   887
slouken@3331
   888
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
slouken@3331
   889
# be used to specify the file name of the resulting .chm file. You 
slouken@3331
   890
# can add a path in front of the file if the result should not be 
slouken@3331
   891
# written to the html output directory.
slouken@3331
   892
slouken@3331
   893
CHM_FILE               = SDL.chm
slouken@3331
   894
slouken@3331
   895
# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
slouken@3331
   896
# be used to specify the location (absolute path including file name) of 
slouken@3331
   897
# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 
slouken@3331
   898
# the HTML help compiler on the generated index.hhp.
slouken@3331
   899
slouken@3331
   900
HHC_LOCATION           = "C:/Program Files/HTML Help Workshop/hhc.exe"
slouken@3331
   901
slouken@3331
   902
# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
slouken@3331
   903
# controls if a separate .chi index file is generated (YES) or that 
slouken@3331
   904
# it should be included in the master .chm file (NO).
slouken@3331
   905
slouken@3331
   906
GENERATE_CHI           = NO
slouken@3331
   907
slouken@3331
   908
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 
slouken@3331
   909
# is used to encode HtmlHelp index (hhk), content (hhc) and project file 
slouken@3331
   910
# content.
slouken@3331
   911
slouken@3331
   912
CHM_INDEX_ENCODING     = 
slouken@3331
   913
slouken@3331
   914
# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
slouken@3331
   915
# controls whether a binary table of contents is generated (YES) or a 
slouken@3331
   916
# normal table of contents (NO) in the .chm file.
slouken@3331
   917
slouken@3331
   918
BINARY_TOC             = NO
slouken@3331
   919
slouken@3331
   920
# The TOC_EXPAND flag can be set to YES to add extra items for group members 
slouken@3331
   921
# to the contents of the HTML help documentation and to the tree view.
slouken@3331
   922
slouken@3331
   923
TOC_EXPAND             = YES
slouken@3331
   924
slouken@3331
   925
# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER 
slouken@3331
   926
# are set, an additional index file will be generated that can be used as input for 
slouken@3331
   927
# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated 
slouken@3331
   928
# HTML documentation.
slouken@3331
   929
slouken@3331
   930
GENERATE_QHP           = NO
slouken@3331
   931
slouken@3331
   932
# If the QHG_LOCATION tag is specified, the QCH_FILE tag can 
slouken@3331
   933
# be used to specify the file name of the resulting .qch file. 
slouken@3331
   934
# The path specified is relative to the HTML output folder.
slouken@3331
   935
slouken@3331
   936
QCH_FILE               = 
slouken@3331
   937
slouken@3331
   938
# The QHP_NAMESPACE tag specifies the namespace to use when generating 
slouken@3331
   939
# Qt Help Project output. For more information please see 
slouken@3331
   940
# http://doc.trolltech.com/qthelpproject.html#namespace
slouken@3331
   941
slouken@3331
   942
QHP_NAMESPACE          = 
slouken@3331
   943
slouken@3331
   944
# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 
slouken@3331
   945
# Qt Help Project output. For more information please see 
slouken@3331
   946
# http://doc.trolltech.com/qthelpproject.html#virtual-folders
slouken@3331
   947
slouken@3331
   948
QHP_VIRTUAL_FOLDER     = doc
slouken@3331
   949
slouken@3331
   950
# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add. 
slouken@3331
   951
# For more information please see 
slouken@3331
   952
# http://doc.trolltech.com/qthelpproject.html#custom-filters
slouken@3331
   953
slouken@3331
   954
QHP_CUST_FILTER_NAME   = 
slouken@3331
   955
slouken@3331
   956
# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see 
slouken@3331
   957
# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.
slouken@3331
   958
slouken@3331
   959
QHP_CUST_FILTER_ATTRS  = 
slouken@3331
   960
slouken@3331
   961
# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's 
slouken@3331
   962
# filter section matches. 
slouken@3331
   963
# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.
slouken@3331
   964
slouken@3331
   965
QHP_SECT_FILTER_ATTRS  = 
slouken@3331
   966
slouken@3331
   967
# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 
slouken@3331
   968
# be used to specify the location of Qt's qhelpgenerator. 
slouken@3331
   969
# If non-empty doxygen will try to run qhelpgenerator on the generated 
slouken@3331
   970
# .qhp file.
slouken@3331
   971
slouken@3331
   972
QHG_LOCATION           = 
slouken@3331
   973
slouken@3331
   974
# The DISABLE_INDEX tag can be used to turn on/off the condensed index at 
slouken@3331
   975
# top of each HTML page. The value NO (the default) enables the index and 
slouken@3331
   976
# the value YES disables it.
slouken@3331
   977
slouken@3331
   978
DISABLE_INDEX          = NO
slouken@3331
   979
slouken@3331
   980
# This tag can be used to set the number of enum values (range [1..20]) 
slouken@3331
   981
# that doxygen will group on one line in the generated HTML documentation.
slouken@3331
   982
slouken@3331
   983
ENUM_VALUES_PER_LINE   = 4
slouken@3331
   984
slouken@3331
   985
# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 
slouken@3331
   986
# structure should be generated to display hierarchical information. 
slouken@3331
   987
# If the tag value is set to YES, a side panel will be generated 
slouken@3331
   988
# containing a tree-like index structure (just like the one that 
slouken@3331
   989
# is generated for HTML Help). For this to work a browser that supports 
slouken@3331
   990
# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). 
slouken@3331
   991
# Windows users are probably better off using the HTML help feature.
slouken@3331
   992
slouken@3331
   993
GENERATE_TREEVIEW      = NO
slouken@3331
   994
slouken@3331
   995
# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories, 
slouken@3331
   996
# and Class Hierarchy pages using a tree view instead of an ordered list.
slouken@3331
   997
slouken@3331
   998
USE_INLINE_TREES       = NO
slouken@3331
   999
slouken@3331
  1000
# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
slouken@3331
  1001
# used to set the initial width (in pixels) of the frame in which the tree 
slouken@3331
  1002
# is shown.
slouken@3331
  1003
slouken@3331
  1004
TREEVIEW_WIDTH         = 250
slouken@3331
  1005
slouken@3331
  1006
# Use this tag to change the font size of Latex formulas included 
slouken@3331
  1007
# as images in the HTML documentation. The default is 10. Note that 
slouken@3331
  1008
# when you change the font size after a successful doxygen run you need 
slouken@3331
  1009
# to manually remove any form_*.png images from the HTML output directory 
slouken@3331
  1010
# to force them to be regenerated.
slouken@3331
  1011
slouken@3331
  1012
FORMULA_FONTSIZE       = 10
slouken@3331
  1013
slouken@3331
  1014
# When the SEARCHENGINE tag is enable doxygen will generate a search box
slouken@3331
  1015
# for the HTML output. The underlying search engine uses javascript 
slouken@3331
  1016
# and DHTML and should work on any modern browser. Note that when using
slouken@3331
  1017
# HTML help (GENERATE_HTMLHELP) or Qt help (GENERATE_QHP) 
slouken@3331
  1018
# there is already a search function so this one should typically 
slouken@3331
  1019
# be disabled.
slouken@3331
  1020
slouken@3331
  1021
SEARCHENGINE           = NO
slouken@3331
  1022
slouken@3331
  1023
#---------------------------------------------------------------------------
slouken@3331
  1024
# configuration options related to the LaTeX output
slouken@3331
  1025
#---------------------------------------------------------------------------
slouken@3331
  1026
slouken@3331
  1027
# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
slouken@3331
  1028
# generate Latex output.
slouken@3331
  1029
slouken@3331
  1030
GENERATE_LATEX         = NO
slouken@3331
  1031
slouken@3331
  1032
# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
slouken@3331
  1033
# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
slouken@3331
  1034
# put in front of it. If left blank `latex' will be used as the default path.
slouken@3331
  1035
slouken@3331
  1036
LATEX_OUTPUT           = latex
slouken@3331
  1037
slouken@3331
  1038
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 
slouken@3331
  1039
# invoked. If left blank `latex' will be used as the default command name.
slouken@3331
  1040
slouken@3331
  1041
LATEX_CMD_NAME         = latex
slouken@3331
  1042
slouken@3331
  1043
# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
slouken@3331
  1044
# generate index for LaTeX. If left blank `makeindex' will be used as the 
slouken@3331
  1045
# default command name.
slouken@3331
  1046
slouken@3331
  1047
MAKEINDEX_CMD_NAME     = makeindex
slouken@3331
  1048
slouken@3331
  1049
# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
slouken@3331
  1050
# LaTeX documents. This may be useful for small projects and may help to 
slouken@3331
  1051
# save some trees in general.
slouken@3331
  1052
slouken@3331
  1053
COMPACT_LATEX          = NO
slouken@3331
  1054
slouken@3331
  1055
# The PAPER_TYPE tag can be used to set the paper type that is used 
slouken@3331
  1056
# by the printer. Possible values are: a4, a4wide, letter, legal and 
slouken@3331
  1057
# executive. If left blank a4wide will be used.
slouken@3331
  1058
slouken@3331
  1059
PAPER_TYPE             = a4wide
slouken@3331
  1060
slouken@3331
  1061
# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
slouken@3331
  1062
# packages that should be included in the LaTeX output.
slouken@3331
  1063
slouken@3331
  1064
EXTRA_PACKAGES         = 
slouken@3331
  1065
slouken@3331
  1066
# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
slouken@3331
  1067
# the generated latex document. The header should contain everything until 
slouken@3331
  1068
# the first chapter. If it is left blank doxygen will generate a 
slouken@3331
  1069
# standard header. Notice: only use this tag if you know what you are doing!
slouken@3331
  1070
slouken@3331
  1071
LATEX_HEADER           = 
slouken@3331
  1072
slouken@3331
  1073
# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
slouken@3331
  1074
# is prepared for conversion to pdf (using ps2pdf). The pdf file will 
slouken@3331
  1075
# contain links (just like the HTML output) instead of page references 
slouken@3331
  1076
# This makes the output suitable for online browsing using a pdf viewer.
slouken@3331
  1077
slouken@3331
  1078
PDF_HYPERLINKS         = YES
slouken@3331
  1079
slouken@3331
  1080
# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
slouken@3331
  1081
# plain latex in the generated Makefile. Set this option to YES to get a 
slouken@3331
  1082
# higher quality PDF documentation.
slouken@3331
  1083
slouken@3331
  1084
USE_PDFLATEX           = YES
slouken@3331
  1085
slouken@3331
  1086
# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
slouken@3331
  1087
# command to the generated LaTeX files. This will instruct LaTeX to keep 
slouken@3331
  1088
# running if errors occur, instead of asking the user for help. 
slouken@3331
  1089
# This option is also used when generating formulas in HTML.
slouken@3331
  1090
slouken@3331
  1091
LATEX_BATCHMODE        = NO
slouken@3331
  1092
slouken@3331
  1093
# If LATEX_HIDE_INDICES is set to YES then doxygen will not 
slouken@3331
  1094
# include the index chapters (such as File Index, Compound Index, etc.) 
slouken@3331
  1095
# in the output.
slouken@3331
  1096
slouken@3331
  1097
LATEX_HIDE_INDICES     = NO
slouken@3331
  1098
slouken@3331
  1099
# If LATEX_SOURCE_CODE is set to YES then doxygen will include
slouken@3331
  1100
# source code with syntax highlighting in the LaTeX output.
slouken@3331
  1101
# Note that which sources are shown also depends on other settings
slouken@3331
  1102
# such as SOURCE_BROWSER.
slouken@3331
  1103
slouken@3331
  1104
LATEX_SOURCE_CODE      = NO
slouken@3331
  1105
slouken@3331
  1106
#---------------------------------------------------------------------------
slouken@3331
  1107
# configuration options related to the RTF output
slouken@3331
  1108
#---------------------------------------------------------------------------
slouken@3331
  1109
slouken@3331
  1110
# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
slouken@3331
  1111
# The RTF output is optimized for Word 97 and may not look very pretty with 
slouken@3331
  1112
# other RTF readers or editors.
slouken@3331
  1113
slouken@3331
  1114
GENERATE_RTF           = NO
slouken@3331
  1115
slouken@3331
  1116
# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
slouken@3331
  1117
# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
slouken@3331
  1118
# put in front of it. If left blank `rtf' will be used as the default path.
slouken@3331
  1119
slouken@3331
  1120
RTF_OUTPUT             = rtf
slouken@3331
  1121
slouken@3331
  1122
# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
slouken@3331
  1123
# RTF documents. This may be useful for small projects and may help to 
slouken@3331
  1124
# save some trees in general.
slouken@3331
  1125
slouken@3331
  1126
COMPACT_RTF            = NO
slouken@3331
  1127
slouken@3331
  1128
# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
slouken@3331
  1129
# will contain hyperlink fields. The RTF file will 
slouken@3331
  1130
# contain links (just like the HTML output) instead of page references. 
slouken@3331
  1131
# This makes the output suitable for online browsing using WORD or other 
slouken@3331
  1132
# programs which support those fields. 
slouken@3331
  1133
# Note: wordpad (write) and others do not support links.
slouken@3331
  1134
slouken@3331
  1135
RTF_HYPERLINKS         = NO
slouken@3331
  1136
slouken@3331
  1137
# Load stylesheet definitions from file. Syntax is similar to doxygen's 
slouken@3331
  1138
# config file, i.e. a series of assignments. You only have to provide 
slouken@3331
  1139
# replacements, missing definitions are set to their default value.
slouken@3331
  1140
slouken@3331
  1141
RTF_STYLESHEET_FILE    = 
slouken@3331
  1142
slouken@3331
  1143
# Set optional variables used in the generation of an rtf document. 
slouken@3331
  1144
# Syntax is similar to doxygen's config file.
slouken@3331
  1145
slouken@3331
  1146
RTF_EXTENSIONS_FILE    = 
slouken@3331
  1147
slouken@3331
  1148
#---------------------------------------------------------------------------
slouken@3331
  1149
# configuration options related to the man page output
slouken@3331
  1150
#---------------------------------------------------------------------------
slouken@3331
  1151
slouken@3331
  1152
# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
slouken@3331
  1153
# generate man pages
slouken@3331
  1154
slouken@3331
  1155
GENERATE_MAN           = NO
slouken@3331
  1156
slouken@3331
  1157
# The MAN_OUTPUT tag is used to specify where the man pages will be put. 
slouken@3331
  1158
# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
slouken@3331
  1159
# put in front of it. If left blank `man' will be used as the default path.
slouken@3331
  1160
slouken@3331
  1161
MAN_OUTPUT             = man
slouken@3331
  1162
slouken@3331
  1163
# The MAN_EXTENSION tag determines the extension that is added to 
slouken@3331
  1164
# the generated man pages (default is the subroutine's section .3)
slouken@3331
  1165
slouken@3331
  1166
MAN_EXTENSION          = .3
slouken@3331
  1167
slouken@3331
  1168
# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
slouken@3331
  1169
# then it will generate one additional man file for each entity 
slouken@3331
  1170
# documented in the real man page(s). These additional files 
slouken@3331
  1171
# only source the real man page, but without them the man command 
slouken@3331
  1172
# would be unable to find the correct page. The default is NO.
slouken@3331
  1173
slouken@3331
  1174
MAN_LINKS              = NO
slouken@3331
  1175
slouken@3331
  1176
#---------------------------------------------------------------------------
slouken@3331
  1177
# configuration options related to the XML output
slouken@3331
  1178
#---------------------------------------------------------------------------
slouken@3331
  1179
slouken@3331
  1180
# If the GENERATE_XML tag is set to YES Doxygen will 
slouken@3331
  1181
# generate an XML file that captures the structure of 
slouken@3331
  1182
# the code including all documentation.
slouken@3331
  1183
slouken@3331
  1184
GENERATE_XML           = NO
slouken@3331
  1185
slouken@3331
  1186
# The XML_OUTPUT tag is used to specify where the XML pages will be put. 
slouken@3331
  1187
# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
slouken@3331
  1188
# put in front of it. If left blank `xml' will be used as the default path.
slouken@3331
  1189
slouken@3331
  1190
XML_OUTPUT             = xml
slouken@3331
  1191
slouken@3331
  1192
# The XML_SCHEMA tag can be used to specify an XML schema, 
slouken@3331
  1193
# which can be used by a validating XML parser to check the 
slouken@3331
  1194
# syntax of the XML files.
slouken@3331
  1195
slouken@3331
  1196
XML_SCHEMA             = 
slouken@3331
  1197
slouken@3331
  1198
# The XML_DTD tag can be used to specify an XML DTD, 
slouken@3331
  1199
# which can be used by a validating XML parser to check the 
slouken@3331
  1200
# syntax of the XML files.
slouken@3331
  1201
slouken@3331
  1202
XML_DTD                = 
slouken@3331
  1203
slouken@3331
  1204
# If the XML_PROGRAMLISTING tag is set to YES Doxygen will 
slouken@3331
  1205
# dump the program listings (including syntax highlighting 
slouken@3331
  1206
# and cross-referencing information) to the XML output. Note that 
slouken@3331
  1207
# enabling this will significantly increase the size of the XML output.
slouken@3331
  1208
slouken@3331
  1209
XML_PROGRAMLISTING     = YES
slouken@3331
  1210
slouken@3331
  1211
#---------------------------------------------------------------------------
slouken@3331
  1212
# configuration options for the AutoGen Definitions output
slouken@3331
  1213
#---------------------------------------------------------------------------
slouken@3331
  1214
slouken@3331
  1215
# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
slouken@3331
  1216
# generate an AutoGen Definitions (see autogen.sf.net) file 
slouken@3331
  1217
# that captures the structure of the code including all 
slouken@3331
  1218
# documentation. Note that this feature is still experimental 
slouken@3331
  1219
# and incomplete at the moment.
slouken@3331
  1220
slouken@3331
  1221
GENERATE_AUTOGEN_DEF   = NO
slouken@3331
  1222
slouken@3331
  1223
#---------------------------------------------------------------------------
slouken@3331
  1224
# configuration options related to the Perl module output
slouken@3331
  1225
#---------------------------------------------------------------------------
slouken@3331
  1226
slouken@3331
  1227
# If the GENERATE_PERLMOD tag is set to YES Doxygen will 
slouken@3331
  1228
# generate a Perl module file that captures the structure of 
slouken@3331
  1229
# the code including all documentation. Note that this 
slouken@3331
  1230
# feature is still experimental and incomplete at the 
slouken@3331
  1231
# moment.
slouken@3331
  1232
slouken@3331
  1233
GENERATE_PERLMOD       = NO
slouken@3331
  1234
slouken@3331
  1235
# If the PERLMOD_LATEX tag is set to YES Doxygen will generate 
slouken@3331
  1236
# the necessary Makefile rules, Perl scripts and LaTeX code to be able 
slouken@3331
  1237
# to generate PDF and DVI output from the Perl module output.
slouken@3331
  1238
slouken@3331
  1239
PERLMOD_LATEX          = NO
slouken@3331
  1240
slouken@3331
  1241
# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 
slouken@3331
  1242
# nicely formatted so it can be parsed by a human reader.  This is useful 
slouken@3331
  1243
# if you want to understand what is going on.  On the other hand, if this 
slouken@3331
  1244
# tag is set to NO the size of the Perl module output will be much smaller 
slouken@3331
  1245
# and Perl will parse it just the same.
slouken@3331
  1246
slouken@3331
  1247
PERLMOD_PRETTY         = YES
slouken@3331
  1248
slouken@3331
  1249
# The names of the make variables in the generated doxyrules.make file 
slouken@3331
  1250
# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 
slouken@3331
  1251
# This is useful so different doxyrules.make files included by the same 
slouken@3331
  1252
# Makefile don't overwrite each other's variables.
slouken@3331
  1253
slouken@3331
  1254
PERLMOD_MAKEVAR_PREFIX = 
slouken@3331
  1255
slouken@3331
  1256
#---------------------------------------------------------------------------
slouken@3331
  1257
# Configuration options related to the preprocessor
slouken@3331
  1258
#---------------------------------------------------------------------------
slouken@3331
  1259
slouken@3331
  1260
# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
slouken@3331
  1261
# evaluate all C-preprocessor directives found in the sources and include 
slouken@3331
  1262
# files.
slouken@3331
  1263
slouken@3331
  1264
ENABLE_PREPROCESSING   = YES
slouken@3331
  1265
slouken@3331
  1266
# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
slouken@3331
  1267
# names in the source code. If set to NO (the default) only conditional 
slouken@3331
  1268
# compilation will be performed. Macro expansion can be done in a controlled 
slouken@3331
  1269
# way by setting EXPAND_ONLY_PREDEF to YES.
slouken@3331
  1270
slouken@3331
  1271
MACRO_EXPANSION        = YES
slouken@3331
  1272
slouken@3331
  1273
# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 
slouken@3331
  1274
# then the macro expansion is limited to the macros specified with the 
slouken@3331
  1275
# PREDEFINED and EXPAND_AS_DEFINED tags.
slouken@3331
  1276
slouken@3331
  1277
EXPAND_ONLY_PREDEF     = YES
slouken@3331
  1278
slouken@3331
  1279
# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 
slouken@3331
  1280
# in the INCLUDE_PATH (see below) will be search if a #include is found.
slouken@3331
  1281
slouken@3331
  1282
SEARCH_INCLUDES        = NO
slouken@3331
  1283
slouken@3331
  1284
# The INCLUDE_PATH tag can be used to specify one or more directories that 
slouken@3331
  1285
# contain include files that are not input files but should be processed by 
slouken@3331
  1286
# the preprocessor.
slouken@3331
  1287
slouken@3331
  1288
INCLUDE_PATH           = 
slouken@3331
  1289
slouken@3331
  1290
# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 
slouken@3331
  1291
# patterns (like *.h and *.hpp) to filter out the header-files in the 
slouken@3331
  1292
# directories. If left blank, the patterns specified with FILE_PATTERNS will 
slouken@3331
  1293
# be used.
slouken@3331
  1294
slouken@3331
  1295
INCLUDE_FILE_PATTERNS  = 
slouken@3331
  1296
slouken@3331
  1297
# The PREDEFINED tag can be used to specify one or more macro names that 
slouken@3331
  1298
# are defined before the preprocessor is started (similar to the -D option of 
slouken@3331
  1299
# gcc). The argument of the tag is a list of macros of the form: name 
slouken@3331
  1300
# or name=definition (no spaces). If the definition and the = are 
slouken@3331
  1301
# omitted =1 is assumed. To prevent a macro definition from being 
slouken@3331
  1302
# undefined via #undef or recursively expanded use the := operator 
slouken@3331
  1303
# instead of the = operator.
slouken@3331
  1304
slouken@3331
  1305
PREDEFINED             = 
slouken@3331
  1306
slouken@3331
  1307
# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 
slouken@3331
  1308
# this tag can be used to specify a list of macro names that should be expanded. 
slouken@3331
  1309
# The macro definition that is found in the sources will be used. 
slouken@3331
  1310
# Use the PREDEFINED tag if you want to use a different macro definition.
slouken@3331
  1311
slouken@3331
  1312
EXPAND_AS_DEFINED      = DECLSPEC \
slouken@3331
  1313
                         SDLCALL
slouken@3331
  1314
slouken@3331
  1315
# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
slouken@3331
  1316
# doxygen's preprocessor will remove all function-like macros that are alone 
slouken@3331
  1317
# on a line, have an all uppercase name, and do not end with a semicolon. Such 
slouken@3331
  1318
# function macros are typically used for boiler-plate code, and will confuse 
slouken@3331
  1319
# the parser if not removed.
slouken@3331
  1320
slouken@3331
  1321
SKIP_FUNCTION_MACROS   = YES
slouken@3331
  1322
slouken@3331
  1323
#---------------------------------------------------------------------------
slouken@3331
  1324
# Configuration::additions related to external references
slouken@3331
  1325
#---------------------------------------------------------------------------
slouken@3331
  1326
slouken@3331
  1327
# The TAGFILES option can be used to specify one or more tagfiles. 
slouken@3331
  1328
# Optionally an initial location of the external documentation 
slouken@3331
  1329
# can be added for each tagfile. The format of a tag file without 
slouken@3331
  1330
# this location is as follows: 
slouken@3331
  1331
#   TAGFILES = file1 file2 ... 
slouken@3331
  1332
# Adding location for the tag files is done as follows: 
slouken@3331
  1333
#   TAGFILES = file1=loc1 "file2 = loc2" ... 
slouken@3331
  1334
# where "loc1" and "loc2" can be relative or absolute paths or 
slouken@3331
  1335
# URLs. If a location is present for each tag, the installdox tool 
slouken@3331
  1336
# does not have to be run to correct the links. 
slouken@3331
  1337
# Note that each tag file must have a unique name 
slouken@3331
  1338
# (where the name does NOT include the path) 
slouken@3331
  1339
# If a tag file is not located in the directory in which doxygen 
slouken@3331
  1340
# is run, you must also specify the path to the tagfile here.
slouken@3331
  1341
slouken@3331
  1342
TAGFILES               = 
slouken@3331
  1343
slouken@3331
  1344
# When a file name is specified after GENERATE_TAGFILE, doxygen will create 
slouken@3331
  1345
# a tag file that is based on the input files it reads.
slouken@3331
  1346
slouken@3331
  1347
GENERATE_TAGFILE       = 
slouken@3331
  1348
slouken@3331
  1349
# If the ALLEXTERNALS tag is set to YES all external classes will be listed 
slouken@3331
  1350
# in the class index. If set to NO only the inherited external classes 
slouken@3331
  1351
# will be listed.
slouken@3331
  1352
slouken@3331
  1353
ALLEXTERNALS           = NO
slouken@3331
  1354
slouken@3331
  1355
# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 
slouken@3331
  1356
# in the modules index. If set to NO, only the current project's groups will 
slouken@3331
  1357
# be listed.
slouken@3331
  1358
slouken@3331
  1359
EXTERNAL_GROUPS        = YES
slouken@3331
  1360
slouken@3331
  1361
# The PERL_PATH should be the absolute path and name of the perl script 
slouken@3331
  1362
# interpreter (i.e. the result of `which perl').
slouken@3331
  1363
slouken@3331
  1364
PERL_PATH              = /usr/bin/perl
slouken@3331
  1365
slouken@3331
  1366
#---------------------------------------------------------------------------
slouken@3331
  1367
# Configuration options related to the dot tool
slouken@3331
  1368
#---------------------------------------------------------------------------
slouken@3331
  1369
slouken@3331
  1370
# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
slouken@3331
  1371
# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 
slouken@3331
  1372
# or super classes. Setting the tag to NO turns the diagrams off. Note that 
slouken@3331
  1373
# this option is superseded by the HAVE_DOT option below. This is only a 
slouken@3331
  1374
# fallback. It is recommended to install and use dot, since it yields more 
slouken@3331
  1375
# powerful graphs.
slouken@3331
  1376
slouken@3331
  1377
CLASS_DIAGRAMS         = NO
slouken@3331
  1378
slouken@3331
  1379
# You can define message sequence charts within doxygen comments using the \msc 
slouken@3331
  1380
# command. Doxygen will then run the mscgen tool (see 
slouken@3331
  1381
# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the 
slouken@3331
  1382
# documentation. The MSCGEN_PATH tag allows you to specify the directory where 
slouken@3331
  1383
# the mscgen tool resides. If left empty the tool is assumed to be found in the 
slouken@3331
  1384
# default search path.
slouken@3331
  1385
slouken@3331
  1386
MSCGEN_PATH            = 
slouken@3331
  1387
slouken@3331
  1388
# If set to YES, the inheritance and collaboration graphs will hide 
slouken@3331
  1389
# inheritance and usage relations if the target is undocumented 
slouken@3331
  1390
# or is not a class.
slouken@3331
  1391
slouken@3331
  1392
HIDE_UNDOC_RELATIONS   = YES
slouken@3331
  1393
slouken@3331
  1394
# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 
slouken@3331
  1395
# available from the path. This tool is part of Graphviz, a graph visualization 
slouken@3331
  1396
# toolkit from AT&T and Lucent Bell Labs. The other options in this section 
slouken@3331
  1397
# have no effect if this option is set to NO (the default)
slouken@3331
  1398
slouken@3331
  1399
HAVE_DOT               = NO
slouken@3331
  1400
slouken@3331
  1401
# By default doxygen will write a font called FreeSans.ttf to the output 
slouken@3331
  1402
# directory and reference it in all dot files that doxygen generates. This 
slouken@3331
  1403
# font does not include all possible unicode characters however, so when you need 
slouken@3331
  1404
# these (or just want a differently looking font) you can specify the font name 
slouken@3331
  1405
# using DOT_FONTNAME. You need need to make sure dot is able to find the font, 
slouken@3331
  1406
# which can be done by putting it in a standard location or by setting the 
slouken@3331
  1407
# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory 
slouken@3331
  1408
# containing the font.
slouken@3331
  1409
slouken@3331
  1410
DOT_FONTNAME           = FreeSans
slouken@3331
  1411
slouken@3331
  1412
# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. 
slouken@3331
  1413
# The default size is 10pt.
slouken@3331
  1414
slouken@3331
  1415
DOT_FONTSIZE           = 10
slouken@3331
  1416
slouken@3331
  1417
# By default doxygen will tell dot to use the output directory to look for the 
slouken@3331
  1418
# FreeSans.ttf font (which doxygen will put there itself). If you specify a 
slouken@3331
  1419
# different font using DOT_FONTNAME you can set the path where dot 
slouken@3331
  1420
# can find it using this tag.
slouken@3331
  1421
slouken@3331
  1422
DOT_FONTPATH           = 
slouken@3331
  1423
slouken@3331
  1424
# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 
slouken@3331
  1425
# will generate a graph for each documented class showing the direct and 
slouken@3331
  1426
# indirect inheritance relations. Setting this tag to YES will force the 
slouken@3331
  1427
# the CLASS_DIAGRAMS tag to NO.
slouken@3331
  1428
slouken@3331
  1429
CLASS_GRAPH            = YES
slouken@3331
  1430
slouken@3331
  1431
# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 
slouken@3331
  1432
# will generate a graph for each documented class showing the direct and 
slouken@3331
  1433
# indirect implementation dependencies (inheritance, containment, and 
slouken@3331
  1434
# class references variables) of the class with other documented classes.
slouken@3331
  1435
slouken@3331
  1436
COLLABORATION_GRAPH    = YES
slouken@3331
  1437
slouken@3331
  1438
# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 
slouken@3331
  1439
# will generate a graph for groups, showing the direct groups dependencies
slouken@3331
  1440
slouken@3331
  1441
GROUP_GRAPHS           = YES
slouken@3331
  1442
slouken@3331
  1443
# If the UML_LOOK tag is set to YES doxygen will generate inheritance and 
slouken@3331
  1444
# collaboration diagrams in a style similar to the OMG's Unified Modeling 
slouken@3331
  1445
# Language.
slouken@3331
  1446
slouken@3331
  1447
UML_LOOK               = NO
slouken@3331
  1448
slouken@3331
  1449
# If set to YES, the inheritance and collaboration graphs will show the 
slouken@3331
  1450
# relations between templates and their instances.
slouken@3331
  1451
slouken@3331
  1452
TEMPLATE_RELATIONS     = NO
slouken@3331
  1453
slouken@3331
  1454
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 
slouken@3331
  1455
# tags are set to YES then doxygen will generate a graph for each documented 
slouken@3331
  1456
# file showing the direct and indirect include dependencies of the file with 
slouken@3331
  1457
# other documented files.
slouken@3331
  1458
slouken@3331
  1459
INCLUDE_GRAPH          = YES
slouken@3331
  1460
slouken@3331
  1461
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 
slouken@3331
  1462
# HAVE_DOT tags are set to YES then doxygen will generate a graph for each 
slouken@3331
  1463
# documented header file showing the documented files that directly or 
slouken@3331
  1464
# indirectly include this file.
slouken@3331
  1465
slouken@3331
  1466
INCLUDED_BY_GRAPH      = YES
slouken@3331
  1467
slouken@3331
  1468
# If the CALL_GRAPH and HAVE_DOT options are set to YES then 
slouken@3331
  1469
# doxygen will generate a call dependency graph for every global function 
slouken@3331
  1470
# or class method. Note that enabling this option will significantly increase 
slouken@3331
  1471
# the time of a run. So in most cases it will be better to enable call graphs 
slouken@3331
  1472
# for selected functions only using the \callgraph command.
slouken@3331
  1473
slouken@3331
  1474
CALL_GRAPH             = NO
slouken@3331
  1475
slouken@3331
  1476
# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then 
slouken@3331
  1477
# doxygen will generate a caller dependency graph for every global function 
slouken@3331
  1478
# or class method. Note that enabling this option will significantly increase 
slouken@3331
  1479
# the time of a run. So in most cases it will be better to enable caller 
slouken@3331
  1480
# graphs for selected functions only using the \callergraph command.
slouken@3331
  1481
slouken@3331
  1482
CALLER_GRAPH           = NO
slouken@3331
  1483
slouken@3331
  1484
# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
slouken@3331
  1485
# will graphical hierarchy of all classes instead of a textual one.
slouken@3331
  1486
slouken@3331
  1487
GRAPHICAL_HIERARCHY    = YES
slouken@3331
  1488
slouken@3331
  1489
# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES 
slouken@3331
  1490
# then doxygen will show the dependencies a directory has on other directories 
slouken@3331
  1491
# in a graphical way. The dependency relations are determined by the #include 
slouken@3331
  1492
# relations between the files in the directories.
slouken@3331
  1493
slouken@3331
  1494
DIRECTORY_GRAPH        = YES
slouken@3331
  1495
slouken@3331
  1496
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
slouken@3331
  1497
# generated by dot. Possible values are png, jpg, or gif 
slouken@3331
  1498
# If left blank png will be used.
slouken@3331
  1499
slouken@3331
  1500
DOT_IMAGE_FORMAT       = png
slouken@3331
  1501
slouken@3331
  1502
# The tag DOT_PATH can be used to specify the path where the dot tool can be 
slouken@3331
  1503
# found. If left blank, it is assumed the dot tool can be found in the path.
slouken@3331
  1504
slouken@3331
  1505
DOT_PATH               = /Applications/Graphviz.app/Contents/MacOS
slouken@3331
  1506
slouken@3331
  1507
# The DOTFILE_DIRS tag can be used to specify one or more directories that 
slouken@3331
  1508
# contain dot files that are included in the documentation (see the 
slouken@3331
  1509
# \dotfile command).
slouken@3331
  1510
slouken@3331
  1511
DOTFILE_DIRS           = 
slouken@3331
  1512
slouken@3331
  1513
# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 
slouken@3331
  1514
# nodes that will be shown in the graph. If the number of nodes in a graph 
slouken@3331
  1515
# becomes larger than this value, doxygen will truncate the graph, which is 
slouken@3331
  1516
# visualized by representing a node as a red box. Note that doxygen if the 
slouken@3331
  1517
# number of direct children of the root node in a graph is already larger than 
slouken@3331
  1518
# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note 
slouken@3331
  1519
# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
slouken@3331
  1520
slouken@3331
  1521
DOT_GRAPH_MAX_NODES    = 67
slouken@3331
  1522
slouken@3331
  1523
# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 
slouken@3331
  1524
# graphs generated by dot. A depth value of 3 means that only nodes reachable 
slouken@3331
  1525
# from the root by following a path via at most 3 edges will be shown. Nodes 
slouken@3331
  1526
# that lay further from the root node will be omitted. Note that setting this 
slouken@3331
  1527
# option to 1 or 2 may greatly reduce the computation time needed for large 
slouken@3331
  1528
# code bases. Also note that the size of a graph can be further restricted by 
slouken@3331
  1529
# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
slouken@3331
  1530
slouken@3331
  1531
MAX_DOT_GRAPH_DEPTH    = 2
slouken@3331
  1532
slouken@3331
  1533
# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 
slouken@3331
  1534
# background. This is disabled by default, because dot on Windows does not 
slouken@3331
  1535
# seem to support this out of the box. Warning: Depending on the platform used, 
slouken@3331
  1536
# enabling this option may lead to badly anti-aliased labels on the edges of 
slouken@3331
  1537
# a graph (i.e. they become hard to read).
slouken@3331
  1538
slouken@3331
  1539
DOT_TRANSPARENT        = NO
slouken@3331
  1540
slouken@3331
  1541
# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 
slouken@3331
  1542
# files in one run (i.e. multiple -o and -T options on the command line). This 
slouken@3331
  1543
# makes dot run faster, but since only newer versions of dot (>1.8.10) 
slouken@3331
  1544
# support this, this feature is disabled by default.
slouken@3331
  1545
slouken@3331
  1546
DOT_MULTI_TARGETS      = NO
slouken@3331
  1547
slouken@3331
  1548
# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
slouken@3331
  1549
# generate a legend page explaining the meaning of the various boxes and 
slouken@3331
  1550
# arrows in the dot generated graphs.
slouken@3331
  1551
slouken@3331
  1552
GENERATE_LEGEND        = YES
slouken@3331
  1553
slouken@3331
  1554
# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 
slouken@3331
  1555
# remove the intermediate dot files that are used to generate 
slouken@3331
  1556
# the various graphs.
slouken@3331
  1557
slouken@3331
  1558
DOT_CLEANUP            = YES