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 config file
21 # that follow. The default is UTF-8 which is also the encoding used for all text
22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24 # 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 = "HomeScreenBinding"
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.
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 = ./doc/api-ref
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 # If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
97 # descriptions after the members that are listed in the file and class
98 # documentation (similar to Javadoc). Set to NO to disable this.
99 # The default value is: YES.
101 BRIEF_MEMBER_DESC = YES
103 # If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief
104 # description of a member or function before the detailed description
106 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
107 # brief descriptions will be completely suppressed.
108 # The default value is: YES.
112 # This tag implements a quasi-intelligent brief description abbreviator that is
113 # used to form the text in various listings. Each string in this list, if found
114 # as the leading text of the brief description, will be stripped from the text
115 # and the result, after processing the whole list, is used as the annotated
116 # text. Otherwise, the brief description is used as-is. If left blank, the
117 # following values are used ($name is automatically replaced with the name of
118 # the entity):The $name class, The $name widget, The $name file, is, provides,
119 # specifies, contains, represents, a, an and the.
121 ABBREVIATE_BRIEF = "The $name class" \
133 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
134 # doxygen will generate a detailed section even if there is only a brief
136 # The default value is: NO.
138 ALWAYS_DETAILED_SEC = NO
140 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
141 # inherited members of a class in the documentation of that class as if those
142 # members were ordinary class members. Constructors, destructors and assignment
143 # operators of the base classes will not be shown.
144 # The default value is: NO.
146 INLINE_INHERITED_MEMB = NO
148 # If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path
149 # before files name in the file list and in the header files. If set to NO the
150 # shortest path that makes the file name unique will be used
151 # The default value is: YES.
153 FULL_PATH_NAMES = YES
155 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
156 # Stripping is only done if one of the specified strings matches the left-hand
157 # part of the path. The tag can be used to show relative paths in the file list.
158 # If left blank the directory from which doxygen is run is used as the path to
161 # Note that you can specify absolute paths here, but also relative paths, which
162 # will be relative from the directory where doxygen is started.
163 # This tag requires that the tag FULL_PATH_NAMES is set to YES.
167 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
168 # path mentioned in the documentation of a class, which tells the reader which
169 # header file to include in order to use a class. If left blank only the name of
170 # the header file containing the class definition is used. Otherwise one should
171 # specify the list of include paths that are normally passed to the compiler
174 STRIP_FROM_INC_PATH =
176 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
177 # less readable) file names. This can be useful is your file systems doesn't
178 # support long names like on DOS, Mac, or CD-ROM.
179 # The default value is: NO.
183 # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
184 # first line (until the first dot) of a Javadoc-style comment as the brief
185 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
186 # style comments (thus requiring an explicit @brief command for a brief
188 # The default value is: NO.
190 JAVADOC_AUTOBRIEF = NO
192 # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
193 # line (until the first dot) of a Qt-style comment as the brief description. If
194 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
195 # requiring an explicit \brief command for a brief description.)
196 # The default value is: NO.
200 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
201 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
202 # a brief description. This used to be the default behavior. The new default is
203 # to treat a multi-line C++ comment block as a detailed description. Set this
204 # tag to YES if you prefer the old behavior instead.
206 # Note that setting this tag to YES also means that rational rose comments are
207 # not recognized any more.
208 # The default value is: NO.
210 MULTILINE_CPP_IS_BRIEF = NO
212 # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
213 # documentation from any documented member that it re-implements.
214 # The default value is: YES.
218 # If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
219 # page for each member. If set to NO, the documentation of a member will be part
220 # of the file/class/namespace that contains it.
221 # The default value is: NO.
223 SEPARATE_MEMBER_PAGES = NO
225 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
226 # uses this value to replace tabs by spaces in code fragments.
227 # Minimum value: 1, maximum value: 16, default value: 4.
231 # This tag can be used to specify a number of aliases that act as commands in
232 # the documentation. An alias has the form:
235 # "sideeffect=@par Side Effects:\n"
236 # will allow you to put the command \sideeffect (or @sideeffect) in the
237 # documentation, which will result in a user-defined paragraph with heading
238 # "Side Effects:". You can put \n's in the value part of an alias to insert
243 # This tag can be used to specify a number of word-keyword mappings (TCL only).
244 # A mapping has the form "name=value". For example adding "class=itcl::class"
245 # will allow you to use the command class in the itcl::class meaning.
249 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
250 # only. Doxygen will then generate output that is more tailored for C. For
251 # instance, some of the names that are used will be different. The list of all
252 # members will be omitted, etc.
253 # The default value is: NO.
255 OPTIMIZE_OUTPUT_FOR_C = NO
257 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
258 # Python sources only. Doxygen will then generate output that is more tailored
259 # for that language. For instance, namespaces will be presented as packages,
260 # qualified scopes will look different, etc.
261 # The default value is: NO.
263 OPTIMIZE_OUTPUT_JAVA = NO
265 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
266 # sources. Doxygen will then generate output that is tailored for Fortran.
267 # The default value is: NO.
269 OPTIMIZE_FOR_FORTRAN = NO
271 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
272 # sources. Doxygen will then generate output that is tailored for VHDL.
273 # The default value is: NO.
275 OPTIMIZE_OUTPUT_VHDL = NO
277 # Doxygen selects the parser to use depending on the extension of the files it
278 # parses. With this tag you can assign which parser to use for a given
279 # extension. Doxygen has a built-in mapping, but you can override or extend it
280 # using this tag. The format is ext=language, where ext is a file extension, and
281 # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
282 # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
283 # FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:
284 # Fortran. In the later case the parser tries to guess whether the code is fixed
285 # or free formatted code, this is the default for Fortran type files), VHDL. For
286 # instance to make doxygen treat .inc files as Fortran files (default is PHP),
287 # and .f files as C (default is Fortran), use: inc=Fortran f=C.
289 # Note: For files without extension you can use no_extension as a placeholder.
291 # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
292 # the files are not read by doxygen.
296 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
297 # according to the Markdown format, which allows for more readable
298 # documentation. See http://daringfireball.net/projects/markdown/ for details.
299 # The output of markdown processing is further processed by doxygen, so you can
300 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
301 # case of backward compatibilities issues.
302 # The default value is: YES.
304 MARKDOWN_SUPPORT = YES
306 # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
307 # to that level are automatically included in the table of contents, even if
308 # they do not have an id attribute.
309 # Note: This feature currently applies only to Markdown headings.
310 # Minimum value: 0, maximum value: 99, default value: 0.
311 # This tag requires that the tag MARKDOWN_SUPPORT is set to YES.
313 TOC_INCLUDE_HEADINGS = 0
315 # When enabled doxygen tries to link words that correspond to documented
316 # classes, or namespaces to their corresponding documentation. Such a link can
317 # be prevented in individual cases by putting a % sign in front of the word or
318 # globally by setting AUTOLINK_SUPPORT to NO.
319 # The default value is: YES.
321 AUTOLINK_SUPPORT = YES
323 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
324 # to include (a tag file for) the STL sources as input, then you should set this
325 # tag to YES in order to let doxygen match functions declarations and
326 # definitions whose arguments contain STL classes (e.g. func(std::string);
327 # versus func(std::string) {}). This also make the inheritance and collaboration
328 # diagrams that involve STL classes more complete and accurate.
329 # The default value is: NO.
331 BUILTIN_STL_SUPPORT = NO
333 # If you use Microsoft's C++/CLI language, you should set this option to YES to
334 # enable parsing support.
335 # The default value is: NO.
339 # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
340 # http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen
341 # will parse them like normal C++ but will assume all classes use public instead
342 # of private inheritance when no explicit protection keyword is present.
343 # The default value is: NO.
347 # For Microsoft's IDL there are propget and propput attributes to indicate
348 # getter and setter methods for a property. Setting this option to YES will make
349 # doxygen to replace the get and set methods by a property in the documentation.
350 # This will only work if the methods are indeed getting or setting a simple
351 # type. If this is not the case, or you want to show the methods anyway, you
352 # should set this option to NO.
353 # The default value is: YES.
355 IDL_PROPERTY_SUPPORT = YES
357 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
358 # tag is set to YES then doxygen will reuse the documentation of the first
359 # member in the group (if any) for the other members of the group. By default
360 # all members of a group must be documented explicitly.
361 # The default value is: NO.
363 DISTRIBUTE_GROUP_DOC = NO
365 # If one adds a struct or class to a group and this option is enabled, then also
366 # any nested class or struct is added to the same group. By default this option
367 # is disabled and one has to add nested compounds explicitly via \ingroup.
368 # The default value is: NO.
370 GROUP_NESTED_COMPOUNDS = NO
372 # Set the SUBGROUPING tag to YES to allow class member groups of the same type
373 # (for instance a group of public functions) to be put as a subgroup of that
374 # type (e.g. under the Public Functions section). Set it to NO to prevent
375 # subgrouping. Alternatively, this can be done per class using the
376 # \nosubgrouping command.
377 # The default value is: YES.
381 # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
382 # are shown inside the group in which they are included (e.g. using \ingroup)
383 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
386 # Note that this feature does not work in combination with
387 # SEPARATE_MEMBER_PAGES.
388 # The default value is: NO.
390 INLINE_GROUPED_CLASSES = NO
392 # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
393 # with only public data fields or simple typedef fields will be shown inline in
394 # the documentation of the scope in which they are defined (i.e. file,
395 # namespace, or group documentation), provided this scope is documented. If set
396 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
397 # Man pages) or section (for LaTeX and RTF).
398 # The default value is: NO.
400 INLINE_SIMPLE_STRUCTS = NO
402 # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
403 # enum is documented as struct, union, or enum with the name of the typedef. So
404 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
405 # with name TypeT. When disabled the typedef will appear as a member of a file,
406 # namespace, or class. And the struct will be named TypeS. This can typically be
407 # useful for C code in case the coding convention dictates that all compound
408 # types are typedef'ed and only the typedef is referenced, never the tag name.
409 # The default value is: NO.
411 TYPEDEF_HIDES_STRUCT = NO
413 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
414 # cache is used to resolve symbols given their name and scope. Since this can be
415 # an expensive process and often the same symbol appears multiple times in the
416 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
417 # doxygen will become slower. If the cache is too large, memory is wasted. The
418 # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
419 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
420 # symbols. At the end of a run doxygen will report the cache usage and suggest
421 # the optimal cache size from a speed point of view.
422 # Minimum value: 0, maximum value: 9, default value: 0.
424 LOOKUP_CACHE_SIZE = 0
426 #---------------------------------------------------------------------------
427 # Build related configuration options
428 #---------------------------------------------------------------------------
430 # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
431 # documentation are documented, even if no documentation was available. Private
432 # class members and static file members will be hidden unless the
433 # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
434 # Note: This will also disable the warnings about undocumented members that are
435 # normally produced when WARNINGS is set to YES.
436 # The default value is: NO.
440 # If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
441 # be included in the documentation.
442 # The default value is: NO.
446 # If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal
447 # scope will be included in the documentation.
448 # The default value is: NO.
452 # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
453 # included in the documentation.
454 # The default value is: NO.
458 # If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined
459 # locally in source files will be included in the documentation. If set to NO,
460 # only classes defined in header files are included. Does not have any effect
462 # The default value is: YES.
464 EXTRACT_LOCAL_CLASSES = YES
466 # This flag is only useful for Objective-C code. If set to YES, local methods,
467 # which are defined in the implementation section but not in the interface are
468 # included in the documentation. If set to NO, only methods in the interface are
470 # The default value is: NO.
472 EXTRACT_LOCAL_METHODS = NO
474 # If this flag is set to YES, the members of anonymous namespaces will be
475 # extracted and appear in the documentation as a namespace called
476 # 'anonymous_namespace{file}', where file will be replaced with the base name of
477 # the file that contains the anonymous namespace. By default anonymous namespace
479 # The default value is: NO.
481 EXTRACT_ANON_NSPACES = NO
483 # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
484 # undocumented members inside documented classes or files. If set to NO these
485 # members will be included in the various overviews, but no documentation
486 # section is generated. This option has no effect if EXTRACT_ALL is enabled.
487 # The default value is: NO.
489 HIDE_UNDOC_MEMBERS = NO
491 # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
492 # undocumented classes that are normally visible in the class hierarchy. If set
493 # to NO, these classes will be included in the various overviews. This option
494 # has no effect if EXTRACT_ALL is enabled.
495 # The default value is: NO.
497 HIDE_UNDOC_CLASSES = NO
499 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
500 # (class|struct|union) declarations. If set to NO, these declarations will be
501 # included in the documentation.
502 # The default value is: NO.
504 HIDE_FRIEND_COMPOUNDS = NO
506 # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
507 # documentation blocks found inside the body of a function. If set to NO, these
508 # blocks will be appended to the function's detailed documentation block.
509 # The default value is: NO.
511 HIDE_IN_BODY_DOCS = NO
513 # The INTERNAL_DOCS tag determines if documentation that is typed after a
514 # \internal command is included. If the tag is set to NO then the documentation
515 # will be excluded. Set it to YES to include the internal documentation.
516 # The default value is: NO.
520 # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
521 # names in lower-case letters. If set to YES, upper-case letters are also
522 # allowed. This is useful if you have classes or files whose names only differ
523 # in case and if your file system supports case sensitive file names. Windows
524 # and Mac users are advised to set this option to NO.
525 # The default value is: system dependent.
527 CASE_SENSE_NAMES = NO
529 # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
530 # their full class and namespace scopes in the documentation. If set to YES, the
531 # scope will be hidden.
532 # The default value is: NO.
534 HIDE_SCOPE_NAMES = NO
536 # If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will
537 # append additional text to a page's title, such as Class Reference. If set to
538 # YES the compound reference will be hidden.
539 # The default value is: NO.
541 HIDE_COMPOUND_REFERENCE= NO
543 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
544 # the files that are included by a file in the documentation of that file.
545 # The default value is: YES.
547 SHOW_INCLUDE_FILES = YES
549 # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
550 # grouped member an include statement to the documentation, telling the reader
551 # which file to include in order to use the member.
552 # The default value is: NO.
554 SHOW_GROUPED_MEMB_INC = NO
556 # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
557 # files with double quotes in the documentation rather than with sharp brackets.
558 # The default value is: NO.
560 FORCE_LOCAL_INCLUDES = NO
562 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
563 # documentation for inline members.
564 # The default value is: YES.
568 # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
569 # (detailed) documentation of file and class members alphabetically by member
570 # name. If set to NO, the members will appear in declaration order.
571 # The default value is: YES.
573 SORT_MEMBER_DOCS = YES
575 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
576 # descriptions of file, namespace and class members alphabetically by member
577 # name. If set to NO, the members will appear in declaration order. Note that
578 # this will also influence the order of the classes in the class list.
579 # The default value is: NO.
583 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
584 # (brief and detailed) documentation of class members so that constructors and
585 # destructors are listed first. If set to NO the constructors will appear in the
586 # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
587 # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
588 # member documentation.
589 # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
590 # detailed member documentation.
591 # The default value is: NO.
593 SORT_MEMBERS_CTORS_1ST = NO
595 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
596 # of group names into alphabetical order. If set to NO the group names will
597 # appear in their defined order.
598 # The default value is: NO.
600 SORT_GROUP_NAMES = NO
602 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
603 # fully-qualified names, including namespaces. If set to NO, the class list will
604 # be sorted only by class name, not including the namespace part.
605 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
606 # Note: This option applies only to the class list, not to the alphabetical
608 # The default value is: NO.
610 SORT_BY_SCOPE_NAME = NO
612 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
613 # type resolution of all parameters of a function it will reject a match between
614 # the prototype and the implementation of a member function even if there is
615 # only one candidate or it is obvious which candidate to choose by doing a
616 # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
617 # accept a match between prototype and implementation in such cases.
618 # The default value is: NO.
620 STRICT_PROTO_MATCHING = NO
622 # The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo
623 # list. This list is created by putting \todo commands in the documentation.
624 # The default value is: YES.
626 GENERATE_TODOLIST = YES
628 # The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test
629 # list. This list is created by putting \test commands in the documentation.
630 # The default value is: YES.
632 GENERATE_TESTLIST = YES
634 # The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug
635 # list. This list is created by putting \bug commands in the documentation.
636 # The default value is: YES.
638 GENERATE_BUGLIST = YES
640 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO)
641 # the deprecated list. This list is created by putting \deprecated commands in
643 # The default value is: YES.
645 GENERATE_DEPRECATEDLIST= YES
647 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
648 # sections, marked by \if <section_label> ... \endif and \cond <section_label>
649 # ... \endcond blocks.
653 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
654 # initial value of a variable or macro / define can have for it to appear in the
655 # documentation. If the initializer consists of more lines than specified here
656 # it will be hidden. Use a value of 0 to hide initializers completely. The
657 # appearance of the value of individual variables and macros / defines can be
658 # controlled using \showinitializer or \hideinitializer command in the
659 # documentation regardless of this setting.
660 # Minimum value: 0, maximum value: 10000, default value: 30.
662 MAX_INITIALIZER_LINES = 30
664 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
665 # the bottom of the documentation of classes and structs. If set to YES, the
666 # list will mention the files that were used to generate the documentation.
667 # The default value is: YES.
669 SHOW_USED_FILES = YES
671 # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
672 # will remove the Files entry from the Quick Index and from the Folder Tree View
674 # The default value is: YES.
678 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
679 # page. This will remove the Namespaces entry from the Quick Index and from the
680 # Folder Tree View (if specified).
681 # The default value is: YES.
683 SHOW_NAMESPACES = YES
685 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
686 # doxygen should invoke to get the current version for each file (typically from
687 # the version control system). Doxygen will invoke the program by executing (via
688 # popen()) the command command input-file, where command is the value of the
689 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
690 # by doxygen. Whatever the program writes to standard output is used as the file
691 # version. For an example see the documentation.
693 FILE_VERSION_FILTER =
695 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
696 # by doxygen. The layout file controls the global structure of the generated
697 # output files in an output format independent way. To create the layout file
698 # that represents doxygen's defaults, run doxygen with the -l option. You can
699 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
700 # will be used as the name of the layout file.
702 # Note that if you run doxygen from a directory containing a file called
703 # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
708 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
709 # the reference definitions. This must be a list of .bib files. The .bib
710 # extension is automatically appended if omitted. This requires the bibtex tool
711 # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
712 # For LaTeX the style of the bibliography can be controlled using
713 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
714 # search path. See also \cite for info how to create references.
718 #---------------------------------------------------------------------------
719 # Configuration options related to warning and progress messages
720 #---------------------------------------------------------------------------
722 # The QUIET tag can be used to turn on/off the messages that are generated to
723 # standard output by doxygen. If QUIET is set to YES this implies that the
725 # The default value is: NO.
729 # The WARNINGS tag can be used to turn on/off the warning messages that are
730 # generated to standard error (stderr) by doxygen. If WARNINGS is set to YES
731 # this implies that the warnings are on.
733 # Tip: Turn warnings on while writing the documentation.
734 # The default value is: YES.
738 # If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate
739 # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
740 # will automatically be disabled.
741 # The default value is: YES.
743 WARN_IF_UNDOCUMENTED = YES
745 # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
746 # potential errors in the documentation, such as not documenting some parameters
747 # in a documented function, or documenting parameters that don't exist or using
748 # markup commands wrongly.
749 # The default value is: YES.
751 WARN_IF_DOC_ERROR = YES
753 # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
754 # are documented, but have no documentation for their parameters or return
755 # value. If set to NO, doxygen will only warn about wrong or incomplete
756 # parameter documentation, but not about the absence of documentation.
757 # The default value is: NO.
759 WARN_NO_PARAMDOC = NO
761 # If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when
762 # a warning is encountered.
763 # The default value is: NO.
767 # The WARN_FORMAT tag determines the format of the warning messages that doxygen
768 # can produce. The string should contain the $file, $line, and $text tags, which
769 # will be replaced by the file and line number from which the warning originated
770 # and the warning text. Optionally the format may contain $version, which will
771 # be replaced by the version of the file (if it could be obtained via
772 # FILE_VERSION_FILTER)
773 # The default value is: $file:$line: $text.
775 WARN_FORMAT = "$file:$line: $text"
777 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
778 # messages should be written. If left blank the output is written to standard
783 #---------------------------------------------------------------------------
784 # Configuration options related to the input files
785 #---------------------------------------------------------------------------
787 # The INPUT tag is used to specify the files and/or directories that contain
788 # documented source files. You may enter file names like myfile.cpp or
789 # directories like /usr/src/myproject. Separate the files or directories with
790 # spaces. See also FILE_PATTERNS and EXTENSION_MAPPING
791 # Note: If this tag is empty the current directory is searched.
793 INPUT = ./include ./libhomescreen ./src
795 # This tag can be used to specify the character encoding of the source files
796 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
797 # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
798 # documentation (see: http://www.gnu.org/software/libiconv) for the list of
799 # possible encodings.
800 # The default value is: UTF-8.
802 INPUT_ENCODING = UTF-8
804 # If the value of the INPUT tag contains directories, you can use the
805 # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
806 # *.h) to filter out the source-files in the directories.
808 # Note that for custom extensions or not directly supported extensions you also
809 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
812 # If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp,
813 # *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h,
814 # *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc,
815 # *.m, *.markdown, *.md, *.mm, *.dox, *.py, *.pyw, *.f90, *.f95, *.f03, *.f08,
816 # *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf and *.qsf.
818 FILE_PATTERNS = *.c \
863 # The RECURSIVE tag can be used to specify whether or not subdirectories should
864 # be searched for input files as well.
865 # The default value is: NO.
869 # The EXCLUDE tag can be used to specify files and/or directories that should be
870 # excluded from the INPUT source files. This way you can easily exclude a
871 # subdirectory from a directory tree whose root is specified with the INPUT tag.
873 # Note that relative paths are relative to the directory from which doxygen is
878 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
879 # directories that are symbolic links (a Unix file system feature) are excluded
881 # The default value is: NO.
883 EXCLUDE_SYMLINKS = NO
885 # If the value of the INPUT tag contains directories, you can use the
886 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
887 # certain files from those directories.
889 # Note that the wildcards are matched against the file with absolute path, so to
890 # exclude all test directories for example use the pattern */test/*
894 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
895 # (namespaces, classes, functions, etc.) that should be excluded from the
896 # output. The symbol name can be a fully qualified name, a word, or if the
897 # wildcard * is used, a substring. Examples: ANamespace, AClass,
898 # AClass::ANamespace, ANamespace::*Test
900 # Note that the wildcards are matched against the file with absolute path, so to
901 # exclude all test directories use the pattern */test/*
905 # The EXAMPLE_PATH tag can be used to specify one or more files or directories
906 # that contain example code fragments that are included (see the \include
911 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
912 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
913 # *.h) to filter out the source-files in the directories. If left blank all
914 # files are included.
918 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
919 # searched for input files to be used with the \include or \dontinclude commands
920 # irrespective of the value of the RECURSIVE tag.
921 # The default value is: NO.
923 EXAMPLE_RECURSIVE = NO
925 # The IMAGE_PATH tag can be used to specify one or more files or directories
926 # that contain images that are to be included in the documentation (see the
931 # The INPUT_FILTER tag can be used to specify a program that doxygen should
932 # invoke to filter for each input file. Doxygen will invoke the filter program
933 # by executing (via popen()) the command:
935 # <filter> <input-file>
937 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
938 # name of an input file. Doxygen will then use the output that the filter
939 # program writes to standard output. If FILTER_PATTERNS is specified, this tag
942 # Note that the filter must not add or remove lines; it is applied before the
943 # code is scanned, but not when the output code is generated. If lines are added
944 # or removed, the anchors will not be placed correctly.
946 # Note that for custom extensions or not directly supported extensions you also
947 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
948 # properly processed by doxygen.
952 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
953 # basis. Doxygen will compare the file name with each pattern and apply the
954 # filter if there is a match. The filters are a list of the form: pattern=filter
955 # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
956 # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
957 # patterns match the file name, INPUT_FILTER is applied.
959 # Note that for custom extensions or not directly supported extensions you also
960 # need to set EXTENSION_MAPPING for the extension otherwise the files are not
961 # properly processed by doxygen.
965 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
966 # INPUT_FILTER) will also be used to filter the input files that are used for
967 # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
968 # The default value is: NO.
970 FILTER_SOURCE_FILES = NO
972 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
973 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
974 # it is also possible to disable source filtering for a specific pattern using
975 # *.ext= (so without naming a filter).
976 # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
978 FILTER_SOURCE_PATTERNS =
980 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
981 # is part of the input, its contents will be placed on the main page
982 # (index.html). This can be useful if you have a project on for instance GitHub
983 # and want to reuse the introduction page also for the doxygen output.
985 USE_MDFILE_AS_MAINPAGE =
987 #---------------------------------------------------------------------------
988 # Configuration options related to source browsing
989 #---------------------------------------------------------------------------
991 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
992 # generated. Documented entities will be cross-referenced with these sources.
994 # Note: To get rid of all source code in the generated output, make sure that
995 # also VERBATIM_HEADERS is set to NO.
996 # The default value is: NO.
1000 # Setting the INLINE_SOURCES tag to YES will include the body of functions,
1001 # classes and enums directly into the documentation.
1002 # The default value is: NO.
1004 INLINE_SOURCES = YES
1006 # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
1007 # special comment blocks from generated source code fragments. Normal C, C++ and
1008 # Fortran comments will always remain visible.
1009 # The default value is: YES.
1011 STRIP_CODE_COMMENTS = YES
1013 # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
1014 # function all documented functions referencing it will be listed.
1015 # The default value is: NO.
1017 REFERENCED_BY_RELATION = NO
1019 # If the REFERENCES_RELATION tag is set to YES then for each documented function
1020 # all documented entities called/used by that function will be listed.
1021 # The default value is: NO.
1023 REFERENCES_RELATION = NO
1025 # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
1026 # to YES then the hyperlinks from functions in REFERENCES_RELATION and
1027 # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
1028 # link to the documentation.
1029 # The default value is: YES.
1031 REFERENCES_LINK_SOURCE = YES
1033 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1034 # source code will show a tooltip with additional information such as prototype,
1035 # brief description and links to the definition and documentation. Since this
1036 # will make the HTML file larger and loading of large files a bit slower, you
1037 # can opt to disable this feature.
1038 # The default value is: YES.
1039 # This tag requires that the tag SOURCE_BROWSER is set to YES.
1041 SOURCE_TOOLTIPS = YES
1043 # If the USE_HTAGS tag is set to YES then the references to source code will
1044 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1045 # source browser. The htags tool is part of GNU's global source tagging system
1046 # (see http://www.gnu.org/software/global/global.html). You will need version
1049 # To use it do the following:
1050 # - Install the latest version of global
1051 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
1052 # - Make sure the INPUT points to the root of the source tree
1053 # - Run doxygen as normal
1055 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
1056 # tools must be available from the command line (i.e. in the search path).
1058 # The result: instead of the source browser generated by doxygen, the links to
1059 # source code will now point to the output of htags.
1060 # The default value is: NO.
1061 # This tag requires that the tag SOURCE_BROWSER is set to YES.
1065 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
1066 # verbatim copy of the header file for each class for which an include is
1067 # specified. Set to NO to disable this.
1068 # See also: Section \class.
1069 # The default value is: YES.
1071 VERBATIM_HEADERS = YES
1073 #---------------------------------------------------------------------------
1074 # Configuration options related to the alphabetical class index
1075 #---------------------------------------------------------------------------
1077 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
1078 # compounds will be generated. Enable this if the project contains a lot of
1079 # classes, structs, unions or interfaces.
1080 # The default value is: YES.
1082 ALPHABETICAL_INDEX = YES
1084 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
1085 # which the alphabetical index list will be split.
1086 # Minimum value: 1, maximum value: 20, default value: 5.
1087 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1089 COLS_IN_ALPHA_INDEX = 5
1091 # In case all classes in a project start with a common prefix, all classes will
1092 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1093 # can be used to specify a prefix (or a list of prefixes) that should be ignored
1094 # while generating the index headers.
1095 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1099 #---------------------------------------------------------------------------
1100 # Configuration options related to the HTML output
1101 #---------------------------------------------------------------------------
1103 # If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output
1104 # The default value is: YES.
1108 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1109 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1111 # The default directory is: html.
1112 # This tag requires that the tag GENERATE_HTML is set to YES.
1116 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1117 # generated HTML page (for example: .htm, .php, .asp).
1118 # The default value is: .html.
1119 # This tag requires that the tag GENERATE_HTML is set to YES.
1121 HTML_FILE_EXTENSION = .html
1123 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1124 # each generated HTML page. If the tag is left blank doxygen will generate a
1127 # To get valid HTML the header file that includes any scripts and style sheets
1128 # that doxygen needs, which is dependent on the configuration options used (e.g.
1129 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1130 # default header using
1131 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1133 # and then modify the file new_header.html. See also section "Doxygen usage"
1134 # for information on how to generate the default header that doxygen normally
1136 # Note: The header is subject to change so you typically have to regenerate the
1137 # default header when upgrading to a newer version of doxygen. For a description
1138 # of the possible markers and block names see the documentation.
1139 # This tag requires that the tag GENERATE_HTML is set to YES.
1143 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1144 # generated HTML page. If the tag is left blank doxygen will generate a standard
1145 # footer. See HTML_HEADER for more information on how to generate a default
1146 # footer and what special commands can be used inside the footer. See also
1147 # section "Doxygen usage" for information on how to generate the default footer
1148 # that doxygen normally uses.
1149 # This tag requires that the tag GENERATE_HTML is set to YES.
1153 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1154 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1155 # the HTML output. If left blank doxygen will generate a default style sheet.
1156 # See also section "Doxygen usage" for information on how to generate the style
1157 # sheet that doxygen normally uses.
1158 # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
1159 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1161 # This tag requires that the tag GENERATE_HTML is set to YES.
1165 # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1166 # cascading style sheets that are included after the standard style sheets
1167 # created by doxygen. Using this option one can overrule certain style aspects.
1168 # This is preferred over using HTML_STYLESHEET since it does not replace the
1169 # standard style sheet and is therefore more robust against future updates.
1170 # Doxygen will copy the style sheet files to the output directory.
1171 # Note: The order of the extra style sheet files is of importance (e.g. the last
1172 # style sheet in the list overrules the setting of the previous ones in the
1173 # list). For an example see the documentation.
1174 # This tag requires that the tag GENERATE_HTML is set to YES.
1176 HTML_EXTRA_STYLESHEET =
1178 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1179 # other source files which should be copied to the HTML output directory. Note
1180 # that these files will be copied to the base HTML output directory. Use the
1181 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1182 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1183 # files will be copied as-is; there are no commands or markers available.
1184 # This tag requires that the tag GENERATE_HTML is set to YES.
1188 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1189 # will adjust the colors in the style sheet and background images according to
1190 # this color. Hue is specified as an angle on a colorwheel, see
1191 # http://en.wikipedia.org/wiki/Hue for more information. For instance the value
1192 # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
1193 # purple, and 360 is red again.
1194 # Minimum value: 0, maximum value: 359, default value: 220.
1195 # This tag requires that the tag GENERATE_HTML is set to YES.
1197 HTML_COLORSTYLE_HUE = 220
1199 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
1200 # in the HTML output. For a value of 0 the output will use grayscales only. A
1201 # value of 255 will produce the most vivid colors.
1202 # Minimum value: 0, maximum value: 255, default value: 100.
1203 # This tag requires that the tag GENERATE_HTML is set to YES.
1205 HTML_COLORSTYLE_SAT = 100
1207 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
1208 # luminance component of the colors in the HTML output. Values below 100
1209 # gradually make the output lighter, whereas values above 100 make the output
1210 # darker. The value divided by 100 is the actual gamma applied, so 80 represents
1211 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1213 # Minimum value: 40, maximum value: 240, default value: 80.
1214 # This tag requires that the tag GENERATE_HTML is set to YES.
1216 HTML_COLORSTYLE_GAMMA = 80
1218 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
1219 # page will contain the date and time when the page was generated. Setting this
1220 # to YES can help to show when doxygen was last run and thus if the
1221 # documentation is up to date.
1222 # The default value is: NO.
1223 # This tag requires that the tag GENERATE_HTML is set to YES.
1227 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1228 # documentation will contain sections that can be hidden and shown after the
1230 # The default value is: NO.
1231 # This tag requires that the tag GENERATE_HTML is set to YES.
1233 HTML_DYNAMIC_SECTIONS = NO
1235 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
1236 # shown in the various tree structured indices initially; the user can expand
1237 # and collapse entries dynamically later on. Doxygen will expand the tree to
1238 # such a level that at most the specified number of entries are visible (unless
1239 # a fully collapsed tree already exceeds this amount). So setting the number of
1240 # entries 1 will produce a full collapsed tree by default. 0 is a special value
1241 # representing an infinite number of entries and will result in a full expanded
1243 # Minimum value: 0, maximum value: 9999, default value: 100.
1244 # This tag requires that the tag GENERATE_HTML is set to YES.
1246 HTML_INDEX_NUM_ENTRIES = 100
1248 # If the GENERATE_DOCSET tag is set to YES, additional index files will be
1249 # generated that can be used as input for Apple's Xcode 3 integrated development
1250 # environment (see: http://developer.apple.com/tools/xcode/), introduced with
1251 # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1252 # Makefile in the HTML output directory. Running make will produce the docset in
1253 # that directory and running make install will install the docset in
1254 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1255 # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
1256 # for more information.
1257 # The default value is: NO.
1258 # This tag requires that the tag GENERATE_HTML is set to YES.
1260 GENERATE_DOCSET = NO
1262 # This tag determines the name of the docset feed. A documentation feed provides
1263 # an umbrella under which multiple documentation sets from a single provider
1264 # (such as a company or product suite) can be grouped.
1265 # The default value is: Doxygen generated docs.
1266 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1268 DOCSET_FEEDNAME = "Doxygen generated docs"
1270 # This tag specifies a string that should uniquely identify the documentation
1271 # set bundle. This should be a reverse domain-name style string, e.g.
1272 # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
1273 # The default value is: org.doxygen.Project.
1274 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1276 DOCSET_BUNDLE_ID = org.doxygen.Project
1278 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1279 # the documentation publisher. This should be a reverse domain-name style
1280 # string, e.g. com.mycompany.MyDocSet.documentation.
1281 # The default value is: org.doxygen.Publisher.
1282 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1284 DOCSET_PUBLISHER_ID = org.doxygen.Publisher
1286 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1287 # The default value is: Publisher.
1288 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1290 DOCSET_PUBLISHER_NAME = Publisher
1292 # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1293 # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1294 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1295 # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1298 # The HTML Help Workshop contains a compiler that can convert all HTML output
1299 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1300 # files are now used as the Windows 98 help format, and will replace the old
1301 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1302 # HTML files also contain an index, a table of contents, and you can search for
1303 # words in the documentation. The HTML workshop also contains a viewer for
1304 # compressed HTML files.
1305 # The default value is: NO.
1306 # This tag requires that the tag GENERATE_HTML is set to YES.
1308 GENERATE_HTMLHELP = NO
1310 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1311 # file. You can add a path in front of the file if the result should not be
1312 # written to the html output directory.
1313 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1317 # The HHC_LOCATION tag can be used to specify the location (absolute path
1318 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
1319 # doxygen will try to run the HTML help compiler on the generated index.hhp.
1320 # The file has to be specified with full path.
1321 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1325 # The GENERATE_CHI flag controls if a separate .chi index file is generated
1326 # (YES) or that it should be included in the master .chm file (NO).
1327 # The default value is: NO.
1328 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1332 # The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc)
1333 # and project file content.
1334 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1336 CHM_INDEX_ENCODING =
1338 # The BINARY_TOC flag controls whether a binary table of contents is generated
1339 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1340 # enables the Previous and Next buttons.
1341 # The default value is: NO.
1342 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1346 # The TOC_EXPAND flag can be set to YES to add extra items for group members to
1347 # the table of contents of the HTML help documentation and to the tree view.
1348 # The default value is: NO.
1349 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1353 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1354 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1355 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1356 # (.qch) of the generated HTML documentation.
1357 # The default value is: NO.
1358 # This tag requires that the tag GENERATE_HTML is set to YES.
1362 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
1363 # the file name of the resulting .qch file. The path specified is relative to
1364 # the HTML output folder.
1365 # This tag requires that the tag GENERATE_QHP is set to YES.
1369 # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1370 # Project output. For more information please see Qt Help Project / Namespace
1371 # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1372 # The default value is: org.doxygen.Project.
1373 # This tag requires that the tag GENERATE_QHP is set to YES.
1375 QHP_NAMESPACE = org.doxygen.Project
1377 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
1378 # Help Project output. For more information please see Qt Help Project / Virtual
1379 # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1381 # The default value is: doc.
1382 # This tag requires that the tag GENERATE_QHP is set to YES.
1384 QHP_VIRTUAL_FOLDER = doc
1386 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1387 # filter to add. For more information please see Qt Help Project / Custom
1388 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1390 # This tag requires that the tag GENERATE_QHP is set to YES.
1392 QHP_CUST_FILTER_NAME =
1394 # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1395 # custom filter to add. For more information please see Qt Help Project / Custom
1396 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1398 # This tag requires that the tag GENERATE_QHP is set to YES.
1400 QHP_CUST_FILTER_ATTRS =
1402 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1403 # project's filter section matches. Qt Help Project / Filter Attributes (see:
1404 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1405 # This tag requires that the tag GENERATE_QHP is set to YES.
1407 QHP_SECT_FILTER_ATTRS =
1409 # The QHG_LOCATION tag can be used to specify the location of Qt's
1410 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1411 # generated .qhp file.
1412 # This tag requires that the tag GENERATE_QHP is set to YES.
1416 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1417 # generated, together with the HTML files, they form an Eclipse help plugin. To
1418 # install this plugin and make it available under the help contents menu in
1419 # Eclipse, the contents of the directory containing the HTML and XML files needs
1420 # to be copied into the plugins directory of eclipse. The name of the directory
1421 # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
1422 # After copying Eclipse needs to be restarted before the help appears.
1423 # The default value is: NO.
1424 # This tag requires that the tag GENERATE_HTML is set to YES.
1426 GENERATE_ECLIPSEHELP = NO
1428 # A unique identifier for the Eclipse help plugin. When installing the plugin
1429 # the directory name containing the HTML and XML files should also have this
1430 # name. Each documentation set should have its own identifier.
1431 # The default value is: org.doxygen.Project.
1432 # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
1434 ECLIPSE_DOC_ID = org.doxygen.Project
1436 # If you want full control over the layout of the generated HTML pages it might
1437 # be necessary to disable the index and replace it with your own. The
1438 # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
1439 # of each HTML page. A value of NO enables the index and the value YES disables
1440 # it. Since the tabs in the index contain the same information as the navigation
1441 # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
1442 # The default value is: NO.
1443 # This tag requires that the tag GENERATE_HTML is set to YES.
1447 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1448 # structure should be generated to display hierarchical information. If the tag
1449 # value is set to YES, a side panel will be generated containing a tree-like
1450 # index structure (just like the one that is generated for HTML Help). For this
1451 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
1452 # (i.e. any modern browser). Windows users are probably better off using the
1453 # HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can
1454 # further fine-tune the look of the index. As an example, the default style
1455 # sheet generated by doxygen has an example that shows how to put an image at
1456 # the root of the tree instead of the PROJECT_NAME. Since the tree basically has
1457 # the same information as the tab index, you could consider setting
1458 # DISABLE_INDEX to YES when enabling this option.
1459 # The default value is: NO.
1460 # This tag requires that the tag GENERATE_HTML is set to YES.
1462 GENERATE_TREEVIEW = NO
1464 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
1465 # doxygen will group on one line in the generated HTML documentation.
1467 # Note that a value of 0 will completely suppress the enum values from appearing
1468 # in the overview section.
1469 # Minimum value: 0, maximum value: 20, default value: 4.
1470 # This tag requires that the tag GENERATE_HTML is set to YES.
1472 ENUM_VALUES_PER_LINE = 4
1474 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
1475 # to set the initial width (in pixels) of the frame in which the tree is shown.
1476 # Minimum value: 0, maximum value: 1500, default value: 250.
1477 # This tag requires that the tag GENERATE_HTML is set to YES.
1479 TREEVIEW_WIDTH = 250
1481 # If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to
1482 # external symbols imported via tag files in a separate window.
1483 # The default value is: NO.
1484 # This tag requires that the tag GENERATE_HTML is set to YES.
1486 EXT_LINKS_IN_WINDOW = NO
1488 # Use this tag to change the font size of LaTeX formulas included as images in
1489 # the HTML documentation. When you change the font size after a successful
1490 # doxygen run you need to manually remove any form_*.png images from the HTML
1491 # output directory to force them to be regenerated.
1492 # Minimum value: 8, maximum value: 50, default value: 10.
1493 # This tag requires that the tag GENERATE_HTML is set to YES.
1495 FORMULA_FONTSIZE = 10
1497 # Use the FORMULA_TRANPARENT tag to determine whether or not the images
1498 # generated for formulas are transparent PNGs. Transparent PNGs are not
1499 # supported properly for IE 6.0, but are supported on all modern browsers.
1501 # Note that when changing this option you need to delete any form_*.png files in
1502 # the HTML output directory before the changes have effect.
1503 # The default value is: YES.
1504 # This tag requires that the tag GENERATE_HTML is set to YES.
1506 FORMULA_TRANSPARENT = YES
1508 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1509 # http://www.mathjax.org) which uses client side Javascript for the rendering
1510 # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
1511 # installed or if you want to formulas look prettier in the HTML output. When
1512 # enabled you may also need to install MathJax separately and configure the path
1513 # to it using the MATHJAX_RELPATH option.
1514 # The default value is: NO.
1515 # This tag requires that the tag GENERATE_HTML is set to YES.
1519 # When MathJax is enabled you can set the default output format to be used for
1520 # the MathJax output. See the MathJax site (see:
1521 # http://docs.mathjax.org/en/latest/output.html) for more details.
1522 # Possible values are: HTML-CSS (which is slower, but has the best
1523 # compatibility), NativeMML (i.e. MathML) and SVG.
1524 # The default value is: HTML-CSS.
1525 # This tag requires that the tag USE_MATHJAX is set to YES.
1527 MATHJAX_FORMAT = HTML-CSS
1529 # When MathJax is enabled you need to specify the location relative to the HTML
1530 # output directory using the MATHJAX_RELPATH option. The destination directory
1531 # should contain the MathJax.js script. For instance, if the mathjax directory
1532 # is located at the same level as the HTML output directory, then
1533 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1534 # Content Delivery Network so you can quickly see the result without installing
1535 # MathJax. However, it is strongly recommended to install a local copy of
1536 # MathJax from http://www.mathjax.org before deployment.
1537 # The default value is: http://cdn.mathjax.org/mathjax/latest.
1538 # This tag requires that the tag USE_MATHJAX is set to YES.
1540 MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest
1542 # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
1543 # extension names that should be enabled during MathJax rendering. For example
1544 # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
1545 # This tag requires that the tag USE_MATHJAX is set to YES.
1547 MATHJAX_EXTENSIONS =
1549 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1550 # of code that will be used on startup of the MathJax code. See the MathJax site
1551 # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
1552 # example see the documentation.
1553 # This tag requires that the tag USE_MATHJAX is set to YES.
1557 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1558 # the HTML output. The underlying search engine uses javascript and DHTML and
1559 # should work on any modern browser. Note that when using HTML help
1560 # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
1561 # there is already a search function so this one should typically be disabled.
1562 # For large projects the javascript based search engine can be slow, then
1563 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1564 # search using the keyboard; to jump to the search box use <access key> + S
1565 # (what the <access key> is depends on the OS and browser, but it is typically
1566 # <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
1567 # key> to jump into the search results window, the results can be navigated
1568 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1569 # the search. The filter options can be selected when the cursor is inside the
1570 # search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
1571 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1573 # The default value is: YES.
1574 # This tag requires that the tag GENERATE_HTML is set to YES.
1578 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1579 # implemented using a web server instead of a web client using Javascript. There
1580 # are two flavors of web server based searching depending on the EXTERNAL_SEARCH
1581 # setting. When disabled, doxygen will generate a PHP script for searching and
1582 # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
1583 # and searching needs to be provided by external tools. See the section
1584 # "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 SERVER_BASED_SEARCH = NO
1590 # When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
1591 # script for searching. Instead the search results are written to an XML file
1592 # which needs to be processed by an external indexer. Doxygen will invoke an
1593 # external search engine pointed to by the SEARCHENGINE_URL option to obtain the
1596 # Doxygen ships with an example indexer (doxyindexer) and search engine
1597 # (doxysearch.cgi) which are based on the open source search engine library
1598 # Xapian (see: http://xapian.org/).
1600 # See the section "External Indexing and Searching" for details.
1601 # The default value is: NO.
1602 # This tag requires that the tag SEARCHENGINE is set to YES.
1604 EXTERNAL_SEARCH = NO
1606 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
1607 # which will return the search results when EXTERNAL_SEARCH is enabled.
1609 # Doxygen ships with an example indexer (doxyindexer) and search engine
1610 # (doxysearch.cgi) which are based on the open source search engine library
1611 # Xapian (see: http://xapian.org/). See the section "External Indexing and
1612 # Searching" for details.
1613 # This tag requires that the tag SEARCHENGINE is set to YES.
1617 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
1618 # search data is written to a file for indexing by an external tool. With the
1619 # SEARCHDATA_FILE tag the name of this file can be specified.
1620 # The default file is: searchdata.xml.
1621 # This tag requires that the tag SEARCHENGINE is set to YES.
1623 SEARCHDATA_FILE = searchdata.xml
1625 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
1626 # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
1627 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1628 # projects and redirect the results back to the right project.
1629 # This tag requires that the tag SEARCHENGINE is set to YES.
1631 EXTERNAL_SEARCH_ID =
1633 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1634 # projects other than the one defined by this configuration file, but that are
1635 # all added to the same external search index. Each project needs to have a
1636 # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
1637 # to a relative location where the documentation can be found. The format is:
1638 # EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
1639 # This tag requires that the tag SEARCHENGINE is set to YES.
1641 EXTRA_SEARCH_MAPPINGS =
1643 #---------------------------------------------------------------------------
1644 # Configuration options related to the LaTeX output
1645 #---------------------------------------------------------------------------
1647 # If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.
1648 # The default value is: YES.
1650 GENERATE_LATEX = YES
1652 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1653 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1655 # The default directory is: latex.
1656 # This tag requires that the tag GENERATE_LATEX is set to YES.
1658 LATEX_OUTPUT = latex
1660 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1663 # Note that when enabling USE_PDFLATEX this option is only used for generating
1664 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1665 # written to the output directory.
1666 # The default file is: latex.
1667 # This tag requires that the tag GENERATE_LATEX is set to YES.
1669 LATEX_CMD_NAME = latex
1671 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
1673 # The default file is: makeindex.
1674 # This tag requires that the tag GENERATE_LATEX is set to YES.
1676 MAKEINDEX_CMD_NAME = makeindex
1678 # If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
1679 # documents. This may be useful for small projects and may help to save some
1681 # The default value is: NO.
1682 # This tag requires that the tag GENERATE_LATEX is set to YES.
1686 # The PAPER_TYPE tag can be used to set the paper type that is used by the
1688 # Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
1689 # 14 inches) and executive (7.25 x 10.5 inches).
1690 # The default value is: a4.
1691 # This tag requires that the tag GENERATE_LATEX is set to YES.
1695 # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
1696 # that should be included in the LaTeX output. The package can be specified just
1697 # by its name or with the correct syntax as to be used with the LaTeX
1698 # \usepackage command. To get the times font for instance you can specify :
1699 # EXTRA_PACKAGES=times or EXTRA_PACKAGES={times}
1700 # To use the option intlimits with the amsmath package you can specify:
1701 # EXTRA_PACKAGES=[intlimits]{amsmath}
1702 # If left blank no extra packages will be included.
1703 # This tag requires that the tag GENERATE_LATEX is set to YES.
1707 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1708 # generated LaTeX document. The header should contain everything until the first
1709 # chapter. If it is left blank doxygen will generate a standard header. See
1710 # section "Doxygen usage" for information on how to let doxygen write the
1711 # default header to a separate file.
1713 # Note: Only use a user-defined header if you know what you are doing! The
1714 # following commands have a special meaning inside the header: $title,
1715 # $datetime, $date, $doxygenversion, $projectname, $projectnumber,
1716 # $projectbrief, $projectlogo. Doxygen will replace $title with the empty
1717 # string, for the replacement values of the other commands the user is referred
1719 # This tag requires that the tag GENERATE_LATEX is set to YES.
1723 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1724 # generated LaTeX document. The footer should contain everything after the last
1725 # chapter. If it is left blank doxygen will generate a standard footer. See
1726 # LATEX_HEADER for more information on how to generate a default footer and what
1727 # special commands can be used inside the footer.
1729 # Note: Only use a user-defined footer if you know what you are doing!
1730 # This tag requires that the tag GENERATE_LATEX is set to YES.
1734 # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1735 # LaTeX style sheets that are included after the standard style sheets created
1736 # by doxygen. Using this option one can overrule certain style aspects. Doxygen
1737 # will copy the style sheet files to the output directory.
1738 # Note: The order of the extra style sheet files is of importance (e.g. the last
1739 # style sheet in the list overrules the setting of the previous ones in the
1741 # This tag requires that the tag GENERATE_LATEX is set to YES.
1743 LATEX_EXTRA_STYLESHEET =
1745 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1746 # other source files which should be copied to the LATEX_OUTPUT output
1747 # directory. Note that the files will be copied as-is; there are no commands or
1748 # markers available.
1749 # This tag requires that the tag GENERATE_LATEX is set to YES.
1753 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
1754 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
1755 # contain links (just like the HTML output) instead of page references. This
1756 # makes the output suitable for online browsing using a PDF viewer.
1757 # The default value is: YES.
1758 # This tag requires that the tag GENERATE_LATEX is set to YES.
1760 PDF_HYPERLINKS = YES
1762 # If the USE_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
1763 # the PDF file directly from the LaTeX files. Set this option to YES, to get a
1764 # higher quality PDF documentation.
1765 # The default value is: YES.
1766 # This tag requires that the tag GENERATE_LATEX is set to YES.
1770 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
1771 # command to the generated LaTeX files. This will instruct LaTeX to keep running
1772 # if errors occur, instead of asking the user for help. This option is also used
1773 # when generating formulas in HTML.
1774 # The default value is: NO.
1775 # This tag requires that the tag GENERATE_LATEX is set to YES.
1777 LATEX_BATCHMODE = NO
1779 # If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
1780 # index chapters (such as File Index, Compound Index, etc.) in the output.
1781 # The default value is: NO.
1782 # This tag requires that the tag GENERATE_LATEX is set to YES.
1784 LATEX_HIDE_INDICES = NO
1786 # If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
1787 # code with syntax highlighting in the LaTeX output.
1789 # Note that which sources are shown also depends on other settings such as
1791 # The default value is: NO.
1792 # This tag requires that the tag GENERATE_LATEX is set to YES.
1794 LATEX_SOURCE_CODE = NO
1796 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1797 # bibliography, e.g. plainnat, or ieeetr. See
1798 # http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
1799 # The default value is: plain.
1800 # This tag requires that the tag GENERATE_LATEX is set to YES.
1802 LATEX_BIB_STYLE = plain
1804 # If the LATEX_TIMESTAMP tag is set to YES then the footer of each generated
1805 # page will contain the date and time when the page was generated. Setting this
1806 # to NO can help when comparing the output of multiple runs.
1807 # The default value is: NO.
1808 # This tag requires that the tag GENERATE_LATEX is set to YES.
1810 LATEX_TIMESTAMP = NO
1812 #---------------------------------------------------------------------------
1813 # Configuration options related to the RTF output
1814 #---------------------------------------------------------------------------
1816 # If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The
1817 # RTF output is optimized for Word 97 and may not look too pretty with other RTF
1819 # The default value is: NO.
1823 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
1824 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1826 # The default directory is: rtf.
1827 # This tag requires that the tag GENERATE_RTF is set to YES.
1831 # If the COMPACT_RTF tag is set to YES, doxygen generates more compact RTF
1832 # documents. This may be useful for small projects and may help to save some
1834 # The default value is: NO.
1835 # This tag requires that the tag GENERATE_RTF is set to YES.
1839 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
1840 # contain hyperlink fields. The RTF file will contain links (just like the HTML
1841 # output) instead of page references. This makes the output suitable for online
1842 # browsing using Word or some other Word compatible readers that support those
1845 # Note: WordPad (write) and others do not support links.
1846 # The default value is: NO.
1847 # This tag requires that the tag GENERATE_RTF is set to YES.
1851 # Load stylesheet definitions from file. Syntax is similar to doxygen's config
1852 # file, i.e. a series of assignments. You only have to provide replacements,
1853 # missing definitions are set to their default value.
1855 # See also section "Doxygen usage" for information on how to generate the
1856 # default style sheet that doxygen normally uses.
1857 # This tag requires that the tag GENERATE_RTF is set to YES.
1859 RTF_STYLESHEET_FILE =
1861 # Set optional variables used in the generation of an RTF document. Syntax is
1862 # similar to doxygen's config file. A template extensions file can be generated
1863 # using doxygen -e rtf extensionFile.
1864 # This tag requires that the tag GENERATE_RTF is set to YES.
1866 RTF_EXTENSIONS_FILE =
1868 # If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
1869 # with syntax highlighting in the RTF output.
1871 # Note that which sources are shown also depends on other settings such as
1873 # The default value is: NO.
1874 # This tag requires that the tag GENERATE_RTF is set to YES.
1876 RTF_SOURCE_CODE = NO
1878 #---------------------------------------------------------------------------
1879 # Configuration options related to the man page output
1880 #---------------------------------------------------------------------------
1882 # If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
1883 # classes and files.
1884 # The default value is: NO.
1888 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
1889 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1890 # it. A directory man3 will be created inside the directory specified by
1892 # The default directory is: man.
1893 # This tag requires that the tag GENERATE_MAN is set to YES.
1897 # The MAN_EXTENSION tag determines the extension that is added to the generated
1898 # man pages. In case the manual section does not start with a number, the number
1899 # 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
1901 # The default value is: .3.
1902 # This tag requires that the tag GENERATE_MAN is set to YES.
1906 # The MAN_SUBDIR tag determines the name of the directory created within
1907 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
1908 # MAN_EXTENSION with the initial . removed.
1909 # This tag requires that the tag GENERATE_MAN is set to YES.
1913 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
1914 # will generate one additional man file for each entity documented in the real
1915 # man page(s). These additional files only source the real man page, but without
1916 # them the man command would be unable to find the correct page.
1917 # The default value is: NO.
1918 # This tag requires that the tag GENERATE_MAN is set to YES.
1922 #---------------------------------------------------------------------------
1923 # Configuration options related to the XML output
1924 #---------------------------------------------------------------------------
1926 # If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
1927 # captures the structure of the code including all documentation.
1928 # The default value is: NO.
1932 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
1933 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1935 # The default directory is: xml.
1936 # This tag requires that the tag GENERATE_XML is set to YES.
1940 # If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program
1941 # listings (including syntax highlighting and cross-referencing information) to
1942 # the XML output. Note that enabling this will significantly increase the size
1943 # of the XML output.
1944 # The default value is: YES.
1945 # This tag requires that the tag GENERATE_XML is set to YES.
1947 XML_PROGRAMLISTING = YES
1949 #---------------------------------------------------------------------------
1950 # Configuration options related to the DOCBOOK output
1951 #---------------------------------------------------------------------------
1953 # If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files
1954 # that can be used to generate PDF.
1955 # The default value is: NO.
1957 GENERATE_DOCBOOK = NO
1959 # The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
1960 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1962 # The default directory is: docbook.
1963 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
1965 DOCBOOK_OUTPUT = docbook
1967 # If the DOCBOOK_PROGRAMLISTING tag is set to YES, doxygen will include the
1968 # program listings (including syntax highlighting and cross-referencing
1969 # information) to the DOCBOOK output. Note that enabling this will significantly
1970 # increase the size of the DOCBOOK output.
1971 # The default value is: NO.
1972 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
1974 DOCBOOK_PROGRAMLISTING = NO
1976 #---------------------------------------------------------------------------
1977 # Configuration options for the AutoGen Definitions output
1978 #---------------------------------------------------------------------------
1980 # If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an
1981 # AutoGen Definitions (see http://autogen.sf.net) file that captures the
1982 # structure of the code including all documentation. Note that this feature is
1983 # still experimental and incomplete at the moment.
1984 # The default value is: NO.
1986 GENERATE_AUTOGEN_DEF = NO
1988 #---------------------------------------------------------------------------
1989 # Configuration options related to the Perl module output
1990 #---------------------------------------------------------------------------
1992 # If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module
1993 # file that captures the structure of the code including all documentation.
1995 # Note that this feature is still experimental and incomplete at the moment.
1996 # The default value is: NO.
1998 GENERATE_PERLMOD = NO
2000 # If the PERLMOD_LATEX tag is set to YES, doxygen will generate the necessary
2001 # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
2002 # output from the Perl module output.
2003 # The default value is: NO.
2004 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2008 # If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely
2009 # formatted so it can be parsed by a human reader. This is useful if you want to
2010 # understand what is going on. On the other hand, if this tag is set to NO, the
2011 # size of the Perl module output will be much smaller and Perl will parse it
2013 # The default value is: YES.
2014 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2016 PERLMOD_PRETTY = YES
2018 # The names of the make variables in the generated doxyrules.make file are
2019 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
2020 # so different doxyrules.make files included by the same Makefile don't
2021 # overwrite each other's variables.
2022 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2024 PERLMOD_MAKEVAR_PREFIX =
2026 #---------------------------------------------------------------------------
2027 # Configuration options related to the preprocessor
2028 #---------------------------------------------------------------------------
2030 # If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all
2031 # C-preprocessor directives found in the sources and include files.
2032 # The default value is: YES.
2034 ENABLE_PREPROCESSING = YES
2036 # If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names
2037 # in the source code. If set to NO, only conditional compilation will be
2038 # performed. Macro expansion can be done in a controlled way by setting
2039 # EXPAND_ONLY_PREDEF to YES.
2040 # The default value is: NO.
2041 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2043 MACRO_EXPANSION = NO
2045 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
2046 # the macro expansion is limited to the macros specified with the PREDEFINED and
2047 # EXPAND_AS_DEFINED tags.
2048 # The default value is: NO.
2049 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2051 EXPAND_ONLY_PREDEF = NO
2053 # If the SEARCH_INCLUDES tag is set to YES, the include files in the
2054 # INCLUDE_PATH will be searched if a #include is found.
2055 # The default value is: YES.
2056 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2058 SEARCH_INCLUDES = YES
2060 # The INCLUDE_PATH tag can be used to specify one or more directories that
2061 # contain include files that are not input files but should be processed by the
2063 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
2067 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
2068 # patterns (like *.h and *.hpp) to filter out the header-files in the
2069 # directories. If left blank, the patterns specified with FILE_PATTERNS will be
2071 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2073 INCLUDE_FILE_PATTERNS =
2075 # The PREDEFINED tag can be used to specify one or more macro names that are
2076 # defined before the preprocessor is started (similar to the -D option of e.g.
2077 # gcc). The argument of the tag is a list of macros of the form: name or
2078 # name=definition (no spaces). If the definition and the "=" are omitted, "=1"
2079 # is assumed. To prevent a macro definition from being undefined via #undef or
2080 # recursively expanded use the := operator instead of the = operator.
2081 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2085 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
2086 # tag can be used to specify a list of macro names that should be expanded. The
2087 # macro definition that is found in the sources will be used. Use the PREDEFINED
2088 # tag if you want to use a different macro definition that overrules the
2089 # definition found in the source code.
2090 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2094 # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
2095 # remove all references to function-like macros that are alone on a line, have
2096 # an all uppercase name, and do not end with a semicolon. Such function macros
2097 # are typically used for boiler-plate code, and will confuse the parser if not
2099 # The default value is: YES.
2100 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2102 SKIP_FUNCTION_MACROS = YES
2104 #---------------------------------------------------------------------------
2105 # Configuration options related to external references
2106 #---------------------------------------------------------------------------
2108 # The TAGFILES tag can be used to specify one or more tag files. For each tag
2109 # file the location of the external documentation should be added. The format of
2110 # a tag file without this location is as follows:
2111 # TAGFILES = file1 file2 ...
2112 # Adding location for the tag files is done as follows:
2113 # TAGFILES = file1=loc1 "file2 = loc2" ...
2114 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
2115 # section "Linking to external documentation" for more information about the use
2117 # Note: Each tag file must have a unique name (where the name does NOT include
2118 # the path). If a tag file is not located in the directory in which doxygen is
2119 # run, you must also specify the path to the tagfile here.
2123 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2124 # tag file that is based on the input files it reads. See section "Linking to
2125 # external documentation" for more information about the usage of tag files.
2129 # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
2130 # the class index. If set to NO, only the inherited external classes will be
2132 # The default value is: NO.
2136 # If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed
2137 # in the modules index. If set to NO, only the current project's groups will be
2139 # The default value is: YES.
2141 EXTERNAL_GROUPS = YES
2143 # If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
2144 # the related pages index. If set to NO, only the current project's pages will
2146 # The default value is: YES.
2148 EXTERNAL_PAGES = YES
2150 # The PERL_PATH should be the absolute path and name of the perl script
2151 # interpreter (i.e. the result of 'which perl').
2152 # The default file (with absolute path) is: /usr/bin/perl.
2154 PERL_PATH = /usr/bin/perl
2156 #---------------------------------------------------------------------------
2157 # Configuration options related to the dot tool
2158 #---------------------------------------------------------------------------
2160 # If the CLASS_DIAGRAMS tag is set to YES, doxygen will generate a class diagram
2161 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2162 # NO turns the diagrams off. Note that this option also works with HAVE_DOT
2163 # disabled, but it is recommended to install and use dot, since it yields more
2165 # The default value is: YES.
2167 CLASS_DIAGRAMS = YES
2169 # You can define message sequence charts within doxygen comments using the \msc
2170 # command. Doxygen will then run the mscgen tool (see:
2171 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2172 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
2173 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2174 # default search path.
2178 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2179 # then run dia to produce the diagram and insert it in the documentation. The
2180 # DIA_PATH tag allows you to specify the directory where the dia binary resides.
2181 # If left empty dia is assumed to be found in the default search path.
2185 # If set to YES the inheritance and collaboration graphs will hide inheritance
2186 # and usage relations if the target is undocumented or is not a class.
2187 # The default value is: YES.
2189 HIDE_UNDOC_RELATIONS = YES
2191 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
2192 # available from the path. This tool is part of Graphviz (see:
2193 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2194 # Bell Labs. The other options in this section have no effect if this option is
2196 # The default value is: NO.
2200 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
2201 # to run in parallel. When set to 0 doxygen will base this on the number of
2202 # processors available in the system. You can set it explicitly to a value
2203 # larger than 0 to get control over the balance between CPU load and processing
2205 # Minimum value: 0, maximum value: 32, default value: 0.
2206 # This tag requires that the tag HAVE_DOT is set to YES.
2210 # When you want a differently looking font in the dot files that doxygen
2211 # generates you can specify the font name using DOT_FONTNAME. You need to make
2212 # sure dot is able to find the font, which can be done by putting it in a
2213 # standard location or by setting the DOTFONTPATH environment variable or by
2214 # setting DOT_FONTPATH to the directory containing the font.
2215 # The default value is: Helvetica.
2216 # This tag requires that the tag HAVE_DOT is set to YES.
2218 DOT_FONTNAME = Helvetica
2220 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2222 # Minimum value: 4, maximum value: 24, default value: 10.
2223 # This tag requires that the tag HAVE_DOT is set to YES.
2227 # By default doxygen will tell dot to use the default font as specified with
2228 # DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
2229 # the path where dot can find it using this tag.
2230 # This tag requires that the tag HAVE_DOT is set to YES.
2234 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2235 # each documented class showing the direct and indirect inheritance relations.
2236 # Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
2237 # The default value is: YES.
2238 # This tag requires that the tag HAVE_DOT is set to YES.
2242 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
2243 # graph for each documented class showing the direct and indirect implementation
2244 # dependencies (inheritance, containment, and class references variables) of the
2245 # class with other documented classes.
2246 # The default value is: YES.
2247 # This tag requires that the tag HAVE_DOT is set to YES.
2249 COLLABORATION_GRAPH = YES
2251 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2252 # groups, showing the direct groups dependencies.
2253 # The default value is: YES.
2254 # This tag requires that the tag HAVE_DOT is set to YES.
2258 # If the UML_LOOK tag is set to YES, doxygen will generate inheritance and
2259 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2261 # The default value is: NO.
2262 # This tag requires that the tag HAVE_DOT is set to YES.
2266 # If the UML_LOOK tag is enabled, the fields and methods are shown inside the
2267 # class node. If there are many fields or methods and many nodes the graph may
2268 # become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
2269 # number of items for each type to make the size more manageable. Set this to 0
2270 # for no limit. Note that the threshold may be exceeded by 50% before the limit
2271 # is enforced. So when you set the threshold to 10, up to 15 fields may appear,
2272 # but if the number exceeds 15, the total amount of fields shown is limited to
2274 # Minimum value: 0, maximum value: 100, default value: 10.
2275 # This tag requires that the tag HAVE_DOT is set to YES.
2277 UML_LIMIT_NUM_FIELDS = 10
2279 # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
2280 # collaboration graphs will show the relations between templates and their
2282 # The default value is: NO.
2283 # This tag requires that the tag HAVE_DOT is set to YES.
2285 TEMPLATE_RELATIONS = NO
2287 # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
2288 # YES then doxygen will generate a graph for each documented file showing the
2289 # direct and indirect include dependencies of the file with other documented
2291 # The default value is: YES.
2292 # This tag requires that the tag HAVE_DOT is set to YES.
2296 # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
2297 # set to YES then doxygen will generate a graph for each documented file showing
2298 # the direct and indirect include dependencies of the file with other documented
2300 # The default value is: YES.
2301 # This tag requires that the tag HAVE_DOT is set to YES.
2303 INCLUDED_BY_GRAPH = YES
2305 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
2306 # dependency graph for every global function or class method.
2308 # Note that enabling this option will significantly increase the time of a run.
2309 # So in most cases it will be better to enable call graphs for selected
2310 # functions only using the \callgraph command. Disabling a call graph can be
2311 # accomplished by means of the command \hidecallgraph.
2312 # The default value is: NO.
2313 # This tag requires that the tag HAVE_DOT is set to YES.
2317 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
2318 # dependency graph for every global function or class method.
2320 # Note that enabling this option will significantly increase the time of a run.
2321 # So in most cases it will be better to enable caller graphs for selected
2322 # functions only using the \callergraph command. Disabling a caller graph can be
2323 # accomplished by means of the command \hidecallergraph.
2324 # The default value is: NO.
2325 # This tag requires that the tag HAVE_DOT is set to YES.
2329 # If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
2330 # hierarchy of all classes instead of a textual one.
2331 # The default value is: YES.
2332 # This tag requires that the tag HAVE_DOT is set to YES.
2334 GRAPHICAL_HIERARCHY = YES
2336 # If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
2337 # dependencies a directory has on other directories in a graphical way. The
2338 # dependency relations are determined by the #include relations between the
2339 # files in the directories.
2340 # The default value is: YES.
2341 # This tag requires that the tag HAVE_DOT is set to YES.
2343 DIRECTORY_GRAPH = YES
2345 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
2346 # generated by dot. For an explanation of the image formats see the section
2347 # output formats in the documentation of the dot tool (Graphviz (see:
2348 # http://www.graphviz.org/)).
2349 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2350 # to make the SVG files visible in IE 9+ (other browsers do not have this
2352 # Possible values are: png, jpg, gif, svg, png:gd, png:gd:gd, png:cairo,
2353 # png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and
2354 # png:gdiplus:gdiplus.
2355 # The default value is: png.
2356 # This tag requires that the tag HAVE_DOT is set to YES.
2358 DOT_IMAGE_FORMAT = png
2360 # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
2361 # enable generation of interactive SVG images that allow zooming and panning.
2363 # Note that this requires a modern browser other than Internet Explorer. Tested
2364 # and working are Firefox, Chrome, Safari, and Opera.
2365 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2366 # the SVG files visible. Older versions of IE do not have SVG support.
2367 # The default value is: NO.
2368 # This tag requires that the tag HAVE_DOT is set to YES.
2370 INTERACTIVE_SVG = NO
2372 # The DOT_PATH tag can be used to specify the path where the dot tool can be
2373 # found. If left blank, it is assumed the dot tool can be found in the path.
2374 # This tag requires that the tag HAVE_DOT is set to YES.
2378 # The DOTFILE_DIRS tag can be used to specify one or more directories that
2379 # contain dot files that are included in the documentation (see the \dotfile
2381 # This tag requires that the tag HAVE_DOT is set to YES.
2385 # The MSCFILE_DIRS tag can be used to specify one or more directories that
2386 # contain msc files that are included in the documentation (see the \mscfile
2391 # The DIAFILE_DIRS tag can be used to specify one or more directories that
2392 # contain dia files that are included in the documentation (see the \diafile
2397 # When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
2398 # path where java can find the plantuml.jar file. If left blank, it is assumed
2399 # PlantUML is not used or called during a preprocessing step. Doxygen will
2400 # generate a warning when it encounters a \startuml command in this case and
2401 # will not generate output for the diagram.
2405 # When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
2406 # configuration file for plantuml.
2410 # When using plantuml, the specified paths are searched for files specified by
2411 # the !include statement in a plantuml block.
2413 PLANTUML_INCLUDE_PATH =
2415 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2416 # that will be shown in the graph. If the number of nodes in a graph becomes
2417 # larger than this value, doxygen will truncate the graph, which is visualized
2418 # by representing a node as a red box. Note that doxygen if the number of direct
2419 # children of the root node in a graph is already larger than
2420 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
2421 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2422 # Minimum value: 0, maximum value: 10000, default value: 50.
2423 # This tag requires that the tag HAVE_DOT is set to YES.
2425 DOT_GRAPH_MAX_NODES = 50
2427 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
2428 # generated by dot. A depth value of 3 means that only nodes reachable from the
2429 # root by following a path via at most 3 edges will be shown. Nodes that lay
2430 # further from the root node will be omitted. Note that setting this option to 1
2431 # or 2 may greatly reduce the computation time needed for large code bases. Also
2432 # note that the size of a graph can be further restricted by
2433 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
2434 # Minimum value: 0, maximum value: 1000, default value: 0.
2435 # This tag requires that the tag HAVE_DOT is set to YES.
2437 MAX_DOT_GRAPH_DEPTH = 0
2439 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
2440 # background. This is disabled by default, because dot on Windows does not seem
2441 # to support this out of the box.
2443 # Warning: Depending on the platform used, enabling this option may lead to
2444 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2446 # The default value is: NO.
2447 # This tag requires that the tag HAVE_DOT is set to YES.
2449 DOT_TRANSPARENT = NO
2451 # Set the DOT_MULTI_TARGETS tag to YES to allow dot to generate multiple output
2452 # files in one run (i.e. multiple -o and -T options on the command line). This
2453 # makes dot run faster, but since only newer versions of dot (>1.8.10) support
2454 # this, this feature is disabled by default.
2455 # The default value is: NO.
2456 # This tag requires that the tag HAVE_DOT is set to YES.
2458 DOT_MULTI_TARGETS = NO
2460 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
2461 # explaining the meaning of the various boxes and arrows in the dot generated
2463 # The default value is: YES.
2464 # This tag requires that the tag HAVE_DOT is set to YES.
2466 GENERATE_LEGEND = YES
2468 # If the DOT_CLEANUP tag is set to YES, doxygen will remove the intermediate dot
2469 # files that are used to generate the various graphs.
2470 # The default value is: YES.
2471 # This tag requires that the tag HAVE_DOT is set to YES.