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