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