Lines Matching refs:will
6 # All text after a hash (#) is considered a comment and will be ignored
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.
35 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
37 # format and will distribute the generated files over these directories.
45 # documentation generated by doxygen is written. Doxygen will use this
66 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
73 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
76 # brief descriptions will be completely suppressed.
82 # in this list, if found as the leading text of the brief description, will be
92 # Doxygen will generate a detailed section even if there is only a brief
97 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited
100 # the base classes will not be shown.
104 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
106 # to NO the shortest path that makes the file name unique will be used.
128 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
135 # will interpret the first line (until the first dot) of a JavaDoc-style
137 # comments will behave just like the Qt-style comments (thus requiring an
151 # will output the detailed description near the top, like JavaDoc.
164 # tag is set to YES, then doxygen will reuse the documentation of the first
177 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
179 # will result in a user-defined paragraph with heading "Side Effects:".
185 # only. Doxygen will then generate output that is more tailored for C.
186 # For instance, some of the names that are used will be different. The list
187 # of all members will be omitted, etc.
192 # only. Doxygen will then generate output that is more tailored for Java.
193 # For instance, namespaces will be presented as packages, qualified scopes
194 # will look different, etc.
210 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
212 # Private class members and static file members will be hidden unless
218 # will be included in the documentation.
223 # will be included in the documentation.
228 # defined locally in source files will be included in the documentation.
240 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
242 # If set to NO (the default) these members will be included in the
248 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
250 # If set to NO (the default) these classes will be included in the various
255 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
257 # If set to NO (the default) these declarations will be included in the
262 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
264 # If set to NO (the default) these blocks will be appended to the
271 # to NO (the default) then the documentation will be excluded.
276 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
285 # will show members with their full class and namespace scopes in the
286 # documentation. If set to YES the scope will be hidden.
291 # will put a list of the files that are included by a file in the documentation
302 # will sort the (detailed) documentation of file and class members
303 # alphabetically by member name. If set to NO the members will appear in
308 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
310 # by member name. If set to NO (the default) the members will appear in
315 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
317 # NO (the default), the class list will be sorted only by class name,
357 # here it will be hidden. Use a value of 0 to hide initializers completely.
366 # list will mention the files that were used to generate the documentation.
371 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
391 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
392 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
397 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
406 # tags, which will be replaced by the file and line number from which the
473 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
487 # invoke to filter for each input file. Doxygen will invoke the filter program
490 # input file. Doxygen will then use the output that the filter program writes
491 # to standard output. If FILTER_PATTERNS is specified, this tag will be
497 # basis. Doxygen will compare the file name with each pattern and apply the
506 # INPUT_FILTER) will be used to filter the input files when producing source
515 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
516 # be generated. Documented entities will be cross-referenced with these sources.
522 # Setting the INLINE_SOURCES tag to YES will include the body
527 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
529 # fragments. Normal C and C++ comments will always remain visible.
535 # functions referencing it will be listed.
541 # called/used by that function will be listed.
546 # will generate a verbatim copy of the header file for each class for
556 # of all compounds will be generated. Enable this if the project
563 # in which this list will be split (can be a number in the range [1..20])
568 # classes will be put under the same header in the alphabetical index.
578 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
583 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
584 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
585 # put in front of it. If left blank `html' will be used as the default path.
591 # doxygen will generate files with .html extension.
596 # each generated HTML page. If it is left blank doxygen will generate a
602 # each generated HTML page. If it is left blank doxygen will generate a
610 # will generate a default style sheet. Note that doxygen will try to copy
612 # stylesheet in the HTML output directory as well, or it will be erased!
617 # files or namespaces will be aligned in HTML using tables. If set to
618 # NO a bullet list will be used.
623 # will be generated that can be used as input for tools like the
638 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
667 # that doxygen will group on one line in the generated HTML documentation.
671 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
690 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
695 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
696 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
697 # put in front of it. If left blank `latex' will be used as the default path.
702 # invoked. If left blank `latex' will be used as the default command name.
707 # generate index for LaTeX. If left blank `makeindex' will be used as the
720 # executive. If left blank a4wide will be used.
731 # the first chapter. If it is left blank doxygen will generate a
737 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
743 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
749 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
750 # command to the generated LaTeX files. This will instruct LaTeX to keep
756 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
766 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
772 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
773 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
774 # put in front of it. If left blank `rtf' will be used as the default path.
785 # will contain hyperlink fields. The RTF file will
808 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
813 # The MAN_OUTPUT tag is used to specify where the man 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 `man' will be used as the default path.
825 # then it will generate one additional man file for each entity
836 # If the GENERATE_XML tag is set to YES Doxygen will
842 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
843 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
844 # put in front of it. If left blank `xml' will be used as the default path.
860 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
863 # enabling this will significantly increase the size of the XML output.
871 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
883 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
891 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
897 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
900 # tag is set to NO the size of the Perl module output will be much smaller
901 # and Perl will parse it just the same.
916 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
922 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
924 # compilation will be performed. Macro expansion can be done in a controlled
936 # in the INCLUDE_PATH (see below) will be search if a #include is found.
948 # directories. If left blank, the patterns specified with FILE_PATTERNS will
965 # The macro definition that is found in the sources will be used.
971 # doxygen's preprocessor will remove all function-like macros that are alone
973 # function macros are typically used for boiler-plate code, and will confuse the
999 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1004 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1006 # will be listed.
1010 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1011 # in the modules index. If set to NO, only the current project's groups will
1025 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1033 # If set to YES, the inheritance and collaboration graphs will hide
1039 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1047 # will generate a graph for each documented class showing the direct and
1048 # indirect inheritance relations. Setting this tag to YES will force the
1054 # will generate a graph for each documented class showing the direct and
1060 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1066 # If set to YES, the inheritance and collaboration graphs will show the
1072 # tags are set to YES then doxygen will generate a graph for each documented
1079 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1085 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1087 # Note that enabling this option will significantly increase the time of a run.
1088 # So in most cases it will be better to enable call graphs for selected
1094 # will graphical hierarchy of all classes instead of a textual one.
1100 # If left blank png will be used.
1117 # this value, doxygen will try to truncate the graph, so that it fits within
1125 # this value, doxygen will try to truncate the graph, so that it fits within
1133 # from the root by following a path via at most 3 edges will be shown. Nodes that
1134 # lay further from the root node will be omitted. Note that setting this option to
1142 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1148 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1159 # used. If set to NO the values of all tags below this one will be ignored.