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 source
66 # brief descriptions will be completely suppressed.
72 # in this list, if found as the leading text of the brief description, will be
90 # the base classes will not be shown.
96 # to NO the shortest path that makes the file name unique will be used.
101 # can be used to strip a user-defined part of the path. Stripping is
103 # the path. The tag can be used to show relative paths in the file list.
109 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
119 # (but less readable) file names. This can be useful is your file systems
132 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
134 # comments) as a brief description. This used to be the default behaviour.
149 # all members of a group must be documented explicitly.
153 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
158 # This tag can be used to specify a number of aliases that acts
169 # For instance, some of the names that are used will be different. The list
170 # of all members will be omitted, etc.
176 # For instance, namespaces will be presented as packages, qualified scopes
182 # the same type (for instance a group of public functions) to be put as a
184 # NO to prevent subgrouping. Alternatively, this can be done per class using
195 # Private class members and static file members will be hidden unless
201 # will be included in the documentation.
206 # will be included in the documentation.
211 # defined locally in source files will be included in the documentation.
225 # If set to NO (the default) these members will be included in the
233 # If set to NO (the default) these classes will be included in the various
240 # If set to NO (the default) these declarations will be included in the
247 # If set to NO (the default) these blocks will be appended to the
254 # to NO (the default) then the documentation will be excluded.
269 # documentation. If set to YES the scope will be hidden.
298 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
300 # NO (the default), the class list will be sorted only by class name,
308 # The GENERATE_TODOLIST tag can be used to enable (YES) or
314 # The GENERATE_TESTLIST tag can be used to enable (YES) or
320 # The GENERATE_BUGLIST tag can be used to enable (YES) or
326 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
332 # The ENABLED_SECTIONS tag can be used to enable conditional
340 # here it will be hidden. Use a value of 0 to hide initializers completely.
342 # documentation can be controlled using \showinitializer or \hideinitializer
357 # The QUIET tag can be used to turn on/off the messages that are generated
362 # The WARNINGS tag can be used to turn on/off the warning messages that are
370 # automatically be disabled.
383 # tags, which will be replaced by the file and line number from which the
388 # The WARN_LOGFILE tag can be used to specify a file to which warning
389 # and error messages should be written. If left blank the output is written
398 # The INPUT tag can be used to specify the files and/or directories that contain
414 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
415 # should be searched for input files as well. Possible values are YES and NO.
420 # The EXCLUDE tag can be used to specify files and/or directories that should
426 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
437 # The EXAMPLE_PATH tag can be used to specify one or more files or
450 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
451 # searched for input files to be used with the \include or \dontinclude
457 # The IMAGE_PATH tag can be used to specify one or more files or
463 # The INPUT_FILTER tag can be used to specify a program that doxygen should
468 # to standard output. If FILTER_PATTERNS is specified, this tag will be
473 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
483 # INPUT_FILTER) will be used to filter the input files when producing source
493 # be generated. Documented entities will be cross-referenced with these sources.
512 # functions referencing it will be listed.
518 # called/used by that function will be listed.
533 # of all compounds will be generated. Enable this if the project
539 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
540 # in which this list will be split (can be a number in the range [1..20])
545 # classes will be put under the same header in the alphabetical index.
546 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
547 # should be ignored while generating the index headers.
560 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
561 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
562 # put in front of it. If left blank `html' will be used as the default path.
566 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
572 # The HTML_HEADER tag can be used to specify a personal HTML header for
578 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
584 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
585 # style sheet that is used by each HTML page. It can be used to
589 # stylesheet in the HTML output directory as well, or it will be erased!
594 # will be generated that can be used as input for tools like the
601 # be used to specify the file name of the resulting .chm file. You
602 # can add a path in front of the file if the result should not be
608 # be used to specify the location (absolute path including file name) of
616 # it should be included in the master .chm file (NO).
626 # The TOC_EXPAND flag can be set to YES to add extra items for group members
631 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
637 # This tag can be used to set the number of enum values (range [1..20])
642 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
651 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
666 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
667 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
668 # put in front of it. If left blank `latex' will be used as the default path.
672 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
673 # invoked. If left blank `latex' will be used as the default command name.
677 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
678 # generate index for LaTeX. If left blank `makeindex' will be used as the
684 # LaTeX documents. This may be useful for small projects and may help to
689 # The PAPER_TYPE tag can be used to set the paper type that is used
691 # executive. If left blank a4wide will be used.
695 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
696 # packages that should be included in the LaTeX output.
700 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
714 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
743 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
744 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
745 # put in front of it. If left blank `rtf' will be used as the default path.
750 # RTF documents. This may be useful for small projects and may help to
784 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
785 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
786 # put in front of it. If left blank `man' will be used as the default path.
799 # would be unable to find the correct page. The default is NO.
813 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
814 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
815 # put in front of it. If left blank `xml' will be used as the default path.
851 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
856 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
857 # nicely formatted so it can be parsed by a human reader. This is useful
859 # tag is set to NO the size of the Perl module output will be much smaller
883 # compilation will be performed. Macro expansion can be done in a controlled
895 # in the INCLUDE_PATH (see below) will be search if a #include is found.
899 # The INCLUDE_PATH tag can be used to specify one or more directories that
900 # contain include files that are not input files but should be processed by
908 # be used.
912 # The PREDEFINED tag can be used to specify one or more macro names that
921 # this tag can be used to specify a list of macro names that should be expanded.
922 # The macro definition that is found in the sources will be used.
939 # The TAGFILES option can be used to specify one or more tagfiles.
941 # can be added for each tagfile. The format of a tag file without
946 # where "loc1" and "loc2" can be relative or absolute paths or
948 # does not have to be run to correct the links.
961 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
963 # will be listed.
967 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
969 # be listed.
973 # The PERL_PATH should be the absolute path and name of the perl script
1045 # So in most cases it will be better to enable call graphs for selected
1055 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1057 # If left blank png will be used.
1061 # The tag DOT_PATH can be used to specify the path where the dot tool can be
1062 # found. If left blank, it is assumed the dot tool can be found on the path.
1066 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1072 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1074 # from the root by following a path via at most 3 edges will be shown. Nodes that
1075 # lay further from the root node will be omitted. Note that setting this option to
1077 # note that a graph may be further truncated if the graph's image dimensions are
1099 # The SEARCHENGINE tag specifies whether or not a search engine should be
1100 # used. If set to NO the values of all tags below this one will be ignored.