Lines Matching refs:file
3 # This file describes the settings to be used by the documentation system
20 # This tag specifies the encoding used for all characters in the config file
72 # performance problems for the file system.
103 # descriptions after the members that are listed in the file and class
124 # the entity):The $name class, The $name widget, The $name file, is, provides,
145 # before files name in the file list and in the header files. If set to NO the
146 # shortest path that makes the file name unique will be used
153 # part of the path. The tag can be used to show relative paths in the file list.
165 # header file to include in order to use a class. If left blank only the name of
166 # the header file containing the class definition is used. Otherwise one should
173 # less readable) file names. This can be useful is your file systems doesn't
216 # of the file/class/namespace that contains it.
236 # alias to insert a newline as if a physical newline was in the original file.
278 # using this tag. The format is ext=language, where ext is a file extension, and
322 # to include (a tag file for) the STL sources as input, then you should set this
392 # the documentation of the scope in which they are defined (i.e. file,
403 # with name TypeT. When disabled the typedef will appear as a member of a file,
430 # class members and static file members will be hidden unless the
450 # If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
474 # 'anonymous_namespace{file}', where file will be replaced with the base name of
475 # the file that contains the anonymous namespace. By default anonymous namespace
518 # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
521 # in case and if your file system supports case sensitive file names. Windows
542 # the files that are included by a file in the documentation of that file.
549 # which file to include in order to use the member.
567 # (detailed) documentation of file and class members alphabetically by member
574 # descriptions of file, namespace and class members alphabetically by member
684 # doxygen should invoke to get the current version for each file (typically from
686 # popen()) the command command input-file, where command is the value of the
687 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
688 # by doxygen. Whatever the program writes to standard output is used as the file
693 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
694 # by doxygen. The layout file controls the global structure of the generated
695 # output files in an output format independent way. To create the layout file
697 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
698 # will be used as the name of the layout file.
700 # Note that if you run doxygen from a directory containing a file called
766 # can produce. The string should contain the $file, $line, and $text tags, which
767 # will be replaced by the file and line number from which the warning originated
769 # be replaced by the version of the file (if it could be obtained via
771 # The default value is: $file:$line: $text.
773 WARN_FORMAT = "$file:$line: $text"
775 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
786 # documented source files. You may enter file names like myfile.cpp or
844 # directories that are symbolic links (a Unix file system feature) are excluded
854 # Note that the wildcards are matched against the file with absolute path, so to
865 # Note that the wildcards are matched against the file with absolute path, so to
897 # invoke to filter for each input file. Doxygen will invoke the filter program
900 # <filter> <input-file>
902 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
903 # name of an input file. Doxygen will then use the output that the filter
917 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
918 # basis. Doxygen will compare the file name with each pattern and apply the
922 # patterns match the file name, INPUT_FILTER is applied.
937 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
945 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
1001 # will make the HTML file larger and loading of large files a bit slower, you
1016 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
1031 # verbatim copy of the header file for each class for which an include is
1111 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1118 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1122 # To get valid HTML the header file that includes any scripts and style sheets
1128 # and then modify the file new_header.html. See also section "Doxygen usage"
1177 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1300 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1305 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1316 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1317 # file. You can add a path in front of the file if the result should not be
1324 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
1326 # The file has to be specified with full path.
1331 # The GENERATE_CHI flag controls if a separate .chi index file is generated
1332 # (YES) or that it should be included in the master .chm file (NO).
1339 # and project file content.
1345 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1360 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1369 # the file name of the resulting .qch file. The path specified is relative to
1414 # generated .qhp file.
1554 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1587 # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
1596 # script for searching. Instead the search results are written to an XML file
1623 # search data is written to a file for indexing by an external tool. With the
1624 # SEARCHDATA_FILE tag the name of this file can be specified.
1625 # The default file is: searchdata.xml.
1639 # projects other than the one defined by this configuration file, but that are
1671 # The default file is: latex.
1678 # The default file is: makeindex.
1716 # default header to a separate file.
1759 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
1768 # the PDF file directly from the LaTeX files. Set this option to YES, to get a
1845 # contain hyperlink fields. The RTF file will contain links (just like the HTML
1856 # Load stylesheet definitions from file. Syntax is similar to doxygen's config
1857 # file, i.e. a series of assignments. You only have to provide replacements,
1867 # similar to doxygen's config file. A template extensions file can be generated
1919 # will generate one additional man file for each entity documented in the real
1931 # If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that
1986 # AutoGen Definitions (see http://autogen.sourceforge.net/) file that captures
1998 # file that captures the structure of the code including all documentation.
2023 # The names of the make variables in the generated doxyrules.make file are
2139 # file the location of the external documentation should be added. The format of
2140 # a tag file without this location is as follows:
2147 # Note: Each tag file must have a unique name (where the name does NOT include
2148 # the path). If a tag file is not located in the directory in which doxygen is
2153 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2154 # tag file that is based on the input files it reads. See section "Linking to
2184 # The default file (with absolute path) is: /usr/bin/perl.
2320 # YES then doxygen will generate a graph for each documented file showing the
2321 # direct and indirect include dependencies of the file with other documented
2329 # set to YES then doxygen will generate a graph for each documented file showing
2330 # the direct and indirect include dependencies of the file with other documented
2430 # path where java can find the plantuml.jar file. If left blank, it is assumed
2438 # configuration file for plantuml.