Lines Matching full:will

6 # All text after a hash (#) is considered a comment and will be ignored
37 # base path where the generated documentation will be put.
38 # If a relative path is entered, it will be relative to the location
39 # where doxygen was started. If left blank the current directory will be used.
43 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
45 # format and will distribute the generated files over these directories.
53 # documentation generated by doxygen is written. Doxygen will use this
65 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
72 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
75 # brief descriptions will be completely suppressed.
81 # 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
100 # operators of 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 regular Qt-style comments
142 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will
145 # will behave just like regular Qt-style comments (thus requiring
164 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
165 # a new page for each member. If set to NO, the documentation of a member will
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 # sources 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 # sources only. Doxygen will then generate output that is more tailored for
193 # Java. For instance, namespaces will be presented as packages, qualified
194 # scopes will look different, etc.
199 # sources only. Doxygen will then generate output that is more tailored for
205 # sources. Doxygen will then generate output that is tailored for
237 # Doxygen will parse them like normal C++ but will assume all classes use public
244 # will make doxygen to replace the get and set methods by a property in the
245 # documentation. This will only work if the methods are indeed getting or
252 # tag is set to YES, then doxygen will reuse the documentation of the first
268 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
269 # with name TypeT. When disabled the typedef will appear as a member of a file,
270 # namespace, or class. And the struct will be named TypeS. This can typically
280 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
282 # Private class members and static file members will be hidden unless
288 # will be included in the documentation.
293 # will be included in the documentation.
298 # defined locally in source files will be included in the documentation.
310 # If this flag is set to YES, the members of anonymous namespaces will be
312 # 'anonymous_namespace{file}', where file will be replaced with the base
318 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
320 # If set to NO (the default) these members will be included in the
326 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
328 # If set to NO (the default) these classes will be included in the various
333 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
335 # If set to NO (the default) these declarations will be included in the
340 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
342 # If set to NO (the default) these blocks will be appended to the
349 # to NO (the default) then the documentation will be excluded.
354 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
363 # will show members with their full class and namespace scopes in the
364 # documentation. If set to YES the scope will be hidden.
369 # will put a list of the files that are included by a file in the documentation
375 # will list include files with double quotes in the documentation
386 # will sort the (detailed) documentation of file and class members
387 # alphabetically by member name. If set to NO the members will appear in
392 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
394 # by member name. If set to NO (the default) the members will appear in
400 # will sort the (brief and detailed) documentation of class members so that
402 # the constructors will appear in the respective orders defined by
404 # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
409 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
411 # the group names will appear in their defined order.
415 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
417 # NO (the default), the class list will be sorted only by class name,
457 # here it will be hidden. Use a value of 0 to hide initializers completely.
466 # list will mention the files that were used to generate the documentation.
471 # This will remove the Files entry from the Quick Index and from the
478 # This will remove the Namespaces entry from the Quick Index
485 # the version control system). Doxygen will invoke the program by executing (via
493 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
498 # DoxygenLayout.xml will be used as the name of the layout file.
517 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
518 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
523 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
532 # or return value. If set to NO (the default) doxygen will only warn about
540 # tags, which will be replaced by the file and line number from which the
542 # $version, which will be replaced by the version of the file (if it could
628 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
642 # invoke to filter for each input file. Doxygen will invoke the filter program
645 # input file. Doxygen will then use the output that the filter program writes
647 # If FILTER_PATTERNS is specified, this tag will be
654 # Doxygen will compare the file name with each pattern and apply the
664 # INPUT_FILTER) will be used to filter the input files when producing source
673 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
674 # be generated. Documented entities will be cross-referenced with these sources.
680 # Setting the INLINE_SOURCES tag to YES will include the body
685 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
687 # fragments. Normal C and C++ comments will always remain visible.
693 # functions referencing it will be listed.
699 # called/used by that function will be listed.
705 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
707 # Otherwise they will link to the documentation.
712 # will point to the HTML generated by the htags(1) tool instead of doxygen
715 # will need version 4.8.6 or higher.
720 # will generate a verbatim copy of the header file for each class for
730 # of all compounds will be generated. Enable this if the project
737 # in which this list will be split (can be a number in the range [1..20])
742 # classes will be put under the same header in the alphabetical index.
752 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
757 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
758 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
759 # put in front of it. If left blank `html' will be used as the default path.
765 # doxygen will generate files with .html extension.
770 # each generated HTML page. If it is left blank doxygen will generate a
776 # each generated HTML page. If it is left blank doxygen will generate a
784 # will generate a default style sheet. Note that doxygen will try to copy
786 # stylesheet in the HTML output directory as well, or it will be erased!
791 # Doxygen will adjust the colors in the stylesheet and background images
801 # the colors in the HTML output. For a value of 0 the output will use
802 # grayscales only. A value of 255 will produce the most vivid colors.
816 # page will contain the date and time when the page was generated. Setting
822 # documentation will contain sections that can be hidden and shown after the
830 # will be generated that can be used as input for Apple's Xcode 3
832 # To create a documentation set, doxygen will generate a Makefile in the
833 # HTML output directory. Running make will produce the docset in that
834 # directory and running "make install" will install the docset in
835 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
852 # will append .docset to the name.
867 # will be generated that can be used as input for tools like the
882 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
911 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
958 # If non-empty doxygen will try to run qhelpgenerator on the generated
964 #  will be generated, which together with the HTML files, form an Eclipse help
987 # that doxygen will group on one line in the generated HTML documentation.
993 # If the tag value is set to YES, a side panel will be generated
1007 # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1028 # When the SEARCHENGINE tag is enabled doxygen will generate a search box
1038 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1040 # using Javascript. Doxygen will generate the search PHP script and index
1052 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1057 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1058 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1059 # put in front of it. If left blank `latex' will be used as the default path.
1064 # invoked. If left blank `latex' will be used as the default command name.
1072 # generate index for LaTeX. If left blank `makeindex' will be used as the
1085 # executive. If left blank a4wide will be used.
1096 # the first chapter. If it is left blank doxygen will generate a
1102 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
1108 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1114 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1115 # command to the generated LaTeX files. This will instruct LaTeX to keep
1121 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
1127 # If LATEX_SOURCE_CODE is set to YES then doxygen will include
1138 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1144 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1145 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1146 # put in front of it. If left blank `rtf' will be used as the default path.
1157 # will contain hyperlink fields. The RTF file will
1180 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1185 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
1186 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1187 # put in front of it. If left blank `man' will be used as the default path.
1197 # then it will generate one additional man file for each entity
1208 # If the GENERATE_XML tag is set to YES Doxygen will
1214 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
1215 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1216 # put in front of it. If left blank `xml' will be used as the default path.
1220 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1223 # enabling this will significantly increase the size of the XML output.
1231 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1243 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
1251 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1257 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1262 # tag is set to NO the size of the Perl module output will be much smaller
1263 # and Perl will parse it just the same.
1278 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1284 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1286 # compilation will be performed. Macro expansion can be done in a controlled
1298 # in the INCLUDE_PATH (see below) will be search if a #include is found.
1310 # directories. If left blank, the patterns specified with FILE_PATTERNS will
1327 # The macro definition that is found in the sources will be used.
1333 # doxygen's preprocessor will remove all function-like macros that are alone
1335 # function macros are typically used for boiler-plate code, and will confuse
1363 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1368 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1370 # will be listed.
1374 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1375 # in the modules index. If set to NO, only the current project's groups will
1384 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1393 # If set to YES, the inheritance and collaboration graphs will hide
1399 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1407 # allowed to run in parallel. When set to 0 (the default) doxygen will
1414 # By default doxygen will write a font called FreeSans.ttf to the output
1430 # By default doxygen will tell dot to use the output directory to look for the
1431 # FreeSans.ttf font (which doxygen will put there itself). If you specify a
1438 # will generate a graph for each documented class showing the direct and
1439 # indirect inheritance relations. Setting this tag to YES will force the
1445 # will generate a graph for each documented class showing the direct and
1452 # will generate a graph for groups, showing the direct groups dependencies
1456 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1462 # If set to YES, the inheritance and collaboration graphs will show the
1468 # tags are set to YES then doxygen will generate a graph for each documented
1475 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1482 # doxygen will generate a call dependency graph for every global function
1483 # or class method. Note that enabling this option will significantly increase
1484 # the time of a run. So in most cases it will be better to enable call graphs
1490 # doxygen will generate a caller dependency graph for every global function
1491 # or class method. Note that enabling this option will significantly increase
1492 # the time of a run. So in most cases it will be better to enable caller
1498 # will graphical hierarchy of all classes instead of a textual one.
1503 # then doxygen will show the dependencies a directory has on other directories
1511 # If left blank png will be used.
1527 # nodes that will be shown in the graph. If the number of nodes in a graph
1528 # becomes larger than this value, doxygen will truncate the graph, which is
1531 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1538 # from the root by following a path via at most 3 edges will be shown. Nodes
1539 # that lay further from the root node will be omitted. Note that setting this
1561 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1567 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will