Lines Matching refs:files

65 # format and will distribute the generated files over these directories. 
67 # source files, where putting all generated files in the same directory would
125 # path before files name in the file list and in the header files. If set
230 # Doxygen selects the parser to use depending on the extension of the files it parses.
236 # .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran),
298 # For small to medium size projects (<1000 input files) the default value is
333 # defined locally in source files will be included in the documentation.
334 # If set to NO only classes defined in header files are included.
354 # undocumented members of documented classes, files or namespaces.
391 # allowed. This is useful if you have classes or files whose names only differ
404 # will put a list of the files that are included by a file in the documentation
483 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
485 # list will mention the files that were used to generate the documentation.
519 # doxygen. The layout file controls the global structure of the generated output files
579 # configuration options related to the input files
582 # The INPUT tag can be used to specify the files and/or directories that contain
583 # documented source files. You may enter file names like "myfile.cpp" or
584 # directories like "/usr/src/myproject". Separate the files or directories
589 # This tag can be used to specify the character encoding of the source files
599 # and *.h) to filter out the source-files in the directories. If left
607 # should be searched for input files as well. Possible values are YES and NO.
612 # The EXCLUDE tag can be used to specify files and/or directories that should
613 # excluded from the INPUT source files. This way you can easily exclude a
618 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
626 # certain files from those directories. Note that the wildcards are matched
640 # The EXAMPLE_PATH tag can be used to specify one or more files or
648 # and *.h) to filter out the source-files in the directories. If left
649 # blank all files are included.
654 # searched for input files to be used with the \include or \dontinclude
660 # The IMAGE_PATH tag can be used to specify one or more files or
684 # is applied to all files.
689 # INPUT_FILTER) will be used to filter the input files when producing source
690 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
698 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
790 # doxygen will generate files with .html extension.
816 # files or namespaces will be aligned in HTML using tables. If set to
829 # If the GENERATE_DOCSET tag is set to YES, additional index files
855 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
1054 # command to the generated LaTeX files. This will instruct LaTeX to keep
1130 # documented in the real man page(s). These additional files
1154 # syntax of the XML files.
1160 # syntax of the XML files.
1213 # This is useful so different doxyrules.make files included by the same
1224 # files.
1241 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1247 # contain include files that are not input files but should be processed by
1253 # patterns (like *.h and *.hpp) to filter out the header-files in the
1294 # Adding location for the tag files is done as follows:
1308 # a tag file that is based on the input files it reads.
1365 # directory and reference it in all dot files that doxygen generates. This
1420 # other documented files.
1426 # documented header file showing the documented files that directly or
1455 # relations between the files in the directories.
1471 # contain dot files that are included in the documentation (see the
1505 # files in one run (i.e. multiple -o and -T options on the command line). This
1518 # remove the intermediate dot files that are used to generate