Lines Matching +full:docs +full:- +full:llvm +full:- +full:man
16 #---------------------------------------------------------------------------
18 #---------------------------------------------------------------------------
21 # that follow. The default is UTF-8 which is also the encoding used for all text
25 # The default value is: UTF-8.
27 DOXYFILE_ENCODING = UTF-8
30 # double-quotes, unless you are using Doxywizard) that should identify the
35 PROJECT_NAME = "LLVM OpenMP"
63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
77 # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
79 # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
80 # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
82 # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
104 # This tag implements a quasi-intelligent brief description abbreviator that is
108 # text. Otherwise, the brief description is used as-is. If left blank, the
137 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
138 # Stripping is only done if one of the specified strings matches the left-hand
149 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
154 # using the -I flag.
160 # support long names like on DOS, Mac, or CD-ROM.
166 # first line (until the first dot) of a Javadoc-style comment as the brief
167 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
175 # line (until the first dot) of a Qt-style comment as the brief description. If
176 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
183 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
185 # to treat a multi-line C++ comment block as a detailed description. Set this
195 # documentation from any documented member that it re-implements.
219 # documentation, which will result in a user-defined paragraph with heading
225 # This tag can be used to specify a number of word-keyword mappings (TCL only).
261 # extension. Doxygen has a built-in mapping, but you can override or extend it
264 # C#, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL. For instance to make
275 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
346 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
360 # Man pages) or section (for LaTeX and RTF).
379 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
389 #---------------------------------------------------------------------------
391 #---------------------------------------------------------------------------
429 # This flag is only useful for Objective-C code. When set to YES local methods,
484 # names in lower-case letters. If set to YES upper-case letters are also
559 # fully-qualified names, including namespaces. If set to NO, the class list will
646 # popen()) the command command input-file, where command is the value of the
647 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
656 # that represents doxygen's defaults, run doxygen with the -l option. You can
677 #---------------------------------------------------------------------------
679 #---------------------------------------------------------------------------
736 #---------------------------------------------------------------------------
738 #---------------------------------------------------------------------------
749 @abs_srcdir@/doxygen-mainpage.dox
752 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
756 # The default value is: UTF-8.
758 INPUT_ENCODING = UTF-8
762 # *.h) to filter out the source-files in the directories. If left blank the
821 # *.h) to filter out the source-files in the directories. If left blank all
843 # <filter> <input-file>
845 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
887 #---------------------------------------------------------------------------
889 #---------------------------------------------------------------------------
892 # generated. Documented entities will be cross-referenced with these sources.
944 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
950 # - Install the latest version of global
951 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
952 # - Make sure the INPUT points to the root of the source tree
953 # - Run doxygen as normal
973 #---------------------------------------------------------------------------
975 #---------------------------------------------------------------------------
999 #---------------------------------------------------------------------------
1001 #---------------------------------------------------------------------------
1008 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1023 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1031 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1043 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1053 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1054 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1065 # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
1081 # files will be copied as-is; there are no commands or markers available.
1162 # The default value is: Doxygen generated docs.
1165 DOCSET_FEEDNAME = "Doxygen generated docs"
1168 # set bundle. This should be a reverse domain-name style string, e.g.
1176 # the documentation publisher. This should be a reverse domain-name style
1192 # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1215 # including file name) of the HTML help compiler ( hhc.exe). If non-empty
1267 # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1275 # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1284 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1292 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1300 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1306 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1343 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1345 # value is set to YES, a side panel will be generated containing a tree-like
1350 # further fine-tune the look of the index. As an example, the default style
1417 # http://docs.mathjax.org/en/latest/output.html) for more details.
1418 # Possible values are: HTML-CSS (which is slower, but has the best
1420 # The default value is: HTML-CSS.
1423 MATHJAX_FORMAT = HTML-CSS
1447 # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
1539 #---------------------------------------------------------------------------
1541 #---------------------------------------------------------------------------
1548 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1606 # Note: Only use a user-defined header if you know what you are doing! The
1620 # Note: Only use a user-defined footer if you know what you are doing!
1627 # directory. Note that the files will be copied as-is; there are no commands or
1684 #---------------------------------------------------------------------------
1686 #---------------------------------------------------------------------------
1695 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
1735 # using doxygen -e rtf extensionFile.
1740 #---------------------------------------------------------------------------
1741 # Configuration options related to the man page output
1742 #---------------------------------------------------------------------------
1744 # If the GENERATE_MAN tag is set to YES doxygen will generate man pages for
1750 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
1754 # The default directory is: man.
1757 MAN_OUTPUT = man
1760 # man pages. In case the manual section does not start with a number, the number
1768 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
1769 # will generate one additional man file for each entity documented in the real
1770 # man page(s). These additional files only source the real man page, but without
1771 # them the man command would be unable to find the correct page.
1777 #---------------------------------------------------------------------------
1779 #---------------------------------------------------------------------------
1796 # listings (including syntax highlighting and cross-referencing information) to
1804 #---------------------------------------------------------------------------
1806 #---------------------------------------------------------------------------
1822 #---------------------------------------------------------------------------
1824 #---------------------------------------------------------------------------
1834 #---------------------------------------------------------------------------
1836 #---------------------------------------------------------------------------
1872 #---------------------------------------------------------------------------
1874 #---------------------------------------------------------------------------
1877 # C-preprocessor directives found in the sources and include files.
1914 # patterns (like *.h and *.hpp) to filter out the header-files in the
1922 # defined before the preprocessor is started (similar to the -D option of e.g.
1941 # remove all references to function-like macros that are alone on a line, have an
1943 # typically used for boiler-plate code, and will confuse the parser if not
1950 #---------------------------------------------------------------------------
1952 #---------------------------------------------------------------------------
2001 #---------------------------------------------------------------------------
2003 #---------------------------------------------------------------------------
2265 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2273 # files in one run (i.e. multiple -o and -T options on the command line). This