|
|
|
|
@ -1,4 +1,4 @@
|
|
|
|
|
# Doxyfile 1.7.2 |
|
|
|
|
# Doxyfile 1.7.5.1 |
|
|
|
|
|
|
|
|
|
# This file describes the settings to be used by the documentation system |
|
|
|
|
# doxygen (www.doxygen.org) for a project. |
|
|
|
|
@ -22,8 +22,9 @@
|
|
|
|
|
|
|
|
|
|
DOXYFILE_ENCODING = UTF-8 |
|
|
|
|
|
|
|
|
|
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded |
|
|
|
|
# by quotes) that should identify the project. |
|
|
|
|
# The PROJECT_NAME tag is a single word (or sequence of words) that should |
|
|
|
|
# identify the project. Note that if you do not use Doxywizard you need |
|
|
|
|
# to put quotes around the project name if it contains spaces. |
|
|
|
|
|
|
|
|
|
PROJECT_NAME = Magnum |
|
|
|
|
|
|
|
|
|
@ -33,6 +34,19 @@ PROJECT_NAME = Magnum
|
|
|
|
|
|
|
|
|
|
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 = |
|
|
|
|
|
|
|
|
|
# With the PROJECT_LOGO tag one can specify an logo or 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 = |
|
|
|
|
|
|
|
|
|
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) |
|
|
|
|
# base path where the generated documentation will be put. |
|
|
|
|
# If a relative path is entered, it will be relative to the location |
|
|
|
|
@ -57,7 +71,7 @@ CREATE_SUBDIRS = NO
|
|
|
|
|
# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, |
|
|
|
|
# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English |
|
|
|
|
# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, |
|
|
|
|
# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak, |
|
|
|
|
# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, |
|
|
|
|
# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. |
|
|
|
|
|
|
|
|
|
OUTPUT_LANGUAGE = English |
|
|
|
|
@ -263,6 +277,22 @@ DISTRIBUTE_GROUP_DOC = NO
|
|
|
|
|
|
|
|
|
|
SUBGROUPING = YES |
|
|
|
|
|
|
|
|
|
# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and |
|
|
|
|
# unions are shown inside the group in which they are included (e.g. using |
|
|
|
|
# @ingroup) instead of on a separate page (for HTML and Man pages) or |
|
|
|
|
# section (for LaTeX and RTF). |
|
|
|
|
|
|
|
|
|
INLINE_GROUPED_CLASSES = NO |
|
|
|
|
|
|
|
|
|
# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and |
|
|
|
|
# unions with only public data fields will be shown inline in the documentation |
|
|
|
|
# of the scope in which they are defined (i.e. file, namespace, or group |
|
|
|
|
# documentation), provided this scope is documented. If set to NO (the default), |
|
|
|
|
# structs, classes, and unions are shown on a separate page (for HTML and Man |
|
|
|
|
# pages) or section (for LaTeX and RTF). |
|
|
|
|
|
|
|
|
|
INLINE_SIMPLE_STRUCTS = NO |
|
|
|
|
|
|
|
|
|
# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum |
|
|
|
|
# is documented as struct, union, or enum with the name of the typedef. So |
|
|
|
|
# typedef struct TypeS {} TypeT, will appear in the documentation as a struct |
|
|
|
|
@ -279,7 +309,7 @@ TYPEDEF_HIDES_STRUCT = NO
|
|
|
|
|
# For small to medium size projects (<1000 input files) the default value is |
|
|
|
|
# probably good enough. For larger projects a too small cache size can cause |
|
|
|
|
# doxygen to be busy swapping symbols to and from disk most of the time |
|
|
|
|
# causing a significant performance penality. |
|
|
|
|
# causing a significant performance penalty. |
|
|
|
|
# If the system has enough physical memory increasing the cache will improve the |
|
|
|
|
# performance by keeping more symbols in memory. Note that the value works on |
|
|
|
|
# a logarithmic scale so increasing the size by one will roughly double the |
|
|
|
|
@ -438,6 +468,15 @@ SORT_GROUP_NAMES = NO
|
|
|
|
|
|
|
|
|
|
SORT_BY_SCOPE_NAME = NO |
|
|
|
|
|
|
|
|
|
# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to |
|
|
|
|
# do proper type resolution of all parameters of a function it will reject a |
|
|
|
|
# match between the prototype and the implementation of a member function even |
|
|
|
|
# if there is only one candidate or it is obvious which candidate to choose |
|
|
|
|
# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen |
|
|
|
|
# will still accept a match between prototype and implementation in such cases. |
|
|
|
|
|
|
|
|
|
STRICT_PROTO_MATCHING = NO |
|
|
|
|
|
|
|
|
|
# The GENERATE_TODOLIST tag can be used to enable (YES) or |
|
|
|
|
# disable (NO) the todo list. This list is created by putting \todo |
|
|
|
|
# commands in the documentation. |
|
|
|
|
@ -521,6 +560,15 @@ FILE_VERSION_FILTER =
|
|
|
|
|
|
|
|
|
|
LAYOUT_FILE = |
|
|
|
|
|
|
|
|
|
# The CITE_BIB_FILES tag can be used to specify one or more bib files |
|
|
|
|
# containing the references data. This must be a list of .bib files. The |
|
|
|
|
# .bib extension is automatically appended if omitted. Using this command |
|
|
|
|
# requires the bibtex tool 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 LATEX_BIB_STYLE. |
|
|
|
|
|
|
|
|
|
CITE_BIB_FILES = |
|
|
|
|
|
|
|
|
|
#--------------------------------------------------------------------------- |
|
|
|
|
# configuration options related to warning and progress messages |
|
|
|
|
#--------------------------------------------------------------------------- |
|
|
|
|
@ -581,7 +629,8 @@ WARN_LOGFILE =
|
|
|
|
|
# directories like "/usr/src/myproject". Separate the files or directories |
|
|
|
|
# with spaces. |
|
|
|
|
|
|
|
|
|
INPUT = src/ doc/ |
|
|
|
|
INPUT = src/ \ |
|
|
|
|
doc/ |
|
|
|
|
|
|
|
|
|
# This tag can be used to specify the character encoding of the source files |
|
|
|
|
# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is |
|
|
|
|
@ -597,9 +646,11 @@ INPUT_ENCODING = UTF-8
|
|
|
|
|
# blank the following patterns are tested: |
|
|
|
|
# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh |
|
|
|
|
# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py |
|
|
|
|
# *.f90 *.f *.vhd *.vhdl |
|
|
|
|
# *.f90 *.f *.for *.vhd *.vhdl |
|
|
|
|
|
|
|
|
|
FILE_PATTERNS = *.cpp *.h *.dox |
|
|
|
|
FILE_PATTERNS = *.cpp \ |
|
|
|
|
*.h \ |
|
|
|
|
*.dox |
|
|
|
|
|
|
|
|
|
# The RECURSIVE tag can be used to turn specify whether or not subdirectories |
|
|
|
|
# should be searched for input files as well. Possible values are YES and NO. |
|
|
|
|
@ -610,6 +661,7 @@ RECURSIVE = YES
|
|
|
|
|
# The EXCLUDE tag can be used to specify files and/or directories that should |
|
|
|
|
# excluded from the INPUT source files. This way you can easily exclude a |
|
|
|
|
# subdirectory from a directory tree whose root is specified with the INPUT tag. |
|
|
|
|
# Note that relative paths are relative to directory from which doxygen is run. |
|
|
|
|
|
|
|
|
|
EXCLUDE = |
|
|
|
|
|
|
|
|
|
@ -678,8 +730,8 @@ INPUT_FILTER =
|
|
|
|
|
# filter if there is a match. |
|
|
|
|
# The filters are a list of the form: |
|
|
|
|
# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further |
|
|
|
|
# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER |
|
|
|
|
# is applied to all files. |
|
|
|
|
# info on how filters are used. If FILTER_PATTERNS is empty or if |
|
|
|
|
# non of the patterns match the file name, INPUT_FILTER is applied. |
|
|
|
|
|
|
|
|
|
FILTER_PATTERNS = |
|
|
|
|
|
|
|
|
|
@ -689,6 +741,14 @@ FILTER_PATTERNS =
|
|
|
|
|
|
|
|
|
|
FILTER_SOURCE_FILES = NO |
|
|
|
|
|
|
|
|
|
# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file |
|
|
|
|
# pattern. A pattern will override the setting for FILTER_PATTERN (if any) |
|
|
|
|
# and it is also possible to disable source filtering for a specific pattern |
|
|
|
|
# using *.ext= (so without naming a filter). This option only has effect when |
|
|
|
|
# FILTER_SOURCE_FILES is enabled. |
|
|
|
|
|
|
|
|
|
FILTER_SOURCE_PATTERNS = |
|
|
|
|
|
|
|
|
|
#--------------------------------------------------------------------------- |
|
|
|
|
# configuration options related to source browsing |
|
|
|
|
#--------------------------------------------------------------------------- |
|
|
|
|
@ -791,7 +851,14 @@ HTML_FILE_EXTENSION = .html
|
|
|
|
|
|
|
|
|
|
# The HTML_HEADER tag can be used to specify a personal HTML header for |
|
|
|
|
# each generated HTML page. If it is left blank doxygen will generate a |
|
|
|
|
# standard header. |
|
|
|
|
# standard header. Note that when using a custom header you are responsible |
|
|
|
|
# for the proper inclusion of any scripts and style sheets that doxygen |
|
|
|
|
# needs, which is dependent on the configuration options used. |
|
|
|
|
# It is adviced to generate a default header using "doxygen -w html |
|
|
|
|
# header.html footer.html stylesheet.css YourConfigFile" and then modify |
|
|
|
|
# that header. Note that the header is subject to change so you typically |
|
|
|
|
# have to redo this when upgrading to a newer version of doxygen or when |
|
|
|
|
# changing the value of configuration settings such as GENERATE_TREEVIEW! |
|
|
|
|
|
|
|
|
|
HTML_HEADER = |
|
|
|
|
|
|
|
|
|
@ -810,6 +877,15 @@ HTML_FOOTER =
|
|
|
|
|
|
|
|
|
|
HTML_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 |
|
|
|
|
# that these files will be copied to the base HTML output directory. Use the |
|
|
|
|
# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these |
|
|
|
|
# files. In the HTML_STYLESHEET file, use the file name only. Also note that |
|
|
|
|
# the files will be copied as-is; there are no commands or markers available. |
|
|
|
|
|
|
|
|
|
HTML_EXTRA_FILES = |
|
|
|
|
|
|
|
|
|
# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. |
|
|
|
|
# Doxygen will adjust the colors in the stylesheet and background images |
|
|
|
|
# according to this color. Hue is specified as an angle on a colorwheel, |
|
|
|
|
@ -1012,9 +1088,10 @@ ECLIPSE_DOC_ID = org.doxygen.Project
|
|
|
|
|
|
|
|
|
|
DISABLE_INDEX = NO |
|
|
|
|
|
|
|
|
|
# This tag can be used to set the number of enum values (range [0,1..20]) |
|
|
|
|
# that doxygen will group on one line in the generated HTML documentation. |
|
|
|
|
# Note that a value of 0 will completely suppress the enum values from appearing in the overview section. |
|
|
|
|
# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values |
|
|
|
|
# (range [0,1..20]) that doxygen will group on one line in the generated HTML |
|
|
|
|
# documentation. Note that a value of 0 will completely suppress the enum |
|
|
|
|
# values from appearing in the overview section. |
|
|
|
|
|
|
|
|
|
ENUM_VALUES_PER_LINE = 4 |
|
|
|
|
|
|
|
|
|
@ -1073,12 +1150,18 @@ USE_MATHJAX = NO
|
|
|
|
|
# HTML output directory using the MATHJAX_RELPATH option. The destination |
|
|
|
|
# directory should contain the MathJax.js script. For instance, if the mathjax |
|
|
|
|
# directory is located at the same level as the HTML output directory, then |
|
|
|
|
# MATHJAX_RELPATH should be ../mathjax. The default value points to the mathjax.org site, so you can quickly see the result without installing |
|
|
|
|
# MATHJAX_RELPATH should be ../mathjax. The default value points to the |
|
|
|
|
# mathjax.org site, so you can quickly see the result without installing |
|
|
|
|
# MathJax, but it is strongly recommended to install a local copy of MathJax |
|
|
|
|
# before deployment. |
|
|
|
|
|
|
|
|
|
MATHJAX_RELPATH = http://www.mathjax.org/mathjax |
|
|
|
|
|
|
|
|
|
# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension |
|
|
|
|
# names that should be enabled during MathJax rendering. |
|
|
|
|
|
|
|
|
|
MATHJAX_EXTENSIONS = |
|
|
|
|
|
|
|
|
|
# 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 should work on any modern browser. Note that when using |
|
|
|
|
@ -1152,6 +1235,13 @@ EXTRA_PACKAGES =
|
|
|
|
|
|
|
|
|
|
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 chapter. If it is left blank doxygen will generate a |
|
|
|
|
# standard footer. Notice: only use this tag if you know what you are doing! |
|
|
|
|
|
|
|
|
|
LATEX_FOOTER = |
|
|
|
|
|
|
|
|
|
# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated |
|
|
|
|
# is prepared for conversion to pdf (using ps2pdf). The pdf file will |
|
|
|
|
# contain links (just like the HTML output) instead of page references |
|
|
|
|
@ -1185,6 +1275,12 @@ LATEX_HIDE_INDICES = NO
|
|
|
|
|
|
|
|
|
|
LATEX_SOURCE_CODE = NO |
|
|
|
|
|
|
|
|
|
# The LATEX_BIB_STYLE tag can be used to specify the style to use for the |
|
|
|
|
# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See |
|
|
|
|
# http://en.wikipedia.org/wiki/BibTeX for more info. |
|
|
|
|
|
|
|
|
|
LATEX_BIB_STYLE = plain |
|
|
|
|
|
|
|
|
|
#--------------------------------------------------------------------------- |
|
|
|
|
# configuration options related to the RTF output |
|
|
|
|
#--------------------------------------------------------------------------- |
|
|
|
|
@ -1361,7 +1457,7 @@ MACRO_EXPANSION = NO
|
|
|
|
|
EXPAND_ONLY_PREDEF = NO |
|
|
|
|
|
|
|
|
|
# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files |
|
|
|
|
# in the INCLUDE_PATH (see below) will be search if a #include is found. |
|
|
|
|
# pointed to by INCLUDE_PATH will be searched when a #include is found. |
|
|
|
|
|
|
|
|
|
SEARCH_INCLUDES = YES |
|
|
|
|
|
|
|
|
|
@ -1391,15 +1487,15 @@ PREDEFINED = DOXYGEN_GENERATING_OUTPUT
|
|
|
|
|
# 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 macro definition that is found in the sources will be used. |
|
|
|
|
# Use the PREDEFINED tag if you want to use a different macro definition. |
|
|
|
|
# Use the PREDEFINED tag if you want to use a different macro definition that |
|
|
|
|
# overrules the definition found in the source code. |
|
|
|
|
|
|
|
|
|
EXPAND_AS_DEFINED = |
|
|
|
|
|
|
|
|
|
# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then |
|
|
|
|
# doxygen's preprocessor will remove all function-like macros that are alone |
|
|
|
|
# on a line, have an all uppercase name, and do not end with a semicolon. Such |
|
|
|
|
# function macros are typically used for boiler-plate code, and will confuse |
|
|
|
|
# the parser if not removed. |
|
|
|
|
# doxygen's preprocessor will remove all references to function-like macros |
|
|
|
|
# that are alone on a line, have an all uppercase name, and do not end with a |
|
|
|
|
# semicolon, because these will confuse the parser if not removed. |
|
|
|
|
|
|
|
|
|
SKIP_FUNCTION_MACROS = YES |
|
|
|
|
|
|
|
|
|
@ -1490,14 +1586,12 @@ HAVE_DOT = YES
|
|
|
|
|
|
|
|
|
|
DOT_NUM_THREADS = 0 |
|
|
|
|
|
|
|
|
|
# By default doxygen will write a font called FreeSans.ttf to the output |
|
|
|
|
# directory and reference it in all dot files that doxygen generates. This |
|
|
|
|
# font does not include all possible unicode characters however, so when you need |
|
|
|
|
# these (or just want a differently looking font) you can specify the font name |
|
|
|
|
# using DOT_FONTNAME. You need need to make 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 setting DOT_FONTPATH to the directory |
|
|
|
|
# containing the font. |
|
|
|
|
# By default doxygen will use the Helvetica font for all dot files that |
|
|
|
|
# doxygen generates. When you want a differently looking font 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 standard location or by setting |
|
|
|
|
# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the |
|
|
|
|
# directory containing the font. |
|
|
|
|
|
|
|
|
|
DOT_FONTNAME = FreeSans.ttf |
|
|
|
|
|
|
|
|
|
@ -1506,10 +1600,9 @@ DOT_FONTNAME = FreeSans.ttf
|
|
|
|
|
|
|
|
|
|
DOT_FONTSIZE = 8 |
|
|
|
|
|
|
|
|
|
# By default doxygen will tell dot to use the output directory to look for the |
|
|
|
|
# FreeSans.ttf font (which doxygen will put there itself). If you specify a |
|
|
|
|
# different font using DOT_FONTNAME you can set the path where dot |
|
|
|
|
# can find it using this tag. |
|
|
|
|
# By default doxygen will tell dot to use the Helvetica font. |
|
|
|
|
# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to |
|
|
|
|
# set the path where dot can find it. |
|
|
|
|
|
|
|
|
|
DOT_FONTPATH = |
|
|
|
|
|
|
|
|
|
@ -1586,11 +1679,22 @@ GRAPHICAL_HIERARCHY = YES
|
|
|
|
|
DIRECTORY_GRAPH = YES |
|
|
|
|
|
|
|
|
|
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images |
|
|
|
|
# generated by dot. Possible values are png, jpg, or gif. |
|
|
|
|
# If left blank png will be used. |
|
|
|
|
# generated by dot. Possible values are svg, png, jpg, or gif. |
|
|
|
|
# If left blank png will be used. 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). |
|
|
|
|
|
|
|
|
|
DOT_IMAGE_FORMAT = png |
|
|
|
|
|
|
|
|
|
# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to |
|
|
|
|
# enable generation of interactive SVG images that allow zooming and panning. |
|
|
|
|
# Note that this requires a modern browser other than Internet Explorer. |
|
|
|
|
# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you |
|
|
|
|
# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files |
|
|
|
|
# visible. Older versions of IE do not have SVG support. |
|
|
|
|
|
|
|
|
|
INTERACTIVE_SVG = NO |
|
|
|
|
|
|
|
|
|
# The tag DOT_PATH can be used to specify the path where the dot tool can be |
|
|
|
|
# found. If left blank, it is assumed the dot tool can be found in the path. |
|
|
|
|
|
|
|
|
|
|