Lines Matching full:will

6 # All text after a hash (#) is considered a comment and will be ignored.
46 # Doxygen will copy the logo to the output directory.
51 # base path where the generated documentation will be put.
52 # If a relative path is entered, it will be relative to the location
53 # where doxygen was started. If left blank the current directory will be used.
57 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
59 # format and will distribute the generated files over these directories.
67 # documentation generated by doxygen is written. Doxygen will use this
79 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
86 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
89 # brief descriptions will be completely suppressed.
95 # in this list, if found as the leading text of the brief description, will be
106 # Doxygen will generate a detailed section even if there is only a brief
111 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
114 # operators of the base classes will not be shown.
118 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
120 # to NO the shortest path that makes the file name unique will be used.
142 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
149 # will interpret the first line (until the first dot) of a JavaDoc-style
151 # comments will behave just like regular Qt-style comments
156 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will
159 # will behave just like regular Qt-style comments (thus requiring
178 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
179 # a new page for each member. If set to NO, the documentation of a member will
191 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
193 # will result in a user-defined paragraph with heading "Side Effects:".
200 # "class=itcl::class" will allow you to use the command class in the
206 # sources only. Doxygen will then generate output that is more tailored for C.
207 # For instance, some of the names that are used will be different. The list
208 # of all members will be omitted, etc.
213 # sources only. Doxygen will then generate output that is more tailored for
214 # Java. For instance, namespaces will be presented as packages, qualified
215 # scopes will look different, etc.
220 # sources only. Doxygen will then generate output that is more tailored for
226 # sources. Doxygen will then generate output that is tailored for
258 # Doxygen will parse them like normal C++ but will assume all classes use public
265 # will make doxygen replace the get and set methods by a property in the
266 # documentation. This will only work if the methods are indeed getting or
273 # tag is set to YES, then doxygen will reuse the documentation of the first
295 # unions with only public data fields will be shown inline in the documentation
305 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
306 # with name TypeT. When disabled the typedef will appear as a member of a file,
307 # namespace, or class. And the struct will be named TypeS. This can typically
315 # When the cache is full, less often used symbols will be written to disk.
320 # If the system has enough physical memory increasing the cache will improve the
322 # a logarithmic scale so increasing the size by one will roughly double the
333 # pre-resolved symbols. If the cache is too small doxygen will become slower.
344 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
346 # Private class members and static file members will be hidden unless
352 # will be included in the documentation.
357 # will be included in the documentation.
362 # defined locally in source files will be included in the documentation.
374 # If this flag is set to YES, the members of anonymous namespaces will be
376 # 'anonymous_namespace{file}', where file will be replaced with the base
382 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
384 # If set to NO (the default) these members will be included in the
390 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
392 # If set to NO (the default) these classes will be included in the various
397 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
399 # If set to NO (the default) these declarations will be included in the
404 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
406 # If set to NO (the default) these blocks will be appended to the
413 # to NO (the default) then the documentation will be excluded.
418 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
427 # will show members with their full class and namespace scopes in the
428 # documentation. If set to YES the scope will be hidden.
433 # will put a list of the files that are included by a file in the documentation
439 # will list include files with double quotes in the documentation
450 # will sort the (detailed) documentation of file and class members
451 # alphabetically by member name. If set to NO the members will appear in
456 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
458 # by member name. If set to NO (the default) the members will appear in
464 # will sort the (brief and detailed) documentation of class members so that
466 # the constructors will appear in the respective orders defined by
468 # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
473 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
475 # the group names will appear in their defined order.
479 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
481 # NO (the default), the class list will be sorted only by class name,
490 # do proper type resolution of all parameters of a function it will reject a
494 # will still accept a match between prototype and implementation in such cases.
530 # here it will be hidden. Use a value of 0 to hide initializers completely.
539 # list will mention the files that were used to generate the documentation.
544 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
550 # This will remove the Files entry from the Quick Index and from the
557 # This will remove the Namespaces entry from the Quick Index
564 # the version control system). Doxygen will invoke the program by executing (via
572 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
577 # DoxygenLayout.xml will be used as the name of the layout file.
606 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
607 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
612 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
621 # or return value. If set to NO (the default) doxygen will only warn about
629 # tags, which will be replaced by the file and line number from which the
631 # $version, which will be replaced by the version of the file (if it could
723 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
737 # invoke to filter for each input file. Doxygen will invoke the filter program
740 # input file. Doxygen will then use the output that the filter program writes
742 # If FILTER_PATTERNS is specified, this tag will be
749 # Doxygen will compare the file name with each pattern and apply the
759 # INPUT_FILTER) will be used to filter the input files when producing source
765 # pattern. A pattern will override the setting for FILTER_PATTERN (if any)
776 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
777 # be generated. Documented entities will be cross-referenced with these sources.
783 # Setting the INLINE_SOURCES tag to YES will include the body
788 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
790 # fragments. Normal C and C++ comments will always remain visible.
796 # functions referencing it will be listed.
802 # called/used by that function will be listed.
808 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
810 # Otherwise they will link to the documentation.
815 # will point to the HTML generated by the htags(1) tool instead of doxygen
818 # will need version 4.8.6 or higher.
823 # will generate a verbatim copy of the header file for each class for
833 # of all compounds will be generated. Enable this if the project
840 # in which this list will be split (can be a number in the range [1..20])
845 # classes will be put under the same header in the alphabetical index.
855 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
860 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
861 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
862 # put in front of it. If left blank `html' will be used as the default path.
868 # doxygen will generate files with .html extension.
873 # each generated HTML page. If it is left blank doxygen will generate a
886 # each generated HTML page. If it is left blank doxygen will generate a
894 # will generate a default style sheet. Note that doxygen will try to copy
896 # style sheet in the HTML output directory as well, or it will be erased!
902 # that these files will be copied to the base HTML output directory. Use the
905 # the files will be copied as-is; there are no commands or markers available.
910 # Doxygen will adjust the colors in the style sheet and background images
920 # the colors in the HTML output. For a value of 0 the output will use
921 # grayscales only. A value of 255 will produce the most vivid colors.
935 # page will contain the date and time when the page was generated. Setting
941 # files or namespaces will be aligned in HTML using tables. If set to
942 # NO a bullet list will be used.
947 # documentation will contain sections that can be hidden and shown after the
955 # will be generated that can be used as input for Apple's Xcode 3
957 # To create a documentation set, doxygen will generate a Makefile in the
958 # HTML output directory. Running make will produce the docset in that
959 # directory and running "make install" will install the docset in
960 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
977 # will append .docset to the name.
992 # will be generated that can be used as input for tools like the
1007 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
1036 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
1083 # If non-empty doxygen will try to run qhelpgenerator on the generated
1089 #  will be generated, which together with the HTML files, form an Eclipse help
1115 # If the tag value is set to YES, a side panel will be generated
1126 # (range [0,1..20]) that doxygen will group on one line in the generated HTML
1127 # documentation. Note that a value of 0 will completely suppress the enum
1132 # By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
1143 # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
1189 # When the SEARCHENGINE tag is enabled doxygen will generate a search box
1199 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1201 # using Javascript. Doxygen will generate the search PHP script and index
1213 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1218 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1219 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1220 # put in front of it. If left blank `latex' will be used as the default path.
1225 # invoked. If left blank `latex' will be used as the default command name.
1233 # generate index for LaTeX. If left blank `makeindex' will be used as the
1246 # executive. If left blank a4wide will be used.
1257 # the first chapter. If it is left blank doxygen will generate a
1264 # the last chapter. If it is left blank doxygen will generate a
1270 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
1276 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1282 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1283 # command to the generated LaTeX files. This will instruct LaTeX to keep
1289 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
1295 # If LATEX_SOURCE_CODE is set to YES then doxygen will include
1312 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1318 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1319 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1320 # put in front of it. If left blank `rtf' will be used as the default path.
1331 # will contain hyperlink fields. The RTF file will
1354 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1359 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
1360 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1361 # put in front of it. If left blank `man' will be used as the default path.
1371 # then it will generate one additional man file for each entity
1382 # If the GENERATE_XML tag is set to YES Doxygen will
1388 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
1389 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1390 # put in front of it. If left blank `xml' will be used as the default path.
1406 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1409 # enabling this will significantly increase the size of the XML output.
1417 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1429 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
1437 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1443 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1448 # tag is set to NO the size of the Perl module output will be much smaller
1449 # and Perl will parse it just the same.
1464 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1470 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1472 # compilation will be performed. Macro expansion can be done in a controlled
1484 # pointed to by INCLUDE_PATH will be searched when a #include is found.
1496 # directories. If left blank, the patterns specified with FILE_PATTERNS will
1516 # The macro definition that is found in the sources will be used.
1523 # doxygen's preprocessor will remove all references to function-like macros
1525 # semicolon, because these will confuse the parser if not removed.
1552 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1557 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1559 # will be listed.
1563 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1564 # in the modules index. If set to NO, only the current project's groups will
1578 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1587 # command. Doxygen will then run the mscgen tool (see
1595 # If set to YES, the inheritance and collaboration graphs will hide
1601 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1609 # allowed to run in parallel. When set to 0 (the default) doxygen will
1616 # By default doxygen will use the Helvetica font for all dot files that
1630 # By default doxygen will tell dot to use the Helvetica font.
1637 # will generate a graph for each documented class showing the direct and
1638 # indirect inheritance relations. Setting this tag to YES will force the
1644 # will generate a graph for each documented class showing the direct and
1651 # will generate a graph for groups, showing the direct groups dependencies
1655 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1661 # If set to YES, the inheritance and collaboration graphs will show the
1667 # tags are set to YES then doxygen will generate a graph for each documented
1674 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1681 # doxygen will generate a call dependency graph for every global function
1682 # or class method. Note that enabling this option will significantly increase
1683 # the time of a run. So in most cases it will be better to enable call graphs
1689 # doxygen will generate a caller dependency graph for every global function
1690 # or class method. Note that enabling this option will significantly increase
1691 # the time of a run. So in most cases it will be better to enable caller
1697 # will generate a graphical hierarchy of all classes instead of a textual one.
1702 # then doxygen will show the dependencies a directory has on other directories
1710 # If left blank png will be used. If you choose svg you need to set
1743 # nodes that will be shown in the graph. If the number of nodes in a graph
1744 # becomes larger than this value, doxygen will truncate the graph, which is
1747 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1754 # from the root by following a path via at most 3 edges will be shown. Nodes
1755 # that lay further from the root node will be omitted. Note that setting this
1777 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1783 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will