docs/doxyfile
author Sam Lantinga <slouken@libsdl.org>
Tue, 25 Sep 2018 20:08:51 -0700
changeset 12224 0582b4e1fa9f
parent 9746 b39bdcf9cdc0
permissions -rw-r--r--
Fixed bug 4268 - Android_JNI_OpenAudioDevice function has error

alittle

where iscapture == 1

1.param set error

(*env)->CallStaticIntMethod(env, mAudioManagerClass, midCaptureOpen, sampleRate, audioBuffer16Bit, audioBufferStereo, desiredBufferFrames)

param:audioBuffer16Bit need change to captureBuffer16Bit

2.logic error

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