Lines Matching refs:file
3 # This file describes the settings to be used by the documentation system
18 # Use doxygen to compare the used configuration file with the template
19 # configuration file:
21 # Use doxygen to compare the used configuration file with the template
22 # configuration file without replacing the environment variables or CMake type
31 # file that follow. The default is UTF-8 which is also the encoding used for all
78 # performance problems for the file system. Adapt CREATE_SUBDIRS_LEVEL to
119 # descriptions after the members that are listed in the file and class
140 # the entity):The $name class, The $name widget, The $name file, is, provides,
145 "The $name file" \
171 # before files name in the file list and in the header files. If set to NO the
172 # shortest path that makes the file name unique will be used
179 # part of the path. The tag can be used to show relative paths in the file list.
191 # header file to include in order to use a class. If left blank only the name of
192 # the header file containing the class definition is used. Otherwise one should
199 # less readable) file names. This can be useful is your file systems doesn't
260 # of the file/class/namespace that contains it.
281 # file. When you need a literal { or } or , in the value part of an alias you
327 # using this tag. The format is ext=language, where ext is a file extension, and
343 # Note see also the list of default file extension mappings.
386 # to include (a tag file for) the STL sources as input, then you should set this
456 # the documentation of the scope in which they are defined (i.e. file,
467 # with name TypeT. When disabled the typedef will appear as a member of a file,
515 # class members and static file members will be hidden unless the
541 # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
565 # 'anonymous_namespace{file}', where file will be replaced with the base name of
566 # the file that contains the anonymous namespace. By default anonymous namespace
649 # will show which file needs to be included to use the class.
655 # the files that are included by a file in the documentation of that file.
662 # which file to include in order to use the member.
680 # (detailed) documentation of file and class members alphabetically by member
687 # descriptions of file, namespace and class members alphabetically by member
797 # doxygen should invoke to get the current version for each file (typically from
799 # popen()) the command command input-file, where command is the value of the
800 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
801 # by doxygen. Whatever the program writes to standard output is used as the file
806 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
807 # by doxygen. The layout file controls the global structure of the generated
808 # output files in an output format independent way. To create the layout file
810 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
811 # will be used as the name of the layout file. See also section "Changing the
814 # Note that if you run doxygen from a directory containing a file called
898 # besides being in the defined file also be shown at the end of a run, unless
907 # can produce. The string should contain the $file, $line, and $text tags, which
908 # will be replaced by the file and line number from which the warning originated
910 # be replaced by the version of the file (if it could be obtained via
913 # The default value is: $file:$line: $text.
915 WARN_FORMAT = "$file:$line: $text"
921 # WARN_LINE_FORMAT = "'vi $file +$line'"
923 # The default value is: at line $line of file $file.
925 WARN_LINE_FORMAT = "at line $line of file $file"
927 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
929 # error (stderr). In case the file specified cannot be opened for writing the
930 # warning and error messages are written to standard error. When as file - is
941 # documented source files. You may enter file names like myfile.cpp or
961 # character encoding on a per file pattern basis. Doxygen will compare the file
977 # Note the list of default checked file patterns might differ from the list of
978 # default file extension mappings.
1044 # directories that are symbolic links (a Unix file system feature) are excluded
1054 # Note that the wildcards are matched against the file with absolute path, so to
1094 # invoke to filter for each input file. Doxygen will invoke the filter program
1097 # <filter> <input-file>
1099 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
1100 # name of an input file. Doxygen will then use the output that the filter
1110 # commands (so in case of a Windows batch file always use @echo OFF), should be
1119 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
1120 # basis. Doxygen will compare the file name with each pattern and apply the
1124 # patterns match the file name, INPUT_FILTER is applied.
1139 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
1147 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
1212 # will make the HTML file larger and loading of large files a bit slower, you
1227 # - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
1242 # verbatim copy of the header file for each class for which an include is
1286 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1293 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1297 # To get valid HTML the header file that includes any scripts and style sheets
1303 # and then modify the file new_header.html. See also section "Doxygen usage"
1357 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1499 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1508 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1519 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1520 # file. You can add a path in front of the file if the result should not be
1527 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
1529 # The file has to be specified with full path.
1534 # The GENERATE_CHI flag controls if a separate .chi index file is generated
1535 # (YES) or that it should be included in the main .chm file (NO).
1542 # and project file content.
1548 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1573 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1582 # the file name of the resulting .qch file. The path specified is relative to
1630 # including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to
1631 # run qhelpgenerator on the generated .qhp file.
1819 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1853 # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
1862 # script for searching. Instead the search results are written to an XML file
1891 # search data is written to a file for indexing by an external tool. With the
1892 # SEARCHDATA_FILE tag the name of this file can be specified.
1893 # The default file is: searchdata.xml.
1907 # projects other than the one defined by this configuration file, but that are
1948 # See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
1950 # The default file is: makeindex.
1958 # Note: This tag is used in the generated output file (.tex).
1999 # and then modify the file new_header.tex. See also section "Doxygen usage" for
2043 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
2052 # specified with LATEX_CMD_NAME to generate the PDF file directly from the LaTeX
2127 # contain hyperlink fields. The RTF file will contain links (just like the HTML
2138 # Load stylesheet definitions from file. Syntax is similar to doxygen's
2139 # configuration file, i.e. a series of assignments. You only have to provide
2149 # similar to doxygen's configuration file. A template extensions file can be
2191 # will generate one additional man file for each entity documented in the real
2203 # If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
2227 # namespace members in file scope as well, matching the HTML output.
2256 # AutoGen Definitions (see https://autogen.sourceforge.net/) file that captures
2268 # file that captures the structure of the code including all documentation.
2293 # The names of the make variables in the generated doxyrules.make file are
2388 # file the location of the external documentation should be added. The format of
2389 # a tag file without this location is as follows:
2396 # Note: Each tag file must have a unique name (where the name does NOT include
2397 # the path). If a tag file is not located in the directory in which doxygen is
2402 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2403 # tag file that is based on the input files it reads. See section "Linking to
2582 # YES then doxygen will generate a graph for each documented file showing the
2583 # direct and indirect include dependencies of the file with other documented
2593 # set to YES then doxygen will generate a graph for each documented file showing
2594 # the direct and indirect include dependencies of the file with other documented
2708 # path where java can find the plantuml.jar file or to the filename of jar file
2716 # configuration file for plantuml.
2783 # output file formats "png", "eps", "svg", and "ismap".