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.
36 # documentation generated by doxygen is written. Doxygen will use this
46 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
48 # Private class members and static file members will be hidden unless
54 # will be included in the documentation.
59 # will be included in the documentation.
64 # defined locally in source files will be included in the documentation.
69 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
71 # If set to NO (the default) these members will be included in the
77 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
79 # If set to NO (the default) these class will be included in the various
84 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
86 # If set to NO (the default) these declarations will be included in the
91 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
93 # If set to NO (the default) these blocks will be appended to the
98 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
105 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
108 # brief descriptions will be completely suppressed.
113 # Doxygen will generate a detailed section even if there is only a brief
118 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited
121 # the base classes will not be shown.
125 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
127 # to NO the shortest path that makes the file name unique will be used.
140 # to NO (the default) then the documentation will be excluded.
145 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
153 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
160 # will show members with their full class and namespace scopes in the
161 # documentation. If set to YES the scope will be hidden.
166 # will generate a verbatim copy of the header file for each class for
172 # will put list of the files that are included by a file in the documentation
178 # will interpret the first line (until the first dot) of a JavaDoc-style
180 # comments will behave just like the Qt-style comments (thus requiring an
194 # will output the detailed description near the top, like JavaDoc.
212 # will sort the (detailed) documentation of file and class members
213 # alphabetically by member name. If set to NO the members will appear in
219 # tag is set to YES, then doxygen will reuse the documentation of the first
256 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
258 # will result in a user defined paragraph with heading "Side Effects:".
271 # here it will be hidden. Use a value of 0 to hide initializers completely.
279 # only. Doxygen will then generate output that is more tailored for C.
280 # For instance some of the names that are used will be different. The list
281 # of all members will be omitted, etc.
286 # only. Doxygen will then generate output that is more tailored for Java.
287 # For instance namespaces will be presented as packages, qualified scopes
288 # will look different, etc.
294 # list will mention the files that were used to generate the documentation.
313 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
314 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
319 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
328 # tags, which will be replaced by the file and line number from which the
395 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
409 # invoke to filter for each input file. Doxygen will invoke the filter program
412 # input file. Doxygen will then use the output that the filter program writes
418 # INPUT_FILTER) will be used to filter the input files when producing source
427 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
428 # be generated. Documented entities will be cross-referenced with these sources.
432 # Setting the INLINE_SOURCES tag to YES will include the body
437 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
439 # fragments. Normal C and C++ comments will always remain visible.
445 # functions referencing it will be listed.
451 # called/used by that function will be listed.
460 # of all compounds will be generated. Enable this if the project
467 # in which this list will be split (can be a number in the range [1..20])
472 # classes will be put under the same header in the alphabetical index.
482 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
487 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
488 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
489 # put in front of it. If left blank `html' will be used as the default path.
495 # doxygen will generate files with .html extension.
500 # each generated HTML page. If it is left blank doxygen will generate a
506 # each generated HTML page. If it is left blank doxygen will generate a
514 # will generate a default style sheet
519 # files or namespaces will be aligned in HTML using tables. If set to
520 # NO a bullet list will be used.
525 # will be generated that can be used as input for tools like the
540 # the HTML help compiler (hhc.exe). If non empty doxygen will try to run
569 # that doxygen will group on one line in the generated HTML documentation.
573 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
592 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
597 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
598 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
599 # put in front of it. If left blank `latex' will be used as the default path.
604 # invoked. If left blank `latex' will be used as the default command name.
609 # generate index for LaTeX. If left blank `makeindex' will be used as the
622 # executive. If left blank a4wide will be used.
633 # the first chapter. If it is left blank doxygen will generate a
639 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
645 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
651 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
652 # command to the generated LaTeX files. This will instruct LaTeX to keep
662 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
668 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
669 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
670 # put in front of it. If left blank `rtf' will be used as the default path.
681 # will contain hyperlink fields. The RTF file will
704 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
709 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
710 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
711 # put in front of it. If left blank `man' will be used as the default path.
721 # then it will generate one additional man file for each entity
732 # If the GENERATE_XML tag is set to YES Doxygen will
756 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
768 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
776 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
782 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
785 # tag is set to NO the size of the Perl module output will be much smaller
786 # and Perl will parse it just the same.
801 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
807 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
809 # compilation will be performed. Macro expansion can be done in a controlled
821 # in the INCLUDE_PATH (see below) will be search if a #include is found.
833 # directories. If left blank, the patterns specified with FILE_PATTERNS will
848 # The macro definition that is found in the sources will be used.
854 # doxygen's preprocessor will remove all function-like macros that are alone
856 # function macros are typically used for boiler-plate code, and will confuse the
869 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
874 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
876 # will be listed.
880 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
881 # in the modules index. If set to NO, only the current project's groups will
895 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
903 # If set to YES, the inheritance and collaboration graphs will hide
909 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
917 # will generate a graph for each documented class showing the direct and
918 # indirect inheritance relations. Setting this tag to YES will force the
924 # will generate a graph for each documented class showing the direct and
930 # If set to YES, the inheritance and collaboration graphs will show the
936 # tags are set to YES then doxygen will generate a graph for each documented
943 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
950 # will graphical hierarchy of all classes instead of a textual one.
956 # If left blank png will be used.
973 # this value, doxygen will try to truncate the graph, so that it fits within
981 # this value, doxygen will try to truncate the graph, so that it fits within
987 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
993 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1004 # used. If set to NO the values of all tags below this one will be ignored.
1010 # A script with this name will be generated by doxygen.
1022 # documentation, with file:// prepended to it, will be used.
1028 # will be used.