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