Lines Matching full:be
3 # This file describes the settings to be used by the documentation system
9 # All text after a single hash (#) is considered a comment and will be ignored.
12 # For lists, items can also be appended using:
14 # Values that contain spaces should be placed between quotes (\" \").
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
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.
66 # option can be useful when feeding doxygen a huge amount of source files, where
75 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
107 # brief descriptions will be completely suppressed.
114 # as the leading text of the brief description, will be stripped from the text
143 # operators of the base classes will not be shown.
150 # shortest path that makes the file name unique will be used
155 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
157 # part of the path. The tag can be used to show relative paths in the file list.
162 # will be relative from the directory where doxygen is started.
167 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
177 # less readable) file names. This can be useful is your file systems doesn't
200 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
202 # a brief description. This used to be the default behavior. The new default is
219 # page for each member. If set to NO, the documentation of a member will be part
225 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
231 # This tag can be used to specify a number of aliases that act as commands in
243 # This tag can be used to specify a number of word-keyword mappings (TCL only).
251 # instance, some of the names that are used will be different. The list of all
252 # members will be omitted, etc.
259 # for that language. For instance, namespaces will be presented as packages,
308 # be prevented in individual cases by putting a % sign in front of the word or
351 # all members of a group must be documented explicitly.
364 # (for instance a group of public functions) to be put as a subgroup of that
366 # subgrouping. Alternatively, this can be done per class using the
384 # with only public data fields or simple typedef fields will be shown inline in
397 # namespace, or class. And the struct will be named TypeS. This can typically be
404 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
405 # cache is used to resolve symbols given their name and scope. Since this can be
423 # class members and static file members will be hidden unless the
432 # be included in the documentation.
438 # scope will be included in the documentation.
443 # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
450 # locally in source files will be included in the documentation. If set to NO,
465 # If this flag is set to YES, the members of anonymous namespaces will be
467 # 'anonymous_namespace{file}', where file will be replaced with the base name of
476 # members will be included in the various overviews, but no documentation
484 # to NO, these classes will be included in the various overviews. This option
491 # (class|struct|union) declarations. If set to NO, these declarations will be
499 # blocks will be appended to the function's detailed documentation block.
506 # will be excluded. Set it to YES to include the internal documentation.
522 # scope will be hidden.
529 # YES the compound reference will be hidden.
593 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
595 # be sorted only by class name, not including the namespace part.
613 # The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo
619 # The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test
625 # The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug
631 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO)
638 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
647 # it will be hidden. Use a value of 0 to hide initializers completely. The
648 # appearance of the value of individual variables and macros / defines can be
676 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
686 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
691 # will be used as the name of the layout file.
699 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
700 # the reference definitions. This must be a list of .bib files. The .bib
702 # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
703 # For LaTeX the style of the bibliography can be controlled using
713 # The QUIET tag can be used to turn on/off the messages that are generated to
720 # The WARNINGS tag can be used to turn on/off the warning messages that are
731 # will automatically be disabled.
744 # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
760 # will be replaced by the file and line number from which the warning originated
762 # be replaced by the version of the file (if it could be obtained via
768 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
769 # messages should be written. If left blank the output is written to standard
786 # This tag can be used to specify the character encoding of the source files
832 # The RECURSIVE tag can be used to specify whether or not subdirectories should
833 # be searched for input files as well.
838 # The EXCLUDE tag can be used to specify files and/or directories that should be
847 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
863 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
864 # (namespaces, classes, functions, etc.) that should be excluded from the
865 # output. The symbol name can be a fully qualified name, a word, or if the
874 # The EXAMPLE_PATH tag can be used to specify one or more files or directories
887 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
888 # searched for input files to be used with the \include or \dontinclude commands
894 # The IMAGE_PATH tag can be used to specify one or more files or directories
895 # that contain images that are to be included in the documentation (see the
900 # The INPUT_FILTER tag can be used to specify a program that doxygen should
909 # will be ignored.
913 # or removed, the anchors will not be placed correctly.
921 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
935 # INPUT_FILTER) will also be used to filter the input files that are used for
941 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
950 # is part of the input, its contents will be placed on the main page
951 # (index.html). This can be useful if you have a project on for instance GitHub
960 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
961 # generated. Documented entities will be cross-referenced with these sources.
983 # function all documented functions referencing it will be listed.
989 # all documented entities called/used by that function will be listed.
1025 # tools must be available from the command line (i.e. in the search path).
1044 # cost of reduced performance. This can be particularly helpful with template
1055 # the include paths will already be set by doxygen for the files and directories
1066 # compounds will be generated. Enable this if the project contains a lot of
1072 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
1073 # which the alphabetical index list will be split.
1080 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1081 # can be used to specify a prefix (or a list of prefixes) that should be ignored
1096 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1097 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1104 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1111 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1131 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1134 # footer and what special commands can be used inside the footer. See also
1141 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1142 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1153 # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1166 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1167 # other source files which should be copied to the HTML output directory. Note
1168 # that these files will be copied to the base HTML output directory. Use the
1171 # files will be copied as-is; there are no commands or markers available.
1216 # documentation will contain sections that can be hidden and shown after the
1236 # If the GENERATE_DOCSET tag is set to YES, additional index files will be
1237 # generated that can be used as input for Apple's Xcode 3 integrated development
1252 # (such as a company or product suite) can be grouped.
1259 # set bundle. This should be a reverse domain-name style string, e.g.
1267 # the documentation publisher. This should be a reverse domain-name style
1282 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1298 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1299 # file. You can add a path in front of the file if the result should not be
1305 # The HHC_LOCATION tag can be used to specify the location (absolute path
1308 # The file has to be specified with full path.
1314 # (YES) or that it should be included in the master .chm file (NO).
1334 # The TOC_EXPAND flag can be set to YES to add extra items for group members to
1342 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1343 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1350 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
1397 # The QHG_LOCATION tag can be used to specify the location of Qt's
1404 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1408 # to be copied into the plugins directory of eclipse. The name of the directory
1409 # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
1410 # After copying Eclipse needs to be restarted before the help appears.
1425 # be necessary to disable the index and replace it with your own. The
1426 # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
1436 # structure should be generated to display hierarchical information. If the tag
1437 # value is set to YES, a side panel will be generated containing a tree-like
1452 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
1462 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
1479 # output directory to force them to be regenerated.
1507 # When MathJax is enabled you can set the default output format to be used for
1521 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1530 # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
1531 # extension names that should be enabled during MathJax rendering. For example
1537 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1538 # of code that will be used on startup of the MathJax code. See the MathJax site
1549 # there is already a search function so this one should typically be disabled.
1550 # For large projects the javascript based search engine can be slow, then
1555 # key> to jump into the search results window, the results can be navigated
1557 # the search. The filter options can be selected when the cursor is inside the
1566 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1571 # and searching needs to be provided by external tools. See the section
1580 # which needs to be processed by an external indexer. Doxygen will invoke an
1607 # SEARCHDATA_FILE tag the name of this file can be specified.
1614 # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
1621 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1625 # to a relative location where the documentation can be found. The format is:
1640 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1641 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1648 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1659 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
1667 # documents. This may be useful for small projects and may help to save some
1674 # The PAPER_TYPE tag can be used to set the paper type that is used by the
1683 # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
1684 # that should be included in the LaTeX output. The package can be specified just
1685 # by its name or with the correct syntax as to be used with the LaTeX
1690 # If left blank no extra packages will be included.
1695 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1711 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1715 # special commands can be used inside the footer.
1722 # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1733 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1734 # other source files which should be copied to the LATEX_OUTPUT output
1735 # directory. Note that the files will be copied as-is; there are no commands or
1784 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1811 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
1812 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1820 # documents. This may be useful for small projects and may help to save some
1850 # similar to doxygen's config file. A template extensions file can be generated
1876 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
1877 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1878 # it. A directory man3 will be created inside the directory specified by
1904 # them the man command would be unable to find the correct page.
1920 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
1921 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1942 # that can be used to generate PDF.
1947 # The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
1948 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1989 # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
1996 # If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely
1997 # formatted so it can be parsed by a human reader. This is useful if you want to
1999 # size of the Perl module output will be much smaller and Perl will parse it
2025 # in the source code. If set to NO, only conditional compilation will be
2026 # performed. Macro expansion can be done in a controlled way by setting
2042 # INCLUDE_PATH will be searched if a #include is found.
2048 # The INCLUDE_PATH tag can be used to specify one or more directories that
2049 # contain include files that are not input files but should be processed by the
2057 # directories. If left blank, the patterns specified with FILE_PATTERNS will be
2063 # The PREDEFINED tag can be used to specify one or more macro names that are
2121 # tag can be used to specify a list of macro names that should be expanded. The
2122 # macro definition that is found in the sources will be used. Use the PREDEFINED
2143 # The TAGFILES tag can be used to specify one or more tag files. For each tag
2144 # file the location of the external documentation should be added. The format of
2149 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
2164 # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
2165 # the class index. If set to NO, only the inherited external classes will be
2171 # If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed
2172 # in the modules index. If set to NO, only the current project's groups will be
2178 # If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
2180 # be listed.
2185 # The PERL_PATH should be the absolute path and name of the perl script
2208 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2216 # If left empty dia is assumed to be found in the default search path.
2247 # sure dot is able to find the font, which can be done by putting it in a
2255 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2303 # become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
2305 # for no limit. Note that the threshold may be exceeded by 50% before the limit
2344 # So in most cases it will be better to enable call graphs for selected
2345 # functions only using the \callgraph command. Disabling a call graph can be
2356 # So in most cases it will be better to enable caller graphs for selected
2357 # functions only using the \callergraph command. Disabling a caller graph can be
2380 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
2397 # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
2409 # The DOT_PATH tag can be used to specify the path where the dot tool can be
2410 # found. If left blank, it is assumed the dot tool can be found in the path.
2415 # The DOTFILE_DIRS tag can be used to specify one or more directories that
2422 # The MSCFILE_DIRS tag can be used to specify one or more directories that
2428 # The DIAFILE_DIRS tag can be used to specify one or more directories that
2434 # When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
2447 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2448 # that will be shown in the graph. If the number of nodes in a graph becomes
2452 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
2453 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2459 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
2461 # root by following a path via at most 3 edges will be shown. Nodes that lay
2462 # further from the root node will be omitted. Note that setting this option to 1
2464 # note that the size of a graph can be further restricted by