Revision 2b455197
Von Christian Ehringfeld vor mehr als 8 Jahren hinzugefügt
| Doxyfile | ||
|---|---|---|
|
# Doxyfile 1.8.10
|
||
|
# Doxyfile 1.8.9.1
|
||
|
|
||
|
# This file describes the settings to be used by the documentation system
|
||
|
# doxygen (www.doxygen.org) for a project.
|
||
| ... | ... | |
|
# title of most generated pages and in a few other places.
|
||
|
# The default value is: My Project.
|
||
|
|
||
|
PROJECT_NAME = "CuteEntityManager"
|
||
|
PROJECT_NAME = CuteEntityManager
|
||
|
|
||
|
# 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
|
||
|
# control system is used.
|
||
|
|
||
|
PROJECT_NUMBER =
|
||
|
PROJECT_NUMBER =
|
||
|
|
||
|
# 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
|
||
|
# quick idea about the purpose of the project. Keep the description short.
|
||
|
|
||
|
PROJECT_BRIEF = "CuteEntityManager can persist, merge, find or delete entities with Qt"
|
||
|
|
||
|
# 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
|
||
|
# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
|
||
|
# the logo to the output directory.
|
||
|
|
||
|
PROJECT_LOGO =
|
||
|
PROJECT_LOGO =
|
||
|
|
||
|
# 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
|
||
| ... | ... | |
|
# the entity):The $name class, The $name widget, The $name file, is, provides,
|
||
|
# specifies, contains, represents, a, an and the.
|
||
|
|
||
|
ABBREVIATE_BRIEF =
|
||
|
ABBREVIATE_BRIEF = "The $name class" \
|
||
|
"The $name widget" \
|
||
|
"The $name file" \
|
||
|
is \
|
||
|
provides \
|
||
|
specifies \
|
||
|
contains \
|
||
|
represents \
|
||
|
a \
|
||
|
an \
|
||
|
the
|
||
|
|
||
|
# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
|
||
|
# doxygen will generate a detailed section even if there is only a brief
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# "Side Effects:". You can put \n's in the value part of an alias to insert
|
||
|
# newlines.
|
||
|
|
||
|
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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
|
||
|
DISTRIBUTE_GROUP_DOC = NO
|
||
|
|
||
|
# If one adds a struct or class to a group and this option is enabled, then also
|
||
|
# any nested class or struct is added to the same group. By default this option
|
||
|
# is disabled and one has to add nested compounds explicitly via \ingroup.
|
||
|
# The default value is: NO.
|
||
|
|
||
|
GROUP_NESTED_COMPOUNDS = NO
|
||
|
|
||
|
# Set the SUBGROUPING tag to YES to allow class member groups of the same type
|
||
|
# (for instance a group of public functions) to be put as a subgroup of that
|
||
|
# type (e.g. under the Public Functions section). Set it to NO to prevent
|
||
| ... | ... | |
|
# and Mac users are advised to set this option to NO.
|
||
|
# The default value is: system dependent.
|
||
|
|
||
|
CASE_SENSE_NAMES = YES
|
||
|
CASE_SENSE_NAMES = NO
|
||
|
|
||
|
# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
|
||
|
# their full class and namespace scopes in the documentation. If set to YES, the
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# messages are off.
|
||
|
# The default value is: NO.
|
||
|
|
||
|
QUIET = NO
|
||
|
QUIET = YES
|
||
|
|
||
|
# The WARNINGS tag can be used to turn on/off the warning messages that are
|
||
|
# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES
|
||
| ... | ... | |
|
# Tip: Turn warnings on while writing the documentation.
|
||
|
# The default value is: YES.
|
||
|
|
||
|
WARNINGS = YES
|
||
|
WARNINGS = NO
|
||
|
|
||
|
# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate
|
||
|
# warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
|
||
|
# will automatically be disabled.
|
||
|
# The default value is: YES.
|
||
|
|
||
|
WARN_IF_UNDOCUMENTED = YES
|
||
|
WARN_IF_UNDOCUMENTED = NO
|
||
|
|
||
|
# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
|
||
|
# potential errors in the documentation, such as not documenting some parameters
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# The INPUT tag is used to specify the files and/or directories that contain
|
||
|
# documented source files. You may enter file names like myfile.cpp or
|
||
|
# directories like /usr/src/myproject. Separate the files or directories with
|
||
|
# spaces. See also FILE_PATTERNS and EXTENSION_MAPPING
|
||
|
# spaces.
|
||
|
# Note: If this tag is empty the current directory is searched.
|
||
|
|
||
|
INPUT =
|
||
|
INPUT = src/
|
||
|
|
||
|
# This tag can be used to specify the character encoding of the source files
|
||
|
# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
|
||
| ... | ... | |
|
|
||
|
# If the value of the INPUT tag contains directories, you can use the
|
||
|
# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
|
||
|
# *.h) to filter out the source-files in the directories.
|
||
|
#
|
||
|
# Note that for custom extensions or not directly supported extensions you also
|
||
|
# need to set EXTENSION_MAPPING for the extension otherwise the files are not
|
||
|
# read by doxygen.
|
||
|
#
|
||
|
# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp,
|
||
|
# *.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, *.f90, *.f, *.for, *.tcl, *.vhd,
|
||
|
# *.vhdl, *.ucf, *.qsf, *.as and *.js.
|
||
|
|
||
|
FILE_PATTERNS =
|
||
|
# *.h) to filter out the source-files in the directories. If left blank the
|
||
|
# following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.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, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf,
|
||
|
# *.qsf, *.as and *.js.
|
||
|
|
||
|
FILE_PATTERNS = *.c \
|
||
|
*.cc \
|
||
|
*.cxx \
|
||
|
*.cpp \
|
||
|
*.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 \
|
||
|
*.f90 \
|
||
|
*.f \
|
||
|
*.for \
|
||
|
*.tcl \
|
||
|
*.vhd \
|
||
|
*.vhdl \
|
||
|
*.ucf \
|
||
|
*.qsf \
|
||
|
*.as \
|
||
|
*.js
|
||
|
|
||
|
# The RECURSIVE tag can be used to specify whether or not subdirectories should
|
||
|
# be searched for input files as well.
|
||
|
# The default value is: NO.
|
||
|
|
||
|
RECURSIVE = NO
|
||
|
RECURSIVE = YES
|
||
|
|
||
|
# The EXCLUDE tag can be used to specify files and/or directories that should be
|
||
|
# excluded from the INPUT source files. This way you can easily exclude a
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
|
# *.h) to filter out the source-files in the directories. If left blank all
|
||
|
# files are included.
|
||
|
|
||
|
EXAMPLE_PATTERNS =
|
||
|
EXAMPLE_PATTERNS = *
|
||
|
|
||
|
# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
|
||
|
# searched for input files to be used with the \include or \dontinclude commands
|
||
| ... | ... | |
|
# that contain images that are to be included in the documentation (see the
|
||
|
# \image command).
|
||
|
|
||
|
IMAGE_PATH =
|
||
|
IMAGE_PATH =
|
||
|
|
||
|
# The INPUT_FILTER tag can be used to specify a program that doxygen should
|
||
|
# invoke to filter for each input file. Doxygen will invoke the filter program
|
||
| ... | ... | |
|
# code is scanned, but not when the output code is generated. If lines are added
|
||
|
# or removed, the anchors will not be placed correctly.
|
||
|
|
||
|
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
|
||
| ... | ... | |
|
# filters are used. If the FILTER_PATTERNS tag is empty or if none of the
|
||
|
# patterns match the file name, INPUT_FILTER is applied.
|
||
|
|
||
|
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
|
||
| ... | ... | |
|
# *.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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
|
||
|
# 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
|
||
|
# to YES can help to show when doxygen was last run and thus if the
|
||
|
# documentation is up to date.
|
||
|
# The default value is: NO.
|
||
|
# to NO can help when comparing the output of multiple runs.
|
||
|
# The default value is: YES.
|
||
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
||
|
|
||
|
HTML_TIMESTAMP = NO
|
||
|
HTML_TIMESTAMP = YES
|
||
|
|
||
|
# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
|
||
|
# documentation will contain sections that can be hidden and shown after the
|
||
| ... | ... | |
|
# The default value is: NO.
|
||
|
# This tag requires that the tag GENERATE_HTML is set to YES.
|
||
|
|
||
|
HTML_DYNAMIC_SECTIONS = YES
|
||
|
HTML_DYNAMIC_SECTIONS = NO
|
||
|
|
||
|
# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
|
||
|
# shown in the various tree structured indices initially; the user can expand
|
||
| ... | ... | |
|
# 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,
|
||
| ... | ... | |
|
# 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).
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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).
|
||
|
# 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://qt-project.org/doc/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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output.
|
||
|
# The default value is: YES.
|
||
|
|
||
|
GENERATE_LATEX = YES
|
||
|
GENERATE_LATEX = NO
|
||
|
|
||
|
# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
|
||
|
# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
|
||
| ... | ... | |
|
PAPER_TYPE = a4
|
||
|
|
||
|
# The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
|
||
|
# that should be included in the LaTeX output. The package can be specified just
|
||
|
# by its name or with the correct syntax as to be used with the LaTeX
|
||
|
# \usepackage command. To get the times font for instance you can specify :
|
||
|
# EXTRA_PACKAGES=times or EXTRA_PACKAGES={times}
|
||
|
# To use the option intlimits with the amsmath package you can specify:
|
||
|
# EXTRA_PACKAGES=[intlimits]{amsmath}
|
||
|
# that should be included in the LaTeX output. To get the times font for
|
||
|
# instance you can specify
|
||
|
# EXTRA_PACKAGES=times
|
||
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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.
|
||
|
# 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.
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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.
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# powerful graphs.
|
||
|
# The default value is: YES.
|
||
|
|
||
|
CLASS_DIAGRAMS = YES
|
||
|
CLASS_DIAGRAMS = NO
|
||
|
|
||
|
# You can define message sequence charts within doxygen comments using the \msc
|
||
|
# command. Doxygen will then run the mscgen tool (see:
|
||
| ... | ... | |
|
# 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.
|
||
| ... | ... | |
|
# set to NO
|
||
|
# The default value is: NO.
|
||
|
|
||
|
HAVE_DOT = NO
|
||
|
HAVE_DOT = YES
|
||
|
|
||
|
# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
|
||
|
# to run in parallel. When set to 0 doxygen will base this on the number of
|
||
| ... | ... | |
|
# 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.
|
||
| ... | ... | |
|
#
|
||
|
# Note that enabling this option will significantly increase the time of a run.
|
||
|
# So in most cases it will be better to enable call graphs for selected
|
||
|
# functions only using the \callgraph command. Disabling a call graph can be
|
||
|
# accomplished by means of the command \hidecallgraph.
|
||
|
# functions only using the \callgraph command.
|
||
|
# The default value is: NO.
|
||
|
# This tag requires that the tag HAVE_DOT is set to YES.
|
||
|
|
||
| ... | ... | |
|
#
|
||
|
# Note that enabling this option will significantly increase the time of a run.
|
||
|
# So in most cases it will be better to enable caller graphs for selected
|
||
|
# functions only using the \callergraph command. Disabling a caller graph can be
|
||
|
# accomplished by means of the command \hidecallergraph.
|
||
|
# functions only using the \callergraph command.
|
||
|
# The default value is: NO.
|
||
|
# This tag requires that the tag HAVE_DOT is set to YES.
|
||
|
|
||
| ... | ... | |
|
DIRECTORY_GRAPH = YES
|
||
|
|
||
|
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
|
||
|
# generated by dot. For an explanation of the image formats see the section
|
||
|
# output formats in the documentation of the dot tool (Graphviz (see:
|
||
|
# http://www.graphviz.org/)).
|
||
|
# generated by dot.
|
||
|
# Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
|
||
|
# to make the SVG files visible in IE 9+ (other browsers do not have this
|
||
|
# requirement).
|
||
|
# Possible values are: png, jpg, gif, svg, png:gd, png:gd:gd, png:cairo,
|
||
|
# png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and
|
||
|
# png:gdiplus:gdiplus.
|
||
|
# Possible values are: png, jpg, gif and svg.
|
||
|
# The default value is: png.
|
||
|
# This tag requires that the tag HAVE_DOT is set to YES.
|
||
|
|
||
| ... | ... | |
|
# 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
|
||
| ... | ... | |
|
# 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 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
|
||
Auch abrufbar als: Unified diff
doxyfile update
added namespace in logger class