|
|
|
@ -1,4 +1,4 @@
|
|
|
|
|
# Doxyfile 1.8.14
|
|
|
|
|
# Doxyfile 1.8.15
|
|
|
|
|
|
|
|
|
|
# This file describes the settings to be used by the documentation system
|
|
|
|
|
# doxygen (www.doxygen.org) for a project.
|
|
|
|
@ -17,10 +17,10 @@
|
|
|
|
|
# Project related configuration options
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
# This tag specifies the encoding used for all characters in the config file
|
|
|
|
|
# that follow. The default is UTF-8 which is also the encoding used for all text
|
|
|
|
|
# before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
|
|
|
|
|
# built into libc) for the transcoding. See
|
|
|
|
|
# This tag specifies the encoding used for all characters in the configuration
|
|
|
|
|
# file that follow. The default is UTF-8 which is also the encoding used for all
|
|
|
|
|
# text before the first occurrence of this tag. Doxygen uses libiconv (or the
|
|
|
|
|
# iconv built into libc) for the transcoding. See
|
|
|
|
|
# https://www.gnu.org/software/libiconv/ for the list of possible encodings.
|
|
|
|
|
# The default value is: UTF-8.
|
|
|
|
|
|
|
|
|
@ -44,7 +44,7 @@ PROJECT_NUMBER = $(PROJECT_NUMBER)
|
|
|
|
|
# for a project that appears at the top of each page and should give viewer a
|
|
|
|
|
# quick idea about the purpose of the project. Keep the description short.
|
|
|
|
|
|
|
|
|
|
PROJECT_BRIEF =
|
|
|
|
|
PROJECT_BRIEF =
|
|
|
|
|
|
|
|
|
|
# With the PROJECT_LOGO tag one can specify a logo or an icon that is included
|
|
|
|
|
# in the documentation. The maximum height of the logo should not exceed 55
|
|
|
|
@ -93,6 +93,14 @@ ALLOW_UNICODE_NAMES = NO
|
|
|
|
|
|
|
|
|
|
OUTPUT_LANGUAGE = English
|
|
|
|
|
|
|
|
|
|
# The OUTPUT_TEXT_DIRECTION tag is used to specify the direction in which all
|
|
|
|
|
# documentation generated by doxygen is written. Doxygen will use this
|
|
|
|
|
# information to generate all generated output in the proper direction.
|
|
|
|
|
# Possible values are: None, LTR, RTL and Context.
|
|
|
|
|
# The default value is: None.
|
|
|
|
|
|
|
|
|
|
OUTPUT_TEXT_DIRECTION = None
|
|
|
|
|
|
|
|
|
|
# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
|
|
|
|
|
# descriptions after the members that are listed in the file and class
|
|
|
|
|
# documentation (similar to Javadoc). Set to NO to disable this.
|
|
|
|
@ -162,7 +170,7 @@ FULL_PATH_NAMES = NO
|
|
|
|
|
# will be relative from the directory where doxygen is started.
|
|
|
|
|
# This tag requires that the tag FULL_PATH_NAMES is set to YES.
|
|
|
|
|
|
|
|
|
|
STRIP_FROM_PATH =
|
|
|
|
|
STRIP_FROM_PATH =
|
|
|
|
|
|
|
|
|
|
# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
|
|
|
|
|
# path mentioned in the documentation of a class, which tells the reader which
|
|
|
|
@ -171,7 +179,7 @@ STRIP_FROM_PATH =
|
|
|
|
|
# specify the list of include paths that are normally passed to the compiler
|
|
|
|
|
# using the -I flag.
|
|
|
|
|
|
|
|
|
|
STRIP_FROM_INC_PATH =
|
|
|
|
|
STRIP_FROM_INC_PATH =
|
|
|
|
|
|
|
|
|
|
# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
|
|
|
|
|
# less readable) file names. This can be useful is your file systems doesn't
|
|
|
|
@ -238,14 +246,18 @@ TAB_SIZE = 4
|
|
|
|
|
# "Side Effects:". You can put \n's in the value part of an alias to insert
|
|
|
|
|
# newlines (in the resulting output). You can put ^^ in the value part of an
|
|
|
|
|
# alias to insert a newline as if a physical newline was in the original file.
|
|
|
|
|
# When you need a literal { or } or , in the value part of an alias you have to
|
|
|
|
|
# escape them by means of a backslash (\), this can lead to conflicts with the
|
|
|
|
|
# commands \{ and \} for these it is advised to use the version @{ and @} or use
|
|
|
|
|
# a double escape (\\{ and \\})
|
|
|
|
|
|
|
|
|
|
ALIASES =
|
|
|
|
|
ALIASES =
|
|
|
|
|
|
|
|
|
|
# This tag can be used to specify a number of word-keyword mappings (TCL only).
|
|
|
|
|
# A mapping has the form "name=value". For example adding "class=itcl::class"
|
|
|
|
|
# will allow you to use the command class in the itcl::class meaning.
|
|
|
|
|
|
|
|
|
|
TCL_SUBST =
|
|
|
|
|
TCL_SUBST =
|
|
|
|
|
|
|
|
|
|
# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
|
|
|
|
|
# only. Doxygen will then generate output that is more tailored for C. For
|
|
|
|
@ -275,28 +287,37 @@ OPTIMIZE_FOR_FORTRAN = NO
|
|
|
|
|
|
|
|
|
|
OPTIMIZE_OUTPUT_VHDL = NO
|
|
|
|
|
|
|
|
|
|
# Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice
|
|
|
|
|
# sources only. Doxygen will then generate output that is more tailored for that
|
|
|
|
|
# language. For instance, namespaces will be presented as modules, types will be
|
|
|
|
|
# separated into more groups, etc.
|
|
|
|
|
# The default value is: NO.
|
|
|
|
|
|
|
|
|
|
OPTIMIZE_OUTPUT_SLICE = NO
|
|
|
|
|
|
|
|
|
|
# Doxygen selects the parser to use depending on the extension of the files it
|
|
|
|
|
# parses. With this tag you can assign which parser to use for a given
|
|
|
|
|
# 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
|
|
|
|
|
# language is one of the parsers supported by doxygen: IDL, Java, Javascript,
|
|
|
|
|
# C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
|
|
|
|
|
# FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:
|
|
|
|
|
# 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.
|
|
|
|
|
# Csharp (C#), C, C++, D, PHP, md (Markdown), Objective-C, Python, Slice,
|
|
|
|
|
# Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:
|
|
|
|
|
# FortranFree, unknown formatted Fortran: 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, tcl. 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 that for custom extensions you also need to set FILE_PATTERNS otherwise
|
|
|
|
|
# the files are not read by doxygen.
|
|
|
|
|
|
|
|
|
|
EXTENSION_MAPPING =
|
|
|
|
|
EXTENSION_MAPPING =
|
|
|
|
|
|
|
|
|
|
# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
|
|
|
|
|
# according to the Markdown format, which allows for more readable
|
|
|
|
|
# documentation. See http://daringfireball.net/projects/markdown/ for details.
|
|
|
|
|
# documentation. See https://daringfireball.net/projects/markdown/ for details.
|
|
|
|
|
# The output of markdown processing is further processed by doxygen, so you can
|
|
|
|
|
# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
|
|
|
|
|
# case of backward compatibilities issues.
|
|
|
|
@ -649,7 +670,7 @@ GENERATE_DEPRECATEDLIST= YES
|
|
|
|
|
# sections, marked by \if <section_label> ... \endif and \cond <section_label>
|
|
|
|
|
# ... \endcond blocks.
|
|
|
|
|
|
|
|
|
|
ENABLED_SECTIONS =
|
|
|
|
|
ENABLED_SECTIONS =
|
|
|
|
|
|
|
|
|
|
# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
|
|
|
|
|
# initial value of a variable or macro / define can have for it to appear in the
|
|
|
|
@ -691,7 +712,7 @@ SHOW_NAMESPACES = YES
|
|
|
|
|
# by doxygen. Whatever the program writes to standard output is used as the file
|
|
|
|
|
# version. For an example see the documentation.
|
|
|
|
|
|
|
|
|
|
FILE_VERSION_FILTER =
|
|
|
|
|
FILE_VERSION_FILTER =
|
|
|
|
|
|
|
|
|
|
# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
|
|
|
|
|
# by doxygen. The layout file controls the global structure of the generated
|
|
|
|
@ -704,7 +725,7 @@ FILE_VERSION_FILTER =
|
|
|
|
|
# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
|
|
|
|
|
# tag is left empty.
|
|
|
|
|
|
|
|
|
|
LAYOUT_FILE =
|
|
|
|
|
LAYOUT_FILE =
|
|
|
|
|
|
|
|
|
|
# The CITE_BIB_FILES tag can be used to specify one or more bib files containing
|
|
|
|
|
# the reference definitions. This must be a list of .bib files. The .bib
|
|
|
|
@ -714,7 +735,7 @@ LAYOUT_FILE =
|
|
|
|
|
# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
|
|
|
|
|
# search path. See also \cite for info how to create references.
|
|
|
|
|
|
|
|
|
|
CITE_BIB_FILES =
|
|
|
|
|
CITE_BIB_FILES =
|
|
|
|
|
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
|
# Configuration options related to warning and progress messages
|
|
|
|
@ -754,7 +775,8 @@ WARN_IF_DOC_ERROR = YES
|
|
|
|
|
# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
|
|
|
|
|
# are documented, but have no documentation for their parameters or return
|
|
|
|
|
# value. If set to NO, doxygen will only warn about wrong or incomplete
|
|
|
|
|
# parameter documentation, but not about the absence of documentation.
|
|
|
|
|
# parameter documentation, but not about the absence of documentation. If
|
|
|
|
|
# EXTRACT_ALL is set to YES then this flag will automatically be disabled.
|
|
|
|
|
# The default value is: NO.
|
|
|
|
|
|
|
|
|
|
WARN_NO_PARAMDOC = NO
|
|
|
|
@ -779,7 +801,7 @@ WARN_FORMAT = "$file:$line: $text"
|
|
|
|
|
# messages should be written. If left blank the output is written to standard
|
|
|
|
|
# error (stderr).
|
|
|
|
|
|
|
|
|
|
WARN_LOGFILE =
|
|
|
|
|
WARN_LOGFILE =
|
|
|
|
|
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
|
# Configuration options related to the input files
|
|
|
|
@ -814,7 +836,7 @@ INPUT_ENCODING = UTF-8
|
|
|
|
|
# *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h,
|
|
|
|
|
# *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc,
|
|
|
|
|
# *.m, *.markdown, *.md, *.mm, *.dox, *.py, *.pyw, *.f90, *.f95, *.f03, *.f08,
|
|
|
|
|
# *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf and *.qsf.
|
|
|
|
|
# *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf, *.qsf and *.ice.
|
|
|
|
|
|
|
|
|
|
FILE_PATTERNS = *.c \
|
|
|
|
|
*.cc \
|
|
|
|
@ -874,7 +896,7 @@ RECURSIVE = YES
|
|
|
|
|
# Note that relative paths are relative to the directory from which doxygen is
|
|
|
|
|
# run.
|
|
|
|
|
|
|
|
|
|
EXCLUDE =
|
|
|
|
|
EXCLUDE =
|
|
|
|
|
|
|
|
|
|
# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
|
|
|
|
|
# directories that are symbolic links (a Unix file system feature) are excluded
|
|
|
|
@ -890,7 +912,7 @@ EXCLUDE_SYMLINKS = NO
|
|
|
|
|
# Note that the wildcards are matched against the file with absolute path, so to
|
|
|
|
|
# exclude all test directories for example use the pattern */test/*
|
|
|
|
|
|
|
|
|
|
EXCLUDE_PATTERNS =
|
|
|
|
|
EXCLUDE_PATTERNS =
|
|
|
|
|
|
|
|
|
|
# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
|
|
|
|
|
# (namespaces, classes, functions, etc.) that should be excluded from the
|
|
|
|
@ -901,13 +923,13 @@ EXCLUDE_PATTERNS =
|
|
|
|
|
# Note that the wildcards are matched against the file with absolute path, so to
|
|
|
|
|
# exclude all test directories use the pattern */test/*
|
|
|
|
|
|
|
|
|
|
EXCLUDE_SYMBOLS =
|
|
|
|
|
EXCLUDE_SYMBOLS =
|
|
|
|
|
|
|
|
|
|
# The EXAMPLE_PATH tag can be used to specify one or more files or directories
|
|
|
|
|
# that contain example code fragments that are included (see the \include
|
|
|
|
|
# command).
|
|
|
|
|
|
|
|
|
|
EXAMPLE_PATH =
|
|
|
|
|
EXAMPLE_PATH =
|
|
|
|
|
|
|
|
|
|
# If the value of the EXAMPLE_PATH tag contains directories, you can use the
|
|
|
|
|
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
|
|
|
|
@ -948,7 +970,7 @@ IMAGE_PATH = images
|
|
|
|
|
# need to set EXTENSION_MAPPING for the extension otherwise the files are not
|
|
|
|
|
# properly processed by doxygen.
|
|
|
|
|
|
|
|
|
|
INPUT_FILTER =
|
|
|
|
|
INPUT_FILTER =
|
|
|
|
|
|
|
|
|
|
# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
|
|
|
|
|
# basis. Doxygen will compare the file name with each pattern and apply the
|
|
|
|
@ -961,7 +983,7 @@ INPUT_FILTER =
|
|
|
|
|
# need to set EXTENSION_MAPPING for the extension otherwise the files are not
|
|
|
|
|
# properly processed by doxygen.
|
|
|
|
|
|
|
|
|
|
FILTER_PATTERNS =
|
|
|
|
|
FILTER_PATTERNS =
|
|
|
|
|
|
|
|
|
|
# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
|
|
|
|
|
# INPUT_FILTER) will also be used to filter the input files that are used for
|
|
|
|
@ -976,14 +998,14 @@ FILTER_SOURCE_FILES = NO
|
|
|
|
|
# *.ext= (so without naming a filter).
|
|
|
|
|
# This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
|
|
|
|
|
|
|
|
|
|
FILTER_SOURCE_PATTERNS =
|
|
|
|
|
FILTER_SOURCE_PATTERNS =
|
|
|
|
|
|
|
|
|
|
# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
|
|
|
|
|
# is part of the input, its contents will be placed on the main page
|
|
|
|
|
# (index.html). This can be useful if you have a project on for instance GitHub
|
|
|
|
|
# and want to reuse the introduction page also for the doxygen output.
|
|
|
|
|
|
|
|
|
|
USE_MDFILE_AS_MAINPAGE =
|
|
|
|
|
USE_MDFILE_AS_MAINPAGE =
|
|
|
|
|
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
|
# Configuration options related to source browsing
|
|
|
|
@ -1012,7 +1034,7 @@ INLINE_SOURCES = NO
|
|
|
|
|
STRIP_CODE_COMMENTS = YES
|
|
|
|
|
|
|
|
|
|
# If the REFERENCED_BY_RELATION tag is set to YES then for each documented
|
|
|
|
|
# function all documented functions referencing it will be listed.
|
|
|
|
|
# entity all documented functions referencing it will be listed.
|
|
|
|
|
# The default value is: NO.
|
|
|
|
|
|
|
|
|
|
REFERENCED_BY_RELATION = NO
|
|
|
|
@ -1049,7 +1071,7 @@ SOURCE_TOOLTIPS = YES
|
|
|
|
|
#
|
|
|
|
|
# To use it do the following:
|
|
|
|
|
# - Install the latest version of global
|
|
|
|
|
# - Enable SOURCE_BROWSER and USE_HTAGS in the config file
|
|
|
|
|
# - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
|
|
|
|
|
# - Make sure the INPUT points to the root of the source tree
|
|
|
|
|
# - Run doxygen as normal
|
|
|
|
|
#
|
|
|
|
@ -1095,7 +1117,7 @@ COLS_IN_ALPHA_INDEX = 5
|
|
|
|
|
# while generating the index headers.
|
|
|
|
|
# This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
|
|
|
|
|
|
|
|
|
|
IGNORE_PREFIX =
|
|
|
|
|
IGNORE_PREFIX =
|
|
|
|
|
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
|
# Configuration options related to the HTML output
|
|
|
|
@ -1139,7 +1161,7 @@ HTML_FILE_EXTENSION = .html
|
|
|
|
|
# of the possible markers and block names see the documentation.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
|
|
|
|
|
|
|
|
|
HTML_HEADER =
|
|
|
|
|
HTML_HEADER =
|
|
|
|
|
|
|
|
|
|
# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
|
|
|
|
|
# generated HTML page. If the tag is left blank doxygen will generate a standard
|
|
|
|
@ -1149,7 +1171,7 @@ HTML_HEADER =
|
|
|
|
|
# that doxygen normally uses.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
|
|
|
|
|
|
|
|
|
HTML_FOOTER =
|
|
|
|
|
HTML_FOOTER =
|
|
|
|
|
|
|
|
|
|
# The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
|
|
|
|
|
# sheet that is used by each HTML page. It can be used to fine-tune the look of
|
|
|
|
@ -1161,7 +1183,7 @@ HTML_FOOTER =
|
|
|
|
|
# obsolete.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
|
|
|
|
|
|
|
|
|
HTML_STYLESHEET =
|
|
|
|
|
HTML_STYLESHEET =
|
|
|
|
|
|
|
|
|
|
# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
|
|
|
|
|
# cascading style sheets that are included after the standard style sheets
|
|
|
|
@ -1174,7 +1196,7 @@ HTML_STYLESHEET =
|
|
|
|
|
# list). For an example see the documentation.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
|
|
|
|
|
|
|
|
|
HTML_EXTRA_STYLESHEET =
|
|
|
|
|
HTML_EXTRA_STYLESHEET =
|
|
|
|
|
|
|
|
|
|
# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
|
|
|
|
|
# other source files which should be copied to the HTML output directory. Note
|
|
|
|
@ -1184,7 +1206,7 @@ HTML_EXTRA_STYLESHEET =
|
|
|
|
|
# files will be copied as-is; there are no commands or markers available.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
|
|
|
|
|
|
|
|
|
HTML_EXTRA_FILES =
|
|
|
|
|
HTML_EXTRA_FILES =
|
|
|
|
|
|
|
|
|
|
# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
|
|
|
|
|
# will adjust the colors in the style sheet and background images according to
|
|
|
|
@ -1195,7 +1217,7 @@ HTML_EXTRA_FILES =
|
|
|
|
|
# Minimum value: 0, maximum value: 359, default value: 220.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
|
|
|
|
|
|
|
|
|
HTML_COLORSTYLE_HUE = 358
|
|
|
|
|
HTML_COLORSTYLE_HUE = 49
|
|
|
|
|
|
|
|
|
|
# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
|
|
|
|
|
# in the HTML output. For a value of 0 the output will use grayscales only. A
|
|
|
|
@ -1203,7 +1225,7 @@ HTML_COLORSTYLE_HUE = 358
|
|
|
|
|
# Minimum value: 0, maximum value: 255, default value: 100.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
|
|
|
|
|
|
|
|
|
HTML_COLORSTYLE_SAT = 69
|
|
|
|
|
HTML_COLORSTYLE_SAT = 155
|
|
|
|
|
|
|
|
|
|
# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
|
|
|
|
|
# luminance component of the colors in the HTML output. Values below 100
|
|
|
|
@ -1214,7 +1236,7 @@ HTML_COLORSTYLE_SAT = 69
|
|
|
|
|
# Minimum value: 40, maximum value: 240, default value: 80.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
|
|
|
|
|
|
|
|
|
HTML_COLORSTYLE_GAMMA = 229
|
|
|
|
|
HTML_COLORSTYLE_GAMMA = 240
|
|
|
|
|
|
|
|
|
|
# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
|
|
|
|
|
# page will contain the date and time when the page was generated. Setting this
|
|
|
|
@ -1259,13 +1281,13 @@ HTML_INDEX_NUM_ENTRIES = 100
|
|
|
|
|
|
|
|
|
|
# If the GENERATE_DOCSET tag is set to YES, additional index files will be
|
|
|
|
|
# generated that can be used as input for Apple's Xcode 3 integrated development
|
|
|
|
|
# environment (see: https://developer.apple.com/tools/xcode/), introduced with
|
|
|
|
|
# OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
|
|
|
|
|
# environment (see: https://developer.apple.com/xcode/), introduced with OSX
|
|
|
|
|
# 10.5 (Leopard). To create a documentation set, doxygen will generate a
|
|
|
|
|
# Makefile in the HTML output directory. Running make will produce the docset in
|
|
|
|
|
# that directory and running make install will install the docset in
|
|
|
|
|
# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
|
|
|
|
|
# startup. See https://developer.apple.com/tools/creatingdocsetswithdoxygen.html
|
|
|
|
|
# for more information.
|
|
|
|
|
# startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy
|
|
|
|
|
# genXcode/_index.html for more information.
|
|
|
|
|
# The default value is: NO.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
|
|
|
|
|
|
|
|
@ -1304,7 +1326,7 @@ DOCSET_PUBLISHER_NAME = Publisher
|
|
|
|
|
# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
|
|
|
|
|
# additional HTML index files: index.hhp, index.hhc, and index.hhk. The
|
|
|
|
|
# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
|
|
|
|
|
# (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
|
|
|
|
|
# (see: https://www.microsoft.com/en-us/download/details.aspx?id=21138) on
|
|
|
|
|
# Windows.
|
|
|
|
|
#
|
|
|
|
|
# The HTML Help Workshop contains a compiler that can convert all HTML output
|
|
|
|
@ -1324,7 +1346,7 @@ GENERATE_HTMLHELP = NO
|
|
|
|
|
# written to the html output directory.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
|
|
|
|
|
|
|
|
|
|
CHM_FILE =
|
|
|
|
|
CHM_FILE =
|
|
|
|
|
|
|
|
|
|
# The HHC_LOCATION tag can be used to specify the location (absolute path
|
|
|
|
|
# including file name) of the HTML help compiler (hhc.exe). If non-empty,
|
|
|
|
@ -1332,7 +1354,7 @@ CHM_FILE =
|
|
|
|
|
# The file has to be specified with full path.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
|
|
|
|
|
|
|
|
|
|
HHC_LOCATION =
|
|
|
|
|
HHC_LOCATION =
|
|
|
|
|
|
|
|
|
|
# The GENERATE_CHI flag controls if a separate .chi index file is generated
|
|
|
|
|
# (YES) or that it should be included in the master .chm file (NO).
|
|
|
|
@ -1345,7 +1367,7 @@ GENERATE_CHI = NO
|
|
|
|
|
# and project file content.
|
|
|
|
|
# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
|
|
|
|
|
|
|
|
|
|
CHM_INDEX_ENCODING =
|
|
|
|
|
CHM_INDEX_ENCODING =
|
|
|
|
|
|
|
|
|
|
# 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. Furthermore it
|
|
|
|
@ -1376,11 +1398,11 @@ GENERATE_QHP = NO
|
|
|
|
|
# the HTML output folder.
|
|
|
|
|
# This tag requires that the tag GENERATE_QHP is set to YES.
|
|
|
|
|
|
|
|
|
|
QCH_FILE =
|
|
|
|
|
QCH_FILE =
|
|
|
|
|
|
|
|
|
|
# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
|
|
|
|
|
# Project output. For more information please see Qt Help Project / Namespace
|
|
|
|
|
# (see: http://doc.qt.io/qt-4.8/qthelpproject.html#namespace).
|
|
|
|
|
# (see: http://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace).
|
|
|
|
|
# The default value is: org.doxygen.Project.
|
|
|
|
|
# This tag requires that the tag GENERATE_QHP is set to YES.
|
|
|
|
|
|
|
|
|
@ -1388,7 +1410,8 @@ QHP_NAMESPACE = org.doxygen.Project
|
|
|
|
|
|
|
|
|
|
# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
|
|
|
|
|
# Help Project output. For more information please see Qt Help Project / Virtual
|
|
|
|
|
# Folders (see: http://doc.qt.io/qt-4.8/qthelpproject.html#virtual-folders).
|
|
|
|
|
# Folders (see: http://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-
|
|
|
|
|
# folders).
|
|
|
|
|
# The default value is: doc.
|
|
|
|
|
# This tag requires that the tag GENERATE_QHP is set to YES.
|
|
|
|
|
|
|
|
|
@ -1396,31 +1419,33 @@ QHP_VIRTUAL_FOLDER = doc
|
|
|
|
|
|
|
|
|
|
# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
|
|
|
|
|
# filter to add. For more information please see Qt Help Project / Custom
|
|
|
|
|
# Filters (see: http://doc.qt.io/qt-4.8/qthelpproject.html#custom-filters).
|
|
|
|
|
# Filters (see: http://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-
|
|
|
|
|
# filters).
|
|
|
|
|
# This tag requires that the tag GENERATE_QHP is set to YES.
|
|
|
|
|
|
|
|
|
|
QHP_CUST_FILTER_NAME =
|
|
|
|
|
QHP_CUST_FILTER_NAME =
|
|
|
|
|
|
|
|
|
|
# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
|
|
|
|
|
# custom filter to add. For more information please see Qt Help Project / Custom
|
|
|
|
|
# Filters (see: http://doc.qt.io/qt-4.8/qthelpproject.html#custom-filters).
|
|
|
|
|
# Filters (see: http://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-
|
|
|
|
|
# filters).
|
|
|
|
|
# This tag requires that the tag GENERATE_QHP is set to YES.
|
|
|
|
|
|
|
|
|
|
QHP_CUST_FILTER_ATTRS =
|
|
|
|
|
QHP_CUST_FILTER_ATTRS =
|
|
|
|
|
|
|
|
|
|
# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
|
|
|
|
|
# project's filter section matches. Qt Help Project / Filter Attributes (see:
|
|
|
|
|
# http://doc.qt.io/qt-4.8/qthelpproject.html#filter-attributes).
|
|
|
|
|
# http://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes).
|
|
|
|
|
# This tag requires that the tag GENERATE_QHP is set to YES.
|
|
|
|
|
|
|
|
|
|
QHP_SECT_FILTER_ATTRS =
|
|
|
|
|
QHP_SECT_FILTER_ATTRS =
|
|
|
|
|
|
|
|
|
|
# The QHG_LOCATION tag can be used to specify the location of Qt's
|
|
|
|
|
# qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
|
|
|
|
|
# generated .qhp file.
|
|
|
|
|
# This tag requires that the tag GENERATE_QHP is set to YES.
|
|
|
|
|
|
|
|
|
|
QHG_LOCATION =
|
|
|
|
|
QHG_LOCATION =
|
|
|
|
|
|
|
|
|
|
# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
|
|
|
|
|
# generated, together with the HTML files, they form an Eclipse help plugin. To
|
|
|
|
@ -1543,7 +1568,7 @@ MATHJAX_FORMAT = HTML-CSS
|
|
|
|
|
# Content Delivery Network so you can quickly see the result without installing
|
|
|
|
|
# MathJax. However, it is strongly recommended to install a local copy of
|
|
|
|
|
# MathJax from https://www.mathjax.org before deployment.
|
|
|
|
|
# The default value is: https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.2/.
|
|
|
|
|
# The default value is: https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/.
|
|
|
|
|
# This tag requires that the tag USE_MATHJAX is set to YES.
|
|
|
|
|
|
|
|
|
|
MATHJAX_RELPATH = https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.2/
|
|
|
|
@ -1553,7 +1578,7 @@ MATHJAX_RELPATH = https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.2/
|
|
|
|
|
# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
|
|
|
|
|
# This tag requires that the tag USE_MATHJAX is set to YES.
|
|
|
|
|
|
|
|
|
|
MATHJAX_EXTENSIONS =
|
|
|
|
|
MATHJAX_EXTENSIONS =
|
|
|
|
|
|
|
|
|
|
# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
|
|
|
|
|
# of code that will be used on startup of the MathJax code. See the MathJax site
|
|
|
|
@ -1561,7 +1586,7 @@ MATHJAX_EXTENSIONS =
|
|
|
|
|
# example see the documentation.
|
|
|
|
|
# This tag requires that the tag USE_MATHJAX is set to YES.
|
|
|
|
|
|
|
|
|
|
MATHJAX_CODEFILE =
|
|
|
|
|
MATHJAX_CODEFILE =
|
|
|
|
|
|
|
|
|
|
# When the SEARCHENGINE tag is enabled doxygen will generate a search box for
|
|
|
|
|
# the HTML output. The underlying search engine uses javascript and DHTML and
|
|
|
|
@ -1621,7 +1646,7 @@ EXTERNAL_SEARCH = NO
|
|
|
|
|
# Searching" for details.
|
|
|
|
|
# This tag requires that the tag SEARCHENGINE is set to YES.
|
|
|
|
|
|
|
|
|
|
SEARCHENGINE_URL =
|
|
|
|
|
SEARCHENGINE_URL =
|
|
|
|
|
|
|
|
|
|
# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
|
|
|
|
|
# search data is written to a file for indexing by an external tool. With the
|
|
|
|
@ -1637,7 +1662,7 @@ SEARCHDATA_FILE = searchdata.xml
|
|
|
|
|
# projects and redirect the results back to the right project.
|
|
|
|
|
# This tag requires that the tag SEARCHENGINE is set to YES.
|
|
|
|
|
|
|
|
|
|
EXTERNAL_SEARCH_ID =
|
|
|
|
|
EXTERNAL_SEARCH_ID =
|
|
|
|
|
|
|
|
|
|
# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
|
|
|
|
|
# projects other than the one defined by this configuration file, but that are
|
|
|
|
@ -1647,7 +1672,7 @@ EXTERNAL_SEARCH_ID =
|
|
|
|
|
# EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
|
|
|
|
|
# This tag requires that the tag SEARCHENGINE is set to YES.
|
|
|
|
|
|
|
|
|
|
EXTRA_SEARCH_MAPPINGS =
|
|
|
|
|
EXTRA_SEARCH_MAPPINGS =
|
|
|
|
|
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
|
# Configuration options related to the LaTeX output
|
|
|
|
@ -1669,21 +1694,34 @@ LATEX_OUTPUT = latex
|
|
|
|
|
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
|
|
|
|
|
# invoked.
|
|
|
|
|
#
|
|
|
|
|
# Note that when enabling USE_PDFLATEX this option is only used for generating
|
|
|
|
|
# bitmaps for formulas in the HTML output, but not in the Makefile that is
|
|
|
|
|
# written to the output directory.
|
|
|
|
|
# The default file is: latex.
|
|
|
|
|
# Note that when not enabling USE_PDFLATEX the default is latex when enabling
|
|
|
|
|
# USE_PDFLATEX the default is pdflatex and when in the later case latex is
|
|
|
|
|
# chosen this is overwritten by pdflatex. For specific output languages the
|
|
|
|
|
# default can have been set differently, this depends on the implementation of
|
|
|
|
|
# the output language.
|
|
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES.
|
|
|
|
|
|
|
|
|
|
LATEX_CMD_NAME = latex
|
|
|
|
|
|
|
|
|
|
# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
|
|
|
|
|
# index for LaTeX.
|
|
|
|
|
# Note: This tag is used in the Makefile / make.bat.
|
|
|
|
|
# See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
|
|
|
|
|
# (.tex).
|
|
|
|
|
# The default file is: makeindex.
|
|
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES.
|
|
|
|
|
|
|
|
|
|
MAKEINDEX_CMD_NAME = makeindex
|
|
|
|
|
|
|
|
|
|
# The LATEX_MAKEINDEX_CMD tag can be used to specify the command name to
|
|
|
|
|
# generate index for LaTeX.
|
|
|
|
|
# Note: This tag is used in the generated output file (.tex).
|
|
|
|
|
# See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat.
|
|
|
|
|
# The default value is: \makeindex.
|
|
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES.
|
|
|
|
|
|
|
|
|
|
LATEX_MAKEINDEX_CMD = \makeindex
|
|
|
|
|
|
|
|
|
|
# If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
|
|
|
|
|
# documents. This may be useful for small projects and may help to save some
|
|
|
|
|
# trees in general.
|
|
|
|
@ -1711,7 +1749,7 @@ PAPER_TYPE = a4
|
|
|
|
|
# If left blank no extra packages will be included.
|
|
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES.
|
|
|
|
|
|
|
|
|
|
EXTRA_PACKAGES =
|
|
|
|
|
EXTRA_PACKAGES =
|
|
|
|
|
|
|
|
|
|
# The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
|
|
|
|
|
# generated LaTeX document. The header should contain everything until the first
|
|
|
|
@ -1727,7 +1765,7 @@ EXTRA_PACKAGES =
|
|
|
|
|
# to HTML_HEADER.
|
|
|
|
|
# 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
|
|
|
|
|
# generated LaTeX document. The footer should contain everything after the last
|
|
|
|
@ -1738,7 +1776,7 @@ LATEX_HEADER =
|
|
|
|
|
# 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.
|
|
|
|
|
|
|
|
|
|
LATEX_FOOTER =
|
|
|
|
|
LATEX_FOOTER =
|
|
|
|
|
|
|
|
|
|
# The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
|
|
|
|
|
# LaTeX style sheets that are included after the standard style sheets created
|
|
|
|
@ -1749,7 +1787,7 @@ LATEX_FOOTER =
|
|
|
|
|
# list).
|
|
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES.
|
|
|
|
|
|
|
|
|
|
LATEX_EXTRA_STYLESHEET =
|
|
|
|
|
LATEX_EXTRA_STYLESHEET =
|
|
|
|
|
|
|
|
|
|
# The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
|
|
|
|
|
# other source files which should be copied to the LATEX_OUTPUT output
|
|
|
|
@ -1757,7 +1795,7 @@ LATEX_EXTRA_STYLESHEET =
|
|
|
|
|
# markers available.
|
|
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES.
|
|
|
|
|
|
|
|
|
|
LATEX_EXTRA_FILES =
|
|
|
|
|
LATEX_EXTRA_FILES =
|
|
|
|
|
|
|
|
|
|
# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
|
|
|
|
|
# prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
|
|
|
|
@ -1818,6 +1856,14 @@ LATEX_BIB_STYLE = plain
|
|
|
|
|
|
|
|
|
|
LATEX_TIMESTAMP = NO
|
|
|
|
|
|
|
|
|
|
# The LATEX_EMOJI_DIRECTORY tag is used to specify the (relative or absolute)
|
|
|
|
|
# path from which the emoji images will be read. If a relative path is entered,
|
|
|
|
|
# it will be relative to the LATEX_OUTPUT directory. If left blank the
|
|
|
|
|
# LATEX_OUTPUT directory will be used.
|
|
|
|
|
# This tag requires that the tag GENERATE_LATEX is set to YES.
|
|
|
|
|
|
|
|
|
|
LATEX_EMOJI_DIRECTORY =
|
|
|
|
|
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
|
# Configuration options related to the RTF output
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
@ -1857,22 +1903,22 @@ COMPACT_RTF = NO
|
|
|
|
|
|
|
|
|
|
RTF_HYPERLINKS = NO
|
|
|
|
|
|
|
|
|
|
# Load stylesheet definitions from file. Syntax is similar to doxygen's config
|
|
|
|
|
# file, i.e. a series of assignments. You only have to provide replacements,
|
|
|
|
|
# missing definitions are set to their default value.
|
|
|
|
|
# Load stylesheet definitions from file. Syntax is similar to doxygen's
|
|
|
|
|
# configuration file, i.e. a series of assignments. You only have to provide
|
|
|
|
|
# replacements, missing definitions are set to their default value.
|
|
|
|
|
#
|
|
|
|
|
# See also section "Doxygen usage" for information on how to generate the
|
|
|
|
|
# default style sheet that doxygen normally uses.
|
|
|
|
|
# This tag requires that the tag GENERATE_RTF is set to YES.
|
|
|
|
|
|
|
|
|
|
RTF_STYLESHEET_FILE =
|
|
|
|
|
RTF_STYLESHEET_FILE =
|
|
|
|
|
|
|
|
|
|
# Set optional variables used in the generation of an RTF document. Syntax is
|
|
|
|
|
# similar to doxygen's config file. A template extensions file can be generated
|
|
|
|
|
# using doxygen -e rtf extensionFile.
|
|
|
|
|
# similar to doxygen's configuration file. A template extensions file can be
|
|
|
|
|
# generated using doxygen -e rtf extensionFile.
|
|
|
|
|
# This tag requires that the tag GENERATE_RTF is set to YES.
|
|
|
|
|
|
|
|
|
|
RTF_EXTENSIONS_FILE =
|
|
|
|
|
RTF_EXTENSIONS_FILE =
|
|
|
|
|
|
|
|
|
|
# If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
|
|
|
|
|
# with syntax highlighting in the RTF output.
|
|
|
|
@ -1917,7 +1963,7 @@ MAN_EXTENSION = .3
|
|
|
|
|
# MAN_EXTENSION with the initial . removed.
|
|
|
|
|
# This tag requires that the tag GENERATE_MAN is set to YES.
|
|
|
|
|
|
|
|
|
|
MAN_SUBDIR =
|
|
|
|
|
MAN_SUBDIR =
|
|
|
|
|
|
|
|
|
|
# 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
|
|
|
|
@ -1955,6 +2001,13 @@ XML_OUTPUT = xml
|
|
|
|
|
|
|
|
|
|
XML_PROGRAMLISTING = YES
|
|
|
|
|
|
|
|
|
|
# If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, doxygen will include
|
|
|
|
|
# namespace members in file scope as well, matching the HTML output.
|
|
|
|
|
# The default value is: NO.
|
|
|
|
|
# This tag requires that the tag GENERATE_XML is set to YES.
|
|
|
|
|
|
|
|
|
|
XML_NS_MEMB_FILE_SCOPE = NO
|
|
|
|
|
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
|
# Configuration options related to the DOCBOOK output
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
@ -2030,7 +2083,7 @@ PERLMOD_PRETTY = YES
|
|
|
|
|
# overwrite each other's variables.
|
|
|
|
|
# This tag requires that the tag GENERATE_PERLMOD is set to YES.
|
|
|
|
|
|
|
|
|
|
PERLMOD_MAKEVAR_PREFIX =
|
|
|
|
|
PERLMOD_MAKEVAR_PREFIX =
|
|
|
|
|
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
|
|
|
# Configuration options related to the preprocessor
|
|
|
|
@ -2071,7 +2124,7 @@ SEARCH_INCLUDES = YES
|
|
|
|
|
# preprocessor.
|
|
|
|
|
# This tag requires that the tag SEARCH_INCLUDES is set to YES.
|
|
|
|
|
|
|
|
|
|
INCLUDE_PATH =
|
|
|
|
|
INCLUDE_PATH =
|
|
|
|
|
|
|
|
|
|
# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
|
|
|
|
|
# patterns (like *.h and *.hpp) to filter out the header-files in the
|
|
|
|
@ -2079,7 +2132,7 @@ INCLUDE_PATH =
|
|
|
|
|
# used.
|
|
|
|
|
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
|
|
|
|
|
|
|
|
|
|
INCLUDE_FILE_PATTERNS =
|
|
|
|
|
INCLUDE_FILE_PATTERNS =
|
|
|
|
|
|
|
|
|
|
# The PREDEFINED tag can be used to specify one or more macro names that are
|
|
|
|
|
# defined before the preprocessor is started (similar to the -D option of e.g.
|
|
|
|
@ -2089,7 +2142,7 @@ INCLUDE_FILE_PATTERNS =
|
|
|
|
|
# recursively expanded use the := operator instead of the = operator.
|
|
|
|
|
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
|
|
|
|
|
|
|
|
|
|
PREDEFINED =
|
|
|
|
|
PREDEFINED =
|
|
|
|
|
|
|
|
|
|
# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
|
|
|
|
|
# tag can be used to specify a list of macro names that should be expanded. The
|
|
|
|
@ -2098,7 +2151,7 @@ PREDEFINED =
|
|
|
|
|
# definition found in the source code.
|
|
|
|
|
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
|
|
|
|
|
|
|
|
|
|
EXPAND_AS_DEFINED =
|
|
|
|
|
EXPAND_AS_DEFINED =
|
|
|
|
|
|
|
|
|
|
# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
|
|
|
|
|
# remove all references to function-like macros that are alone on a line, have
|
|
|
|
@ -2127,13 +2180,13 @@ SKIP_FUNCTION_MACROS = YES
|
|
|
|
|
# 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.
|
|
|
|
|
|
|
|
|
|
TAGFILES =
|
|
|
|
|
TAGFILES =
|
|
|
|
|
|
|
|
|
|
# When a file name is specified after GENERATE_TAGFILE, doxygen will create a
|
|
|
|
|
# tag file that is based on the input files it reads. See section "Linking to
|
|
|
|
|
# external documentation" for more information about the usage of tag files.
|
|
|
|
|
|
|
|
|
|
GENERATE_TAGFILE =
|
|
|
|
|
GENERATE_TAGFILE =
|
|
|
|
|
|
|
|
|
|
# If the ALLEXTERNALS tag is set to YES, all external class will be listed in
|
|
|
|
|
# the class index. If set to NO, only the inherited external classes will be
|
|
|
|
@ -2182,14 +2235,14 @@ CLASS_DIAGRAMS = NO
|
|
|
|
|
# the mscgen tool resides. If left empty the tool is assumed to be found in the
|
|
|
|
|
# default search path.
|
|
|
|
|
|
|
|
|
|
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 =
|
|
|
|
|
DIA_PATH =
|
|
|
|
|
|
|
|
|
|
# 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.
|
|
|
|
@ -2238,7 +2291,7 @@ DOT_FONTSIZE = 10
|
|
|
|
|
# the path where dot can find it using this tag.
|
|
|
|
|
# This tag requires that the tag HAVE_DOT is set to YES.
|
|
|
|
|
|
|
|
|
|
DOT_FONTPATH =
|
|
|
|
|
DOT_FONTPATH =
|
|
|
|
|
|
|
|
|
|
# If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
|
|
|
|
|
# each documented class showing the direct and indirect inheritance relations.
|
|
|
|
@ -2382,26 +2435,26 @@ INTERACTIVE_SVG = NO
|
|
|
|
|
# found. If left blank, it is assumed the dot tool can be found in the path.
|
|
|
|
|
# This tag requires that the tag HAVE_DOT is set to YES.
|
|
|
|
|
|
|
|
|
|
DOT_PATH =
|
|
|
|
|
DOT_PATH =
|
|
|
|
|
|
|
|
|
|
# The DOTFILE_DIRS tag can be used to specify one or more directories that
|
|
|
|
|
# contain dot files that are included in the documentation (see the \dotfile
|
|
|
|
|
# command).
|
|
|
|
|
# This tag requires that the tag HAVE_DOT is set to YES.
|
|
|
|
|
|
|
|
|
|
DOTFILE_DIRS =
|
|
|
|
|
DOTFILE_DIRS =
|
|
|
|
|
|
|
|
|
|
# The MSCFILE_DIRS tag can be used to specify one or more directories that
|
|
|
|
|
# contain msc files that are included in the documentation (see the \mscfile
|
|
|
|
|
# command).
|
|
|
|
|
|
|
|
|
|
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 =
|
|
|
|
|
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
|
|
|
|
@ -2409,17 +2462,17 @@ DIAFILE_DIRS =
|
|
|
|
|
# generate a warning when it encounters a \startuml command in this case and
|
|
|
|
|
# will not generate output for the diagram.
|
|
|
|
|
|
|
|
|
|
PLANTUML_JAR_PATH =
|
|
|
|
|
PLANTUML_JAR_PATH =
|
|
|
|
|
|
|
|
|
|
# When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
|
|
|
|
|
# configuration file for plantuml.
|
|
|
|
|
|
|
|
|
|
PLANTUML_CFG_FILE =
|
|
|
|
|
PLANTUML_CFG_FILE =
|
|
|
|
|
|
|
|
|
|
# When using plantuml, the specified paths are searched for files specified by
|
|
|
|
|
# the !include statement in a plantuml block.
|
|
|
|
|
|
|
|
|
|
PLANTUML_INCLUDE_PATH =
|
|
|
|
|
PLANTUML_INCLUDE_PATH =
|
|
|
|
|
|
|
|
|
|
# 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
|
|
|
|
|