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 that
48 # otherwise cause performance problems for the file system.
66 # the file and class documentation (similar to JavaDoc).
85 # "The $name file" "is" "provides" "specifies" "contains"
104 # path before files name in the file list and in the header files. If set
105 # to NO the shortest path that makes the file name unique will be used.
112 # the path. The tag can be used to show relative paths in the file list.
120 # the reader which header file to include in order to use a class.
121 # If left blank only the name of the header file containing the class
128 # (but less readable) file names. This can be useful is your file systems
164 # be part of the file/class/namespace that contains it.
197 # include (a tag file for) the STL sources as input, then you should
231 # Private class members and static file members will be hidden unless
241 # If the EXTRACT_STATIC tag is set to YES all static members of a file
296 # file names in lower-case letters. If set to YES upper-case letters are also
298 # in case and if your file system supports case sensitive file names. Windows
310 # will put a list of the files that are included by a file in the documentation
311 # of that file.
321 # will sort the (detailed) documentation of file and class members
328 # brief documentation of file, namespace and class members alphabetically
396 # doxygen should invoke to get the current version for each file (typically from the
398 # popen()) the command <command> <input-file>, where <command> is the value of
399 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
401 # is used as the file version. See the manual for examples.
442 # doxygen can produce. The string should contain the $file, $line, and $text
443 # tags, which will be replaced by the file and line number from which the
445 # $version, which will be replaced by the version of the file (if it could
448 WARN_FORMAT            = "$file:$line: $text"
450 # The WARN_LOGFILE tag can be used to specify a file to which warning
461 # documented source files. You may enter file names like "myfile.cpp" or
505 # against the file with absolute path, so to exclude all test directories
544 # invoke to filter for each input file. Doxygen will invoke the filter program
545 # by executing (via popen()) the command <filter> <input-file>, where <filter>
546 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
547 # input file. Doxygen will then use the output that the filter program writes
553 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
554 # basis.  Doxygen will compare the file name with each pattern and apply the
618 # will generate a verbatim copy of the header file for each class for
661 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
683 # the style sheet file to the HTML output directory, so don't put your own
696 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
702 # be used to specify the file name of the resulting .chm file. You
703 # can add a path in front of the file if the result should not be
709 # be used to specify the location (absolute path including file name) of
716 # controls if a separate .chi index file is generated (YES) or that
717 # it should be included in the master .chm file (NO).
723 # normal table of contents (NO) in the .chm file.
809 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
857 # will contain hyperlink fields. The RTF file will
865 # Load stylesheet definitions from file. Syntax is similar to doxygen's
866 # config file, i.e. a series of assignments. You only have to provide
872 # Syntax is similar to doxygen's config file.
897 # then it will generate one additional man file for each entity
909 # generate an XML file that captures the structure of
944 # generate an AutoGen Definitions (see autogen.sf.net) file
956 # generate a Perl module file that captures the structure of
977 # The names of the make variables in the generated doxyrules.make file
1056 # can be added for each tagfile. The format of a tag file without
1064 # Note that each tag file must have a unique name
1066 # If a tag file is not located in the directory in which doxygen
1071 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1072 # a tag file that is based on the input files it reads.
1159 # file showing the direct and indirect include dependencies of the file with
1166 # documented header file showing the documented files that directly or
1167 # indirectly include this file.