|
|
@ -1,4 +1,4 @@ |
|
|
|
# Doxyfile 1.8.5 |
|
|
|
# Doxyfile 1.8.8 |
|
|
|
|
|
|
|
|
|
|
|
# This file describes the settings to be used by the documentation system |
|
|
|
# This file describes the settings to be used by the documentation system |
|
|
|
# doxygen (www.doxygen.org) for a project. |
|
|
|
# doxygen (www.doxygen.org) for a project. |
|
|
@ -32,13 +32,13 @@ DOXYFILE_ENCODING = UTF-8 |
|
|
|
# title of most generated pages and in a few other places. |
|
|
|
# title of most generated pages and in a few other places. |
|
|
|
# The default value is: My Project. |
|
|
|
# The default value is: My Project. |
|
|
|
|
|
|
|
|
|
|
|
PROJECT_NAME = GLM |
|
|
|
PROJECT_NAME = 0.9.6 |
|
|
|
|
|
|
|
|
|
|
|
# The PROJECT_NUMBER tag can be used to enter a project or revision number. This |
|
|
|
# The PROJECT_NUMBER tag can be used to enter a project or revision number. This |
|
|
|
# could be handy for archiving the generated documentation or if some version |
|
|
|
# could be handy for archiving the generated documentation or if some version |
|
|
|
# control system is used. |
|
|
|
# control system is used. |
|
|
|
|
|
|
|
|
|
|
|
PROJECT_NUMBER = 0.9.5 |
|
|
|
PROJECT_NUMBER = |
|
|
|
|
|
|
|
|
|
|
|
# Using the PROJECT_BRIEF tag one can provide an optional one line description |
|
|
|
# Using the PROJECT_BRIEF tag one can provide an optional one line description |
|
|
|
# for a project that appears at the top of each page and should give viewer a |
|
|
|
# for a project that appears at the top of each page and should give viewer a |
|
|
@ -51,7 +51,7 @@ PROJECT_BRIEF = |
|
|
|
# and the maximum width should not exceed 200 pixels. Doxygen will copy the logo |
|
|
|
# and the maximum width should not exceed 200 pixels. Doxygen will copy the logo |
|
|
|
# to the output directory. |
|
|
|
# to the output directory. |
|
|
|
|
|
|
|
|
|
|
|
PROJECT_LOGO = G:/Repository/glm/doc/logo.png |
|
|
|
PROJECT_LOGO = E:/Source/G-Truc/glm/doc/logo.png |
|
|
|
|
|
|
|
|
|
|
|
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path |
|
|
|
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path |
|
|
|
# into which the generated documentation will be written. If a relative path is |
|
|
|
# into which the generated documentation will be written. If a relative path is |
|
|
@ -70,15 +70,25 @@ OUTPUT_DIRECTORY = . |
|
|
|
|
|
|
|
|
|
|
|
CREATE_SUBDIRS = NO |
|
|
|
CREATE_SUBDIRS = NO |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII |
|
|
|
|
|
|
|
# characters to appear in the names of generated files. If set to NO, non-ASCII |
|
|
|
|
|
|
|
# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode |
|
|
|
|
|
|
|
# U+3044. |
|
|
|
|
|
|
|
# The default value is: NO. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ALLOW_UNICODE_NAMES = NO |
|
|
|
|
|
|
|
|
|
|
|
# The OUTPUT_LANGUAGE tag is used to specify the language in which all |
|
|
|
# The OUTPUT_LANGUAGE tag is used to specify the language in which all |
|
|
|
# documentation generated by doxygen is written. Doxygen will use this |
|
|
|
# documentation generated by doxygen is written. Doxygen will use this |
|
|
|
# information to generate all constant output in the proper language. |
|
|
|
# information to generate all constant output in the proper language. |
|
|
|
# Possible values are: Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese- |
|
|
|
# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese, |
|
|
|
# Traditional, Croatian, Czech, Danish, Dutch, English, Esperanto, Farsi, |
|
|
|
# Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States), |
|
|
|
# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en, |
|
|
|
# Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian, |
|
|
|
# Korean, Korean-en, Latvian, Norwegian, Macedonian, Persian, Polish, |
|
|
|
# Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages), |
|
|
|
# Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, |
|
|
|
# Korean, Korean-en (Korean with English messages), Latvian, Lithuanian, |
|
|
|
# Turkish, Ukrainian and Vietnamese. |
|
|
|
# Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian, |
|
|
|
|
|
|
|
# Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish, |
|
|
|
|
|
|
|
# Ukrainian and Vietnamese. |
|
|
|
# The default value is: English. |
|
|
|
# The default value is: English. |
|
|
|
|
|
|
|
|
|
|
|
OUTPUT_LANGUAGE = English |
|
|
|
OUTPUT_LANGUAGE = English |
|
|
@ -269,9 +279,12 @@ OPTIMIZE_OUTPUT_VHDL = NO |
|
|
|
# extension. Doxygen has a built-in mapping, but you can override or extend it |
|
|
|
# extension. Doxygen has a built-in mapping, but you can override or extend it |
|
|
|
# using this tag. The format is ext=language, where ext is a file extension, and |
|
|
|
# using this tag. The format is ext=language, where ext is a file extension, and |
|
|
|
# language is one of the parsers supported by doxygen: IDL, Java, Javascript, |
|
|
|
# language is one of the parsers supported by doxygen: IDL, Java, Javascript, |
|
|
|
# C#, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL. For instance to make |
|
|
|
# C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran: |
|
|
|
# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C |
|
|
|
# FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran: |
|
|
|
# (default is Fortran), use: inc=Fortran f=C. |
|
|
|
# Fortran. In the later case the parser tries to guess whether the code is fixed |
|
|
|
|
|
|
|
# or free formatted code, this is the default for Fortran type files), VHDL. For |
|
|
|
|
|
|
|
# instance to make doxygen treat .inc files as Fortran files (default is PHP), |
|
|
|
|
|
|
|
# and .f files as C (default is Fortran), use: inc=Fortran f=C. |
|
|
|
# |
|
|
|
# |
|
|
|
# Note For files without extension you can use no_extension as a placeholder. |
|
|
|
# Note For files without extension you can use no_extension as a placeholder. |
|
|
|
# |
|
|
|
# |
|
|
@ -510,6 +523,13 @@ HIDE_SCOPE_NAMES = YES |
|
|
|
|
|
|
|
|
|
|
|
SHOW_INCLUDE_FILES = NO |
|
|
|
SHOW_INCLUDE_FILES = NO |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each |
|
|
|
|
|
|
|
# grouped member an include statement to the documentation, telling the reader |
|
|
|
|
|
|
|
# which file to include in order to use the member. |
|
|
|
|
|
|
|
# The default value is: NO. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SHOW_GROUPED_MEMB_INC = NO |
|
|
|
|
|
|
|
|
|
|
|
# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include |
|
|
|
# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include |
|
|
|
# files with double quotes in the documentation rather than with sharp brackets. |
|
|
|
# files with double quotes in the documentation rather than with sharp brackets. |
|
|
|
# The default value is: NO. |
|
|
|
# The default value is: NO. |
|
|
@ -531,7 +551,8 @@ SORT_MEMBER_DOCS = YES |
|
|
|
|
|
|
|
|
|
|
|
# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief |
|
|
|
# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief |
|
|
|
# descriptions of file, namespace and class members alphabetically by member |
|
|
|
# descriptions of file, namespace and class members alphabetically by member |
|
|
|
# name. If set to NO the members will appear in declaration order. |
|
|
|
# name. If set to NO the members will appear in declaration order. Note that |
|
|
|
|
|
|
|
# this will also influence the order of the classes in the class list. |
|
|
|
# The default value is: NO. |
|
|
|
# The default value is: NO. |
|
|
|
|
|
|
|
|
|
|
|
SORT_BRIEF_DOCS = YES |
|
|
|
SORT_BRIEF_DOCS = YES |
|
|
@ -669,8 +690,7 @@ LAYOUT_FILE = |
|
|
|
# to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info. |
|
|
|
# to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info. |
|
|
|
# For LaTeX the style of the bibliography can be controlled using |
|
|
|
# For LaTeX the style of the bibliography can be controlled using |
|
|
|
# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the |
|
|
|
# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the |
|
|
|
# search path. Do not use file names with spaces, bibtex cannot handle them. See |
|
|
|
# search path. See also \cite for info how to create references. |
|
|
|
# also \cite for info how to create references. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CITE_BIB_FILES = |
|
|
|
CITE_BIB_FILES = |
|
|
|
|
|
|
|
|
|
|
@ -970,7 +990,7 @@ USE_HTAGS = NO |
|
|
|
VERBATIM_HEADERS = YES |
|
|
|
VERBATIM_HEADERS = YES |
|
|
|
|
|
|
|
|
|
|
|
# If the CLANG_ASSISTED_PARSING tag is set to YES, then doxygen will use the |
|
|
|
# If the CLANG_ASSISTED_PARSING tag is set to YES, then doxygen will use the |
|
|
|
# clang parser (see: http://clang.llvm.org/) for more acurate parsing at the |
|
|
|
# clang parser (see: http://clang.llvm.org/) for more accurate parsing at the |
|
|
|
# cost of reduced performance. This can be particularly helpful with template |
|
|
|
# cost of reduced performance. This can be particularly helpful with template |
|
|
|
# rich C++ code for which doxygen's built-in parser lacks the necessary type |
|
|
|
# rich C++ code for which doxygen's built-in parser lacks the necessary type |
|
|
|
# information. |
|
|
|
# information. |
|
|
@ -1080,13 +1100,15 @@ HTML_FOOTER = |
|
|
|
|
|
|
|
|
|
|
|
HTML_STYLESHEET = |
|
|
|
HTML_STYLESHEET = |
|
|
|
|
|
|
|
|
|
|
|
# The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user- |
|
|
|
# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined |
|
|
|
# defined cascading style sheet that is included after the standard style sheets |
|
|
|
# cascading style sheets that are included after the standard style sheets |
|
|
|
# created by doxygen. Using this option one can overrule certain style aspects. |
|
|
|
# created by doxygen. Using this option one can overrule certain style aspects. |
|
|
|
# This is preferred over using HTML_STYLESHEET since it does not replace the |
|
|
|
# This is preferred over using HTML_STYLESHEET since it does not replace the |
|
|
|
# standard style sheet and is therefor more robust against future updates. |
|
|
|
# standard style sheet and is therefor more robust against future updates. |
|
|
|
# Doxygen will copy the style sheet file to the output directory. For an example |
|
|
|
# Doxygen will copy the style sheet files to the output directory. |
|
|
|
# see the documentation. |
|
|
|
# Note: The order of the extra stylesheet files is of importance (e.g. the last |
|
|
|
|
|
|
|
# stylesheet in the list overrules the setting of the previous ones in the |
|
|
|
|
|
|
|
# list). For an example see the documentation. |
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES. |
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES. |
|
|
|
|
|
|
|
|
|
|
|
HTML_EXTRA_STYLESHEET = |
|
|
|
HTML_EXTRA_STYLESHEET = |
|
|
@ -1251,7 +1273,8 @@ GENERATE_CHI = NO |
|
|
|
CHM_INDEX_ENCODING = |
|
|
|
CHM_INDEX_ENCODING = |
|
|
|
|
|
|
|
|
|
|
|
# The BINARY_TOC flag controls whether a binary table of contents is generated ( |
|
|
|
# The BINARY_TOC flag controls whether a binary table of contents is generated ( |
|
|
|
# YES) or a normal table of contents ( NO) in the .chm file. |
|
|
|
# YES) or a normal table of contents ( NO) in the .chm file. Furthermore it |
|
|
|
|
|
|
|
# enables the Previous and Next buttons. |
|
|
|
# The default value is: NO. |
|
|
|
# The default value is: NO. |
|
|
|
# This tag requires that the tag GENERATE_HTMLHELP is set to YES. |
|
|
|
# This tag requires that the tag GENERATE_HTMLHELP is set to YES. |
|
|
|
|
|
|
|
|
|
|
@ -1491,11 +1514,11 @@ SEARCHENGINE = NO |
|
|
|
|
|
|
|
|
|
|
|
# When the SERVER_BASED_SEARCH tag is enabled the search engine will be |
|
|
|
# When the SERVER_BASED_SEARCH tag is enabled the search engine will be |
|
|
|
# implemented using a web server instead of a web client using Javascript. There |
|
|
|
# implemented using a web server instead of a web client using Javascript. There |
|
|
|
# are two flavours of web server based searching depending on the |
|
|
|
# are two flavors of web server based searching depending on the EXTERNAL_SEARCH |
|
|
|
# EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for |
|
|
|
# setting. When disabled, doxygen will generate a PHP script for searching and |
|
|
|
# searching and an index file used by the script. When EXTERNAL_SEARCH is |
|
|
|
# an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing |
|
|
|
# enabled the indexing and searching needs to be provided by external tools. See |
|
|
|
# and searching needs to be provided by external tools. See the section |
|
|
|
# the section "External Indexing and Searching" for details. |
|
|
|
# "External Indexing and Searching" for details. |
|
|
|
# The default value is: NO. |
|
|
|
# The default value is: NO. |
|
|
|
# This tag requires that the tag SEARCHENGINE is set to YES. |
|
|
|
# This tag requires that the tag SEARCHENGINE is set to YES. |
|
|
|
|
|
|
|
|
|
|
@ -1623,17 +1646,19 @@ EXTRA_PACKAGES = |
|
|
|
# |
|
|
|
# |
|
|
|
# Note: Only use a user-defined header if you know what you are doing! The |
|
|
|
# Note: Only use a user-defined header if you know what you are doing! The |
|
|
|
# following commands have a special meaning inside the header: $title, |
|
|
|
# following commands have a special meaning inside the header: $title, |
|
|
|
# $datetime, $date, $doxygenversion, $projectname, $projectnumber. Doxygen will |
|
|
|
# $datetime, $date, $doxygenversion, $projectname, $projectnumber, |
|
|
|
# replace them by respectively the title of the page, the current date and time, |
|
|
|
# $projectbrief, $projectlogo. Doxygen will replace $title with the empy string, |
|
|
|
# only the current date, the version number of doxygen, the project name (see |
|
|
|
# for the replacement values of the other commands the user is refered to |
|
|
|
# PROJECT_NAME), or the project number (see PROJECT_NUMBER). |
|
|
|
# HTML_HEADER. |
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES. |
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES. |
|
|
|
|
|
|
|
|
|
|
|
LATEX_HEADER = |
|
|
|
LATEX_HEADER = |
|
|
|
|
|
|
|
|
|
|
|
# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the |
|
|
|
# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the |
|
|
|
# generated LaTeX document. The footer should contain everything after the last |
|
|
|
# generated LaTeX document. The footer should contain everything after the last |
|
|
|
# chapter. If it is left blank doxygen will generate a standard footer. |
|
|
|
# chapter. If it is left blank doxygen will generate a standard footer. See |
|
|
|
|
|
|
|
# LATEX_HEADER for more information on how to generate a default footer and what |
|
|
|
|
|
|
|
# special commands can be used inside the footer. |
|
|
|
# |
|
|
|
# |
|
|
|
# Note: Only use a user-defined footer if you know what you are doing! |
|
|
|
# Note: Only use a user-defined footer if you know what you are doing! |
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES. |
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES. |
|
|
@ -1657,7 +1682,7 @@ LATEX_EXTRA_FILES = |
|
|
|
|
|
|
|
|
|
|
|
PDF_HYPERLINKS = NO |
|
|
|
PDF_HYPERLINKS = NO |
|
|
|
|
|
|
|
|
|
|
|
# If the LATEX_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate |
|
|
|
# If the USE_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate |
|
|
|
# the PDF file directly from the LaTeX files. Set this option to YES to get a |
|
|
|
# the PDF file directly from the LaTeX files. Set this option to YES to get a |
|
|
|
# higher quality PDF documentation. |
|
|
|
# higher quality PDF documentation. |
|
|
|
# The default value is: YES. |
|
|
|
# The default value is: YES. |
|
|
@ -1783,6 +1808,13 @@ MAN_OUTPUT = man |
|
|
|
|
|
|
|
|
|
|
|
MAN_EXTENSION = .3 |
|
|
|
MAN_EXTENSION = .3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# The MAN_SUBDIR tag determines the name of the directory created within |
|
|
|
|
|
|
|
# MAN_OUTPUT in which the man pages are placed. If defaults to man followed by |
|
|
|
|
|
|
|
# MAN_EXTENSION with the initial . removed. |
|
|
|
|
|
|
|
# This tag requires that the tag GENERATE_MAN is set to YES. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
MAN_SUBDIR = |
|
|
|
|
|
|
|
|
|
|
|
# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it |
|
|
|
# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it |
|
|
|
# will generate one additional man file for each entity documented in the real |
|
|
|
# will generate one additional man file for each entity documented in the real |
|
|
|
# man page(s). These additional files only source the real man page, but without |
|
|
|
# man page(s). These additional files only source the real man page, but without |
|
|
@ -1810,18 +1842,6 @@ GENERATE_XML = NO |
|
|
|
|
|
|
|
|
|
|
|
XML_OUTPUT = xml |
|
|
|
XML_OUTPUT = xml |
|
|
|
|
|
|
|
|
|
|
|
# The XML_SCHEMA tag can be used to specify a XML schema, which can be used by a |
|
|
|
|
|
|
|
# validating XML parser to check the syntax of the XML files. |
|
|
|
|
|
|
|
# This tag requires that the tag GENERATE_XML is set to YES. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
XML_SCHEMA = |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# The XML_DTD tag can be used to specify a XML DTD, which can be used by a |
|
|
|
|
|
|
|
# validating XML parser to check the syntax of the XML files. |
|
|
|
|
|
|
|
# This tag requires that the tag GENERATE_XML is set to YES. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
XML_DTD = |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program |
|
|
|
# If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program |
|
|
|
# listings (including syntax highlighting and cross-referencing information) to |
|
|
|
# listings (including syntax highlighting and cross-referencing information) to |
|
|
|
# the XML output. Note that enabling this will significantly increase the size |
|
|
|
# the XML output. Note that enabling this will significantly increase the size |
|
|
@ -1849,6 +1869,15 @@ GENERATE_DOCBOOK = NO |
|
|
|
|
|
|
|
|
|
|
|
DOCBOOK_OUTPUT = docbook |
|
|
|
DOCBOOK_OUTPUT = docbook |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# If the DOCBOOK_PROGRAMLISTING tag is set to YES doxygen will include the |
|
|
|
|
|
|
|
# program listings (including syntax highlighting and cross-referencing |
|
|
|
|
|
|
|
# information) to the DOCBOOK output. Note that enabling this will significantly |
|
|
|
|
|
|
|
# increase the size of the DOCBOOK output. |
|
|
|
|
|
|
|
# The default value is: NO. |
|
|
|
|
|
|
|
# This tag requires that the tag GENERATE_DOCBOOK is set to YES. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DOCBOOK_PROGRAMLISTING = NO |
|
|
|
|
|
|
|
|
|
|
|
#--------------------------------------------------------------------------- |
|
|
|
#--------------------------------------------------------------------------- |
|
|
|
# Configuration options for the AutoGen Definitions output |
|
|
|
# Configuration options for the AutoGen Definitions output |
|
|
|
#--------------------------------------------------------------------------- |
|
|
|
#--------------------------------------------------------------------------- |
|
|
@ -1968,9 +1997,9 @@ PREDEFINED = |
|
|
|
EXPAND_AS_DEFINED = |
|
|
|
EXPAND_AS_DEFINED = |
|
|
|
|
|
|
|
|
|
|
|
# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will |
|
|
|
# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will |
|
|
|
# remove all refrences to function-like macros that are alone on a line, have an |
|
|
|
# remove all references to function-like macros that are alone on a line, have |
|
|
|
# all uppercase name, and do not end with a semicolon. Such function macros are |
|
|
|
# an all uppercase name, and do not end with a semicolon. Such function macros |
|
|
|
# typically used for boiler-plate code, and will confuse the parser if not |
|
|
|
# are typically used for boiler-plate code, and will confuse the parser if not |
|
|
|
# removed. |
|
|
|
# removed. |
|
|
|
# The default value is: YES. |
|
|
|
# The default value is: YES. |
|
|
|
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES. |
|
|
|
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES. |
|
|
@ -1990,7 +2019,7 @@ SKIP_FUNCTION_MACROS = YES |
|
|
|
# where loc1 and loc2 can be relative or absolute paths or URLs. See the |
|
|
|
# where loc1 and loc2 can be relative or absolute paths or URLs. See the |
|
|
|
# section "Linking to external documentation" for more information about the use |
|
|
|
# section "Linking to external documentation" for more information about the use |
|
|
|
# of tag files. |
|
|
|
# of tag files. |
|
|
|
# Note: Each tag file must have an unique name (where the name does NOT include |
|
|
|
# Note: Each tag file must have a unique name (where the name does NOT include |
|
|
|
# the path). If a tag file is not located in the directory in which doxygen is |
|
|
|
# the path). If a tag file is not located in the directory in which doxygen is |
|
|
|
# run, you must also specify the path to the tagfile here. |
|
|
|
# run, you must also specify the path to the tagfile here. |
|
|
|
|
|
|
|
|
|
|
@ -2050,6 +2079,13 @@ CLASS_DIAGRAMS = YES |
|
|
|
|
|
|
|
|
|
|
|
MSCGEN_PATH = |
|
|
|
MSCGEN_PATH = |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# You can include diagrams made with dia in doxygen documentation. Doxygen will |
|
|
|
|
|
|
|
# then run dia to produce the diagram and insert it in the documentation. The |
|
|
|
|
|
|
|
# DIA_PATH tag allows you to specify the directory where the dia binary resides. |
|
|
|
|
|
|
|
# If left empty dia is assumed to be found in the default search path. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DIA_PATH = |
|
|
|
|
|
|
|
|
|
|
|
# If set to YES, the inheritance and collaboration graphs will hide inheritance |
|
|
|
# If set to YES, the inheritance and collaboration graphs will hide inheritance |
|
|
|
# and usage relations if the target is undocumented or is not a class. |
|
|
|
# and usage relations if the target is undocumented or is not a class. |
|
|
|
# The default value is: YES. |
|
|
|
# The default value is: YES. |
|
|
@ -2075,7 +2111,7 @@ HAVE_DOT = NO |
|
|
|
|
|
|
|
|
|
|
|
DOT_NUM_THREADS = 0 |
|
|
|
DOT_NUM_THREADS = 0 |
|
|
|
|
|
|
|
|
|
|
|
# When you want a differently looking font n the dot files that doxygen |
|
|
|
# When you want a differently looking font in the dot files that doxygen |
|
|
|
# generates you can specify the font name using DOT_FONTNAME. You need to make |
|
|
|
# generates you can specify the font name using DOT_FONTNAME. You need to make |
|
|
|
# sure dot is able to find the font, which can be done by putting it in a |
|
|
|
# sure dot is able to find the font, which can be done by putting it in a |
|
|
|
# standard location or by setting the DOTFONTPATH environment variable or by |
|
|
|
# standard location or by setting the DOTFONTPATH environment variable or by |
|
|
@ -2250,6 +2286,21 @@ DOTFILE_DIRS = |
|
|
|
|
|
|
|
|
|
|
|
MSCFILE_DIRS = |
|
|
|
MSCFILE_DIRS = |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# The DIAFILE_DIRS tag can be used to specify one or more directories that |
|
|
|
|
|
|
|
# contain dia files that are included in the documentation (see the \diafile |
|
|
|
|
|
|
|
# command). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DIAFILE_DIRS = |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the |
|
|
|
|
|
|
|
# path where java can find the plantuml.jar file. If left blank, it is assumed |
|
|
|
|
|
|
|
# PlantUML is not used or called during a preprocessing step. Doxygen will |
|
|
|
|
|
|
|
# generate a warning when it encounters a \startuml command in this case and |
|
|
|
|
|
|
|
# will not generate output for the diagram. |
|
|
|
|
|
|
|
# This tag requires that the tag HAVE_DOT is set to YES. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PLANTUML_JAR_PATH = |
|
|
|
|
|
|
|
|
|
|
|
# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes |
|
|
|
# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes |
|
|
|
# that will be shown in the graph. If the number of nodes in a graph becomes |
|
|
|
# that will be shown in the graph. If the number of nodes in a graph becomes |
|
|
|
# larger than this value, doxygen will truncate the graph, which is visualized |
|
|
|
# larger than this value, doxygen will truncate the graph, which is visualized |
|
|
|