3 # This file describes the settings to be used by the documentation system
4 # doxygen (www.doxygen.org) for a project.
6 # All text after a double hash (##) is considered a comment and is placed in
7 # front of the TAG it is preceding.
9 # All text after a single hash (#) is considered a comment and will be ignored.
11 # TAG = value [value, ...]
12 # For lists, items can also be appended using:
13 # TAG += value [value, ...]
14 # Values that contain spaces should be placed between quotes (\" \").
16 #---------------------------------------------------------------------------
17 # Project related configuration options
18 #---------------------------------------------------------------------------
20 # This tag specifies the encoding used for all characters in the configuration
21 # file that follow. The default is UTF-8 which is also the encoding used for all
22 # text before the first occurrence of this tag. Doxygen uses libiconv (or the
23 # iconv built into libc) for the transcoding. See
24 # https://www.gnu.org/software/libiconv/ for the list of possible encodings.
25 # The default value is: UTF-8.
27 DOXYFILE_ENCODING = UTF-8
29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
30 # double-quotes, unless you are using Doxywizard) that should identify the
31 # project for which the documentation is generated. This name is used in the
32 # title of most generated pages and in a few other places.
33 # The default value is: My Project.
35 PROJECT_NAME = fetchmail
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
38 # could be handy for archiving the generated documentation or if some version
39 # control system is used.
41 PROJECT_NUMBER = legacy_63
43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
44 # for a project that appears at the top of each page and should give viewer a
45 # quick idea about the purpose of the project. Keep the description short.
49 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
50 # in the documentation. The maximum height of the logo should not exceed 55
51 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
52 # the logo to the output directory.
56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
57 # into which the generated documentation will be written. If a relative path is
58 # entered, it will be relative to the location where doxygen was started. If
59 # left blank the current directory will be used.
61 OUTPUT_DIRECTORY = dox
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
64 # directories (in 2 levels) under the output directory of each output format and
65 # will distribute the generated files over these directories. Enabling this
66 # option can be useful when feeding doxygen a huge amount of source files, where
67 # putting all generated files in the same directory would otherwise causes
68 # performance problems for the file system.
69 # The default value is: NO.
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
75 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
77 # The default value is: NO.
79 ALLOW_UNICODE_NAMES = NO
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
82 # documentation generated by doxygen is written. Doxygen will use this
83 # information to generate all constant output in the proper language.
84 # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
85 # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
86 # Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,
87 # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
88 # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
89 # Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,
90 # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
91 # Ukrainian and Vietnamese.
92 # The default value is: English.
94 OUTPUT_LANGUAGE = English
96 # The OUTPUT_TEXT_DIRECTION tag is used to specify the direction in which all
97 # documentation generated by doxygen is written. Doxygen will use this
98 # information to generate all generated output in the proper direction.
99 # Possible values are: None, LTR, RTL and Context.
100 # The default value is: None.
102 OUTPUT_TEXT_DIRECTION = None
104 # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
105 # descriptions after the members that are listed in the file and class
106 # documentation (similar to Javadoc). Set to NO to disable this.
107 # The default value is: YES.
109 BRIEF_MEMBER_DESC = YES
111 # If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief
112 # description of a member or function before the detailed description
114 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
115 # brief descriptions will be completely suppressed.
116 # The default value is: YES.
120 # This tag implements a quasi-intelligent brief description abbreviator that is
121 # used to form the text in various listings. Each string in this list, if found
122 # as the leading text of the brief description, will be stripped from the text
123 # and the result, after processing the whole list, is used as the annotated
124 # text. Otherwise, the brief description is used as-is. If left blank, the
125 # following values are used ($name is automatically replaced with the name of
126 # the entity):The $name class, The $name widget, The $name file, is, provides,
127 # specifies, contains, represents, a, an and the.
131 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
132 # doxygen will generate a detailed section even if there is only a brief
134 # The default value is: NO.
136 ALWAYS_DETAILED_SEC = NO
138 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
139 # inherited members of a class in the documentation of that class as if those
140 # members were ordinary class members. Constructors, destructors and assignment
141 # operators of the base classes will not be shown.
142 # The default value is: NO.
144 INLINE_INHERITED_MEMB = NO
146 # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path
147 # before files name in the file list and in the header files. If set to NO the
148 # shortest path that makes the file name unique will be used
149 # The default value is: YES.
151 FULL_PATH_NAMES = YES
153 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
154 # Stripping is only done if one of the specified strings matches the left-hand
155 # part of the path. The tag can be used to show relative paths in the file list.
156 # If left blank the directory from which doxygen is run is used as the path to
159 # Note that you can specify absolute paths here, but also relative paths, which
160 # will be relative from the directory where doxygen is started.
161 # This tag requires that the tag FULL_PATH_NAMES is set to YES.
165 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
166 # path mentioned in the documentation of a class, which tells the reader which
167 # header file to include in order to use a class. If left blank only the name of
168 # the header file containing the class definition is used. Otherwise one should
169 # specify the list of include paths that are normally passed to the compiler
172 STRIP_FROM_INC_PATH =
174 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
175 # less readable) file names. This can be useful is your file systems doesn't
176 # support long names like on DOS, Mac, or CD-ROM.
177 # The default value is: NO.
181 # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
182 # first line (until the first dot) of a Javadoc-style comment as the brief
183 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
184 # style comments (thus requiring an explicit @brief command for a brief
186 # The default value is: NO.
188 JAVADOC_AUTOBRIEF = NO
190 # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
191 # line (until the first dot) of a Qt-style comment as the brief description. If
192 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
193 # requiring an explicit \brief command for a brief description.)
194 # The default value is: NO.
198 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
199 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
200 # a brief description. This used to be the default behavior. The new default is
201 # to treat a multi-line C++ comment block as a detailed description. Set this
202 # tag to YES if you prefer the old behavior instead.
204 # Note that setting this tag to YES also means that rational rose comments are
205 # not recognized any more.
206 # The default value is: NO.
208 MULTILINE_CPP_IS_BRIEF = NO
210 # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
211 # documentation from any documented member that it re-implements.
212 # The default value is: YES.
216 # If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
217 # page for each member. If set to NO, the documentation of a member will be part
218 # of the file/class/namespace that contains it.
219 # The default value is: NO.
221 SEPARATE_MEMBER_PAGES = NO
223 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
224 # uses this value to replace tabs by spaces in code fragments.
225 # Minimum value: 1, maximum value: 16, default value: 4.
229 # This tag can be used to specify a number of aliases that act as commands in
230 # the documentation. An alias has the form:
233 # "sideeffect=@par Side Effects:\n"
234 # will allow you to put the command \sideeffect (or @sideeffect) in the
235 # documentation, which will result in a user-defined paragraph with heading
236 # "Side Effects:". You can put \n's in the value part of an alias to insert
237 # newlines (in the resulting output). You can put ^^ in the value part of an
238 # alias to insert a newline as if a physical newline was in the original file.
239 # When you need a literal { or } or , in the value part of an alias you have to
240 # escape them by means of a backslash (\), this can lead to conflicts with the
241 # commands \{ and \} for these it is advised to use the version @{ and @} or use
242 # a double escape (\\{ and \\})
246 # This tag can be used to specify a number of word-keyword mappings (TCL only).
247 # A mapping has the form "name=value". For example adding "class=itcl::class"
248 # will allow you to use the command class in the itcl::class meaning.
252 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
253 # only. Doxygen will then generate output that is more tailored for C. For
254 # instance, some of the names that are used will be different. The list of all
255 # members will be omitted, etc.
256 # The default value is: NO.
258 OPTIMIZE_OUTPUT_FOR_C = YES
260 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
261 # Python sources only. Doxygen will then generate output that is more tailored
262 # for that language. For instance, namespaces will be presented as packages,
263 # qualified scopes will look different, etc.
264 # The default value is: NO.
266 OPTIMIZE_OUTPUT_JAVA = NO
268 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
269 # sources. Doxygen will then generate output that is tailored for Fortran.
270 # The default value is: NO.
272 OPTIMIZE_FOR_FORTRAN = NO
274 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
275 # sources. Doxygen will then generate output that is tailored for VHDL.
276 # The default value is: NO.
278 OPTIMIZE_OUTPUT_VHDL = NO
280 # Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice
281 # sources only. Doxygen will then generate output that is more tailored for that
282 # language. For instance, namespaces will be presented as modules, types will be
283 # separated into more groups, etc.
284 # The default value is: NO.
286 OPTIMIZE_OUTPUT_SLICE = NO
288 # Doxygen selects the parser to use depending on the extension of the files it
289 # parses. With this tag you can assign which parser to use for a given
290 # extension. Doxygen has a built-in mapping, but you can override or extend it
291 # using this tag. The format is ext=language, where ext is a file extension, and
292 # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
293 # Csharp (C#), C, C++, D, PHP, md (Markdown), Objective-C, Python, Slice,
294 # Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:
295 # FortranFree, unknown formatted Fortran: Fortran. In the later case the parser
296 # tries to guess whether the code is fixed or free formatted code, this is the
297 # default for Fortran type files), VHDL, tcl. For instance to make doxygen treat
298 # .inc files as Fortran files (default is PHP), and .f files as C (default is
299 # Fortran), use: inc=Fortran f=C.
301 # Note: For files without extension you can use no_extension as a placeholder.
303 # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
304 # the files are not read by doxygen.
308 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
309 # according to the Markdown format, which allows for more readable
310 # documentation. See https://daringfireball.net/projects/markdown/ for details.
311 # The output of markdown processing is further processed by doxygen, so you can
312 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
313 # case of backward compatibilities issues.
314 # The default value is: YES.
316 MARKDOWN_SUPPORT = YES
318 # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
319 # to that level are automatically included in the table of contents, even if
320 # they do not have an id attribute.
321 # Note: This feature currently applies only to Markdown headings.
322 # Minimum value: 0, maximum value: 99, default value: 0.
323 # This tag requires that the tag MARKDOWN_SUPPORT is set to YES.
325 TOC_INCLUDE_HEADINGS = 0
327 # When enabled doxygen tries to link words that correspond to documented
328 # classes, or namespaces to their corresponding documentation. Such a link can
329 # be prevented in individual cases by putting a % sign in front of the word or
330 # globally by setting AUTOLINK_SUPPORT to NO.
331 # The default value is: YES.
333 AUTOLINK_SUPPORT = YES
335 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
336 # to include (a tag file for) the STL sources as input, then you should set this
337 # tag to YES in order to let doxygen match functions declarations and
338 # definitions whose arguments contain STL classes (e.g. func(std::string);
339 # versus func(std::string) {}). This also make the inheritance and collaboration
340 # diagrams that involve STL classes more complete and accurate.
341 # The default value is: NO.
343 BUILTIN_STL_SUPPORT = NO
345 # If you use Microsoft's C++/CLI language, you should set this option to YES to
346 # enable parsing support.
347 # The default value is: NO.
351 # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
352 # https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen
353 # will parse them like normal C++ but will assume all classes use public instead
354 # of private inheritance when no explicit protection keyword is present.
355 # The default value is: NO.
359 # For Microsoft's IDL there are propget and propput attributes to indicate
360 # getter and setter methods for a property. Setting this option to YES will make
361 # doxygen to replace the get and set methods by a property in the documentation.
362 # This will only work if the methods are indeed getting or setting a simple
363 # type. If this is not the case, or you want to show the methods anyway, you
364 # should set this option to NO.
365 # The default value is: YES.
367 IDL_PROPERTY_SUPPORT = YES
369 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
370 # tag is set to YES then doxygen will reuse the documentation of the first
371 # member in the group (if any) for the other members of the group. By default
372 # all members of a group must be documented explicitly.
373 # The default value is: NO.
375 DISTRIBUTE_GROUP_DOC = NO
377 # If one adds a struct or class to a group and this option is enabled, then also
378 # any nested class or struct is added to the same group. By default this option
379 # is disabled and one has to add nested compounds explicitly via \ingroup.
380 # The default value is: NO.
382 GROUP_NESTED_COMPOUNDS = NO
384 # Set the SUBGROUPING tag to YES to allow class member groups of the same type
385 # (for instance a group of public functions) to be put as a subgroup of that
386 # type (e.g. under the Public Functions section). Set it to NO to prevent
387 # subgrouping. Alternatively, this can be done per class using the
388 # \nosubgrouping command.
389 # The default value is: YES.
393 # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
394 # are shown inside the group in which they are included (e.g. using \ingroup)
395 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
398 # Note that this feature does not work in combination with
399 # SEPARATE_MEMBER_PAGES.
400 # The default value is: NO.
402 INLINE_GROUPED_CLASSES = NO
404 # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
405 # with only public data fields or simple typedef fields will be shown inline in
406 # the documentation of the scope in which they are defined (i.e. file,
407 # namespace, or group documentation), provided this scope is documented. If set
408 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
409 # Man pages) or section (for LaTeX and RTF).
410 # The default value is: NO.
412 INLINE_SIMPLE_STRUCTS = NO
414 # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
415 # enum is documented as struct, union, or enum with the name of the typedef. So
416 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
417 # with name TypeT. When disabled the typedef will appear as a member of a file,
418 # namespace, or class. And the struct will be named TypeS. This can typically be
419 # useful for C code in case the coding convention dictates that all compound
420 # types are typedef'ed and only the typedef is referenced, never the tag name.
421 # The default value is: NO.
423 TYPEDEF_HIDES_STRUCT = NO
425 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
426 # cache is used to resolve symbols given their name and scope. Since this can be
427 # an expensive process and often the same symbol appears multiple times in the
428 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
429 # doxygen will become slower. If the cache is too large, memory is wasted. The
430 # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
431 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
432 # symbols. At the end of a run doxygen will report the cache usage and suggest
433 # the optimal cache size from a speed point of view.
434 # Minimum value: 0, maximum value: 9, default value: 0.
436 LOOKUP_CACHE_SIZE = 0
438 #---------------------------------------------------------------------------
439 # Build related configuration options
440 #---------------------------------------------------------------------------
442 # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
443 # documentation are documented, even if no documentation was available. Private
444 # class members and static file members will be hidden unless the
445 # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
446 # Note: This will also disable the warnings about undocumented members that are
447 # normally produced when WARNINGS is set to YES.
448 # The default value is: NO.
452 # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
453 # be included in the documentation.
454 # The default value is: NO.
458 # If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal
459 # scope will be included in the documentation.
460 # The default value is: NO.
464 # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
465 # included in the documentation.
466 # The default value is: NO.
470 # If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined
471 # locally in source files will be included in the documentation. If set to NO,
472 # only classes defined in header files are included. Does not have any effect
474 # The default value is: YES.
476 EXTRACT_LOCAL_CLASSES = YES
478 # This flag is only useful for Objective-C code. If set to YES, local methods,
479 # which are defined in the implementation section but not in the interface are
480 # included in the documentation. If set to NO, only methods in the interface are
482 # The default value is: NO.
484 EXTRACT_LOCAL_METHODS = NO
486 # If this flag is set to YES, the members of anonymous namespaces will be
487 # extracted and appear in the documentation as a namespace called
488 # 'anonymous_namespace{file}', where file will be replaced with the base name of
489 # the file that contains the anonymous namespace. By default anonymous namespace
491 # The default value is: NO.
493 EXTRACT_ANON_NSPACES = NO
495 # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
496 # undocumented members inside documented classes or files. If set to NO these
497 # members will be included in the various overviews, but no documentation
498 # section is generated. This option has no effect if EXTRACT_ALL is enabled.
499 # The default value is: NO.
501 HIDE_UNDOC_MEMBERS = NO
503 # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
504 # undocumented classes that are normally visible in the class hierarchy. If set
505 # to NO, these classes will be included in the various overviews. This option
506 # has no effect if EXTRACT_ALL is enabled.
507 # The default value is: NO.
509 HIDE_UNDOC_CLASSES = NO
511 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
512 # (class|struct|union) declarations. If set to NO, these declarations will be
513 # included in the documentation.
514 # The default value is: NO.
516 HIDE_FRIEND_COMPOUNDS = NO
518 # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
519 # documentation blocks found inside the body of a function. If set to NO, these
520 # blocks will be appended to the function's detailed documentation block.
521 # The default value is: NO.
523 HIDE_IN_BODY_DOCS = NO
525 # The INTERNAL_DOCS tag determines if documentation that is typed after a
526 # \internal command is included. If the tag is set to NO then the documentation
527 # will be excluded. Set it to YES to include the internal documentation.
528 # The default value is: NO.
532 # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
533 # names in lower-case letters. If set to YES, upper-case letters are also
534 # allowed. This is useful if you have classes or files whose names only differ
535 # in case and if your file system supports case sensitive file names. Windows
536 # and Mac users are advised to set this option to NO.
537 # The default value is: system dependent.
539 CASE_SENSE_NAMES = YES
541 # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
542 # their full class and namespace scopes in the documentation. If set to YES, the
543 # scope will be hidden.
544 # The default value is: NO.
546 HIDE_SCOPE_NAMES = NO
548 # If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will
549 # append additional text to a page's title, such as Class Reference. If set to
550 # YES the compound reference will be hidden.
551 # The default value is: NO.
553 HIDE_COMPOUND_REFERENCE= NO
555 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
556 # the files that are included by a file in the documentation of that file.
557 # The default value is: YES.
559 SHOW_INCLUDE_FILES = YES
561 # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
562 # grouped member an include statement to the documentation, telling the reader
563 # which file to include in order to use the member.
564 # The default value is: NO.
566 SHOW_GROUPED_MEMB_INC = NO
568 # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
569 # files with double quotes in the documentation rather than with sharp brackets.
570 # The default value is: NO.
572 FORCE_LOCAL_INCLUDES = NO
574 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
575 # documentation for inline members.
576 # The default value is: YES.
580 # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
581 # (detailed) documentation of file and class members alphabetically by member
582 # name. If set to NO, the members will appear in declaration order.
583 # The default value is: YES.
585 SORT_MEMBER_DOCS = YES
587 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
588 # descriptions of file, namespace and class members alphabetically by member
589 # name. If set to NO, the members will appear in declaration order. Note that
590 # this will also influence the order of the classes in the class list.
591 # The default value is: NO.
595 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
596 # (brief and detailed) documentation of class members so that constructors and
597 # destructors are listed first. If set to NO the constructors will appear in the
598 # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
599 # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
600 # member documentation.
601 # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
602 # detailed member documentation.
603 # The default value is: NO.
605 SORT_MEMBERS_CTORS_1ST = NO
607 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
608 # of group names into alphabetical order. If set to NO the group names will
609 # appear in their defined order.
610 # The default value is: NO.
612 SORT_GROUP_NAMES = NO
614 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
615 # fully-qualified names, including namespaces. If set to NO, the class list will
616 # be sorted only by class name, not including the namespace part.
617 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
618 # Note: This option applies only to the class list, not to the alphabetical
620 # The default value is: NO.
622 SORT_BY_SCOPE_NAME = NO
624 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
625 # type resolution of all parameters of a function it will reject a match between
626 # the prototype and the implementation of a member function even if there is
627 # only one candidate or it is obvious which candidate to choose by doing a
628 # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
629 # accept a match between prototype and implementation in such cases.
630 # The default value is: NO.
632 STRICT_PROTO_MATCHING = NO
634 # The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo
635 # list. This list is created by putting \todo commands in the documentation.
636 # The default value is: YES.
638 GENERATE_TODOLIST = YES
640 # The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test
641 # list. This list is created by putting \test commands in the documentation.
642 # The default value is: YES.
644 GENERATE_TESTLIST = YES
646 # The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug
647 # list. This list is created by putting \bug commands in the documentation.
648 # The default value is: YES.
650 GENERATE_BUGLIST = YES
652 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO)
653 # the deprecated list. This list is created by putting \deprecated commands in
655 # The default value is: YES.
657 GENERATE_DEPRECATEDLIST= YES
659 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
660 # sections, marked by \if <section_label> ... \endif and \cond <section_label>
661 # ... \endcond blocks.
665 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
666 # initial value of a variable or macro / define can have for it to appear in the
667 # documentation. If the initializer consists of more lines than specified here
668 # it will be hidden. Use a value of 0 to hide initializers completely. The
669 # appearance of the value of individual variables and macros / defines can be
670 # controlled using \showinitializer or \hideinitializer command in the
671 # documentation regardless of this setting.
672 # Minimum value: 0, maximum value: 10000, default value: 30.
674 MAX_INITIALIZER_LINES = 30
676 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
677 # the bottom of the documentation of classes and structs. If set to YES, the
678 # list will mention the files that were used to generate the documentation.
679 # The default value is: YES.
681 SHOW_USED_FILES = YES
683 # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
684 # will remove the Files entry from the Quick Index and from the Folder Tree View
686 # The default value is: YES.
690 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
691 # page. This will remove the Namespaces entry from the Quick Index and from the
692 # Folder Tree View (if specified).
693 # The default value is: YES.
695 SHOW_NAMESPACES = YES
697 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
698 # doxygen should invoke to get the current version for each file (typically from
699 # the version control system). Doxygen will invoke the program by executing (via
700 # popen()) the command command input-file, where command is the value of the
701 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
702 # by doxygen. Whatever the program writes to standard output is used as the file
703 # version. For an example see the documentation.
705 FILE_VERSION_FILTER =
707 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
708 # by doxygen. The layout file controls the global structure of the generated
709 # output files in an output format independent way. To create the layout file
710 # that represents doxygen's defaults, run doxygen with the -l option. You can
711 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
712 # will be used as the name of the layout file.
714 # Note that if you run doxygen from a directory containing a file called
715 # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
720 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
721 # the reference definitions. This must be a list of .bib files. The .bib
722 # extension is automatically appended if omitted. This requires the bibtex tool
723 # to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info.
724 # For LaTeX the style of the bibliography can be controlled using
725 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
726 # search path. See also \cite for info how to create references.
730 #---------------------------------------------------------------------------
731 # Configuration options related to warning and progress messages
732 #---------------------------------------------------------------------------
734 # The QUIET tag can be used to turn on/off the messages that are generated to
735 # standard output by doxygen. If QUIET is set to YES this implies that the
737 # The default value is: NO.
741 # The WARNINGS tag can be used to turn on/off the warning messages that are
742 # generated to standard error (stderr) by doxygen. If WARNINGS is set to YES
743 # this implies that the warnings are on.
745 # Tip: Turn warnings on while writing the documentation.
746 # The default value is: YES.
750 # If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate
751 # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
752 # will automatically be disabled.
753 # The default value is: YES.
755 WARN_IF_UNDOCUMENTED = YES
757 # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
758 # potential errors in the documentation, such as not documenting some parameters
759 # in a documented function, or documenting parameters that don't exist or using
760 # markup commands wrongly.
761 # The default value is: YES.
763 WARN_IF_DOC_ERROR = YES
765 # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
766 # are documented, but have no documentation for their parameters or return
767 # value. If set to NO, doxygen will only warn about wrong or incomplete
768 # parameter documentation, but not about the absence of documentation. If
769 # EXTRACT_ALL is set to YES then this flag will automatically be disabled.
770 # The default value is: NO.
772 WARN_NO_PARAMDOC = NO
774 # If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when
775 # a warning is encountered.
776 # The default value is: NO.
780 # The WARN_FORMAT tag determines the format of the warning messages that doxygen
781 # can produce. The string should contain the $file, $line, and $text tags, which
782 # will be replaced by the file and line number from which the warning originated
783 # and the warning text. Optionally the format may contain $version, which will
784 # be replaced by the version of the file (if it could be obtained via
785 # FILE_VERSION_FILTER)
786 # The default value is: $file:$line: $text.
788 WARN_FORMAT = "$file:$line: $text"
790 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
791 # messages should be written. If left blank the output is written to standard
796 #---------------------------------------------------------------------------
797 # Configuration options related to the input files
798 #---------------------------------------------------------------------------
800 # The INPUT tag is used to specify the files and/or directories that contain
801 # documented source files. You may enter file names like myfile.cpp or
802 # directories like /usr/src/myproject. Separate the files or directories with
803 # spaces. See also FILE_PATTERNS and EXTENSION_MAPPING
804 # Note: If this tag is empty the current directory is searched.
808 # This tag can be used to specify the character encoding of the source files
809 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
810 # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
811 # documentation (see: https://www.gnu.org/software/libiconv/) for the list of
812 # possible encodings.
813 # The default value is: UTF-8.
815 INPUT_ENCODING = UTF-8
817 # If the value of the INPUT tag contains directories, you can use the
818 # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
819 # *.h) to filter out the source-files in the directories.
821 # Note that for custom extensions or not directly supported extensions you also
822 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
825 # If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp,
826 # *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h,
827 # *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc,
828 # *.m, *.markdown, *.md, *.mm, *.dox, *.py, *.pyw, *.f90, *.f95, *.f03, *.f08,
829 # *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf, *.qsf and *.ice.
831 FILE_PATTERNS = *.c \
836 # The RECURSIVE tag can be used to specify whether or not subdirectories should
837 # be searched for input files as well.
838 # The default value is: NO.
842 # The EXCLUDE tag can be used to specify files and/or directories that should be
843 # excluded from the INPUT source files. This way you can easily exclude a
844 # subdirectory from a directory tree whose root is specified with the INPUT tag.
846 # Note that relative paths are relative to the directory from which doxygen is
851 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
852 # directories that are symbolic links (a Unix file system feature) are excluded
854 # The default value is: NO.
856 EXCLUDE_SYMLINKS = NO
858 # If the value of the INPUT tag contains directories, you can use the
859 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
860 # certain files from those directories.
862 # Note that the wildcards are matched against the file with absolute path, so to
863 # exclude all test directories for example use the pattern */test/*
867 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
868 # (namespaces, classes, functions, etc.) that should be excluded from the
869 # output. The symbol name can be a fully qualified name, a word, or if the
870 # wildcard * is used, a substring. Examples: ANamespace, AClass,
871 # AClass::ANamespace, ANamespace::*Test
873 # Note that the wildcards are matched against the file with absolute path, so to
874 # exclude all test directories use the pattern */test/*
878 # The EXAMPLE_PATH tag can be used to specify one or more files or directories
879 # that contain example code fragments that are included (see the \include
884 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
885 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
886 # *.h) to filter out the source-files in the directories. If left blank all
887 # files are included.
891 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
892 # searched for input files to be used with the \include or \dontinclude commands
893 # irrespective of the value of the RECURSIVE tag.
894 # The default value is: NO.
896 EXAMPLE_RECURSIVE = NO
898 # The IMAGE_PATH tag can be used to specify one or more files or directories
899 # that contain images that are to be included in the documentation (see the
904 # The INPUT_FILTER tag can be used to specify a program that doxygen should
905 # invoke to filter for each input file. Doxygen will invoke the filter program
906 # by executing (via popen()) the command:
908 # <filter> <input-file>
910 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
911 # name of an input file. Doxygen will then use the output that the filter
912 # program writes to standard output. If FILTER_PATTERNS is specified, this tag
915 # Note that the filter must not add or remove lines; it is applied before the
916 # code is scanned, but not when the output code is generated. If lines are added
917 # or removed, the anchors will not be placed correctly.
919 # Note that for custom extensions or not directly supported extensions you also
920 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
921 # properly processed by doxygen.
925 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
926 # basis. Doxygen will compare the file name with each pattern and apply the
927 # filter if there is a match. The filters are a list of the form: pattern=filter
928 # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
929 # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
930 # patterns match the file name, INPUT_FILTER is applied.
932 # Note that for custom extensions or not directly supported extensions you also
933 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
934 # properly processed by doxygen.
938 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
939 # INPUT_FILTER) will also be used to filter the input files that are used for
940 # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
941 # The default value is: NO.
943 FILTER_SOURCE_FILES = NO
945 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
946 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
947 # it is also possible to disable source filtering for a specific pattern using
948 # *.ext= (so without naming a filter).
949 # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
951 FILTER_SOURCE_PATTERNS =
953 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
954 # is part of the input, its contents will be placed on the main page
955 # (index.html). This can be useful if you have a project on for instance GitHub
956 # and want to reuse the introduction page also for the doxygen output.
958 USE_MDFILE_AS_MAINPAGE =
960 #---------------------------------------------------------------------------
961 # Configuration options related to source browsing
962 #---------------------------------------------------------------------------
964 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
965 # generated. Documented entities will be cross-referenced with these sources.
967 # Note: To get rid of all source code in the generated output, make sure that
968 # also VERBATIM_HEADERS is set to NO.
969 # The default value is: NO.
973 # Setting the INLINE_SOURCES tag to YES will include the body of functions,
974 # classes and enums directly into the documentation.
975 # The default value is: NO.
979 # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
980 # special comment blocks from generated source code fragments. Normal C, C++ and
981 # Fortran comments will always remain visible.
982 # The default value is: YES.
984 STRIP_CODE_COMMENTS = NO
986 # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
987 # entity all documented functions referencing it will be listed.
988 # The default value is: NO.
990 REFERENCED_BY_RELATION = YES
992 # If the REFERENCES_RELATION tag is set to YES then for each documented function
993 # all documented entities called/used by that function will be listed.
994 # The default value is: NO.
996 REFERENCES_RELATION = YES
998 # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
999 # to YES then the hyperlinks from functions in REFERENCES_RELATION and
1000 # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
1001 # link to the documentation.
1002 # The default value is: YES.
1004 REFERENCES_LINK_SOURCE = YES
1006 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1007 # source code will show a tooltip with additional information such as prototype,
1008 # brief description and links to the definition and documentation. Since this
1009 # will make the HTML file larger and loading of large files a bit slower, you
1010 # can opt to disable this feature.
1011 # The default value is: YES.
1012 # This tag requires that the tag SOURCE_BROWSER is set to YES.
1014 SOURCE_TOOLTIPS = YES
1016 # If the USE_HTAGS tag is set to YES then the references to source code will
1017 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1018 # source browser. The htags tool is part of GNU's global source tagging system
1019 # (see https://www.gnu.org/software/global/global.html). You will need version
1022 # To use it do the following:
1023 # - Install the latest version of global
1024 # - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
1025 # - Make sure the INPUT points to the root of the source tree
1026 # - Run doxygen as normal
1028 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
1029 # tools must be available from the command line (i.e. in the search path).
1031 # The result: instead of the source browser generated by doxygen, the links to
1032 # source code will now point to the output of htags.
1033 # The default value is: NO.
1034 # This tag requires that the tag SOURCE_BROWSER is set to YES.
1038 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
1039 # verbatim copy of the header file for each class for which an include is
1040 # specified. Set to NO to disable this.
1041 # See also: Section \class.
1042 # The default value is: YES.
1044 VERBATIM_HEADERS = YES
1046 #---------------------------------------------------------------------------
1047 # Configuration options related to the alphabetical class index
1048 #---------------------------------------------------------------------------
1050 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
1051 # compounds will be generated. Enable this if the project contains a lot of
1052 # classes, structs, unions or interfaces.
1053 # The default value is: YES.
1055 ALPHABETICAL_INDEX = YES
1057 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
1058 # which the alphabetical index list will be split.
1059 # Minimum value: 1, maximum value: 20, default value: 5.
1060 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1062 COLS_IN_ALPHA_INDEX = 5
1064 # In case all classes in a project start with a common prefix, all classes will
1065 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1066 # can be used to specify a prefix (or a list of prefixes) that should be ignored
1067 # while generating the index headers.
1068 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1072 #---------------------------------------------------------------------------
1073 # Configuration options related to the HTML output
1074 #---------------------------------------------------------------------------
1076 # If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output
1077 # The default value is: YES.
1081 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1082 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1084 # The default directory is: html.
1085 # This tag requires that the tag GENERATE_HTML is set to YES.
1089 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1090 # generated HTML page (for example: .htm, .php, .asp).
1091 # The default value is: .html.
1092 # This tag requires that the tag GENERATE_HTML is set to YES.
1094 HTML_FILE_EXTENSION = .html
1096 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1097 # each generated HTML page. If the tag is left blank doxygen will generate a
1100 # To get valid HTML the header file that includes any scripts and style sheets
1101 # that doxygen needs, which is dependent on the configuration options used (e.g.
1102 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1103 # default header using
1104 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1106 # and then modify the file new_header.html. See also section "Doxygen usage"
1107 # for information on how to generate the default header that doxygen normally
1109 # Note: The header is subject to change so you typically have to regenerate the
1110 # default header when upgrading to a newer version of doxygen. For a description
1111 # of the possible markers and block names see the documentation.
1112 # This tag requires that the tag GENERATE_HTML is set to YES.
1116 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1117 # generated HTML page. If the tag is left blank doxygen will generate a standard
1118 # footer. See HTML_HEADER for more information on how to generate a default
1119 # footer and what special commands can be used inside the footer. See also
1120 # section "Doxygen usage" for information on how to generate the default footer
1121 # that doxygen normally uses.
1122 # This tag requires that the tag GENERATE_HTML is set to YES.
1126 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1127 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1128 # the HTML output. If left blank doxygen will generate a default style sheet.
1129 # See also section "Doxygen usage" for information on how to generate the style
1130 # sheet that doxygen normally uses.
1131 # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
1132 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1134 # This tag requires that the tag GENERATE_HTML is set to YES.
1138 # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1139 # cascading style sheets that are included after the standard style sheets
1140 # created by doxygen. Using this option one can overrule certain style aspects.
1141 # This is preferred over using HTML_STYLESHEET since it does not replace the
1142 # standard style sheet and is therefore more robust against future updates.
1143 # Doxygen will copy the style sheet files to the output directory.
1144 # Note: The order of the extra style sheet files is of importance (e.g. the last
1145 # style sheet in the list overrules the setting of the previous ones in the
1146 # list). For an example see the documentation.
1147 # This tag requires that the tag GENERATE_HTML is set to YES.
1149 HTML_EXTRA_STYLESHEET =
1151 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1152 # other source files which should be copied to the HTML output directory. Note
1153 # that these files will be copied to the base HTML output directory. Use the
1154 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1155 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1156 # files will be copied as-is; there are no commands or markers available.
1157 # This tag requires that the tag GENERATE_HTML is set to YES.
1161 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1162 # will adjust the colors in the style sheet and background images according to
1163 # this color. Hue is specified as an angle on a colorwheel, see
1164 # https://en.wikipedia.org/wiki/Hue for more information. For instance the value
1165 # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
1166 # purple, and 360 is red again.
1167 # Minimum value: 0, maximum value: 359, default value: 220.
1168 # This tag requires that the tag GENERATE_HTML is set to YES.
1170 HTML_COLORSTYLE_HUE = 220
1172 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
1173 # in the HTML output. For a value of 0 the output will use grayscales only. A
1174 # value of 255 will produce the most vivid colors.
1175 # Minimum value: 0, maximum value: 255, default value: 100.
1176 # This tag requires that the tag GENERATE_HTML is set to YES.
1178 HTML_COLORSTYLE_SAT = 100
1180 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
1181 # luminance component of the colors in the HTML output. Values below 100
1182 # gradually make the output lighter, whereas values above 100 make the output
1183 # darker. The value divided by 100 is the actual gamma applied, so 80 represents
1184 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1186 # Minimum value: 40, maximum value: 240, default value: 80.
1187 # This tag requires that the tag GENERATE_HTML is set to YES.
1189 HTML_COLORSTYLE_GAMMA = 80
1191 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
1192 # page will contain the date and time when the page was generated. Setting this
1193 # to YES can help to show when doxygen was last run and thus if the
1194 # documentation is up to date.
1195 # The default value is: NO.
1196 # This tag requires that the tag GENERATE_HTML is set to YES.
1198 HTML_TIMESTAMP = YES
1200 # If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML
1201 # documentation will contain a main index with vertical navigation menus that
1202 # are dynamically created via Javascript. If disabled, the navigation index will
1203 # consists of multiple levels of tabs that are statically embedded in every HTML
1204 # page. Disable this option to support browsers that do not have Javascript,
1205 # like the Qt help browser.
1206 # The default value is: YES.
1207 # This tag requires that the tag GENERATE_HTML is set to YES.
1209 HTML_DYNAMIC_MENUS = YES
1211 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1212 # documentation will contain sections that can be hidden and shown after the
1214 # The default value is: NO.
1215 # This tag requires that the tag GENERATE_HTML is set to YES.
1217 HTML_DYNAMIC_SECTIONS = NO
1219 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
1220 # shown in the various tree structured indices initially; the user can expand
1221 # and collapse entries dynamically later on. Doxygen will expand the tree to
1222 # such a level that at most the specified number of entries are visible (unless
1223 # a fully collapsed tree already exceeds this amount). So setting the number of
1224 # entries 1 will produce a full collapsed tree by default. 0 is a special value
1225 # representing an infinite number of entries and will result in a full expanded
1227 # Minimum value: 0, maximum value: 9999, default value: 100.
1228 # This tag requires that the tag GENERATE_HTML is set to YES.
1230 HTML_INDEX_NUM_ENTRIES = 100
1232 # If the GENERATE_DOCSET tag is set to YES, additional index files will be
1233 # generated that can be used as input for Apple's Xcode 3 integrated development
1234 # environment (see: https://developer.apple.com/xcode/), introduced with OSX
1235 # 10.5 (Leopard). To create a documentation set, doxygen will generate a
1236 # Makefile in the HTML output directory. Running make will produce the docset in
1237 # that directory and running make install will install the docset in
1238 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1239 # startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy
1240 # genXcode/_index.html for more information.
1241 # The default value is: NO.
1242 # This tag requires that the tag GENERATE_HTML is set to YES.
1244 GENERATE_DOCSET = NO
1246 # This tag determines the name of the docset feed. A documentation feed provides
1247 # an umbrella under which multiple documentation sets from a single provider
1248 # (such as a company or product suite) can be grouped.
1249 # The default value is: Doxygen generated docs.
1250 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1252 DOCSET_FEEDNAME = "Doxygen generated docs"
1254 # This tag specifies a string that should uniquely identify the documentation
1255 # set bundle. This should be a reverse domain-name style string, e.g.
1256 # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
1257 # The default value is: org.doxygen.Project.
1258 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1260 DOCSET_BUNDLE_ID = org.doxygen.Project
1262 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1263 # the documentation publisher. This should be a reverse domain-name style
1264 # string, e.g. com.mycompany.MyDocSet.documentation.
1265 # The default value is: org.doxygen.Publisher.
1266 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1268 DOCSET_PUBLISHER_ID = org.doxygen.Publisher
1270 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1271 # The default value is: Publisher.
1272 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1274 DOCSET_PUBLISHER_NAME = Publisher
1276 # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1277 # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1278 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1279 # (see: https://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1282 # The HTML Help Workshop contains a compiler that can convert all HTML output
1283 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1284 # files are now used as the Windows 98 help format, and will replace the old
1285 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1286 # HTML files also contain an index, a table of contents, and you can search for
1287 # words in the documentation. The HTML workshop also contains a viewer for
1288 # compressed HTML files.
1289 # The default value is: NO.
1290 # This tag requires that the tag GENERATE_HTML is set to YES.
1292 GENERATE_HTMLHELP = NO
1294 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1295 # file. You can add a path in front of the file if the result should not be
1296 # written to the html output directory.
1297 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1301 # The HHC_LOCATION tag can be used to specify the location (absolute path
1302 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
1303 # doxygen will try to run the HTML help compiler on the generated index.hhp.
1304 # The file has to be specified with full path.
1305 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1309 # The GENERATE_CHI flag controls if a separate .chi index file is generated
1310 # (YES) or that it should be included in the master .chm file (NO).
1311 # The default value is: NO.
1312 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1316 # The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc)
1317 # and project file content.
1318 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1320 CHM_INDEX_ENCODING =
1322 # The BINARY_TOC flag controls whether a binary table of contents is generated
1323 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1324 # enables the Previous and Next buttons.
1325 # The default value is: NO.
1326 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1330 # The TOC_EXPAND flag can be set to YES to add extra items for group members to
1331 # the table of contents of the HTML help documentation and to the tree view.
1332 # The default value is: NO.
1333 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1337 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1338 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1339 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1340 # (.qch) of the generated HTML documentation.
1341 # The default value is: NO.
1342 # This tag requires that the tag GENERATE_HTML is set to YES.
1346 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
1347 # the file name of the resulting .qch file. The path specified is relative to
1348 # the HTML output folder.
1349 # This tag requires that the tag GENERATE_QHP is set to YES.
1353 # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1354 # Project output. For more information please see Qt Help Project / Namespace
1355 # (see: http://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).
1356 # The default value is: org.doxygen.Project.
1357 # This tag requires that the tag GENERATE_QHP is set to YES.
1359 QHP_NAMESPACE = org.doxygen.Project
1361 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
1362 # Help Project output. For more information please see Qt Help Project / Virtual
1363 # Folders (see: http://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-
1365 # The default value is: doc.
1366 # This tag requires that the tag GENERATE_QHP is set to YES.
1368 QHP_VIRTUAL_FOLDER = doc
1370 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1371 # filter to add. For more information please see Qt Help Project / Custom
1372 # Filters (see: http://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-
1374 # This tag requires that the tag GENERATE_QHP is set to YES.
1376 QHP_CUST_FILTER_NAME =
1378 # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1379 # custom filter to add. For more information please see Qt Help Project / Custom
1380 # Filters (see: http://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-
1382 # This tag requires that the tag GENERATE_QHP is set to YES.
1384 QHP_CUST_FILTER_ATTRS =
1386 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1387 # project's filter section matches. Qt Help Project / Filter Attributes (see:
1388 # http://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).
1389 # This tag requires that the tag GENERATE_QHP is set to YES.
1391 QHP_SECT_FILTER_ATTRS =
1393 # The QHG_LOCATION tag can be used to specify the location of Qt's
1394 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1395 # generated .qhp file.
1396 # This tag requires that the tag GENERATE_QHP is set to YES.
1400 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1401 # generated, together with the HTML files, they form an Eclipse help plugin. To
1402 # install this plugin and make it available under the help contents menu in
1403 # Eclipse, the contents of the directory containing the HTML and XML files needs
1404 # to be copied into the plugins directory of eclipse. The name of the directory
1405 # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
1406 # After copying Eclipse needs to be restarted before the help appears.
1407 # The default value is: NO.
1408 # This tag requires that the tag GENERATE_HTML is set to YES.
1410 GENERATE_ECLIPSEHELP = NO
1412 # A unique identifier for the Eclipse help plugin. When installing the plugin
1413 # the directory name containing the HTML and XML files should also have this
1414 # name. Each documentation set should have its own identifier.
1415 # The default value is: org.doxygen.Project.
1416 # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
1418 ECLIPSE_DOC_ID = org.doxygen.Project
1420 # If you want full control over the layout of the generated HTML pages it might
1421 # be necessary to disable the index and replace it with your own. The
1422 # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
1423 # of each HTML page. A value of NO enables the index and the value YES disables
1424 # it. Since the tabs in the index contain the same information as the navigation
1425 # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
1426 # The default value is: NO.
1427 # This tag requires that the tag GENERATE_HTML is set to YES.
1431 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1432 # structure should be generated to display hierarchical information. If the tag
1433 # value is set to YES, a side panel will be generated containing a tree-like
1434 # index structure (just like the one that is generated for HTML Help). For this
1435 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
1436 # (i.e. any modern browser). Windows users are probably better off using the
1437 # HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can
1438 # further fine-tune the look of the index. As an example, the default style
1439 # sheet generated by doxygen has an example that shows how to put an image at
1440 # the root of the tree instead of the PROJECT_NAME. Since the tree basically has
1441 # the same information as the tab index, you could consider setting
1442 # DISABLE_INDEX to YES when enabling this option.
1443 # The default value is: NO.
1444 # This tag requires that the tag GENERATE_HTML is set to YES.
1446 GENERATE_TREEVIEW = YES
1448 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
1449 # doxygen will group on one line in the generated HTML documentation.
1451 # Note that a value of 0 will completely suppress the enum values from appearing
1452 # in the overview section.
1453 # Minimum value: 0, maximum value: 20, default value: 4.
1454 # This tag requires that the tag GENERATE_HTML is set to YES.
1456 ENUM_VALUES_PER_LINE = 4
1458 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
1459 # to set the initial width (in pixels) of the frame in which the tree is shown.
1460 # Minimum value: 0, maximum value: 1500, default value: 250.
1461 # This tag requires that the tag GENERATE_HTML is set to YES.
1463 TREEVIEW_WIDTH = 250
1465 # If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to
1466 # external symbols imported via tag files in a separate window.
1467 # The default value is: NO.
1468 # This tag requires that the tag GENERATE_HTML is set to YES.
1470 EXT_LINKS_IN_WINDOW = NO
1472 # Use this tag to change the font size of LaTeX formulas included as images in
1473 # the HTML documentation. When you change the font size after a successful
1474 # doxygen run you need to manually remove any form_*.png images from the HTML
1475 # output directory to force them to be regenerated.
1476 # Minimum value: 8, maximum value: 50, default value: 10.
1477 # This tag requires that the tag GENERATE_HTML is set to YES.
1479 FORMULA_FONTSIZE = 10
1481 # Use the FORMULA_TRANSPARENT tag to determine whether or not the images
1482 # generated for formulas are transparent PNGs. Transparent PNGs are not
1483 # supported properly for IE 6.0, but are supported on all modern browsers.
1485 # Note that when changing this option you need to delete any form_*.png files in
1486 # the HTML output directory before the changes have effect.
1487 # The default value is: YES.
1488 # This tag requires that the tag GENERATE_HTML is set to YES.
1490 FORMULA_TRANSPARENT = YES
1492 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1493 # https://www.mathjax.org) which uses client side Javascript for the rendering
1494 # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
1495 # installed or if you want to formulas look prettier in the HTML output. When
1496 # enabled you may also need to install MathJax separately and configure the path
1497 # to it using the MATHJAX_RELPATH option.
1498 # The default value is: NO.
1499 # This tag requires that the tag GENERATE_HTML is set to YES.
1503 # When MathJax is enabled you can set the default output format to be used for
1504 # the MathJax output. See the MathJax site (see:
1505 # http://docs.mathjax.org/en/latest/output.html) for more details.
1506 # Possible values are: HTML-CSS (which is slower, but has the best
1507 # compatibility), NativeMML (i.e. MathML) and SVG.
1508 # The default value is: HTML-CSS.
1509 # This tag requires that the tag USE_MATHJAX is set to YES.
1511 MATHJAX_FORMAT = HTML-CSS
1513 # When MathJax is enabled you need to specify the location relative to the HTML
1514 # output directory using the MATHJAX_RELPATH option. The destination directory
1515 # should contain the MathJax.js script. For instance, if the mathjax directory
1516 # is located at the same level as the HTML output directory, then
1517 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1518 # Content Delivery Network so you can quickly see the result without installing
1519 # MathJax. However, it is strongly recommended to install a local copy of
1520 # MathJax from https://www.mathjax.org before deployment.
1521 # The default value is: https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/.
1522 # This tag requires that the tag USE_MATHJAX is set to YES.
1524 MATHJAX_RELPATH = https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/
1526 # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
1527 # extension names that should be enabled during MathJax rendering. For example
1528 # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
1529 # This tag requires that the tag USE_MATHJAX is set to YES.
1531 MATHJAX_EXTENSIONS =
1533 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1534 # of code that will be used on startup of the MathJax code. See the MathJax site
1535 # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
1536 # example see the documentation.
1537 # This tag requires that the tag USE_MATHJAX is set to YES.
1541 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1542 # the HTML output. The underlying search engine uses javascript and DHTML and
1543 # should work on any modern browser. Note that when using HTML help
1544 # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
1545 # there is already a search function so this one should typically be disabled.
1546 # For large projects the javascript based search engine can be slow, then
1547 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1548 # search using the keyboard; to jump to the search box use <access key> + S
1549 # (what the <access key> is depends on the OS and browser, but it is typically
1550 # <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
1551 # key> to jump into the search results window, the results can be navigated
1552 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1553 # the search. The filter options can be selected when the cursor is inside the
1554 # search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
1555 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1557 # The default value is: YES.
1558 # This tag requires that the tag GENERATE_HTML is set to YES.
1562 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1563 # implemented using a web server instead of a web client using Javascript. There
1564 # are two flavors of web server based searching depending on the EXTERNAL_SEARCH
1565 # setting. When disabled, doxygen will generate a PHP script for searching and
1566 # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
1567 # and searching needs to be provided by external tools. See the section
1568 # "External Indexing and Searching" for details.
1569 # The default value is: NO.
1570 # This tag requires that the tag SEARCHENGINE is set to YES.
1572 SERVER_BASED_SEARCH = NO
1574 # When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
1575 # script for searching. Instead the search results are written to an XML file
1576 # which needs to be processed by an external indexer. Doxygen will invoke an
1577 # external search engine pointed to by the SEARCHENGINE_URL option to obtain the
1580 # Doxygen ships with an example indexer (doxyindexer) and search engine
1581 # (doxysearch.cgi) which are based on the open source search engine library
1582 # Xapian (see: https://xapian.org/).
1584 # See the section "External Indexing and Searching" for details.
1585 # The default value is: NO.
1586 # This tag requires that the tag SEARCHENGINE is set to YES.
1588 EXTERNAL_SEARCH = NO
1590 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
1591 # which will return the search results when EXTERNAL_SEARCH is enabled.
1593 # Doxygen ships with an example indexer (doxyindexer) and search engine
1594 # (doxysearch.cgi) which are based on the open source search engine library
1595 # Xapian (see: https://xapian.org/). See the section "External Indexing and
1596 # Searching" for details.
1597 # This tag requires that the tag SEARCHENGINE is set to YES.
1601 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
1602 # search data is written to a file for indexing by an external tool. With the
1603 # SEARCHDATA_FILE tag the name of this file can be specified.
1604 # The default file is: searchdata.xml.
1605 # This tag requires that the tag SEARCHENGINE is set to YES.
1607 SEARCHDATA_FILE = searchdata.xml
1609 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
1610 # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
1611 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1612 # projects and redirect the results back to the right project.
1613 # This tag requires that the tag SEARCHENGINE is set to YES.
1615 EXTERNAL_SEARCH_ID =
1617 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1618 # projects other than the one defined by this configuration file, but that are
1619 # all added to the same external search index. Each project needs to have a
1620 # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
1621 # to a relative location where the documentation can be found. The format is:
1622 # EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
1623 # This tag requires that the tag SEARCHENGINE is set to YES.
1625 EXTRA_SEARCH_MAPPINGS =
1627 #---------------------------------------------------------------------------
1628 # Configuration options related to the LaTeX output
1629 #---------------------------------------------------------------------------
1631 # If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.
1632 # The default value is: YES.
1636 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1637 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1639 # The default directory is: latex.
1640 # This tag requires that the tag GENERATE_LATEX is set to YES.
1642 LATEX_OUTPUT = latex
1644 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1647 # Note that when not enabling USE_PDFLATEX the default is latex when enabling
1648 # USE_PDFLATEX the default is pdflatex and when in the later case latex is
1649 # chosen this is overwritten by pdflatex. For specific output languages the
1650 # default can have been set differently, this depends on the implementation of
1651 # the output language.
1652 # This tag requires that the tag GENERATE_LATEX is set to YES.
1654 LATEX_CMD_NAME = latex
1656 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
1658 # Note: This tag is used in the Makefile / make.bat.
1659 # See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
1661 # The default file is: makeindex.
1662 # This tag requires that the tag GENERATE_LATEX is set to YES.
1664 MAKEINDEX_CMD_NAME = makeindex
1666 # The LATEX_MAKEINDEX_CMD tag can be used to specify the command name to
1667 # generate index for LaTeX.
1668 # Note: This tag is used in the generated output file (.tex).
1669 # See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat.
1670 # The default value is: \makeindex.
1671 # This tag requires that the tag GENERATE_LATEX is set to YES.
1673 LATEX_MAKEINDEX_CMD = \makeindex
1675 # If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
1676 # documents. This may be useful for small projects and may help to save some
1678 # The default value is: NO.
1679 # This tag requires that the tag GENERATE_LATEX is set to YES.
1683 # The PAPER_TYPE tag can be used to set the paper type that is used by the
1685 # Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
1686 # 14 inches) and executive (7.25 x 10.5 inches).
1687 # The default value is: a4.
1688 # This tag requires that the tag GENERATE_LATEX is set to YES.
1692 # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
1693 # that should be included in the LaTeX output. The package can be specified just
1694 # by its name or with the correct syntax as to be used with the LaTeX
1695 # \usepackage command. To get the times font for instance you can specify :
1696 # EXTRA_PACKAGES=times or EXTRA_PACKAGES={times}
1697 # To use the option intlimits with the amsmath package you can specify:
1698 # EXTRA_PACKAGES=[intlimits]{amsmath}
1699 # If left blank no extra packages will be included.
1700 # This tag requires that the tag GENERATE_LATEX is set to YES.
1704 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1705 # generated LaTeX document. The header should contain everything until the first
1706 # chapter. If it is left blank doxygen will generate a standard header. See
1707 # section "Doxygen usage" for information on how to let doxygen write the
1708 # default header to a separate file.
1710 # Note: Only use a user-defined header if you know what you are doing! The
1711 # following commands have a special meaning inside the header: $title,
1712 # $datetime, $date, $doxygenversion, $projectname, $projectnumber,
1713 # $projectbrief, $projectlogo. Doxygen will replace $title with the empty
1714 # string, for the replacement values of the other commands the user is referred
1716 # This tag requires that the tag GENERATE_LATEX is set to YES.
1720 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1721 # generated LaTeX document. The footer should contain everything after the last
1722 # chapter. If it is left blank doxygen will generate a standard footer. See
1723 # LATEX_HEADER for more information on how to generate a default footer and what
1724 # special commands can be used inside the footer.
1726 # Note: Only use a user-defined footer if you know what you are doing!
1727 # This tag requires that the tag GENERATE_LATEX is set to YES.
1731 # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1732 # LaTeX style sheets that are included after the standard style sheets created
1733 # by doxygen. Using this option one can overrule certain style aspects. Doxygen
1734 # will copy the style sheet files to the output directory.
1735 # Note: The order of the extra style sheet files is of importance (e.g. the last
1736 # style sheet in the list overrules the setting of the previous ones in the
1738 # This tag requires that the tag GENERATE_LATEX is set to YES.
1740 LATEX_EXTRA_STYLESHEET =
1742 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1743 # other source files which should be copied to the LATEX_OUTPUT output
1744 # directory. Note that the files will be copied as-is; there are no commands or
1745 # markers available.
1746 # This tag requires that the tag GENERATE_LATEX is set to YES.
1750 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
1751 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
1752 # contain links (just like the HTML output) instead of page references. This
1753 # makes the output suitable for online browsing using a PDF viewer.
1754 # The default value is: YES.
1755 # This tag requires that the tag GENERATE_LATEX is set to YES.
1759 # If the USE_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
1760 # the PDF file directly from the LaTeX files. Set this option to YES, to get a
1761 # higher quality PDF documentation.
1762 # The default value is: YES.
1763 # This tag requires that the tag GENERATE_LATEX is set to YES.
1767 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
1768 # command to the generated LaTeX files. This will instruct LaTeX to keep running
1769 # if errors occur, instead of asking the user for help. This option is also used
1770 # when generating formulas in HTML.
1771 # The default value is: NO.
1772 # This tag requires that the tag GENERATE_LATEX is set to YES.
1774 LATEX_BATCHMODE = NO
1776 # If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
1777 # index chapters (such as File Index, Compound Index, etc.) in the output.
1778 # The default value is: NO.
1779 # This tag requires that the tag GENERATE_LATEX is set to YES.
1781 LATEX_HIDE_INDICES = NO
1783 # If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
1784 # code with syntax highlighting in the LaTeX output.
1786 # Note that which sources are shown also depends on other settings such as
1788 # The default value is: NO.
1789 # This tag requires that the tag GENERATE_LATEX is set to YES.
1791 LATEX_SOURCE_CODE = NO
1793 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1794 # bibliography, e.g. plainnat, or ieeetr. See
1795 # https://en.wikipedia.org/wiki/BibTeX and \cite for more info.
1796 # The default value is: plain.
1797 # This tag requires that the tag GENERATE_LATEX is set to YES.
1799 LATEX_BIB_STYLE = plain
1801 # If the LATEX_TIMESTAMP tag is set to YES then the footer of each generated
1802 # page will contain the date and time when the page was generated. Setting this
1803 # to NO can help when comparing the output of multiple runs.
1804 # The default value is: NO.
1805 # This tag requires that the tag GENERATE_LATEX is set to YES.
1807 LATEX_TIMESTAMP = NO
1809 # The LATEX_EMOJI_DIRECTORY tag is used to specify the (relative or absolute)
1810 # path from which the emoji images will be read. If a relative path is entered,
1811 # it will be relative to the LATEX_OUTPUT directory. If left blank the
1812 # LATEX_OUTPUT directory will be used.
1813 # This tag requires that the tag GENERATE_LATEX is set to YES.
1815 LATEX_EMOJI_DIRECTORY =
1817 #---------------------------------------------------------------------------
1818 # Configuration options related to the RTF output
1819 #---------------------------------------------------------------------------
1821 # If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The
1822 # RTF output is optimized for Word 97 and may not look too pretty with other RTF
1824 # The default value is: NO.
1828 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
1829 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1831 # The default directory is: rtf.
1832 # This tag requires that the tag GENERATE_RTF is set to YES.
1836 # If the COMPACT_RTF tag is set to YES, doxygen generates more compact RTF
1837 # documents. This may be useful for small projects and may help to save some
1839 # The default value is: NO.
1840 # This tag requires that the tag GENERATE_RTF is set to YES.
1844 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
1845 # contain hyperlink fields. The RTF file will contain links (just like the HTML
1846 # output) instead of page references. This makes the output suitable for online
1847 # browsing using Word or some other Word compatible readers that support those
1850 # Note: WordPad (write) and others do not support links.
1851 # The default value is: NO.
1852 # This tag requires that the tag GENERATE_RTF is set to YES.
1856 # Load stylesheet definitions from file. Syntax is similar to doxygen's
1857 # configuration file, i.e. a series of assignments. You only have to provide
1858 # replacements, missing definitions are set to their default value.
1860 # See also section "Doxygen usage" for information on how to generate the
1861 # default style sheet that doxygen normally uses.
1862 # This tag requires that the tag GENERATE_RTF is set to YES.
1864 RTF_STYLESHEET_FILE =
1866 # Set optional variables used in the generation of an RTF document. Syntax is
1867 # similar to doxygen's configuration file. A template extensions file can be
1868 # generated using doxygen -e rtf extensionFile.
1869 # This tag requires that the tag GENERATE_RTF is set to YES.
1871 RTF_EXTENSIONS_FILE =
1873 # If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
1874 # with syntax highlighting in the RTF output.
1876 # Note that which sources are shown also depends on other settings such as
1878 # The default value is: NO.
1879 # This tag requires that the tag GENERATE_RTF is set to YES.
1881 RTF_SOURCE_CODE = NO
1883 #---------------------------------------------------------------------------
1884 # Configuration options related to the man page output
1885 #---------------------------------------------------------------------------
1887 # If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
1888 # classes and files.
1889 # The default value is: NO.
1893 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
1894 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1895 # it. A directory man3 will be created inside the directory specified by
1897 # The default directory is: man.
1898 # This tag requires that the tag GENERATE_MAN is set to YES.
1902 # The MAN_EXTENSION tag determines the extension that is added to the generated
1903 # man pages. In case the manual section does not start with a number, the number
1904 # 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
1906 # The default value is: .3.
1907 # This tag requires that the tag GENERATE_MAN is set to YES.
1911 # The MAN_SUBDIR tag determines the name of the directory created within
1912 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
1913 # MAN_EXTENSION with the initial . removed.
1914 # This tag requires that the tag GENERATE_MAN is set to YES.
1918 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
1919 # will generate one additional man file for each entity documented in the real
1920 # man page(s). These additional files only source the real man page, but without
1921 # them the man command would be unable to find the correct page.
1922 # The default value is: NO.
1923 # This tag requires that the tag GENERATE_MAN is set to YES.
1927 #---------------------------------------------------------------------------
1928 # Configuration options related to the XML output
1929 #---------------------------------------------------------------------------
1931 # If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
1932 # captures the structure of the code including all documentation.
1933 # The default value is: NO.
1937 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
1938 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1940 # The default directory is: xml.
1941 # This tag requires that the tag GENERATE_XML is set to YES.
1945 # If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program
1946 # listings (including syntax highlighting and cross-referencing information) to
1947 # the XML output. Note that enabling this will significantly increase the size
1948 # of the XML output.
1949 # The default value is: YES.
1950 # This tag requires that the tag GENERATE_XML is set to YES.
1952 XML_PROGRAMLISTING = YES
1954 # If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, doxygen will include
1955 # namespace members in file scope as well, matching the HTML output.
1956 # The default value is: NO.
1957 # This tag requires that the tag GENERATE_XML is set to YES.
1959 XML_NS_MEMB_FILE_SCOPE = NO
1961 #---------------------------------------------------------------------------
1962 # Configuration options related to the DOCBOOK output
1963 #---------------------------------------------------------------------------
1965 # If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files
1966 # that can be used to generate PDF.
1967 # The default value is: NO.
1969 GENERATE_DOCBOOK = NO
1971 # The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
1972 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1974 # The default directory is: docbook.
1975 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
1977 DOCBOOK_OUTPUT = docbook
1979 # If the DOCBOOK_PROGRAMLISTING tag is set to YES, doxygen will include the
1980 # program listings (including syntax highlighting and cross-referencing
1981 # information) to the DOCBOOK output. Note that enabling this will significantly
1982 # increase the size of the DOCBOOK output.
1983 # The default value is: NO.
1984 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
1986 DOCBOOK_PROGRAMLISTING = NO
1988 #---------------------------------------------------------------------------
1989 # Configuration options for the AutoGen Definitions output
1990 #---------------------------------------------------------------------------
1992 # If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an
1993 # AutoGen Definitions (see http://autogen.sourceforge.net/) file that captures
1994 # the structure of the code including all documentation. Note that this feature
1995 # is still experimental and incomplete at the moment.
1996 # The default value is: NO.
1998 GENERATE_AUTOGEN_DEF = NO
2000 #---------------------------------------------------------------------------
2001 # Configuration options related to the Perl module output
2002 #---------------------------------------------------------------------------
2004 # If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
2005 # file that captures the structure of the code including all documentation.
2007 # Note that this feature is still experimental and incomplete at the moment.
2008 # The default value is: NO.
2010 GENERATE_PERLMOD = NO
2012 # If the PERLMOD_LATEX tag is set to YES, doxygen will generate the necessary
2013 # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
2014 # output from the Perl module output.
2015 # The default value is: NO.
2016 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2020 # If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely
2021 # formatted so it can be parsed by a human reader. This is useful if you want to
2022 # understand what is going on. On the other hand, if this tag is set to NO, the
2023 # size of the Perl module output will be much smaller and Perl will parse it
2025 # The default value is: YES.
2026 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2028 PERLMOD_PRETTY = YES
2030 # The names of the make variables in the generated doxyrules.make file are
2031 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
2032 # so different doxyrules.make files included by the same Makefile don't
2033 # overwrite each other's variables.
2034 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2036 PERLMOD_MAKEVAR_PREFIX =
2038 #---------------------------------------------------------------------------
2039 # Configuration options related to the preprocessor
2040 #---------------------------------------------------------------------------
2042 # If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all
2043 # C-preprocessor directives found in the sources and include files.
2044 # The default value is: YES.
2046 ENABLE_PREPROCESSING = YES
2048 # If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names
2049 # in the source code. If set to NO, only conditional compilation will be
2050 # performed. Macro expansion can be done in a controlled way by setting
2051 # EXPAND_ONLY_PREDEF to YES.
2052 # The default value is: NO.
2053 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2055 MACRO_EXPANSION = NO
2057 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
2058 # the macro expansion is limited to the macros specified with the PREDEFINED and
2059 # EXPAND_AS_DEFINED tags.
2060 # The default value is: NO.
2061 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2063 EXPAND_ONLY_PREDEF = NO
2065 # If the SEARCH_INCLUDES tag is set to YES, the include files in the
2066 # INCLUDE_PATH will be searched if a #include is found.
2067 # The default value is: YES.
2068 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2070 SEARCH_INCLUDES = YES
2072 # The INCLUDE_PATH tag can be used to specify one or more directories that
2073 # contain include files that are not input files but should be processed by the
2075 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
2077 INCLUDE_PATH = /usr/include \
2082 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
2083 # patterns (like *.h and *.hpp) to filter out the header-files in the
2084 # directories. If left blank, the patterns specified with FILE_PATTERNS will be
2086 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2088 INCLUDE_FILE_PATTERNS =
2090 # The PREDEFINED tag can be used to specify one or more macro names that are
2091 # defined before the preprocessor is started (similar to the -D option of e.g.
2092 # gcc). The argument of the tag is a list of macros of the form: name or
2093 # name=definition (no spaces). If the definition and the "=" are omitted, "=1"
2094 # is assumed. To prevent a macro definition from being undefined via #undef or
2095 # recursively expanded use the := operator instead of the = operator.
2096 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2100 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
2101 # tag can be used to specify a list of macro names that should be expanded. The
2102 # macro definition that is found in the sources will be used. Use the PREDEFINED
2103 # tag if you want to use a different macro definition that overrules the
2104 # definition found in the source code.
2105 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2109 # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
2110 # remove all references to function-like macros that are alone on a line, have
2111 # an all uppercase name, and do not end with a semicolon. Such function macros
2112 # are typically used for boiler-plate code, and will confuse the parser if not
2114 # The default value is: YES.
2115 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2117 SKIP_FUNCTION_MACROS = YES
2119 #---------------------------------------------------------------------------
2120 # Configuration options related to external references
2121 #---------------------------------------------------------------------------
2123 # The TAGFILES tag can be used to specify one or more tag files. For each tag
2124 # file the location of the external documentation should be added. The format of
2125 # a tag file without this location is as follows:
2126 # TAGFILES = file1 file2 ...
2127 # Adding location for the tag files is done as follows:
2128 # TAGFILES = file1=loc1 "file2 = loc2" ...
2129 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
2130 # section "Linking to external documentation" for more information about the use
2132 # Note: Each tag file must have a unique name (where the name does NOT include
2133 # the path). If a tag file is not located in the directory in which doxygen is
2134 # run, you must also specify the path to the tagfile here.
2138 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2139 # tag file that is based on the input files it reads. See section "Linking to
2140 # external documentation" for more information about the usage of tag files.
2144 # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
2145 # the class index. If set to NO, only the inherited external classes will be
2147 # The default value is: NO.
2151 # If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed
2152 # in the modules index. If set to NO, only the current project's groups will be
2154 # The default value is: YES.
2156 EXTERNAL_GROUPS = YES
2158 # If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
2159 # the related pages index. If set to NO, only the current project's pages will
2161 # The default value is: YES.
2163 EXTERNAL_PAGES = YES
2165 # The PERL_PATH should be the absolute path and name of the perl script
2166 # interpreter (i.e. the result of 'which perl').
2167 # The default file (with absolute path) is: /usr/bin/perl.
2169 PERL_PATH = /usr/bin/perl
2171 #---------------------------------------------------------------------------
2172 # Configuration options related to the dot tool
2173 #---------------------------------------------------------------------------
2175 # If the CLASS_DIAGRAMS tag is set to YES, doxygen will generate a class diagram
2176 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2177 # NO turns the diagrams off. Note that this option also works with HAVE_DOT
2178 # disabled, but it is recommended to install and use dot, since it yields more
2180 # The default value is: YES.
2184 # You can define message sequence charts within doxygen comments using the \msc
2185 # command. Doxygen will then run the mscgen tool (see:
2186 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2187 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
2188 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2189 # default search path.
2193 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2194 # then run dia to produce the diagram and insert it in the documentation. The
2195 # DIA_PATH tag allows you to specify the directory where the dia binary resides.
2196 # If left empty dia is assumed to be found in the default search path.
2200 # If set to YES the inheritance and collaboration graphs will hide inheritance
2201 # and usage relations if the target is undocumented or is not a class.
2202 # The default value is: YES.
2204 HIDE_UNDOC_RELATIONS = YES
2206 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
2207 # available from the path. This tool is part of Graphviz (see:
2208 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2209 # Bell Labs. The other options in this section have no effect if this option is
2211 # The default value is: NO.
2215 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
2216 # to run in parallel. When set to 0 doxygen will base this on the number of
2217 # processors available in the system. You can set it explicitly to a value
2218 # larger than 0 to get control over the balance between CPU load and processing
2220 # Minimum value: 0, maximum value: 32, default value: 0.
2221 # This tag requires that the tag HAVE_DOT is set to YES.
2225 # When you want a differently looking font in the dot files that doxygen
2226 # generates you can specify the font name using DOT_FONTNAME. You need to make
2227 # sure dot is able to find the font, which can be done by putting it in a
2228 # standard location or by setting the DOTFONTPATH environment variable or by
2229 # setting DOT_FONTPATH to the directory containing the font.
2230 # The default value is: Helvetica.
2231 # This tag requires that the tag HAVE_DOT is set to YES.
2233 DOT_FONTNAME = Helvetica
2235 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2237 # Minimum value: 4, maximum value: 24, default value: 10.
2238 # This tag requires that the tag HAVE_DOT is set to YES.
2242 # By default doxygen will tell dot to use the default font as specified with
2243 # DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
2244 # the path where dot can find it using this tag.
2245 # This tag requires that the tag HAVE_DOT is set to YES.
2249 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2250 # each documented class showing the direct and indirect inheritance relations.
2251 # Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
2252 # The default value is: YES.
2253 # This tag requires that the tag HAVE_DOT is set to YES.
2257 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
2258 # graph for each documented class showing the direct and indirect implementation
2259 # dependencies (inheritance, containment, and class references variables) of the
2260 # class with other documented classes.
2261 # The default value is: YES.
2262 # This tag requires that the tag HAVE_DOT is set to YES.
2264 COLLABORATION_GRAPH = YES
2266 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2267 # groups, showing the direct groups dependencies.
2268 # The default value is: YES.
2269 # This tag requires that the tag HAVE_DOT is set to YES.
2273 # If the UML_LOOK tag is set to YES, doxygen will generate inheritance and
2274 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2276 # The default value is: NO.
2277 # This tag requires that the tag HAVE_DOT is set to YES.
2281 # If the UML_LOOK tag is enabled, the fields and methods are shown inside the
2282 # class node. If there are many fields or methods and many nodes the graph may
2283 # become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
2284 # number of items for each type to make the size more manageable. Set this to 0
2285 # for no limit. Note that the threshold may be exceeded by 50% before the limit
2286 # is enforced. So when you set the threshold to 10, up to 15 fields may appear,
2287 # but if the number exceeds 15, the total amount of fields shown is limited to
2289 # Minimum value: 0, maximum value: 100, default value: 10.
2290 # This tag requires that the tag HAVE_DOT is set to YES.
2292 UML_LIMIT_NUM_FIELDS = 10
2294 # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
2295 # collaboration graphs will show the relations between templates and their
2297 # The default value is: NO.
2298 # This tag requires that the tag HAVE_DOT is set to YES.
2300 TEMPLATE_RELATIONS = NO
2302 # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
2303 # YES then doxygen will generate a graph for each documented file showing the
2304 # direct and indirect include dependencies of the file with other documented
2306 # The default value is: YES.
2307 # This tag requires that the tag HAVE_DOT is set to YES.
2311 # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
2312 # set to YES then doxygen will generate a graph for each documented file showing
2313 # the direct and indirect include dependencies of the file with other documented
2315 # The default value is: YES.
2316 # This tag requires that the tag HAVE_DOT is set to YES.
2318 INCLUDED_BY_GRAPH = YES
2320 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
2321 # dependency graph for every global function or class method.
2323 # Note that enabling this option will significantly increase the time of a run.
2324 # So in most cases it will be better to enable call graphs for selected
2325 # functions only using the \callgraph command. Disabling a call graph can be
2326 # accomplished by means of the command \hidecallgraph.
2327 # The default value is: NO.
2328 # This tag requires that the tag HAVE_DOT is set to YES.
2332 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
2333 # dependency graph for every global function or class method.
2335 # Note that enabling this option will significantly increase the time of a run.
2336 # So in most cases it will be better to enable caller graphs for selected
2337 # functions only using the \callergraph command. Disabling a caller graph can be
2338 # accomplished by means of the command \hidecallergraph.
2339 # The default value is: NO.
2340 # This tag requires that the tag HAVE_DOT is set to YES.
2344 # If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
2345 # hierarchy of all classes instead of a textual one.
2346 # The default value is: YES.
2347 # This tag requires that the tag HAVE_DOT is set to YES.
2349 GRAPHICAL_HIERARCHY = YES
2351 # If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
2352 # dependencies a directory has on other directories in a graphical way. The
2353 # dependency relations are determined by the #include relations between the
2354 # files in the directories.
2355 # The default value is: YES.
2356 # This tag requires that the tag HAVE_DOT is set to YES.
2358 DIRECTORY_GRAPH = YES
2360 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
2361 # generated by dot. For an explanation of the image formats see the section
2362 # output formats in the documentation of the dot tool (Graphviz (see:
2363 # http://www.graphviz.org/)).
2364 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2365 # to make the SVG files visible in IE 9+ (other browsers do not have this
2367 # Possible values are: png, jpg, gif, svg, png:gd, png:gd:gd, png:cairo,
2368 # png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and
2369 # png:gdiplus:gdiplus.
2370 # The default value is: png.
2371 # This tag requires that the tag HAVE_DOT is set to YES.
2373 DOT_IMAGE_FORMAT = png
2375 # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
2376 # enable generation of interactive SVG images that allow zooming and panning.
2378 # Note that this requires a modern browser other than Internet Explorer. Tested
2379 # and working are Firefox, Chrome, Safari, and Opera.
2380 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2381 # the SVG files visible. Older versions of IE do not have SVG support.
2382 # The default value is: NO.
2383 # This tag requires that the tag HAVE_DOT is set to YES.
2385 INTERACTIVE_SVG = NO
2387 # The DOT_PATH tag can be used to specify the path where the dot tool can be
2388 # found. If left blank, it is assumed the dot tool can be found in the path.
2389 # This tag requires that the tag HAVE_DOT is set to YES.
2393 # The DOTFILE_DIRS tag can be used to specify one or more directories that
2394 # contain dot files that are included in the documentation (see the \dotfile
2396 # This tag requires that the tag HAVE_DOT is set to YES.
2400 # The MSCFILE_DIRS tag can be used to specify one or more directories that
2401 # contain msc files that are included in the documentation (see the \mscfile
2406 # The DIAFILE_DIRS tag can be used to specify one or more directories that
2407 # contain dia files that are included in the documentation (see the \diafile
2412 # When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
2413 # path where java can find the plantuml.jar file. If left blank, it is assumed
2414 # PlantUML is not used or called during a preprocessing step. Doxygen will
2415 # generate a warning when it encounters a \startuml command in this case and
2416 # will not generate output for the diagram.
2420 # When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
2421 # configuration file for plantuml.
2425 # When using plantuml, the specified paths are searched for files specified by
2426 # the !include statement in a plantuml block.
2428 PLANTUML_INCLUDE_PATH =
2430 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2431 # that will be shown in the graph. If the number of nodes in a graph becomes
2432 # larger than this value, doxygen will truncate the graph, which is visualized
2433 # by representing a node as a red box. Note that doxygen if the number of direct
2434 # children of the root node in a graph is already larger than
2435 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
2436 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2437 # Minimum value: 0, maximum value: 10000, default value: 50.
2438 # This tag requires that the tag HAVE_DOT is set to YES.
2440 DOT_GRAPH_MAX_NODES = 50
2442 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
2443 # generated by dot. A depth value of 3 means that only nodes reachable from the
2444 # root by following a path via at most 3 edges will be shown. Nodes that lay
2445 # further from the root node will be omitted. Note that setting this option to 1
2446 # or 2 may greatly reduce the computation time needed for large code bases. Also
2447 # note that the size of a graph can be further restricted by
2448 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
2449 # Minimum value: 0, maximum value: 1000, default value: 0.
2450 # This tag requires that the tag HAVE_DOT is set to YES.
2452 MAX_DOT_GRAPH_DEPTH = 0
2454 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
2455 # background. This is disabled by default, because dot on Windows does not seem
2456 # to support this out of the box.
2458 # Warning: Depending on the platform used, enabling this option may lead to
2459 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2461 # The default value is: NO.
2462 # This tag requires that the tag HAVE_DOT is set to YES.
2464 DOT_TRANSPARENT = NO
2466 # Set the DOT_MULTI_TARGETS tag to YES to allow dot to generate multiple output
2467 # files in one run (i.e. multiple -o and -T options on the command line). This
2468 # makes dot run faster, but since only newer versions of dot (>1.8.10) support
2469 # this, this feature is disabled by default.
2470 # The default value is: NO.
2471 # This tag requires that the tag HAVE_DOT is set to YES.
2473 DOT_MULTI_TARGETS = NO
2475 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
2476 # explaining the meaning of the various boxes and arrows in the dot generated
2478 # The default value is: YES.
2479 # This tag requires that the tag HAVE_DOT is set to YES.
2481 GENERATE_LEGEND = YES
2483 # If the DOT_CLEANUP tag is set to YES, doxygen will remove the intermediate dot
2484 # files that are used to generate the various graphs.
2485 # The default value is: YES.
2486 # This tag requires that the tag HAVE_DOT is set to YES.