Lines Matching refs:be
3 # This file describes the settings to be used by the documentation system
6 # All text after a hash (#) is considered a comment and will be ignored
9 # For lists items can also be appended using:
11 # Values that contain spaces should be placed between quotes (" ")
22 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
23 # This could be handy for archiving the generated documentation or
29 # base path where the generated documentation will be put.
30 # If a relative path is entered, it will be relative to the location
31 # where doxygen was started. If left blank the current directory will be used.
38 # Enabling this option can be useful when feeding doxygen a huge amount of
56 # This tag can be used to specify the encoding used in the generated output.
76 # brief descriptions will be completely suppressed.
82 # in this list, if found as the leading text of the brief description, will be
101 # operators of the base classes will not be shown.
107 # to NO the shortest path that makes the file name unique will be used.
112 # can be used to strip a user-defined part of the path. Stripping is
114 # the path. The tag can be used to show relative paths in the file list.
120 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
130 # (but less readable) file names. This can be useful is your file systems
143 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
145 # comments) as a brief description. This used to be the default behaviour.
167 # all members of a group must be documented explicitly.
173 # be part of the file/class/namespace that contains it.
177 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
182 # This tag can be used to specify a number of aliases that acts
195 # For instance, some of the names that are used will be different. The list
196 # of all members will be omitted, etc.
202 # For instance, namespaces will be presented as packages, qualified scopes
208 # the same type (for instance a group of public functions) to be put as a
210 # NO to prevent subgrouping. Alternatively, this can be done per class using
221 # Private class members and static file members will be hidden unless
227 # will be included in the documentation.
232 # will be included in the documentation.
237 # defined locally in source files will be included in the documentation.
251 # If set to NO (the default) these members will be included in the
259 # If set to NO (the default) these classes will be included in the various
266 # If set to NO (the default) these declarations will be included in the
273 # If set to NO (the default) these blocks will be appended to the
280 # to NO (the default) then the documentation will be excluded.
295 # documentation. If set to YES the scope will be hidden.
324 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
326 # NO (the default), the class list will be sorted only by class name,
334 # The GENERATE_TODOLIST tag can be used to enable (YES) or
340 # The GENERATE_TESTLIST tag can be used to enable (YES) or
346 # The GENERATE_BUGLIST tag can be used to enable (YES) or
352 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
358 # The ENABLED_SECTIONS tag can be used to enable conditional
366 # here it will be hidden. Use a value of 0 to hide initializers completely.
368 # documentation can be controlled using \showinitializer or \hideinitializer
385 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
399 # The QUIET tag can be used to turn on/off the messages that are generated
404 # The WARNINGS tag can be used to turn on/off the warning messages that are
412 # automatically be disabled.
423 # This WARN_NO_PARAMDOC option can be abled to get warnings for
433 # tags, which will be replaced by the file and line number from which the
435 # $version, which will be replaced by the version of the file (if it could
436 # be obtained via FILE_VERSION_FILTER)
440 # The WARN_LOGFILE tag can be used to specify a file to which warning
441 # and error messages should be written. If left blank the output is written
450 # The INPUT tag can be used to specify the files and/or directories that contain
466 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
467 # should be searched for input files as well. Possible values are YES and NO.
472 # The EXCLUDE tag can be used to specify files and/or directories that should
478 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
490 # The EXAMPLE_PATH tag can be used to specify one or more files or
503 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
504 # searched for input files to be used with the \include or \dontinclude
510 # The IMAGE_PATH tag can be used to specify one or more files or
516 # The INPUT_FILTER tag can be used to specify a program that doxygen should
521 # to standard output. If FILTER_PATTERNS is specified, this tag will be
526 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
536 # INPUT_FILTER) will be used to filter the input files when producing source
546 # be generated. Documented entities will be cross-referenced with these sources.
565 # functions referencing it will be listed.
571 # called/used by that function will be listed.
586 # of all compounds will be generated. Enable this if the project
592 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
593 # in which this list will be split (can be a number in the range [1..20])
598 # classes will be put under the same header in the alphabetical index.
599 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
600 # should be ignored while generating the index headers.
613 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
614 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
615 # put in front of it. If left blank `html' will be used as the default path.
619 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
625 # The HTML_HEADER tag can be used to specify a personal HTML header for
631 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
637 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
638 # style sheet that is used by each HTML page. It can be used to
642 # stylesheet in the HTML output directory as well, or it will be erased!
647 # files or namespaces will be aligned in HTML using tables. If set to
648 # NO a bullet list will be used.
653 # will be generated that can be used as input for tools like the
660 # be used to specify the file name of the resulting .chm file. You
661 # can add a path in front of the file if the result should not be
667 # be used to specify the location (absolute path including file name) of
675 # it should be included in the master .chm file (NO).
685 # The TOC_EXPAND flag can be set to YES to add extra items for group members
690 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
696 # This tag can be used to set the number of enum values (range [1..20])
701 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
710 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
725 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
726 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
727 # put in front of it. If left blank `latex' will be used as the default path.
731 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
732 # invoked. If left blank `latex' will be used as the default command name.
736 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
737 # generate index for LaTeX. If left blank `makeindex' will be used as the
743 # LaTeX documents. This may be useful for small projects and may help to
748 # The PAPER_TYPE tag can be used to set the paper type that is used
750 # executive. If left blank a4wide will be used.
754 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
755 # packages that should be included in the LaTeX output.
759 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
773 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
802 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
803 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
804 # put in front of it. If left blank `rtf' will be used as the default path.
809 # RTF documents. This may be useful for small projects and may help to
843 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
844 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
845 # put in front of it. If left blank `man' will be used as the default path.
858 # would be unable to find the correct page. The default is NO.
872 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
873 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
874 # put in front of it. If left blank `xml' will be used as the default path.
878 # The XML_SCHEMA tag can be used to specify an XML schema,
879 # which can be used by a validating XML parser to check the
884 # The XML_DTD tag can be used to specify an XML DTD,
885 # which can be used by a validating XML parser to check the
922 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
927 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
928 # nicely formatted so it can be parsed by a human reader. This is useful
930 # tag is set to NO the size of the Perl module output will be much smaller
954 # compilation will be performed. Macro expansion can be done in a controlled
966 # in the INCLUDE_PATH (see below) will be search if a #include is found.
970 # The INCLUDE_PATH tag can be used to specify one or more directories that
971 # contain include files that are not input files but should be processed by
979 # be used.
983 # The PREDEFINED tag can be used to specify one or more macro names that
994 # this tag can be used to specify a list of macro names that should be expanded.
995 # The macro definition that is found in the sources will be used.
1012 # The TAGFILES option can be used to specify one or more tagfiles.
1014 # can be added for each tagfile. The format of a tag file without
1019 # where "loc1" and "loc2" can be relative or absolute paths or
1021 # does not have to be run to correct the links.
1034 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1036 # will be listed.
1040 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1042 # be listed.
1046 # The PERL_PATH should be the absolute path and name of the perl script
1124 # So in most cases it will be better to enable call graphs for selected
1141 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1143 # If left blank png will be used.
1147 # The tag DOT_PATH can be used to specify the path where the dot tool can be
1148 # found. If left blank, it is assumed the dot tool can be found in the path.
1152 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1158 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1166 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1174 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1176 # from the root by following a path via at most 3 edges will be shown. Nodes
1177 # that lay further from the root node will be omitted. Note that setting this
1179 # code bases. Also note that a graph may be further truncated if the graph's
1217 # The SEARCHENGINE tag specifies whether or not a search engine should be
1218 # used. If set to NO the values of all tags below this one will be ignored.