Lines Matching refs:files

45 # format and will distribute the generated files over these directories.
47 # source files, where putting all generated files in the same directory would
105 # path before files name in the file list and in the header files. If set
210 # Doxygen selects the parser to use depending on the extension of the files it parses.
216 # .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran),
278 # For small to medium size projects (<1000 input files) the default value is
313 # defined locally in source files will be included in the documentation.
314 # If set to NO only classes defined in header files are included.
334 # undocumented members of documented classes, files or namespaces.
371 # allowed. This is useful if you have classes or files whose names only differ
384 # will put a list of the files that are included by a file in the documentation
463 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
465 # list will mention the files that were used to generate the documentation.
499 # doxygen. The layout file controls the global structure of the generated output files
559 # configuration options related to the input files
562 # The INPUT tag can be used to specify the files and/or directories that contain
563 # documented source files. You may enter file names like "myfile.cpp" or
564 # directories like "/usr/src/myproject". Separate the files or directories
569 # This tag can be used to specify the character encoding of the source files
579 # and *.h) to filter out the source-files in the directories. If left
587 # should be searched for input files as well. Possible values are YES and NO.
592 # The EXCLUDE tag can be used to specify files and/or directories that should
593 # excluded from the INPUT source files. This way you can easily exclude a
598 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
606 # certain files from those directories. Note that the wildcards are matched
620 # The EXAMPLE_PATH tag can be used to specify one or more files or
628 # and *.h) to filter out the source-files in the directories. If left
629 # blank all files are included.
634 # searched for input files to be used with the \include or \dontinclude
640 # The IMAGE_PATH tag can be used to specify one or more files or
664 # is applied to all files.
669 # INPUT_FILTER) will be used to filter the input files when producing source
670 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
678 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
770 # doxygen will generate files with .html extension.
796 # files or namespaces will be aligned in HTML using tables. If set to
809 # If the GENERATE_DOCSET tag is set to YES, additional index files
835 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
1034 # command to the generated LaTeX files. This will instruct LaTeX to keep
1110 # documented in the real man page(s). These additional files
1134 # syntax of the XML files.
1140 # syntax of the XML files.
1193 # This is useful so different doxyrules.make files included by the same
1204 # files.
1221 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1227 # contain include files that are not input files but should be processed by
1233 # patterns (like *.h and *.hpp) to filter out the header-files in the
1274 # Adding location for the tag files is done as follows:
1288 # a tag file that is based on the input files it reads.
1345 # directory and reference it in all dot files that doxygen generates. This
1400 # other documented files.
1406 # documented header file showing the documented files that directly or
1435 # relations between the files in the directories.
1451 # contain dot files that are included in the documentation (see the
1485 # files in one run (i.e. multiple -o and -T options on the command line). This
1498 # remove the intermediate dot files that are used to generate