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
48 # otherwise cause performance problems for the file system.
67 # the file and class documentation (similar to JavaDoc).
86 # "The $name file" "is" "provides" "specifies" "contains"
105 # path before files name in the file list and in the header files. If set
106 # to NO the shortest path that makes the file name unique will be used.
113 # the path. The tag can be used to show relative paths in the file list.
121 # the reader which header file to include in order to use a class.
122 # If left blank only the name of the header file containing the class
129 # (but less readable) file names. This can be useful is your file systems
166 # be part of the file/class/namespace that contains it.
213 # The format is ext=language, where ext is a file extension, and language is one of
222 # to include (a tag file for) the STL sources as input, then you should
268 # with name TypeT. When disabled the typedef will appear as a member of a file,
297 # Private class members and static file members will be hidden unless
307 # If the EXTRACT_STATIC tag is set to YES all static members of a file
327 # 'anonymous_namespace{file}', where file will be replaced with the base
328 # name of the file that contains the anonymous namespace. By default
370 # file names in lower-case letters. If set to YES upper-case letters are also
372 # in case and if your file system supports case sensitive file names. Windows
384 # will put a list of the files that are included by a file in the documentation
385 # of that file.
395 # will sort the (detailed) documentation of file and class members
402 # brief documentation of file, namespace and class members alphabetically
489 # doxygen should invoke to get the current version for each file (typically from
491 # popen()) the command <command> <input-file>, where <command> is the value of
492 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
494 # is used as the file version. See the manual for examples.
498 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by
499 # doxygen. The layout file controls the global structure of the generated output files
500 # in an output format independent way. The create the layout file that represents
502 # file name after the option, if omitted DoxygenLayout.xml will be used as the name
503 # of the layout file.
544 # doxygen can produce. The string should contain the $file, $line, and $text
545 # tags, which will be replaced by the file and line number from which the
547 # $version, which will be replaced by the version of the file (if it could
550 WARN_FORMAT            = "$file:$line: $text"
552 # The WARN_LOGFILE tag can be used to specify a file to which warning
563 # documented source files. You may enter file names like "myfile.cpp" or
607 # against the file with absolute path, so to exclude all test directories
647 # invoke to filter for each input file. Doxygen will invoke the filter program
648 # by executing (via popen()) the command <filter> <input-file>, where <filter>
649 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
650 # input file. Doxygen will then use the output that the filter program writes
657 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
659 # Doxygen will compare the file name with each pattern and apply the
725 # will generate a verbatim copy of the header file for each class for
768 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
790 # the style sheet file to the HTML output directory, so don't put your own
837 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
843 # be used to specify the file name of the resulting .chm file. You
844 # can add a path in front of the file if the result should not be
850 # be used to specify the location (absolute path including file name) of
857 # controls if a separate .chi index file is generated (YES) or that
858 # it should be included in the master .chm file (NO).
863 # is used to encode HtmlHelp index (hhk), content (hhc) and project file
870 # normal table of contents (NO) in the .chm file.
880 # are set, an additional index file will be generated that can be used as input for
887 # be used to specify the file name of the resulting .qch file.
924 # .qhp file.
1021 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
1069 # will contain hyperlink fields. The RTF file will
1077 # Load stylesheet definitions from file. Syntax is similar to doxygen's
1078 # config file, i.e. a series of assignments. You only have to provide
1084 # Syntax is similar to doxygen's config file.
1109 # then it will generate one additional man file for each entity
1121 # generate an XML file that captures the structure of
1156 # generate an AutoGen Definitions (see autogen.sf.net) file
1168 # generate a Perl module file that captures the structure of
1191 # The names of the make variables in the generated doxyrules.make file
1270 # can be added for each tagfile. The format of a tag file without
1280 # Note that each tag file must have a unique name
1282 # If a tag file is not located in the directory in which doxygen
1287 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1288 # a tag file that is based on the input files it reads.
1399 # file showing the direct and indirect include dependencies of the file with
1406 # documented header file showing the documented files that directly or
1407 # indirectly include this file.