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.
47 # Private class members and static file members will be hidden unless
53 # will be included in the documentation.
58 # will be included in the documentation.
64 # If set to NO (the default) these members will be included in the
72 # If set to NO (the default) these class will be included in the various
87 # brief descriptions will be completely suppressed.
99 # to NO the shortest path that makes the file name unique will be used.
104 # can be used to strip a user defined part of the path. Stripping is
112 # to NO (the default) then the documentation will be excluded.
132 # (but less readable) file names. This can be useful is your file systems
139 # documentation. If set to YES the scope will be hidden.
184 # all members of a group must be documented explicitly.
188 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
193 # The GENERATE_TODOLIST tag can be used to enable (YES) or
199 # The GENERATE_TESTLIST tag can be used to enable (YES) or
205 # The GENERATE_BUGLIST tag can be used to enable (YES) or
211 # This tag can be used to specify a number of aliases that acts
220 # The ENABLED_SECTIONS tag can be used to enable conditional
228 # here it will be hidden. Use a value of 0 to hide initializers completely.
230 # documentation can be controlled using \showinitializer or \hideinitializer
237 # For instance some of the names that are used will be different. The list
238 # of all members will be omitted, etc.
252 # The QUIET tag can be used to turn on/off the messages that are generated
257 # The WARNINGS tag can be used to turn on/off the warning messages that are
265 # automatically be disabled.
271 # tags, which will be replaced by the file and line number from which the
276 # The WARN_LOGFILE tag can be used to specify a file to which warning
277 # and error messages should be written. If left blank the output is written
286 # The INPUT tag can be used to specify the files and/or directories that contain
302 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
303 # should be searched for input files as well. Possible values are YES and NO.
308 # The EXCLUDE tag can be used to specify files and/or directories that should
320 # The EXAMPLE_PATH tag can be used to specify one or more files or
333 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
334 # searched for input files to be used with the \include or \dontinclude
340 # The IMAGE_PATH tag can be used to specify one or more files or
346 # The INPUT_FILTER tag can be used to specify a program that doxygen should
356 # INPUT_FILTER) will be used to filter the input files when producing source
366 # be generated. Documented entities will be cross-referenced with these sources.
377 # functions referencing it will be listed.
383 # called/used by that function will be listed.
392 # of all compounds will be generated. Enable this if the project
398 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
399 # in which this list will be split (can be a number in the range [1..20])
404 # classes will be put under the same header in the alphabetical index.
405 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
406 # should be ignored while generating the index headers.
419 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
420 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
421 # put in front of it. If left blank `html' will be used as the default path.
425 # The HTML_HEADER tag can be used to specify a personal HTML header for
431 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
437 # The HTML_STYLESHEET tag can be used to specify a user defined cascading
438 # style sheet that is used by each HTML page. It can be used to
445 # files or namespaces will be aligned in HTML using tables. If set to
446 # NO a bullet list will be used.
451 # will be generated that can be used as input for tools like the
459 # it should be included in the master .chm file (NO).
469 # The TOC_EXPAND flag can be set to YES to add extra items for group members
474 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
480 # This tag can be used to set the number of enum values (range [1..20])
485 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
495 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
510 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
511 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
512 # put in front of it. If left blank `latex' will be used as the default path.
517 # LaTeX documents. This may be useful for small projects and may help to
522 # The PAPER_TYPE tag can be used to set the paper type that is used
524 # executive. If left blank a4wide will be used.
528 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
529 # packages that should be included in the LaTeX output.
533 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
547 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
570 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
571 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
572 # put in front of it. If left blank `rtf' will be used as the default path.
577 # RTF documents. This may be useful for small projects and may help to
611 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
612 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
613 # put in front of it. If left blank `man' will be used as the default path.
626 # would be unable to find the correct page. The default is NO.
654 # compilation will be performed. Macro expansion can be done in a controlled
666 # in the INCLUDE_PATH (see below) will be search if a #include is found.
670 # The INCLUDE_PATH tag can be used to specify one or more directories that
671 # contain include files that are not input files but should be processed by
679 # be used.
683 # The PREDEFINED tag can be used to specify one or more macro names that
692 # this tag can be used to specify a list of macro names that should be expanded.
693 # The macro definition that is found in the sources will be used.
709 # The TAGFILES tag can be used to specify one or more tagfiles.
718 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
720 # will be listed.
724 # The PERL_PATH should be the absolute path and name of the perl script
792 # The tag DOT_PATH can be used to specify the path where the dot tool can be
793 # found. If left blank, it is assumed the dot tool can be found on the path.
797 # The DOTFILE_DIRS tag can be used to specify one or more directories that
803 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
811 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
835 # The SEARCHENGINE tag specifies whether or not a search engine should be
836 # used. If set to NO the values of all tags below this one will be ignored.
840 # The CGI_NAME tag should be the name of the CGI script that
842 # A script with this name will be generated by doxygen.