Lines Matching full:the

3 # This file describes the settings to be used by the documentation system
7 # front of the TAG it is preceding.
10 # The format is:
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.
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
33 # The default value is: My Project.
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
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 an logo or icon that is included in
50 # the documentation. The maximum height of the logo should not exceed 55 pixels
51 # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo
52 # 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.
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
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 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
75 # information to generate all constant output in the proper language.
84 # The default value is: English.
88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member
89 # descriptions after the members that are listed in the file and class
91 # The default value is: YES.
95 # If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief
96 # description of a member or function before the detailed description
98 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
100 # The default value is: YES.
105 # used to form the text in various listings. Each string in this list, if found
106 # as the leading text of the brief description, will be stripped from the text
107 # and the result, after processing the whole list, is used as the annotated
108 # text. Otherwise, the brief description is used as-is. If left blank, the
109 # following values are used ($name is automatically replaced with the name of
110 # the entity):The $name class, The $name widget, The $name file, is, provides,
111 # specifies, contains, represents, a, an and the.
115 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
118 # The default value is: NO.
122 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
123 # inherited members of a class in the documentation of that class as if those
125 # operators of the base classes will not be shown.
126 # The default value is: NO.
130 # If the FULL_PATH_NAMES tag is set to YES doxygen will prepend the full path
131 # before files name in the file list and in the header files. If set to NO the
132 # shortest path that makes the file name unique will be used
133 # The default value is: YES.
137 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
138 # Stripping is only done if one of the specified strings matches the left-hand
139 # part of the path. The tag can be used to show relative paths in the file list.
140 # If left blank the directory from which doxygen is run is used as the path to
144 # will be relative from the directory where doxygen is started.
145 # This tag requires that the tag FULL_PATH_NAMES is set to YES.
149 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
150 # path mentioned in the documentation of a class, which tells the reader which
151 # header file to include in order to use a class. If left blank only the name of
152 # the header file containing the class definition is used. Otherwise one should
153 # specify the list of include paths that are normally passed to the compiler
154 # using the -I flag.
158 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
161 # The default value is: NO.
165 # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
166 # first line (until the first dot) of a Javadoc-style comment as the brief
167 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
170 # The default value is: NO.
174 # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
175 # line (until the first dot) of a Qt-style comment as the brief description. If
176 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
178 # The default value is: NO.
182 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
184 # a brief description. This used to be the default behavior. The new default is
186 # tag to YES if you prefer the old behavior instead.
190 # The default value is: NO.
194 # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
196 # The default value is: YES.
200 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce a
201 # new page for each member. If set to NO, the documentation of a member will be
202 # part of the file/class/namespace that contains it.
203 # The default value is: NO.
207 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
214 # the documentation. An alias has the form:
218 # will allow you to put the command \sideeffect (or @sideeffect) in the
220 # "Side Effects:". You can put \n's in the value part of an alias to insert
226 # A mapping has the form "name=value". For example adding "class=itcl::class"
227 # will allow you to use the command class in the itcl::class meaning.
231 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
233 # instance, some of the names that are used will be different. The list of all
235 # The default value is: NO.
239 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
243 # The default value is: NO.
247 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
249 # The default value is: NO.
253 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
255 # The default value is: NO.
259 # Doxygen selects the parser to use depending on the extension of the files it
262 # using this tag. The format is ext=language, where ext is a file extension, and
263 # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
271 # the files are not read by doxygen.
275 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
276 # according to the Markdown format, which allows for more readable
278 # The output of markdown processing is further processed by doxygen, so you can
281 # The default value is: YES.
287 # be prevented in individual cases by by putting a % sign in front of the word
289 # The default value is: YES.
294 # to include (a tag file for) the STL sources as input, then you should set this
297 # versus func(std::string) {}). This also make the inheritance and collaboration
299 # The default value is: NO.
305 # The default value is: NO.
309 # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
313 # The default value is: NO.
319 # doxygen to replace the get and set methods by a property in the documentation.
320 # This will only work if the methods are indeed getting or setting a simple
321 # type. If this is not the case, or you want to show the methods anyway, you
323 # The default value is: YES.
327 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
328 # tag is set to YES, then doxygen will reuse the documentation of the first
329 # member in the group (if any) for the other members of the group. By default
331 # The default value is: NO.
335 # Set the SUBGROUPING tag to YES to allow class member groups of the same type
337 # type (e.g. under the Public Functions section). Set it to NO to prevent
338 # subgrouping. Alternatively, this can be done per class using the
340 # The default value is: YES.
344 # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
345 # are shown inside the group in which they are included (e.g. using \ingroup)
351 # The default value is: NO.
355 # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
357 # the documentation of the scope in which they are defined (i.e. file,
361 # The default value is: NO.
366 # enum is documented as struct, union, or enum with the name of the typedef. So
367 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
368 # with name TypeT. When disabled the typedef will appear as a member of a file,
369 # namespace, or class. And the struct will be named TypeS. This can typically be
370 # useful for C code in case the coding convention dictates that all compound
371 # types are typedef'ed and only the typedef is referenced, never the tag name.
372 # The default value is: NO.
376 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
378 # an expensive process and often the same symbol appears multiple times in the
379 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
380 # doxygen will become slower. If the cache is too large, memory is wasted. The
381 # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
382 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
383 # symbols. At the end of a run doxygen will report the cache usage and suggest
384 # the optimal cache size from a speed point of view.
393 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
395 # class members and static file members will be hidden unless the
397 # Note: This will also disable the warnings about undocumented members that are
399 # The default value is: NO.
403 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class will
404 # be included in the documentation.
405 # The default value is: NO.
409 # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
410 # scope will be included in the documentation.
411 # The default value is: NO.
415 # If the EXTRACT_STATIC tag is set to YES all static members of a file will be
416 # included in the documentation.
417 # The default value is: NO.
421 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) defined
422 # locally in source files will be included in the documentation. If set to NO
425 # The default value is: YES.
430 # which are defined in the implementation section but not in the interface are
431 # included in the documentation. If set to NO only methods in the interface are
433 # The default value is: NO.
437 # If this flag is set to YES, the members of anonymous namespaces will be
438 # extracted and appear in the documentation as a namespace called
439 # 'anonymous_namespace{file}', where file will be replaced with the base name of
440 # the file that contains the anonymous namespace. By default anonymous namespace
442 # The default value is: NO.
446 # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
448 # members will be included in the various overviews, but no documentation
450 # The default value is: NO.
454 # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
455 # undocumented classes that are normally visible in the class hierarchy. If set
456 # to NO these classes will be included in the various overviews. This option has
458 # The default value is: NO.
462 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
464 # included in the documentation.
465 # The default value is: NO.
469 # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
470 # documentation blocks found inside the body of a function. If set to NO these
471 # blocks will be appended to the function's detailed documentation block.
472 # The default value is: NO.
476 # The INTERNAL_DOCS tag determines if documentation that is typed after a
477 # \internal command is included. If the tag is set to NO then the documentation
478 # will be excluded. Set it to YES to include the internal documentation.
479 # The default value is: NO.
483 # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
488 # The default value is: system dependent.
492 # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
493 # their full class and namespace scopes in the documentation. If set to YES the
495 # The default value is: NO.
499 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
500 # the files that are included by a file in the documentation of that file.
501 # The default value is: YES.
505 # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
506 # grouped member an include statement to the documentation, telling the reader
507 # which file to include in order to use the member.
508 # The default value is: NO.
512 # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
513 # files with double quotes in the documentation rather than with sharp brackets.
514 # The default value is: NO.
518 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
520 # The default value is: YES.
524 # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
526 # name. If set to NO the members will appear in declaration order.
527 # The default value is: YES.
531 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
533 # name. If set to NO the members will appear in declaration order. Note that
534 # this will also influence the order of the classes in the class list.
535 # The default value is: NO.
539 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
541 # destructors are listed first. If set to NO the constructors will appear in the
547 # The default value is: NO.
551 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
552 # of group names into alphabetical order. If set to NO the group names will
554 # The default value is: NO.
558 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
559 # fully-qualified names, including namespaces. If set to NO, the class list will
560 # be sorted only by class name, not including the namespace part.
562 # Note: This option applies only to the class list, not to the alphabetical
564 # The default value is: NO.
568 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
570 # the prototype and the implementation of a member function even if there is
574 # The default value is: NO.
578 # The GENERATE_TODOLIST tag can be used to enable ( YES) or disable ( NO) the
579 # todo list. This list is created by putting \todo commands in the
581 # The default value is: YES.
585 # The GENERATE_TESTLIST tag can be used to enable ( YES) or disable ( NO) the
586 # test list. This list is created by putting \test commands in the
588 # The default value is: YES.
592 # The GENERATE_BUGLIST tag can be used to enable ( YES) or disable ( NO) the bug
593 # list. This list is created by putting \bug commands in the documentation.
594 # The default value is: YES.
598 # The GENERATE_DEPRECATEDLIST tag can be used to enable ( YES) or disable ( NO)
599 # the deprecated list. This list is created by putting \deprecated commands in
600 # the documentation.
601 # The default value is: YES.
605 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
611 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
612 # initial value of a variable or macro / define can have for it to appear in the
613 # documentation. If the initializer consists of more lines than specified here
614 # it will be hidden. Use a value of 0 to hide initializers completely. The
615 # appearance of the value of individual variables and macros / defines can be
616 # controlled using \showinitializer or \hideinitializer command in the
622 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
623 # the bottom of the documentation of classes and structs. If set to YES the list
624 # will mention the files that were used to generate the documentation.
625 # The default value is: YES.
629 # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
630 # will remove the Files entry from the Quick Index and from the Folder Tree View
632 # The default value is: YES.
636 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
637 # page. This will remove the Namespaces entry from the Quick Index and from the
639 # The default value is: YES.
643 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
644 # doxygen should invoke to get the current version for each file (typically from
645 # the version control system). Doxygen will invoke the program by executing (via
646 # popen()) the command command input-file, where command is the value of the
647 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
648 # by doxygen. Whatever the program writes to standard output is used as the file
649 # version. For an example see the documentation.
653 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
654 # by doxygen. The layout file controls the global structure of the generated
655 # output files in an output format independent way. To create the layout file
656 # that represents doxygen's defaults, run doxygen with the -l option. You can
657 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
658 # will be used as the name of the layout file.
661 # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
666 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
667 # the reference definitions. This must be a list of .bib files. The .bib
668 # extension is automatically appended if omitted. This requires the bibtex tool
670 # For LaTeX the style of the bibliography can be controlled using
671 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
681 # The QUIET tag can be used to turn on/off the messages that are generated to
682 # standard output by doxygen. If QUIET is set to YES this implies that the
684 # The default value is: NO.
688 # The WARNINGS tag can be used to turn on/off the warning messages that are
690 # this implies that the warnings are on.
692 # Tip: Turn warnings on while writing the documentation.
693 # The default value is: YES.
697 # If the WARN_IF_UNDOCUMENTED tag is set to YES, then doxygen will generate
700 # The default value is: YES.
704 # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
705 # potential errors in the documentation, such as not documenting some parameters
708 # The default value is: YES.
715 # documentation, but not about the absence of documentation.
716 # The default value is: NO.
720 # The WARN_FORMAT tag determines the format of the warning messages that doxygen
721 # can produce. The string should contain the $file, $line, and $text tags, which
722 # will be replaced by the file and line number from which the warning originated
723 # and the warning text. Optionally the format may contain $version, which will
724 # be replaced by the version of the file (if it could be obtained via
726 # The default value is: $file:$line: $text.
730 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
731 # messages should be written. If left blank the output is written to standard
737 # Configuration options related to the input files
740 # The INPUT tag is used to specify the files and/or directories that contain
742 # directories like /usr/src/myproject. Separate the files or directories with
744 # Note: If this tag is empty the current directory is searched.
750 # This tag can be used to specify the character encoding of the source files
751 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
752 # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
753 # documentation (see: http://www.gnu.org/software/libiconv) for the list of
755 # The default value is: UTF-8.
759 # If the value of the INPUT tag contains directories, you can use the
761 # *.h) to filter out the source-files in the directories. If left blank the
770 # The RECURSIVE tag can be used to specify whether or not subdirectories should
772 # The default value is: NO.
776 # The EXCLUDE tag can be used to specify files and/or directories that should be
777 # excluded from the INPUT source files. This way you can easily exclude a
778 # subdirectory from a directory tree whose root is specified with the INPUT tag.
780 # Note that relative paths are relative to the directory from which doxygen is
785 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
787 # from the input.
788 # The default value is: NO.
792 # If the value of the INPUT tag contains directories, you can use the
796 # Note that the wildcards are matched against the file with absolute path, so to
797 # exclude all test directories for example use the pattern */test/*
801 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
802 # (namespaces, classes, functions, etc.) that should be excluded from the
803 # output. The symbol name can be a fully qualified name, a word, or if the
807 # Note that the wildcards are matched against the file with absolute path, so to
808 # exclude all test directories use the pattern */test/*
812 # The EXAMPLE_PATH tag can be used to specify one or more files or directories
813 # that contain example code fragments that are included (see the \include
818 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
820 # *.h) to filter out the source-files in the directories. If left blank all
825 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
826 # searched for input files to be used with the \include or \dontinclude commands
827 # irrespective of the value of the RECURSIVE tag.
828 # The default value is: NO.
832 # The IMAGE_PATH tag can be used to specify one or more files or directories
833 # that contain images that are to be included in the documentation (see the
838 # The INPUT_FILTER tag can be used to specify a program that doxygen should
839 # invoke to filter for each input file. Doxygen will invoke the filter program
840 # by executing (via popen()) the command:
844 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
845 # name of an input file. Doxygen will then use the output that the filter
849 # Note that the filter must not add or remove lines; it is applied before the
850 # code is scanned, but not when the output code is generated. If lines are added
851 # or removed, the anchors will not be placed correctly.
855 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
856 # basis. Doxygen will compare the file name with each pattern and apply the
857 # filter if there is a match. The filters are a list of the form: pattern=filter
859 # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
860 # patterns match the file name, INPUT_FILTER is applied.
864 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
865 # INPUT_FILTER ) will also be used to filter the input files that are used for
866 # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
867 # The default value is: NO.
871 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
872 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
875 # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
879 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
880 # is part of the input, its contents will be placed on the main page
882 # and want to reuse the introduction page also for the doxygen output.
890 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
893 # Note: To get rid of all source code in the generated output, make sure that
895 # The default value is: NO.
899 # Setting the INLINE_SOURCES tag to YES will include the body of functions,
900 # classes and enums directly into the documentation.
901 # The default value is: NO.
905 # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
908 # The default value is: YES.
912 # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
914 # The default value is: NO.
918 # If the REFERENCES_RELATION tag is set to YES then for each documented function
920 # The default value is: NO.
924 # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
925 # to YES, then the hyperlinks from functions in REFERENCES_RELATION and
926 # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
927 # link to the documentation.
928 # The default value is: YES.
932 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
934 # brief description and links to the definition and documentation. Since this
935 # will make the HTML file larger and loading of large files a bit slower, you
937 # The default value is: YES.
938 # This tag requires that the tag SOURCE_BROWSER is set to YES.
942 # If the USE_HTAGS tag is set to YES then the references to source code will
943 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
944 # source browser. The htags tool is part of GNU's global source tagging system
948 # To use it do the following:
949 # - Install the latest version of global
950 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
951 # - Make sure the INPUT points to the root of the source tree
955 # tools must be available from the command line (i.e. in the search path).
957 # The result: instead of the source browser generated by doxygen, the links to
958 # source code will now point to the output of htags.
959 # The default value is: NO.
960 # This tag requires that the tag SOURCE_BROWSER is set to YES.
964 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
965 # verbatim copy of the header file for each class for which an include is
968 # The default value is: YES.
973 # Configuration options related to the alphabetical class index
976 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
977 # compounds will be generated. Enable this if the project contains a lot of
979 # The default value is: YES.
983 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
984 # which the alphabetical index list will be split.
986 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
991 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
993 # while generating the index headers.
994 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
999 # Configuration options related to the HTML output
1002 # If the GENERATE_HTML tag is set to YES doxygen will generate HTML output
1003 # The default value is: YES.
1007 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1008 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1010 # The default directory is: html.
1011 # This tag requires that the tag GENERATE_HTML is set to YES.
1015 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1017 # The default value is: .html.
1018 # This tag requires that the tag GENERATE_HTML is set to YES.
1022 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1023 # each generated HTML page. If the tag is left blank doxygen will generate a
1026 # To get valid HTML the header file that includes any scripts and style sheets
1027 # that doxygen needs, which is dependent on the configuration options used (e.g.
1028 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1032 # and then modify the file new_header.html. See also section "Doxygen usage"
1033 # for information on how to generate the default header that doxygen normally
1035 # Note: The header is subject to change so you typically have to regenerate the
1037 # of the possible markers and block names see the documentation.
1038 # This tag requires that the tag GENERATE_HTML is set to YES.
1042 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1043 # generated HTML page. If the tag is left blank doxygen will generate a standard
1045 # footer and what special commands can be used inside the footer. See also
1046 # section "Doxygen usage" for information on how to generate the default footer
1048 # This tag requires that the tag GENERATE_HTML is set to YES.
1052 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1053 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1054 # the HTML output. If left blank doxygen will generate a default style sheet.
1055 # See also section "Doxygen usage" for information on how to generate the style
1058 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1060 # This tag requires that the tag GENERATE_HTML is set to YES.
1064 # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
1065 # defined cascading style sheet that is included after the standard style sheets
1067 # This is preferred over using HTML_STYLESHEET since it does not replace the
1069 # Doxygen will copy the style sheet file to the output directory. For an example
1070 # see the documentation.
1071 # This tag requires that the tag GENERATE_HTML is set to YES.
1075 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1076 # other source files which should be copied to the HTML output directory. Note
1077 # that these files will be copied to the base HTML output directory. Use the
1078 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1079 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1081 # This tag requires that the tag GENERATE_HTML is set to YES.
1085 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1086 # will adjust the colors in the stylesheet and background images according to
1088 # http://en.wikipedia.org/wiki/Hue for more information. For instance the value
1092 # This tag requires that the tag GENERATE_HTML is set to YES.
1096 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
1097 # in the HTML output. For a value of 0 the output will use grayscales only. A
1098 # value of 255 will produce the most vivid colors.
1100 # This tag requires that the tag GENERATE_HTML is set to YES.
1104 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
1105 # luminance component of the colors in the HTML output. Values below 100
1106 # gradually make the output lighter, whereas values above 100 make the output
1107 # darker. The value divided by 100 is the actual gamma applied, so 80 represents
1108 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1109 # change the gamma.
1111 # This tag requires that the tag GENERATE_HTML is set to YES.
1115 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
1116 # page will contain the date and time when the page was generated. Setting this
1117 # to NO can help when comparing the output of multiple runs.
1118 # The default value is: YES.
1119 # This tag requires that the tag GENERATE_HTML is set to YES.
1123 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1124 # documentation will contain sections that can be hidden and shown after the
1126 # The default value is: NO.
1127 # This tag requires that the tag GENERATE_HTML is set to YES.
1131 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
1132 # shown in the various tree structured indices initially; the user can expand
1133 # and collapse entries dynamically later on. Doxygen will expand the tree to
1134 # such a level that at most the specified number of entries are visible (unless
1135 # a fully collapsed tree already exceeds this amount). So setting the number of
1140 # This tag requires that the tag GENERATE_HTML is set to YES.
1144 # If the GENERATE_DOCSET tag is set to YES, additional index files will be
1148 # Makefile in the HTML output directory. Running make will produce the docset in
1149 # that directory and running make install will install the docset in
1153 # The default value is: NO.
1154 # This tag requires that the tag GENERATE_HTML is set to YES.
1158 # This tag determines the name of the docset feed. A documentation feed provides
1161 # The default value is: Doxygen generated docs.
1162 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1166 # This tag specifies a string that should uniquely identify the documentation
1168 # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
1169 # The default value is: org.doxygen.Project.
1170 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1174 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1175 # the documentation publisher. This should be a reverse domain-name style
1177 # The default value is: org.doxygen.Publisher.
1178 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1182 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1183 # The default value is: Publisher.
1184 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1188 # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1189 # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1194 # The HTML Help Workshop contains a compiler that can convert all HTML output
1196 # files are now used as the Windows 98 help format, and will replace the old
1197 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1199 # words in the documentation. The HTML workshop also contains a viewer for
1201 # The default value is: NO.
1202 # This tag requires that the tag GENERATE_HTML is set to YES.
1206 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1207 # file. You can add a path in front of the file if the result should not be
1208 # written to the html output directory.
1209 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1213 # The HHC_LOCATION tag can be used to specify the location (absolute path
1214 # including file name) of the HTML help compiler ( hhc.exe). If non-empty
1215 # doxygen will try to run the HTML help compiler on the generated index.hhp.
1216 # The file has to be specified with full path.
1217 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1221 # The GENERATE_CHI flag controls if a separate .chi index file is generated (
1222 # YES) or that it should be included in the master .chm file ( NO).
1223 # The default value is: NO.
1224 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1228 # The CHM_INDEX_ENCODING is used to encode HtmlHelp index ( hhk), content ( hhc)
1230 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1234 # The BINARY_TOC flag controls whether a binary table of contents is generated (
1235 # YES) or a normal table of contents ( NO) in the .chm file.
1236 # The default value is: NO.
1237 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1241 # The TOC_EXPAND flag can be set to YES to add extra items for group members to
1242 # the table of contents of the HTML help documentation and to the tree view.
1243 # The default value is: NO.
1244 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1248 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1251 # (.qch) of the generated HTML documentation.
1252 # The default value is: NO.
1253 # This tag requires that the tag GENERATE_HTML is set to YES.
1257 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
1258 # the file name of the resulting .qch file. The path specified is relative to
1259 # the HTML output folder.
1260 # This tag requires that the tag GENERATE_QHP is set to YES.
1264 # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1267 # The default value is: org.doxygen.Project.
1268 # This tag requires that the tag GENERATE_QHP is set to YES.
1272 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
1276 # The default value is: doc.
1277 # This tag requires that the tag GENERATE_QHP is set to YES.
1281 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1285 # This tag requires that the tag GENERATE_QHP is set to YES.
1289 # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1293 # This tag requires that the tag GENERATE_QHP is set to YES.
1297 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1300 # This tag requires that the tag GENERATE_QHP is set to YES.
1304 # The QHG_LOCATION tag can be used to specify the location of Qt's
1305 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1307 # This tag requires that the tag GENERATE_QHP is set to YES.
1311 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1312 # generated, together with the HTML files, they form an Eclipse help plugin. To
1313 # install this plugin and make it available under the help contents menu in
1314 # Eclipse, the contents of the directory containing the HTML and XML files needs
1315 # to be copied into the plugins directory of eclipse. The name of the directory
1316 # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
1317 # After copying Eclipse needs to be restarted before the help appears.
1318 # The default value is: NO.
1319 # This tag requires that the tag GENERATE_HTML is set to YES.
1323 # A unique identifier for the Eclipse help plugin. When installing the plugin
1324 # the directory name containing the HTML and XML files should also have this
1326 # The default value is: org.doxygen.Project.
1327 # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
1331 # If you want full control over the layout of the generated HTML pages it might
1332 # be necessary to disable the index and replace it with your own. The
1333 # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
1334 # of each HTML page. A value of NO enables the index and the value YES disables
1335 # it. Since the tabs in the index contain the same information as the navigation
1337 # The default value is: NO.
1338 # This tag requires that the tag GENERATE_HTML is set to YES.
1342 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1343 # structure should be generated to display hierarchical information. If the tag
1345 # index structure (just like the one that is generated for HTML Help). For this
1347 # (i.e. any modern browser). Windows users are probably better off using the
1349 # further fine-tune the look of the index. As an example, the default style
1351 # the root of the tree instead of the PROJECT_NAME. Since the tree basically has
1352 # the same information as the tab index, you could consider setting
1354 # The default value is: NO.
1355 # This tag requires that the tag GENERATE_HTML is set to YES.
1359 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
1360 # doxygen will group on one line in the generated HTML documentation.
1362 # Note that a value of 0 will completely suppress the enum values from appearing
1363 # in the overview section.
1365 # This tag requires that the tag GENERATE_HTML is set to YES.
1369 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
1370 # to set the initial width (in pixels) of the frame in which the tree is shown.
1372 # This tag requires that the tag GENERATE_HTML is set to YES.
1376 # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open links to
1378 # The default value is: NO.
1379 # This tag requires that the tag GENERATE_HTML is set to YES.
1383 # Use this tag to change the font size of LaTeX formulas included as images in
1384 # the HTML documentation. When you change the font size after a successful
1385 # doxygen run you need to manually remove any form_*.png images from the HTML
1388 # This tag requires that the tag GENERATE_HTML is set to YES.
1392 # Use the FORMULA_TRANPARENT tag to determine whether or not the images
1397 # the HTML output directory before the changes have effect.
1398 # The default value is: YES.
1399 # This tag requires that the tag GENERATE_HTML is set to YES.
1403 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1404 # http://www.mathjax.org) which uses client side Javascript for the rendering
1406 # installed or if you want to formulas look prettier in the HTML output. When
1407 # enabled you may also need to install MathJax separately and configure the path
1408 # to it using the MATHJAX_RELPATH option.
1409 # The default value is: NO.
1410 # This tag requires that the tag GENERATE_HTML is set to YES.
1414 # When MathJax is enabled you can set the default output format to be used for
1415 # the MathJax output. See the MathJax site (see:
1417 # Possible values are: HTML-CSS (which is slower, but has the best
1419 # The default value is: HTML-CSS.
1420 # This tag requires that the tag USE_MATHJAX is set to YES.
1424 # When MathJax is enabled you need to specify the location relative to the HTML
1425 # output directory using the MATHJAX_RELPATH option. The destination directory
1426 # should contain the MathJax.js script. For instance, if the mathjax directory
1427 # is located at the same level as the HTML output directory, then
1428 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1429 # Content Delivery Network so you can quickly see the result without installing
1432 # The default value is: http://cdn.mathjax.org/mathjax/latest.
1433 # This tag requires that the tag USE_MATHJAX is set to YES.
1437 # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
1440 # This tag requires that the tag USE_MATHJAX is set to YES.
1444 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1445 # of code that will be used on startup of the MathJax code. See the MathJax site
1447 # example see the documentation.
1448 # This tag requires that the tag USE_MATHJAX is set to YES.
1452 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1453 # the HTML output. The underlying search engine uses javascript and DHTML and
1457 # For large projects the javascript based search engine can be slow, then
1459 # search using the keyboard; to jump to the search box use <access key> + S
1460 # (what the <access key> is depends on the OS and browser, but it is typically
1461 # <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
1462 # key> to jump into the search results window, the results can be navigated
1463 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1464 # the search. The filter options can be selected when the cursor is inside the
1465 # search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
1466 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1468 # The default value is: YES.
1469 # This tag requires that the tag GENERATE_HTML is set to YES.
1473 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1475 # are two flavours of web server based searching depending on the
1477 # searching and an index file used by the script. When EXTERNAL_SEARCH is
1478 # enabled the indexing and searching needs to be provided by external tools. See
1479 # the section "External Indexing and Searching" for details.
1480 # The default value is: NO.
1481 # This tag requires that the tag SEARCHENGINE is set to YES.
1485 # When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
1486 # script for searching. Instead the search results are written to an XML file
1488 # external search engine pointed to by the SEARCHENGINE_URL option to obtain the
1492 # (doxysearch.cgi) which are based on the open source search engine library
1495 # See the section "External Indexing and Searching" for details.
1496 # The default value is: NO.
1497 # This tag requires that the tag SEARCHENGINE is set to YES.
1501 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
1502 # which will return the search results when EXTERNAL_SEARCH is enabled.
1505 # (doxysearch.cgi) which are based on the open source search engine library
1506 # Xapian (see: http://xapian.org/). See the section "External Indexing and
1508 # This tag requires that the tag SEARCHENGINE is set to YES.
1512 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
1513 # search data is written to a file for indexing by an external tool. With the
1514 # SEARCHDATA_FILE tag the name of this file can be specified.
1515 # The default file is: searchdata.xml.
1516 # This tag requires that the tag SEARCHENGINE is set to YES.
1520 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
1521 # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
1523 # projects and redirect the results back to the right project.
1524 # This tag requires that the tag SEARCHENGINE is set to YES.
1528 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1529 # projects other than the one defined by this configuration file, but that are
1530 # all added to the same external search index. Each project needs to have a
1531 # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
1532 # to a relative location where the documentation can be found. The format is:
1534 # This tag requires that the tag SEARCHENGINE is set to YES.
1539 # Configuration options related to the LaTeX output
1542 # If the GENERATE_LATEX tag is set to YES doxygen will generate LaTeX output.
1543 # The default value is: YES.
1547 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1548 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1550 # The default directory is: latex.
1551 # This tag requires that the tag GENERATE_LATEX is set to YES.
1555 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1559 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1560 # written to the output directory.
1561 # The default file is: latex.
1562 # This tag requires that the tag GENERATE_LATEX is set to YES.
1566 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
1568 # The default file is: makeindex.
1569 # This tag requires that the tag GENERATE_LATEX is set to YES.
1573 # If the COMPACT_LATEX tag is set to YES doxygen generates more compact LaTeX
1576 # The default value is: NO.
1577 # This tag requires that the tag GENERATE_LATEX is set to YES.
1581 # The PAPER_TYPE tag can be used to set the paper type that is used by the
1585 # The default value is: a4.
1586 # This tag requires that the tag GENERATE_LATEX is set to YES.
1590 # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
1591 # that should be included in the LaTeX output. To get the times font for
1595 # This tag requires that the tag GENERATE_LATEX is set to YES.
1599 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1600 # generated LaTeX document. The header should contain everything until the first
1602 # section "Doxygen usage" for information on how to let doxygen write the
1605 # Note: Only use a user-defined header if you know what you are doing! The
1606 # following commands have a special meaning inside the header: $title,
1608 # replace them by respectively the title of the page, the current date and time,
1609 # only the current date, the version number of doxygen, the project name (see
1610 # PROJECT_NAME), or the project number (see PROJECT_NUMBER).
1611 # This tag requires that the tag GENERATE_LATEX is set to YES.
1615 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1616 # generated LaTeX document. The footer should contain everything after the last
1620 # This tag requires that the tag GENERATE_LATEX is set to YES.
1624 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1625 # other source files which should be copied to the LATEX_OUTPUT output
1626 # directory. Note that the files will be copied as-is; there are no commands or
1628 # This tag requires that the tag GENERATE_LATEX is set to YES.
1632 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
1633 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
1634 # contain links (just like the HTML output) instead of page references. This
1635 # makes the output suitable for online browsing using a PDF viewer.
1636 # The default value is: YES.
1637 # This tag requires that the tag GENERATE_LATEX is set to YES.
1641 # If the LATEX_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
1642 # the PDF file directly from the LaTeX files. Set this option to YES to get a
1644 # The default value is: YES.
1645 # This tag requires that the tag GENERATE_LATEX is set to YES.
1649 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
1650 # command to the generated LaTeX files. This will instruct LaTeX to keep running
1651 # if errors occur, instead of asking the user for help. This option is also used
1653 # The default value is: NO.
1654 # This tag requires that the tag GENERATE_LATEX is set to YES.
1658 # If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
1659 # index chapters (such as File Index, Compound Index, etc.) in the output.
1660 # The default value is: NO.
1661 # This tag requires that the tag GENERATE_LATEX is set to YES.
1665 # If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
1666 # code with syntax highlighting in the LaTeX output.
1670 # The default value is: NO.
1671 # This tag requires that the tag GENERATE_LATEX is set to YES.
1675 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1678 # The default value is: plain.
1679 # This tag requires that the tag GENERATE_LATEX is set to YES.
1684 # Configuration options related to the RTF output
1687 # If the GENERATE_RTF tag is set to YES doxygen will generate RTF output. The
1690 # The default value is: NO.
1694 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
1695 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1697 # The default directory is: rtf.
1698 # This tag requires that the tag GENERATE_RTF is set to YES.
1702 # If the COMPACT_RTF tag is set to YES doxygen generates more compact RTF
1705 # The default value is: NO.
1706 # This tag requires that the tag GENERATE_RTF is set to YES.
1710 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
1711 # contain hyperlink fields. The RTF file will contain links (just like the HTML
1712 # output) instead of page references. This makes the output suitable for online
1717 # The default value is: NO.
1718 # This tag requires that the tag GENERATE_RTF is set to YES.
1726 # See also section "Doxygen usage" for information on how to generate the
1728 # This tag requires that the tag GENERATE_RTF is set to YES.
1732 # Set optional variables used in the generation of an RTF document. Syntax is
1735 # This tag requires that the tag GENERATE_RTF is set to YES.
1740 # Configuration options related to the man page output
1743 # If the GENERATE_MAN tag is set to YES doxygen will generate man pages for
1745 # The default value is: NO.
1749 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
1750 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1751 # it. A directory man3 will be created inside the directory specified by
1753 # The default directory is: man.
1754 # This tag requires that the tag GENERATE_MAN is set to YES.
1758 # The MAN_EXTENSION tag determines the extension that is added to the generated
1759 # man pages. In case the manual section does not start with a number, the number
1760 # 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
1762 # The default value is: .3.
1763 # This tag requires that the tag GENERATE_MAN is set to YES.
1767 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
1768 # will generate one additional man file for each entity documented in the real
1769 # man page(s). These additional files only source the real man page, but without
1770 # them the man command would be unable to find the correct page.
1771 # The default value is: NO.
1772 # This tag requires that the tag GENERATE_MAN is set to YES.
1777 # Configuration options related to the XML output
1780 # If the GENERATE_XML tag is set to YES doxygen will generate an XML file that
1781 # captures the structure of the code including all documentation.
1782 # The default value is: NO.
1786 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
1787 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1789 # The default directory is: xml.
1790 # This tag requires that the tag GENERATE_XML is set to YES.
1794 # If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program
1796 # the XML output. Note that enabling this will significantly increase the size
1797 # of the XML output.
1798 # The default value is: YES.
1799 # This tag requires that the tag GENERATE_XML is set to YES.
1804 # Configuration options related to the DOCBOOK output
1807 # If the GENERATE_DOCBOOK tag is set to YES doxygen will generate Docbook files
1809 # The default value is: NO.
1813 # The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
1814 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1816 # The default directory is: docbook.
1817 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
1822 # Configuration options for the AutoGen Definitions output
1825 # If the GENERATE_AUTOGEN_DEF tag is set to YES doxygen will generate an AutoGen
1826 # Definitions (see http://autogen.sf.net) file that captures the structure of
1827 # the code including all documentation. Note that this feature is still
1828 # experimental and incomplete at the moment.
1829 # The default value is: NO.
1834 # Configuration options related to the Perl module output
1837 # If the GENERATE_PERLMOD tag is set to YES doxygen will generate a Perl module
1838 # file that captures the structure of the code including all documentation.
1840 # Note that this feature is still experimental and incomplete at the moment.
1841 # The default value is: NO.
1845 # If the PERLMOD_LATEX tag is set to YES doxygen will generate the necessary
1847 # output from the Perl module output.
1848 # The default value is: NO.
1849 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
1853 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be nicely
1855 # understand what is going on. On the other hand, if this tag is set to NO the
1856 # size of the Perl module output will be much smaller and Perl will parse it
1857 # just the same.
1858 # The default value is: YES.
1859 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
1863 # The names of the make variables in the generated doxyrules.make file are
1864 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
1865 # so different doxyrules.make files included by the same Makefile don't
1867 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
1872 # Configuration options related to the preprocessor
1875 # If the ENABLE_PREPROCESSING tag is set to YES doxygen will evaluate all
1876 # C-preprocessor directives found in the sources and include files.
1877 # The default value is: YES.
1881 # If the MACRO_EXPANSION tag is set to YES doxygen will expand all macro names
1882 # in the source code. If set to NO only conditional compilation will be
1885 # The default value is: NO.
1886 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1890 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
1891 # the macro expansion is limited to the macros specified with the PREDEFINED and
1893 # The default value is: NO.
1894 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1898 # If the SEARCH_INCLUDES tag is set to YES the includes files in the
1900 # The default value is: YES.
1901 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1905 # The INCLUDE_PATH tag can be used to specify one or more directories that
1906 # contain include files that are not input files but should be processed by the
1908 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
1912 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1913 # patterns (like *.h and *.hpp) to filter out the header-files in the
1914 # directories. If left blank, the patterns specified with FILE_PATTERNS will be
1916 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1920 # The PREDEFINED tag can be used to specify one or more macro names that are
1921 # defined before the preprocessor is started (similar to the -D option of e.g.
1922 # gcc). The argument of the tag is a list of macros of the form: name or
1923 # name=definition (no spaces). If the definition and the "=" are omitted, "=1"
1925 # recursively expanded use the := operator instead of the = operator.
1926 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1930 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
1931 # tag can be used to specify a list of macro names that should be expanded. The
1932 # macro definition that is found in the sources will be used. Use the PREDEFINED
1933 # tag if you want to use a different macro definition that overrules the
1934 # definition found in the source code.
1935 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1939 # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
1942 # typically used for boiler-plate code, and will confuse the parser if not
1944 # The default value is: YES.
1945 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1953 # The TAGFILES tag can be used to specify one or more tag files. For each tag
1954 # file the location of the external documentation should be added. The format of
1957 # Adding location for the tag files is done as follows:
1959 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
1960 # section "Linking to external documentation" for more information about the use
1962 # Note: Each tag file must have an unique name (where the name does NOT include
1963 # the path). If a tag file is not located in the directory in which doxygen is
1964 # run, you must also specify the path to the tagfile here.
1969 # tag file that is based on the input files it reads. See section "Linking to
1970 # external documentation" for more information about the usage of tag files.
1974 # If the ALLEXTERNALS tag is set to YES all external class will be listed in the
1975 # class index. If set to NO only the inherited external classes will be listed.
1976 # The default value is: NO.
1980 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed in
1981 # the modules index. If set to NO, only the current project's groups will be
1983 # The default value is: YES.
1987 # If the EXTERNAL_PAGES tag is set to YES all external pages will be listed in
1988 # the related pages index. If set to NO, only the current project's pages will
1990 # The default value is: YES.
1994 # The PERL_PATH should be the absolute path and name of the perl script
1995 # interpreter (i.e. the result of 'which perl').
1996 # The default file (with absolute path) is: /usr/bin/perl.
2001 # Configuration options related to the dot tool
2004 # If the CLASS_DIAGRAMS tag is set to YES doxygen will generate a class diagram
2005 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2006 # NO turns the diagrams off. Note that this option also works with HAVE_DOT
2009 # The default value is: YES.
2013 # You can define message sequence charts within doxygen comments using the \msc
2014 # command. Doxygen will then run the mscgen tool (see:
2015 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2016 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
2017 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2023 # then run dia to produce the diagram and insert it in the documentation. The
2024 # DIA_PATH tag allows you to specify the directory where the dia binary resides.
2025 # If left empty dia is assumed to be found in the default search path.
2029 # If set to YES, the inheritance and collaboration graphs will hide inheritance
2030 # and usage relations if the target is undocumented or is not a class.
2031 # The default value is: YES.
2035 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
2036 # available from the path. This tool is part of Graphviz (see:
2038 # Bell Labs. The other options in this section have no effect if this option is
2040 # The default value is: NO.
2044 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
2045 # to run in parallel. When set to 0 doxygen will base this on the number of
2046 # processors available in the system. You can set it explicitly to a value
2047 # larger than 0 to get control over the balance between CPU load and processing
2050 # This tag requires that the tag HAVE_DOT is set to YES.
2054 # When you want a differently looking font n the dot files that doxygen
2055 # generates you can specify the font name using DOT_FONTNAME. You need to make
2056 # sure dot is able to find the font, which can be done by putting it in a
2057 # standard location or by setting the DOTFONTPATH environment variable or by
2058 # setting DOT_FONTPATH to the directory containing the font.
2059 # The default value is: Helvetica.
2060 # This tag requires that the tag HAVE_DOT is set to YES.
2064 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2067 # This tag requires that the tag HAVE_DOT is set to YES.
2071 # By default doxygen will tell dot to use the default font as specified with
2073 # the path where dot can find it using this tag.
2074 # This tag requires that the tag HAVE_DOT is set to YES.
2078 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2079 # each documented class showing the direct and indirect inheritance relations.
2080 # Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
2081 # The default value is: YES.
2082 # This tag requires that the tag HAVE_DOT is set to YES.
2086 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
2087 # graph for each documented class showing the direct and indirect implementation
2088 # dependencies (inheritance, containment, and class references variables) of the
2090 # The default value is: YES.
2091 # This tag requires that the tag HAVE_DOT is set to YES.
2095 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2096 # groups, showing the direct groups dependencies.
2097 # The default value is: YES.
2098 # This tag requires that the tag HAVE_DOT is set to YES.
2102 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
2103 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2105 # The default value is: NO.
2106 # This tag requires that the tag HAVE_DOT is set to YES.
2110 # If the UML_LOOK tag is enabled, the fields and methods are shown inside the
2111 # class node. If there are many fields or methods and many nodes the graph may
2112 # become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
2113 # number of items for each type to make the size more manageable. Set this to 0
2114 # for no limit. Note that the threshold may be exceeded by 50% before the limit
2115 # is enforced. So when you set the threshold to 10, up to 15 fields may appear,
2116 # but if the number exceeds 15, the total amount of fields shown is limited to
2119 # This tag requires that the tag HAVE_DOT is set to YES.
2123 # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
2124 # collaboration graphs will show the relations between templates and their
2126 # The default value is: NO.
2127 # This tag requires that the tag HAVE_DOT is set to YES.
2131 # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
2132 # YES then doxygen will generate a graph for each documented file showing the
2133 # direct and indirect include dependencies of the file with other documented
2135 # The default value is: YES.
2136 # This tag requires that the tag HAVE_DOT is set to YES.
2140 # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
2142 # the direct and indirect include dependencies of the file with other documented
2144 # The default value is: YES.
2145 # This tag requires that the tag HAVE_DOT is set to YES.
2149 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
2152 # Note that enabling this option will significantly increase the time of a run.
2154 # functions only using the \callgraph command.
2155 # The default value is: NO.
2156 # This tag requires that the tag HAVE_DOT is set to YES.
2160 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
2163 # Note that enabling this option will significantly increase the time of a run.
2165 # functions only using the \callergraph command.
2166 # The default value is: NO.
2167 # This tag requires that the tag HAVE_DOT is set to YES.
2171 # If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
2173 # The default value is: YES.
2174 # This tag requires that the tag HAVE_DOT is set to YES.
2178 # If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
2179 # dependencies a directory has on other directories in a graphical way. The
2180 # dependency relations are determined by the #include relations between the
2181 # files in the directories.
2182 # The default value is: YES.
2183 # This tag requires that the tag HAVE_DOT is set to YES.
2187 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
2190 # to make the SVG files visible in IE 9+ (other browsers do not have this
2193 # The default value is: png.
2194 # This tag requires that the tag HAVE_DOT is set to YES.
2204 # the SVG files visible. Older versions of IE do not have SVG support.
2205 # The default value is: NO.
2206 # This tag requires that the tag HAVE_DOT is set to YES.
2210 # The DOT_PATH tag can be used to specify the path where the dot tool can be
2211 # found. If left blank, it is assumed the dot tool can be found in the path.
2212 # This tag requires that the tag HAVE_DOT is set to YES.
2216 # The DOTFILE_DIRS tag can be used to specify one or more directories that
2217 # contain dot files that are included in the documentation (see the \dotfile
2219 # This tag requires that the tag HAVE_DOT is set to YES.
2223 # The MSCFILE_DIRS tag can be used to specify one or more directories that
2224 # contain msc files that are included in the documentation (see the \mscfile
2229 # The DIAFILE_DIRS tag can be used to specify one or more directories that
2230 # contain dia files that are included in the documentation (see the \diafile
2235 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2236 # that will be shown in the graph. If the number of nodes in a graph becomes
2237 # larger than this value, doxygen will truncate the graph, which is visualized
2238 # by representing a node as a red box. Note that doxygen if the number of direct
2239 # children of the root node in a graph is already larger than
2240 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
2241 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2243 # This tag requires that the tag HAVE_DOT is set to YES.
2247 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
2248 # generated by dot. A depth value of 3 means that only nodes reachable from the
2250 # further from the root node will be omitted. Note that setting this option to 1
2251 # or 2 may greatly reduce the computation time needed for large code bases. Also
2252 # note that the size of a graph can be further restricted by
2255 # This tag requires that the tag HAVE_DOT is set to YES.
2259 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
2261 # to support this out of the box.
2263 # Warning: Depending on the platform used, enabling this option may lead to
2264 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2266 # The default value is: NO.
2267 # This tag requires that the tag HAVE_DOT is set to YES.
2271 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
2272 # files in one run (i.e. multiple -o and -T options on the command line). This
2275 # The default value is: NO.
2276 # This tag requires that the tag HAVE_DOT is set to YES.
2280 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
2281 # explaining the meaning of the various boxes and arrows in the dot generated
2283 # The default value is: YES.
2284 # This tag requires that the tag HAVE_DOT is set to YES.
2288 # If the DOT_CLEANUP tag is set to YES doxygen will remove the intermediate dot
2289 # files that are used to generate the various graphs.
2290 # The default value is: YES.
2291 # This tag requires that the tag HAVE_DOT is set to YES.