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 
56 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
63 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
66 # brief descriptions will be completely suppressed.
72 # in this list, if found as the leading text of the brief description, will be 
82 # Doxygen will generate a detailed section even if there is only a brief 
87 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited 
90 # the base classes will not be shown.
94 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
96 # to NO the shortest path that makes the file name unique will be used.
118 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
125 # will interpret the first line (until the first dot) of a JavaDoc-style 
127 # comments will behave just like the Qt-style comments (thus requiring an 
147 # tag is set to YES, then doxygen will reuse the documentation of the first 
160 # For example adding "sideeffect=\par Side Effects:\n" will allow you to 
162 # will result in a user-defined paragraph with heading "Side Effects:". 
168 # only. Doxygen will then generate output that is more tailored for C. 
169 # For instance, some of the names that are used will be different. The list 
170 # of all members will be omitted, etc.
175 # only. Doxygen will then generate output that is more tailored for Java. 
176 # For instance, namespaces will be presented as packages, qualified scopes 
177 # will look different, etc.
193 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
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. 
223 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
225 # If set to NO (the default) these members will be included in the 
231 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
233 # If set to NO (the default) these classes will be included in the various 
238 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
240 # If set to NO (the default) these declarations will be included in the 
245 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 
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. 
259 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
268 # will show members with their full class and namespace scopes in the 
269 # documentation. If set to YES the scope will be hidden.
274 # will put a list of the files that are included by a file in the documentation 
285 # will sort the (detailed) documentation of file and class members 
286 # alphabetically by member name. If set to NO the members will appear in 
291 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 
293 # by member name. If set to NO (the default) the members will appear in 
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, 
340 # here it will be hidden. Use a value of 0 to hide initializers completely. 
349 # list will mention the files that were used to generate the documentation.
368 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
369 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
374 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 
383 # tags, which will be replaced by the file and line number from which the 
450 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
464 # invoke to filter for each input file. Doxygen will invoke the filter program 
467 # input file. Doxygen will then use the output that the filter program writes 
468 # to standard output.  If FILTER_PATTERNS is specified, this tag will be 
474 # basis.  Doxygen will compare the file name with each pattern and apply the 
483 # INPUT_FILTER) will be used to filter the input files when producing source 
492 # If the SOURCE_BROWSER tag is set to YES then a list of source files will 
493 # be generated. Documented entities will be cross-referenced with these sources. 
499 # Setting the INLINE_SOURCES tag to YES will include the body 
504 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
506 # fragments. Normal C and C++ comments will always remain visible.
512 # functions referencing it will be listed.
518 # called/used by that function will be listed.
523 # will generate a verbatim copy of the header file for each class for 
533 # of all compounds will be generated. Enable this if the project 
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. 
555 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
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.
568 # doxygen will generate files with .html extension.
573 # each generated HTML page. If it is left blank doxygen will generate a 
579 # each generated HTML page. If it is left blank doxygen will generate a 
587 # will generate a default style sheet. Note that doxygen will try to copy 
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 
609 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 
638 # that doxygen will group on one line in the generated HTML documentation.
642 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
661 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
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.
673 # invoked. If left blank `latex' will be used as the default command name.
678 # generate index for LaTeX. If left blank `makeindex' will be used as the 
691 # executive. If left blank a4wide will be used.
702 # the first chapter. If it is left blank doxygen will generate a 
708 # is prepared for conversion to pdf (using ps2pdf). The pdf file will 
714 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
720 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
721 # command to the generated LaTeX files. This will instruct LaTeX to keep 
727 # If LATEX_HIDE_INDICES is set to YES then doxygen will not 
737 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
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.
756 # will contain hyperlink fields. The RTF file will 
779 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
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.
796 # then it will generate one additional man file for each entity 
807 # If the GENERATE_XML tag is set to YES Doxygen will 
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.
819 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will 
822 # enabling this will significantly increase the size of the XML output.
830 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
842 # If the GENERATE_PERLMOD tag is set to YES Doxygen will 
850 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate 
856 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 
859 # tag is set to NO the size of the Perl module output will be much smaller 
860 # and Perl will parse it just the same.
875 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
881 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
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.
907 # directories. If left blank, the patterns specified with FILE_PATTERNS will 
922 # The macro definition that is found in the sources will be used. 
928 # doxygen's preprocessor will remove all function-like macros that are alone 
930 # function macros are typically used for boiler-plate code, and will confuse the 
956 # When a file name is specified after GENERATE_TAGFILE, doxygen will create 
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 
968 # in the modules index. If set to NO, only the current project's groups will 
982 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
990 # If set to YES, the inheritance and collaboration graphs will hide 
996 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 
1004 # will generate a graph for each documented class showing the direct and 
1005 # indirect inheritance relations. Setting this tag to YES will force the 
1011 # will generate a graph for each documented class showing the direct and 
1017 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and 
1023 # If set to YES, the inheritance and collaboration graphs will show the 
1029 # tags are set to YES then doxygen will generate a graph for each documented 
1036 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each 
1042 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will 
1044 # Note that enabling this option will significantly increase the time of a run. 
1045 # So in most cases it will be better to enable call graphs for selected 
1051 # will graphical hierarchy of all classes instead of a textual one.
1057 # If left blank png will be used.
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 
1083 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
1089 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 
1100 # used. If set to NO the values of all tags below this one will be ignored.