Lines Matching +full:docs +full:- +full:flang +full:- +full:html
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 = "FLANG"
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.
162 # support long names like on DOS, Mac, or CD-ROM.
168 # first line (until the first dot) of a Javadoc-style comment as the brief
169 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
177 # line (until the first dot) of a Qt-style comment as the brief description. If
178 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
185 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
187 # to treat a multi-line C++ comment block as a detailed description. Set this
197 # documentation from any documented member that it re-implements.
221 # documentation, which will result in a user-defined paragraph with heading
227 # This tag can be used to specify a number of word-keyword mappings (TCL only).
263 # extension. Doxygen has a built-in mapping, but you can override or extend it
266 # C#, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL. For instance to make
277 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
281 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
348 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
361 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
381 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
391 #---------------------------------------------------------------------------
393 #---------------------------------------------------------------------------
431 # This flag is only useful for Objective-C code. When set to YES local methods,
486 # names in lower-case letters. If set to YES upper-case letters are also
561 # fully-qualified names, including namespaces. If set to NO, the class list will
648 # popen()) the command command input-file, where command is the value of the
649 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
658 # that represents doxygen's defaults, run doxygen with the -l option. You can
679 #---------------------------------------------------------------------------
681 #---------------------------------------------------------------------------
738 #---------------------------------------------------------------------------
740 #---------------------------------------------------------------------------
751 @abs_top_srcdir@/doxygen-mainpage.dox
754 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
758 # The default value is: UTF-8.
760 INPUT_ENCODING = UTF-8
764 # *.h) to filter out the source-files in the directories. If left blank the
823 # *.h) to filter out the source-files in the directories. If left blank all
845 # <filter> <input-file>
847 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
884 # (index.html). This can be useful if you have a project on for instance GitHub
889 #---------------------------------------------------------------------------
891 #---------------------------------------------------------------------------
894 # generated. Documented entities will be cross-referenced with these sources.
938 # will make the HTML file larger and loading of large files a bit slower, you
946 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
948 # (see http://www.gnu.org/software/global/global.html). You will need version
952 # - Install the latest version of global
953 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
954 # - Make sure the INPUT points to the root of the source tree
955 # - Run doxygen as normal
975 #---------------------------------------------------------------------------
977 #---------------------------------------------------------------------------
1001 #---------------------------------------------------------------------------
1002 # Configuration options related to the HTML output
1003 #---------------------------------------------------------------------------
1005 # If the GENERATE_HTML tag is set to YES doxygen will generate HTML output
1010 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1013 # The default directory is: html.
1016 HTML_OUTPUT = html
1019 # generated HTML page (for example: .htm, .php, .asp).
1020 # The default value is: .html.
1023 HTML_FILE_EXTENSION = .html
1025 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1026 # each generated HTML page. If the tag is left blank doxygen will generate a
1029 # To get valid HTML the header file that includes any scripts and style sheets
1033 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1035 # and then modify the file new_header.html. See also section "Doxygen usage"
1045 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1046 # generated HTML page. If the tag is left blank doxygen will generate a standard
1055 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1056 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1057 # the HTML output. If left blank doxygen will generate a default style sheet.
1067 # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
1079 # other source files which should be copied to the HTML output directory. Note
1080 # that these files will be copied to the base HTML output directory. Use the
1083 # files will be copied as-is; there are no commands or markers available.
1088 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1100 # in the HTML output. For a value of 0 the output will use grayscales only. A
1108 # luminance component of the colors in the HTML output. Values below 100
1118 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
1126 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1151 # Makefile in the HTML output directory. Running make will produce the docset in
1154 # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
1164 # The default value is: Doxygen generated docs.
1167 DOCSET_FEEDNAME = "Doxygen generated docs"
1170 # set bundle. This should be a reverse domain-name style string, e.g.
1178 # the documentation publisher. This should be a reverse domain-name style
1192 # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1193 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1194 # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1197 # The HTML Help Workshop contains a compiler that can convert all HTML output
1198 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1201 # HTML files also contain an index, a table of contents, and you can search for
1202 # words in the documentation. The HTML workshop also contains a viewer for
1203 # compressed HTML files.
1211 # written to the html output directory.
1217 # including file name) of the HTML help compiler ( hhc.exe). If non-empty
1218 # doxygen will try to run the HTML help compiler on the generated index.hhp.
1245 # the table of contents of the HTML help documentation and to the tree view.
1254 # (.qch) of the generated HTML documentation.
1262 # the HTML output folder.
1269 # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1277 # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1286 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1294 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1302 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1308 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1315 # generated, together with the HTML files, they form an Eclipse help plugin. To
1317 # Eclipse, the contents of the directory containing the HTML and XML files needs
1327 # the directory name containing the HTML and XML files should also have this
1334 # If you want full control over the layout of the generated HTML pages it might
1337 # of each HTML page. A value of NO enables the index and the value YES disables
1345 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1347 # value is set to YES, a side panel will be generated containing a tree-like
1348 # index structure (just like the one that is generated for HTML Help). For this
1351 # HTML help feature. Via custom stylesheets (see HTML_EXTRA_STYLESHEET) one can
1352 # further fine-tune the look of the index. As an example, the default style
1363 # doxygen will group on one line in the generated HTML documentation.
1387 # the HTML documentation. When you change the font size after a successful
1388 # doxygen run you need to manually remove any form_*.png images from the HTML
1400 # the HTML output directory before the changes have effect.
1409 # installed or if you want to formulas look prettier in the HTML output. When
1419 # http://docs.mathjax.org/en/latest/output.html) for more details.
1420 # Possible values are: HTML-CSS (which is slower, but has the best
1422 # The default value is: HTML-CSS.
1425 MATHJAX_FORMAT = HTML-CSS
1427 # When MathJax is enabled you need to specify the location relative to the HTML
1430 # is located at the same level as the HTML output directory, then
1449 # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
1456 # the HTML output. The underlying search engine uses javascript and DHTML and
1457 # should work on any modern browser. Note that when using HTML help
1529 EXTERNAL_SEARCH_ID = flang
1541 #---------------------------------------------------------------------------
1543 #---------------------------------------------------------------------------
1550 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1562 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1608 # Note: Only use a user-defined header if you know what you are doing! The
1622 # Note: Only use a user-defined footer if you know what you are doing!
1629 # directory. Note that the files will be copied as-is; there are no commands or
1637 # contain links (just like the HTML output) instead of page references. This
1655 # when generating formulas in HTML.
1686 #---------------------------------------------------------------------------
1688 #---------------------------------------------------------------------------
1697 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
1714 # contain hyperlink fields. The RTF file will contain links (just like the HTML
1737 # using doxygen -e rtf extensionFile.
1742 #---------------------------------------------------------------------------
1744 #---------------------------------------------------------------------------
1779 #---------------------------------------------------------------------------
1781 #---------------------------------------------------------------------------
1810 # listings (including syntax highlighting and cross-referencing information) to
1818 #---------------------------------------------------------------------------
1820 #---------------------------------------------------------------------------
1836 #---------------------------------------------------------------------------
1838 #---------------------------------------------------------------------------
1848 #---------------------------------------------------------------------------
1850 #---------------------------------------------------------------------------
1886 #---------------------------------------------------------------------------
1888 #---------------------------------------------------------------------------
1891 # C-preprocessor directives found in the sources and include files.
1928 # patterns (like *.h and *.hpp) to filter out the header-files in the
1936 # defined before the preprocessor is started (similar to the -D option of e.g.
1955 # remove all refrences to function-like macros that are alone on a line, have an
1957 # typically used for boiler-plate code, and will confuse the parser if not
1964 #---------------------------------------------------------------------------
1966 #---------------------------------------------------------------------------
2015 #---------------------------------------------------------------------------
2017 #---------------------------------------------------------------------------
2020 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2279 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2287 # files in one run (i.e. multiple -o and -T options on the command line). This