Lines Matching refs:file
3 # This file describes the settings to be used by the documentation system
17 # This tag specifies the encoding used for all characters in the config file
62 # otherwise cause performance problems for the file system.
81 # the file and class documentation (similar to JavaDoc).
100 # "The $name file" "is" "provides" "specifies" "contains"
119 # path before files name in the file list and in the header files. If set
120 # to NO the shortest path that makes the file name unique will be used.
127 # the path. The tag can be used to show relative paths in the file list.
137 # the reader which header file to include in order to use a class.
138 # If left blank only the name of the header file containing the class
145 # (but less readable) file names. This can be useful if your file system
182 # be part of the file/class/namespace that contains it.
236 # using this tag. The format is ext=language, where ext is a file extension,
263 # to include (a tag file for) the STL sources as input, then you should
315 # of the scope in which they are defined (i.e. file, namespace, or group
325 # with name TypeT. When disabled the typedef will appear as a member of a file,
349 # Private class members and static file members will be hidden unless
364 # If the EXTRACT_STATIC tag is set to YES all static members of a file
384 # 'anonymous_namespace{file}', where file will be replaced with the base
385 # name of the file that contains the anonymous namespace. By default
427 # file names in lower-case letters. If set to YES upper-case letters are also
429 # in case and if your file system supports case sensitive file names. Windows
441 # will put a list of the files that are included by a file in the documentation
442 # of that file.
458 # will sort the (detailed) documentation of file and class members
465 # brief documentation of file, namespace and class members alphabetically
565 # doxygen should invoke to get the current version for each file (typically from
567 # popen()) the command <command> <input-file>, where <command> is the value of
568 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
570 # is used as the file version. See the manual for examples.
574 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
575 # by doxygen. The layout file controls the global structure of the generated
576 # output files in an output format independent way. To create the layout file
578 # You can optionally specify a file name after the option, if omitted
579 # DoxygenLayout.xml will be used as the name of the layout file.
590 # file names with spaces, bibtex cannot handle them.
631 # doxygen can produce. The string should contain the $file, $line, and $text
632 # tags, which will be replaced by the file and line number from which the
634 # $version, which will be replaced by the version of the file (if it could
637 WARN_FORMAT = "$file:$line: $text"
639 # The WARN_LOGFILE tag can be used to specify a file to which warning
650 # documented source files. You may enter file names like "myfile.cpp" or
733 # directories that are symbolic links (a Unix file system feature) are excluded
741 # against the file with absolute path, so to exclude all test directories
781 # invoke to filter for each input file. Doxygen will invoke the filter program
782 # by executing (via popen()) the command <filter> <input-file>, where <filter>
783 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
784 # input file. Doxygen will then use the output that the filter program writes
790 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
791 # basis. Doxygen will compare the file name with each pattern and apply the
795 # non of the patterns match the file name, INPUT_FILTER is applied.
805 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
813 # If the USE_MD_FILE_AS_MAINPAGE tag refers to the name of a markdown file that
870 # will generate a verbatim copy of the header file for each class for
913 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
952 # robust against future updates. Doxygen will copy the style sheet file to
961 # files. In the HTML_STYLESHEET file, use the file name only. Also note that
1055 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
1061 # be used to specify the file name of the resulting .chm file. You
1062 # can add a path in front of the file if the result should not be
1068 # be used to specify the location (absolute path including file name) of
1075 # controls if a separate .chi index file is generated (YES) or that
1076 # it should be included in the master .chm file (NO).
1081 # is used to encode HtmlHelp index (hhk), content (hhc) and project file
1088 # normal table of contents (NO) in the .chm file.
1098 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
1105 # be used to specify the file name of the resulting .qch file.
1146 # .qhp file.
1267 # searching and an index file used by the script. When EXTERNAL_SEARCH is
1274 # script for searching. Instead the search results are written to an XML file
1292 # search data is written to a file for indexing by an external tool. With the
1293 # SEARCHDATA_FILE tag the name of this file can be specified.
1305 # projects other than the one defined by this configuration file, but that are
1374 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
1435 # will contain hyperlink fields. The RTF file will
1443 # Load style sheet definitions from file. Syntax is similar to doxygen's
1444 # config file, i.e. a series of assignments. You only have to provide
1450 # Syntax is similar to doxygen's config file.
1475 # then it will generate one additional man file for each entity
1487 # generate an XML file that captures the structure of
1511 # generate an AutoGen Definitions (see autogen.sf.net) file
1523 # generate a Perl module file that captures the structure of
1544 # The names of the make variables in the generated doxyrules.make file
1637 # tag file the location of the external documentation should be added. The
1638 # format of a tag file without this location is as follows:
1643 # or URLs. Note that each tag file must have a unique name (where the name does
1644 # NOT include the path). If a tag file is not located in the directory in which
1649 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1650 # a tag file that is based on the input files it reads.
1774 # file showing the direct and indirect include dependencies of the file with
1781 # documented header file showing the documented files that directly or
1782 # indirectly include this file.