Doxyfile - OpenGrok cross reference for /uoscore-uedhoc-latest/Doxyfile

Lines Matching +full:- +full:- +full:output +full:- +full:file
3 # This file describes the settings to be used by the documentation system
16 #---------------------------------------------------------------------------
18 #---------------------------------------------------------------------------
21 # file that follow. The default is UTF-8 which is also the encoding used for all
25 # The default value is: UTF-8.
27 DOXYFILE_ENCODING      = UTF-8
30 # double-quotes, unless you are using Doxywizard) that should identify the
52 # the logo to the output directory.
61 OUTPUT_DIRECTORY       = /home/stefan/workspaces/github/uoscore-uedhoc/doxygen
63 # If the CREATE_SUBDIRS tag is set to YES then doxygen will create 4096 sub-
64 # directories (in 2 levels) under the output directory of each output format and
68 # performance problems for the file system.
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
83 # information to generate all constant output in the proper language.
85 # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
87 # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
88 # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
90 # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
98 # information to generate all generated output in the proper direction.
105 # descriptions after the members that are listed in the file and class
120 # This tag implements a quasi-intelligent brief description abbreviator that is
124 # text. Otherwise, the brief description is used as-is. If left blank, the
126 # the entity):The $name class, The $name widget, The $name file, is, provides,
131                          "The $name file" \
157 # before files name in the file list and in the header files. If set to NO the
158 # shortest path that makes the file name unique will be used
163 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
164 # Stripping is only done if one of the specified strings matches the left-hand
165 # part of the path. The tag can be used to show relative paths in the file list.
175 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
177 # header file to include in order to use a class. If left blank only the name of
178 # the header file containing the class definition is used. Otherwise one should
180 # using the -I flag.
185 # less readable) file names. This can be useful is your file systems doesn't
186 # support long names like on DOS, Mac, or CD-ROM.
192 # first line (until the first dot) of a Javadoc-style comment as the brief
193 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
203 # as being the beginning of a Javadoc-style comment "banner". If set to NO, the
204 # Javadoc-style will behave just like regular comments and it will not be
211 # line (until the first dot) of a Qt-style comment as the brief description. If
212 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
219 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
221 # to treat a multi-line C++ comment block as a detailed description. Set this
239 # documentation from any documented member that it re-implements.
246 # of the file/class/namespace that contains it.
263 # documentation, which will result in a user-defined paragraph with heading
265 # newlines (in the resulting output). You can put ^^ in the value part of an
266 # alias to insert a newline as if a physical newline was in the original file.
275 # only. Doxygen will then generate output that is more tailored for C. For
283 # Python sources only. Doxygen will then generate output that is more tailored
291 # sources. Doxygen will then generate output that is tailored for Fortran.
297 # sources. Doxygen will then generate output that is tailored for VHDL.
303 # sources only. Doxygen will then generate output that is more tailored for that
312 # extension. Doxygen has a built-in mapping, but you can override or extend it
313 # using this tag. The format is ext=language, where ext is a file extension, and
315 # Csharp (C#), C, C++, D, PHP, md (Markdown), Objective-C, Python, Slice, VHDL,
329 # Note see also the list of default file extension mappings.
333 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
336 # The output of markdown processing is further processed by doxygen, so you can
343 # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
361 # to include (a tag file for) the STL sources as input, then you should set this
431 # the documentation of the scope in which they are defined (i.e. file,
442 # with name TypeT. When disabled the typedef will appear as a member of a file,
453 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
476 #---------------------------------------------------------------------------
478 #---------------------------------------------------------------------------
482 # class members and static file members will be hidden unless the
508 # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
522 # This flag is only useful for Objective-C code. If set to YES, local methods,
532 # 'anonymous_namespace{file}', where file will be replaced with the base name of
533 # the file that contains the anonymous namespace. By default anonymous namespace
541 # parameters remain unnamed in the output.
589 # output files written for symbols that only differ in casing, such as for two
614 # the files that are included by a file in the documentation of that file.
621 # which file to include in order to use the member.
639 # (detailed) documentation of file and class members alphabetically by member
646 # descriptions of file, namespace and class members alphabetically by member
673 # fully-qualified names, including namespaces. If set to NO, the class list will
756 # doxygen should invoke to get the current version for each file (typically from
758 # popen()) the command command input-file, where command is the value of the
759 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
760 # by doxygen. Whatever the program writes to standard output is used as the file
765 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
766 # by doxygen. The layout file controls the global structure of the generated
767 # output files in an output format independent way. To create the layout file
768 # that represents doxygen's defaults, run doxygen with the -l option. You can
769 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
770 # will be used as the name of the layout file.
772 # Note that if you run doxygen from a directory containing a file called
788 #---------------------------------------------------------------------------
790 #---------------------------------------------------------------------------
793 # standard output by doxygen. If QUIET is set to YES this implies that the
835 # at the end of the doxygen process doxygen will return with a non-zero status.
842 # can produce. The string should contain the $file, $line, and $text tags, which
843 # will be replaced by the file and line number from which the warning originated
845 # be replaced by the version of the file (if it could be obtained via
847 # The default value is: $file:$line: $text.
849 WARN_FORMAT            = "$file:$line: $text"
851 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
852 # messages should be written. If left blank the output is written to standard
857 #---------------------------------------------------------------------------
859 #---------------------------------------------------------------------------
862 # documented source files. You may enter file names like myfile.cpp or
867 INPUT                  = /home/stefan/workspaces/github/uoscore-uedhoc/inc
870 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
874 # The default value is: UTF-8.
876 INPUT_ENCODING         = UTF-8
880 # *.h) to filter out the source-files in the directories.
886 # Note the list of default checked file patterns might differ from the list of
887 # default file extension mappings.
958 # directories that are symbolic links (a Unix file system feature) are excluded
968 # Note that the wildcards are matched against the file with absolute path, so to
975 # output. The symbol name can be a fully qualified name, a word, or if the
979 # Note that the wildcards are matched against the file with absolute path, so to
992 # *.h) to filter out the source-files in the directories. If left blank all
1011 # invoke to filter for each input file. Doxygen will invoke the filter program
1014 # <filter> <input-file>
1016 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
1017 # name of an input file. Doxygen will then use the output that the filter
1018 # program writes to standard output. If FILTER_PATTERNS is specified, this tag
1022 # code is scanned, but not when the output code is generated. If lines are added
1031 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
1032 # basis. Doxygen will compare the file name with each pattern and apply the
1036 # patterns match the file name, INPUT_FILTER is applied.
1051 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
1059 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
1062 # and want to reuse the introduction page also for the doxygen output.
1066 #---------------------------------------------------------------------------
1068 #---------------------------------------------------------------------------
1071 # generated. Documented entities will be cross-referenced with these sources.
1073 # Note: To get rid of all source code in the generated output, make sure that
1115 # will make the HTML file larger and loading of large files a bit slower, you
1123 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1129 # - Install the latest version of global
1130 # - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
1131 # - Make sure the INPUT points to the root of the source tree
1132 # - Run doxygen as normal
1138 # source code will now point to the output of htags.
1145 # verbatim copy of the header file for each class for which an include is
1156 # which doxygen's built-in parser lacks the necessary type information.
1158 # generated with the -Duse_libclang=ON option for CMake.
1178 # path to the directory containing a file called compile_commands.json. This
1179 # file is the compilation database (see:
1182 # specifying the -p option to a clang tool, such as clang-check. These options
1186 # generated with the -Duse_libclang=ON option for CMake.
1190 #---------------------------------------------------------------------------
1192 #---------------------------------------------------------------------------
1209 #---------------------------------------------------------------------------
1210 # Configuration options related to the HTML output
1211 #---------------------------------------------------------------------------
1213 # If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output
1226 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1233 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1237 # To get valid HTML the header file that includes any scripts and style sheets
1241 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1243 # and then modify the file new_header.html. See also section "Doxygen usage"
1253 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1263 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1264 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1265 # the HTML output. If left blank doxygen will generate a default style sheet.
1275 # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1280 # Doxygen will copy the style sheet files to the output directory.
1289 # other source files which should be copied to the HTML output directory. Note
1290 # that these files will be copied to the base HTML output directory. Use the
1292 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1293 # files will be copied as-is; there are no commands or markers available.
1298 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1310 # in the HTML output. For a value of 0 the output will use grayscales only. A
1318 # luminance component of the colors in the HTML output. Values below 100
1319 # gradually make the output lighter, whereas values above 100 make the output
1374 # output directory. Running make will produce the docset in that directory and
1393 # set bundle. This should be a reverse domain-name style string, e.g.
1401 # the documentation publisher. This should be a reverse domain-name style
1416 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1418 # https://www.microsoft.com/en-us/download/details.aspx?id=21138) on Windows.
1420 # The HTML Help Workshop contains a compiler that can convert all HTML output
1421 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1432 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1433 # file. You can add a path in front of the file if the result should not be
1434 # written to the html output directory.
1440 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
1442 # The file has to be specified with full path.
1447 # The GENERATE_CHI flag controls if a separate .chi index file is generated
1448 # (YES) or that it should be included in the main .chm file (NO).
1455 # and project file content.
1461 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1476 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1485 # the file name of the resulting .qch file. The path specified is relative to
1486 # the HTML output folder.
1492 # Project output. For more information please see Qt Help Project / Namespace
1494 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).
1501 # Help Project output. For more information please see Qt Help Project / Virtual
1503 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders).
1512 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
1520 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters).
1527 # https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).
1533 # including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to
1534 # run qhelpgenerator on the generated .qhp file.
1570 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1572 # value is set to YES, a side panel will be generated containing a tree-like
1577 # further fine-tune the look of the index. As an example, the default style
1614 # the HTML output. These images will generally look nicer at scaled resolutions.
1625 # output directory to force them to be regenerated.
1636 # the HTML output directory before the changes have effect.
1650 # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
1651 # installed or if you want to formulas look prettier in the HTML output. When
1659 # When MathJax is enabled you can set the default output format to be used for
1660 # the MathJax output. See the MathJax site (see:
1661 # http://docs.mathjax.org/en/v2.7-latest/output.html) for more details.
1662 # Possible values are: HTML-CSS (which is slower, but has the best
1664 # The default value is: HTML-CSS.
1667 MATHJAX_FORMAT         = HTML-CSS
1670 # output directory using the MATHJAX_RELPATH option. The destination directory
1672 # is located at the same level as the HTML output directory, then
1689 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1692 # http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an
1699 # the HTML output. The underlying search engine uses javascript and DHTML and
1723 # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
1732 # script for searching. Instead the search results are written to an XML file
1761 # search data is written to a file for indexing by an external tool. With the
1762 # SEARCHDATA_FILE tag the name of this file can be specified.
1763 # The default file is: searchdata.xml.
1777 # projects other than the one defined by this configuration file, but that are
1786 #---------------------------------------------------------------------------
1787 # Configuration options related to the LaTeX output
1788 #---------------------------------------------------------------------------
1790 # If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.
1808 # chosen this is overwritten by pdflatex. For specific output languages the
1810 # the output language.
1818 # See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
1820 # The default file is: makeindex.
1828 # Note: This tag is used in the generated output file (.tex).
1853 # that should be included in the LaTeX output. The package can be specified just
1868 # default header to a separate file.
1870 # Note: Only use a user-defined header if you know what you are doing! The
1886 # Note: Only use a user-defined footer if you know what you are doing!
1891 # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1894 # will copy the style sheet files to the output directory.
1903 # other source files which should be copied to the LATEX_OUTPUT output
1904 # directory. Note that the files will be copied as-is; there are no commands or
1911 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
1912 # contain links (just like the HTML output) instead of page references. This
1913 # makes the output suitable for online browsing using a PDF viewer.
1920 # specified with LATEX_CMD_NAME to generate the PDF file directly from the LaTeX
1939 # index chapters (such as File Index, Compound Index, etc.) in the output.
1946 # code with syntax highlighting in the LaTeX output.
1965 # to NO can help when comparing the output of multiple runs.
1979 #---------------------------------------------------------------------------
1980 # Configuration options related to the RTF output
1981 #---------------------------------------------------------------------------
1983 # If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The
1984 # RTF output is optimized for Word 97 and may not look too pretty with other RTF
2007 # contain hyperlink fields. The RTF file will contain links (just like the HTML
2008 # output) instead of page references. This makes the output suitable for online
2018 # Load stylesheet definitions from file. Syntax is similar to doxygen's
2019 # configuration file, i.e. a series of assignments. You only have to provide
2029 # similar to doxygen's configuration file. A template extensions file can be
2030 # generated using doxygen -e rtf extensionFile.
2036 # with syntax highlighting in the RTF output.
2045 #---------------------------------------------------------------------------
2046 # Configuration options related to the man page output
2047 #---------------------------------------------------------------------------
2080 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
2081 # will generate one additional man file for each entity documented in the real
2089 #---------------------------------------------------------------------------
2090 # Configuration options related to the XML output
2091 #---------------------------------------------------------------------------
2093 # If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
2108 # listings (including syntax highlighting and cross-referencing information) to
2109 # the XML output. Note that enabling this will significantly increase the size
2110 # of the XML output.
2117 # namespace members in file scope as well, matching the HTML output.
2123 #---------------------------------------------------------------------------
2124 # Configuration options related to the DOCBOOK output
2125 #---------------------------------------------------------------------------
2142 # program listings (including syntax highlighting and cross-referencing
2143 # information) to the DOCBOOK output. Note that enabling this will significantly
2144 # increase the size of the DOCBOOK output.
2150 #---------------------------------------------------------------------------
2151 # Configuration options for the AutoGen Definitions output
2152 #---------------------------------------------------------------------------
2155 # AutoGen Definitions (see http://autogen.sourceforge.net/) file that captures
2162 #---------------------------------------------------------------------------
2163 # Configuration options related to Sqlite3 output
2164 #---------------------------------------------------------------------------
2166 #---------------------------------------------------------------------------
2167 # Configuration options related to the Perl module output
2168 #---------------------------------------------------------------------------
2171 # file that captures the structure of the code including all documentation.
2180 # output from the Perl module output.
2186 # If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely
2189 # size of the Perl module output will be much smaller and Perl will parse it
2196 # The names of the make variables in the generated doxyrules.make file are
2204 #---------------------------------------------------------------------------
2206 #---------------------------------------------------------------------------
2209 # C-preprocessor directives found in the sources and include files.
2246 # patterns (like *.h and *.hpp) to filter out the header-files in the
2254 # defined before the preprocessor is started (similar to the -D option of e.g.
2273 # remove all references to function-like macros that are alone on a line, have
2275 # are typically used for boiler-plate code, and will confuse the parser if not
2282 #---------------------------------------------------------------------------
2284 #---------------------------------------------------------------------------
2287 # file the location of the external documentation should be added. The format of
2288 # a tag file without this location is as follows:
2295 # Note: Each tag file must have a unique name (where the name does NOT include
2296 # the path). If a tag file is not located in the directory in which doxygen is
2301 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2302 # tag file that is based on the input files it reads. See section "Linking to
2328 #---------------------------------------------------------------------------
2330 #---------------------------------------------------------------------------
2473 # YES then doxygen will generate a graph for each documented file showing the
2474 # direct and indirect include dependencies of the file with other documented
2482 # set to YES then doxygen will generate a graph for each documented file showing
2483 # the direct and indirect include dependencies of the file with other documented
2532 # output formats in the documentation of the dot tool (Graphviz (see:
2585 # path where java can find the plantuml.jar file. If left blank, it is assumed
2588 # will not generate output for the diagram.
2593 # configuration file for plantuml.
2631 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2638 # Set the DOT_MULTI_TARGETS tag to YES to allow dot to generate multiple output
2639 # files in one run (i.e. multiple -o and -T options on the command line). This