Lines Matching +full:cancel +full:- +full:in +full:- +full:progress

6 # All text after a double hash (##) is considered a comment and is placed in
19 # doxygen -x [configFile]
23 # doxygen -x_noenv [configFile]
25 #---------------------------------------------------------------------------
27 #---------------------------------------------------------------------------
29 # This tag specifies the encoding used for all characters in the configuration
30 # file that follow. The default is UTF-8 which is also the encoding used for all
34 # The default value is: UTF-8.
36 DOXYFILE_ENCODING      = UTF-8
39 # double-quotes, unless you are using Doxywizard) that should identify the
40 # project for which the documentation is generated. This name is used in the
41 # title of most generated pages and in a few other places.
44 PROJECT_NAME           = "CMSIS-DSP"
59 # in the documentation. The maximum height of the logo should not exceed 55
73 # sub-directories (in 2 levels) under the output directory of each output format
76 # putting all generated files in the same directory would otherwise causes
78 # control the number of sub-directories.
83 # Controls the number of sub-directories that will be created when
85 # level increment doubles the number of directories, resulting in 4096
87 # sub-directories are organized in 2 levels, the first level always has a fixed
94 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
95 # characters to appear in the names of generated files. If set to NO, non-ASCII
102 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
104 # information to generate all constant output in the proper language.
106 # Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, English
108 # Hindi, Hungarian, Indonesian, Italian, Japanese, Japanese-en (Japanese with
109 # English messages), Korean, Korean-en (Korean with English messages), Latvian,
111 # Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish,
118 # descriptions after the members that are listed in the file and class
133 # This tag implements a quasi-intelligent brief description abbreviator that is
134 # used to form the text in various listings. Each string in this list, if found
137 # text. Otherwise, the brief description is used as-is. If left blank, the
162 # inherited members of a class in the documentation of that class as if those
170 # before files name in the file list and in the header files. If set to NO the
176 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
177 # Stripping is only done if one of the specified strings matches the left-hand
178 # part of the path. The tag can be used to show relative paths in the file list.
188 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
189 # path mentioned in the documentation of a class, which tells the reader which
190 # header file to include in order to use a class. If left blank only the name of
193 # using the -I flag.
199 # support long names like on DOS, Mac, or CD-ROM.
205 # first line (until the first dot) of a Javadoc-style comment as the brief
206 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
216 # as being the beginning of a Javadoc-style comment "banner". If set to NO, the
217 # Javadoc-style will behave just like regular comments and it will not be
224 # line (until the first dot) of a Qt-style comment as the brief description. If
225 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
232 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
234 # to treat a multi-line C++ comment block as a detailed description. Set this
252 # documentation from any documented member that it re-implements.
264 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
265 # uses this value to replace tabs by spaces in code fragments.
270 # This tag can be used to specify a number of aliases that act as commands in
275 # will allow you to put the command \sideeffect (or @sideeffect) in the
276 # documentation, which will result in a user-defined paragraph with heading
277 # "Side Effects:". Note that you cannot put \n's in the value part of an alias
278 # to insert newlines (in the resulting output). You can put ^^ in the value part
279 # of an alias to insert a newline as if a physical newline was in the original
280 # file. When you need a literal { or } or , in the value part of an alias you
327 # extension. Doxygen has a built-in mapping, but you can override or extend it
330 # Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice,
332 # FortranFree, unknown formatted Fortran: Fortran. In the later case the parser
348 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
352 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
358 # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
359 # to that level are automatically included in the table of contents, even if
369 # be prevented in individual cases by putting a % sign in front of the word or
377 # tag to YES in order to let doxygen match functions declarations and
401 # doxygen to replace the get and set methods by a property in the documentation.
409 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
411 # member in the group (if any) for the other members of the group. By default
434 # are shown inside the group in which they are included (e.g. using \ingroup)
438 # Note that this feature does not work in combination with
445 # with only public data fields or simple typedef fields will be shown inline in
446 # the documentation of the scope in which they are defined (i.e. file,
456 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
459 # useful for C code in case the coding convention dictates that all compound
467 # an expensive process and often the same symbol appears multiple times in the
468 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
480 # cores available in the system. You can set it explicitly to a value larger
485 # encounter. Generating dot graphs in parallel is controlled by the
491 #---------------------------------------------------------------------------
493 #---------------------------------------------------------------------------
495 # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
506 # be included in the documentation.
512 # methods of a class will be included in the documentation.
518 # scope will be included in the documentation.
524 # included in the documentation.
530 # locally in source files will be included in the documentation. If set to NO,
531 # only classes defined in header files are included. Does not have any effect
537 # This flag is only useful for Objective-C code. If set to YES, local methods,
538 # which are defined in the implementation section but not in the interface are
539 # included in the documentation. If set to NO, only methods in the interface are
546 # extracted and appear in the documentation as a namespace called
554 # If this flag is set to YES, the name of an unnamed parameter in a declaration
556 # parameters remain unnamed in the output.
563 # members will be included in the various overviews, but no documentation
570 # undocumented classes that are normally visible in the class hierarchy. If set
571 # to NO, these classes will be included in the various overviews. This option
579 # declarations. If set to NO, these declarations will be included in the
600 # able to match the capabilities of the underlying filesystem. In case the
601 # filesystem is case sensitive (i.e. it supports files in the same directory
602 # whose names only differ in casing), the option must be set to YES to properly
603 # deal with such files in case they appear in the input. For filesystems that
605 # output files written for symbols that only differ in casing, such as for two
617 # their full class and namespace scopes in the documentation. If set to YES, the
637 # the files that are included by a file in the documentation of that file.
644 # which file to include in order to use the member.
650 # files with double quotes in the documentation rather than with sharp brackets.
655 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
663 # name. If set to NO, the members will appear in declaration order.
670 # name. If set to NO, the members will appear in declaration order. Note that
671 # this will also influence the order of the classes in the class list.
678 # destructors are listed first. If set to NO the constructors will appear in the
690 # appear in their defined order.
696 # fully-qualified names, including namespaces. If set to NO, the class list will
710 # accept a match between prototype and implementation in such cases.
716 # list. This list is created by putting \todo commands in the documentation.
722 # list. This list is created by putting \test commands in the documentation.
728 # list. This list is created by putting \bug commands in the documentation.
734 # the deprecated list. This list is created by putting \deprecated commands in
747 # initial value of a variable or macro / define can have for it to appear in the
751 # controlled using \showinitializer or \hideinitializer command in the
781 # popen()) the command command input-file, where command is the value of the
782 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
790 # output files in an output format independent way. To create the layout file
791 # that represents doxygen's defaults, run doxygen with the -l option. You can
807 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
812 #---------------------------------------------------------------------------
813 # Configuration options related to warning and progress messages
814 #---------------------------------------------------------------------------
840 # potential errors in the documentation, such as documenting some parameters in
875 # at the end of the doxygen process doxygen will return with a non-zero status.
892 # In the $text part of the WARN_FORMAT command it is possible that a reference
904 # error (stderr). In case the file specified cannot be opened for writing the
905 # warning and error messages are written to standard error. When as file - is
911 #---------------------------------------------------------------------------
913 #---------------------------------------------------------------------------
942 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
947 # The default value is: UTF-8.
949 INPUT_ENCODING         = UTF-8
956 # form: pattern=encoding (like *.php=ISO-8859-1). See cfg_input_encoding
963 # *.h) to filter out the source-files in the directories.
1109 # *.h) to filter out the source-files in the directories. If left blank all
1122 # that contain images that are to be included in the documentation (see the
1131 # <filter> <input-file>
1133 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
1144 # commands (so in case of a Windows batch file always use @echo OFF), should be
1197 #---------------------------------------------------------------------------
1199 #---------------------------------------------------------------------------
1202 # generated. Documented entities will be cross-referenced with these sources.
1204 # Note: To get rid of all source code in the generated output, make sure that
1236 # to YES then the hyperlinks from functions in REFERENCES_RELATION and
1243 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1254 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1260 # - Install the latest version of global
1261 # - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
1262 # - Make sure the INPUT points to the root of the source tree
1263 # - Run doxygen as normal
1265 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
1266 # tools must be available from the command line (i.e. in the search path).
1287 # which doxygen's built-in parser lacks the necessary type information.
1289 # generated with the -Duse_libclang=ON option for CMake.
1315 # specifying the -p option to a clang tool, such as clang-check. These options
1319 # generated with the -Duse_libclang=ON option for CMake.
1323 #---------------------------------------------------------------------------
1325 #---------------------------------------------------------------------------
1336 # tag works for classes, function and member names. The entity will be placed in
1343 #---------------------------------------------------------------------------
1345 #---------------------------------------------------------------------------
1353 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1367 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1375 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1387 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1397 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1398 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1403 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1409 # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1416 # style sheet in the list overrules the setting of the previous ones in the
1418 # Note: Since the styling of scrollbars can currently not be overruled in
1434 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1435 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1436 # files will be copied as-is; there are no commands or markers available.
1459 # will adjust the colors in the style sheet and background images according to
1460 # this color. Hue is specified as an angle on a color-wheel, see
1470 # in the HTML output. For a value of 0 the output will use gray-scales only. A
1478 # luminance component of the colors in the HTML output. Values below 100
1500 # consists of multiple levels of tabs that are statically embedded in every HTML
1517 # shown in the various tree structured indices initially; the user can expand
1522 # representing an infinite number of entries and will result in a full expanded
1533 # create a documentation set, doxygen will generate a Makefile in the HTML
1534 # output directory. Running make will produce the docset in that directory and
1535 # running make install will install the docset in
1560 # set bundle. This should be a reverse domain-name style string, e.g.
1568 # the documentation publisher. This should be a reverse domain-name style
1584 # on Windows. In the beginning of 2021 Microsoft took the original page, with
1586 # in maintenance mode). You can download the HTML help workshop from the web
1589 # ad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe).
1594 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1596 # words in the documentation. The HTML workshop also contains a viewer for
1604 # file. You can add a path in front of the file if the result should not be
1611 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
1619 # (YES) or that it should be included in the main .chm file (NO).
1632 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1665 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).
1674 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).
1683 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
1691 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
1698 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).
1704 # including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to
1712 # install this plugin and make it available under the help contents menu in
1734 # it. Since the tabs in the index contain the same information as the navigation
1741 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1743 # value is set to YES, a side panel will be generated containing a tree-like
1748 # further fine tune the look of the index (see "Fine-tuning the output"). As an
1771 # doxygen will group on one line in the generated HTML documentation.
1774 # in the overview section.
1781 # to set the initial width (in pixels) of the frame in which the tree is shown.
1788 # external symbols imported via tag files in a separate window.
1812 # Use this tag to change the font size of LaTeX formulas included as images in
1822 # to create new LaTeX commands to be used in formulas as building blocks. See
1829 # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
1830 # installed or if you want to formulas look prettier in the HTML output. When
1852 # http://docs.mathjax.org/en/v2.7-latest/output.html) and MathJax version 3
1855 # Possible values are: HTML-CSS (which is slower, but has the best
1860 # translated into HTML-CSS) and SVG.
1861 # The default value is: HTML-CSS.
1864 MATHJAX_FORMAT         = HTML-CSS
1874 # - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2
1875 # - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3
1883 # https://docs.mathjax.org/en/v2.7-latest/tex.html#tex-and-latex-extensions):
1895 # http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an
1912 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1915 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1973 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1989 #---------------------------------------------------------------------------
1991 #---------------------------------------------------------------------------
1999 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2010 # USE_PDFLATEX the default is pdflatex and when in the later case latex is
2020 # Note: This tag is used in the Makefile / make.bat.
2021 # See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
2029 # generate index for LaTeX. In case there is no backslash (\) as first character
2030 # it will be automatically added in the LaTeX code.
2031 # Note: This tag is used in the generated output file (.tex).
2032 # See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat.
2040 # trees in general.
2056 # that should be included in the LaTeX output. The package can be specified just
2067 # The LATEX_HEADER tag can be used to specify a user-defined LaTeX header for
2071 # doxygen -w latex new_header.tex new_footer.tex new_stylesheet.sty
2075 # Note: Only use a user-defined header if you know what you are doing!
2084 # The LATEX_FOOTER tag can be used to specify a user-defined LaTeX footer for
2090 # normally uses. Note: Only use a user-defined footer if you know what you are
2096 # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
2101 # style sheet in the list overrules the setting of the previous ones in the
2109 # directory. Note that the files will be copied as-is; there are no commands or
2143 # index chapters (such as File Index, Compound Index, etc.) in the output.
2173 #---------------------------------------------------------------------------
2175 #---------------------------------------------------------------------------
2185 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2194 # trees in general.
2222 # Set optional variables used in the generation of an RTF document. Syntax is
2224 # generated using doxygen -e rtf extensionFile.
2229 #---------------------------------------------------------------------------
2231 #---------------------------------------------------------------------------
2240 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2249 # man pages. In case the manual section does not start with a number, the number
2258 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
2265 # will generate one additional man file for each entity documented in the real
2273 #---------------------------------------------------------------------------
2275 #---------------------------------------------------------------------------
2284 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2292 # listings (including syntax highlighting and cross-referencing information) to
2301 # namespace members in file scope as well, matching the HTML output.
2307 #---------------------------------------------------------------------------
2309 #---------------------------------------------------------------------------
2318 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
2325 #---------------------------------------------------------------------------
2327 #---------------------------------------------------------------------------
2337 #---------------------------------------------------------------------------
2339 #---------------------------------------------------------------------------
2367 # The names of the make variables in the generated doxyrules.make file are
2368 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
2375 #---------------------------------------------------------------------------
2377 #---------------------------------------------------------------------------
2380 # C-preprocessor directives found in the sources and include files.
2386 # in the source code. If set to NO, only conditional compilation will be
2387 # performed. Macro expansion can be done in a controlled way by setting
2402 # If the SEARCH_INCLUDES tag is set to YES, the include files in the
2418 # patterns (like *.h and *.hpp) to filter out the header-files in the
2426 # defined before the preprocessor is started (similar to the -D option of e.g.
2437 # macro definition that is found in the sources will be used. Use the PREDEFINED
2439 # definition found in the source code.
2445 # remove all references to function-like macros that are alone on a line, have
2447 # are typically used for boiler-plate code, and will confuse the parser if not
2454 #---------------------------------------------------------------------------
2456 #---------------------------------------------------------------------------
2468 # the path). If a tag file is not located in the directory in which doxygen is
2479 # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
2487 # in the modules index. If set to NO, only the current project's groups will be
2493 # If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
2500 #---------------------------------------------------------------------------
2502 #---------------------------------------------------------------------------
2504 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2505 # then run dia to produce the diagram and insert it in the documentation. The
2507 # If left empty dia is assumed to be found in the default search path.
2520 # Bell Labs. The other options in this section have no effect if this option is
2527 # to run in parallel. When set to 0 doxygen will base this on the number of
2528 # processors available in the system. You can set it explicitly to a value
2537 # subgraphs. When you want a differently looking font in the dot files that
2541 # to find the font, which can be done by putting it in a standard location or by
2566 # You can set the path where dot can find font specified with fontname in
2574 # relations. In case HAVE_DOT is set as well dot will be used to draw the graph,
2575 # otherwise the built-in generator will be used. If the CLASS_GRAPH tag is set
2594 # in the manual.
2601 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2622 # methods without types and arguments in the UML graphs. If the DOT_UML_DETAILS
2624 # methods in the UML graphs. If the DOT_UML_DETAILS tag is set to NONE, doxygen
2625 # will not generate fields with class member information in the UML graphs. The
2673 # So in most cases it will be better to enable call graphs for selected
2685 # So in most cases it will be better to enable caller graphs for selected
2701 # dependencies a directory has on other directories in a graphical way. The
2703 # files in the directories.
2710 # of child directories generated in directory dependency graphs by dot.
2718 # output formats in the documentation of the dot tool (Graphviz (see:
2720 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2721 # to make the SVG files visible in IE 9+ (other browsers do not have this
2736 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2744 # found. If left blank, it is assumed the dot tool can be found in the path.
2750 # contain dot files that are included in the documentation (see the \dotfile
2757 # contain msc files that are included in the documentation (see the \mscfile
2763 # contain dia files that are included in the documentation (see the \diafile
2772 # \startuml command in this case and will not generate output for the diagram.
2782 # the !include statement in a plantuml block.
2787 # that will be shown in the graph. If the number of nodes in a graph becomes
2790 # children of the root node in a graph is already larger than
2811 # files in one run (i.e. multiple -o and -T options on the command line). This
2820 # explaining the meaning of the various boxes and arrows in the dot generated