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