|
@@ -1,14 +1,14 @@
|
|
-# Doxyfile 1.5.8
|
|
|
|
|
|
+# Doxyfile 1.7.3
|
|
|
|
|
|
# This file describes the settings to be used by the documentation system
|
|
# This file describes the settings to be used by the documentation system
|
|
-# doxygen (www.doxygen.org) for a project
|
|
|
|
|
|
+# doxygen (www.doxygen.org) for a project.
|
|
#
|
|
#
|
|
-# All text after a hash (#) is considered a comment and will be ignored
|
|
|
|
|
|
+# All text after a hash (#) is considered a comment and will be ignored.
|
|
# The format is:
|
|
# The format is:
|
|
# TAG = value [value, ...]
|
|
# TAG = value [value, ...]
|
|
# For lists items can also be appended using:
|
|
# For lists items can also be appended using:
|
|
# TAG += value [value, ...]
|
|
# TAG += value [value, ...]
|
|
-# Values that contain spaces should be placed between quotes (" ")
|
|
|
|
|
|
+# Values that contain spaces should be placed between quotes (" ").
|
|
|
|
|
|
#---------------------------------------------------------------------------
|
|
#---------------------------------------------------------------------------
|
|
# Project related configuration options
|
|
# Project related configuration options
|
|
@@ -33,6 +33,17 @@ PROJECT_NAME = @PROJECT_NAME@
|
|
|
|
|
|
PROJECT_NUMBER = @CTK_VERSION@
|
|
PROJECT_NUMBER = @CTK_VERSION@
|
|
|
|
|
|
|
|
+# 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 = The Common Toolkit is a community effort to provide support code for medical image analysis, surgical navigation, and related projects.
|
|
|
|
+
|
|
|
|
+# 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 = @CTK_SOURCE_DIR@/ctkLogo-small-transparent.png
|
|
|
|
+
|
|
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
|
|
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
|
|
# base path where the generated documentation will be put.
|
|
# base path where the generated documentation will be put.
|
|
# If a relative path is entered, it will be relative to the location
|
|
# If a relative path is entered, it will be relative to the location
|
|
@@ -54,11 +65,11 @@ CREATE_SUBDIRS = NO
|
|
# information to generate all constant output in the proper language.
|
|
# information to generate all constant output in the proper language.
|
|
# The default language is English, other supported languages are:
|
|
# The default language is English, other supported languages are:
|
|
# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
|
|
# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
|
|
-# Croatian, Czech, Danish, Dutch, 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, Slovene,
|
|
|
|
-# Spanish, Swedish, and Ukrainian.
|
|
|
|
|
|
+# 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-Cyrillic, Slovak,
|
|
|
|
+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
|
|
|
|
|
|
OUTPUT_LANGUAGE = English
|
|
OUTPUT_LANGUAGE = English
|
|
|
|
|
|
@@ -136,7 +147,7 @@ STRIP_FROM_PATH = @CTK_SOURCE_DIR@
|
|
STRIP_FROM_INC_PATH = @CTK_SOURCE_DIR@/
|
|
STRIP_FROM_INC_PATH = @CTK_SOURCE_DIR@/
|
|
|
|
|
|
# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
|
|
# 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
|
|
|
|
|
|
+# (but less readable) file names. This can be useful if your file system
|
|
# doesn't support long names like on DOS, Mac, or CD-ROM.
|
|
# doesn't support long names like on DOS, Mac, or CD-ROM.
|
|
|
|
|
|
SHORT_NAMES = NO
|
|
SHORT_NAMES = NO
|
|
@@ -217,14 +228,15 @@ OPTIMIZE_FOR_FORTRAN = NO
|
|
|
|
|
|
OPTIMIZE_OUTPUT_VHDL = NO
|
|
OPTIMIZE_OUTPUT_VHDL = 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, VHDL, C, C++. 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
|
|
|
|
|
|
+# 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, CSharp, C,
|
|
|
|
+# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. 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 that for custom extensions
|
|
|
|
+# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
|
|
|
|
|
|
EXTENSION_MAPPING =
|
|
EXTENSION_MAPPING =
|
|
|
|
|
|
@@ -232,7 +244,7 @@ EXTENSION_MAPPING =
|
|
# to include (a tag file for) the STL sources as input, then you should
|
|
# to include (a tag file for) the STL sources as input, then you should
|
|
# set this tag to YES in order to let doxygen match functions declarations and
|
|
# set this tag to YES in order to let doxygen match functions declarations and
|
|
# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
|
|
# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
|
|
-# func(std::string) {}). This also make the inheritance and collaboration
|
|
|
|
|
|
+# func(std::string) {}). This also makes the inheritance and collaboration
|
|
# diagrams that involve STL classes more complete and accurate.
|
|
# diagrams that involve STL classes more complete and accurate.
|
|
|
|
|
|
BUILTIN_STL_SUPPORT = NO
|
|
BUILTIN_STL_SUPPORT = NO
|
|
@@ -250,7 +262,7 @@ SIP_SUPPORT = NO
|
|
|
|
|
|
# For Microsoft's IDL there are propget and propput attributes to indicate getter
|
|
# For Microsoft's IDL there are propget and propput attributes to indicate getter
|
|
# and setter methods for a property. Setting this option to YES (the default)
|
|
# and setter methods for a property. Setting this option to YES (the default)
|
|
-# will make doxygen to replace the get and set methods by a property in the
|
|
|
|
|
|
+# will make doxygen replace the get and set methods by a property in the
|
|
# documentation. This will only work if the methods are indeed getting or
|
|
# documentation. This will only work if the methods are indeed getting or
|
|
# setting a simple type. If this is not the case, or you want to show the
|
|
# setting a simple type. If this is not the case, or you want to show the
|
|
# methods anyway, you should set this option to NO.
|
|
# methods anyway, you should set this option to NO.
|
|
@@ -288,10 +300,10 @@ TYPEDEF_HIDES_STRUCT = NO
|
|
# For small to medium size projects (<1000 input files) the default value is
|
|
# 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
|
|
# 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
|
|
# 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
|
|
# 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
|
|
# performance by keeping more symbols in memory. Note that the value works on
|
|
-# a logarithmic scale so increasing the size by one will rougly double the
|
|
|
|
|
|
+# a logarithmic scale so increasing the size by one will roughly double the
|
|
# memory usage. The cache size is given by this formula:
|
|
# memory usage. The cache size is given by this formula:
|
|
# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
|
|
# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
|
|
# corresponding to a cache size of 2^16 = 65536 symbols
|
|
# corresponding to a cache size of 2^16 = 65536 symbols
|
|
@@ -336,7 +348,7 @@ EXTRACT_LOCAL_METHODS = YES
|
|
# extracted and appear in the documentation as a namespace called
|
|
# extracted and appear in the documentation as a namespace called
|
|
# 'anonymous_namespace{file}', where file will be replaced with the base
|
|
# 'anonymous_namespace{file}', where file will be replaced with the base
|
|
# name of the file that contains the anonymous namespace. By default
|
|
# name of the file that contains the anonymous namespace. By default
|
|
-# anonymous namespace are hidden.
|
|
|
|
|
|
+# anonymous namespaces are hidden.
|
|
|
|
|
|
EXTRACT_ANON_NSPACES = NO
|
|
EXTRACT_ANON_NSPACES = NO
|
|
|
|
|
|
@@ -396,6 +408,12 @@ HIDE_SCOPE_NAMES = NO
|
|
|
|
|
|
SHOW_INCLUDE_FILES = YES
|
|
SHOW_INCLUDE_FILES = YES
|
|
|
|
|
|
|
|
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
|
|
|
|
+# will list include files with double quotes in the documentation
|
|
|
|
+# rather than with sharp brackets.
|
|
|
|
+
|
|
|
|
+FORCE_LOCAL_INCLUDES = NO
|
|
|
|
+
|
|
# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
|
|
# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
|
|
# is inserted in the documentation for inline members.
|
|
# is inserted in the documentation for inline members.
|
|
|
|
|
|
@@ -415,6 +433,16 @@ SORT_MEMBER_DOCS = YES
|
|
|
|
|
|
SORT_BRIEF_DOCS = YES
|
|
SORT_BRIEF_DOCS = YES
|
|
|
|
|
|
|
|
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
|
|
|
|
+# will sort the (brief and detailed) documentation of class members so that
|
|
|
|
+# constructors and destructors are listed first. If set to NO (the default)
|
|
|
|
+# the constructors will appear in the respective orders defined by
|
|
|
|
+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
|
|
|
|
+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
|
|
|
|
+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
|
|
|
|
+
|
|
|
|
+SORT_MEMBERS_CTORS_1ST = NO
|
|
|
|
+
|
|
# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
|
|
# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
|
|
# hierarchy of group names into alphabetical order. If set to NO (the default)
|
|
# hierarchy of group names into alphabetical order. If set to NO (the default)
|
|
# the group names will appear in their defined order.
|
|
# the group names will appear in their defined order.
|
|
@@ -431,6 +459,12 @@ SORT_GROUP_NAMES = NO
|
|
|
|
|
|
SORT_BY_SCOPE_NAME = 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
|
|
# The GENERATE_TODOLIST tag can be used to enable (YES) or
|
|
# disable (NO) the todo list. This list is created by putting \todo
|
|
# disable (NO) the todo list. This list is created by putting \todo
|
|
# commands in the documentation.
|
|
# commands in the documentation.
|
|
@@ -461,10 +495,10 @@ GENERATE_DEPRECATEDLIST= YES
|
|
ENABLED_SECTIONS =
|
|
ENABLED_SECTIONS =
|
|
|
|
|
|
# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
|
|
# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
|
|
-# the initial value of a variable or define consists of for it to appear in
|
|
|
|
|
|
+# the initial value of a variable or macro consists of for it to appear in
|
|
# the documentation. If the initializer consists of more lines than specified
|
|
# the documentation. If the initializer consists of more lines than specified
|
|
# here it will be hidden. Use a value of 0 to hide initializers completely.
|
|
# here it will be hidden. Use a value of 0 to hide initializers completely.
|
|
-# The appearance of the initializer of individual variables and defines in the
|
|
|
|
|
|
+# The appearance of the initializer of individual variables and macros in the
|
|
# documentation can be controlled using \showinitializer or \hideinitializer
|
|
# documentation can be controlled using \showinitializer or \hideinitializer
|
|
# command in the documentation regardless of this setting.
|
|
# command in the documentation regardless of this setting.
|
|
|
|
|
|
@@ -489,7 +523,8 @@ SHOW_DIRECTORIES = YES
|
|
SHOW_FILES = YES
|
|
SHOW_FILES = YES
|
|
|
|
|
|
# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
|
|
# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
|
|
-# Namespaces page. This will remove the Namespaces entry from the Quick Index
|
|
|
|
|
|
+# Namespaces page.
|
|
|
|
+# This will remove the Namespaces entry from the Quick Index
|
|
# and from the Folder Tree View (if specified). The default is YES.
|
|
# and from the Folder Tree View (if specified). The default is YES.
|
|
|
|
|
|
SHOW_NAMESPACES = YES
|
|
SHOW_NAMESPACES = YES
|
|
@@ -504,12 +539,12 @@ SHOW_NAMESPACES = YES
|
|
|
|
|
|
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 output files
|
|
|
|
-# in an output format independent way. The create the layout file that represents
|
|
|
|
-# doxygen's defaults, run doxygen with the -l option. You can optionally specify a
|
|
|
|
-# file name after the option, if omitted DoxygenLayout.xml will be used as the name
|
|
|
|
-# of the layout file.
|
|
|
|
|
|
+# 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
|
|
|
|
+# output files in an output format independent way. The create the layout file
|
|
|
|
+# that represents doxygen's defaults, run doxygen with the -l option.
|
|
|
|
+# You can optionally specify a file name after the option, if omitted
|
|
|
|
+# DoxygenLayout.xml will be used as the name of the layout file.
|
|
|
|
|
|
LAYOUT_FILE =
|
|
LAYOUT_FILE =
|
|
|
|
|
|
@@ -541,7 +576,7 @@ WARN_IF_UNDOCUMENTED = YES
|
|
|
|
|
|
WARN_IF_DOC_ERROR = YES
|
|
WARN_IF_DOC_ERROR = YES
|
|
|
|
|
|
-# This WARN_NO_PARAMDOC option can be abled to get warnings for
|
|
|
|
|
|
+# The WARN_NO_PARAMDOC option can be enabled to get warnings for
|
|
# functions that are documented, but have no documentation for their parameters
|
|
# functions that are documented, but have no documentation for their parameters
|
|
# or return value. If set to NO (the default) doxygen will only warn about
|
|
# or return value. If set to NO (the default) doxygen will only warn about
|
|
# wrong or incomplete parameter documentation, but not about the absence of
|
|
# wrong or incomplete parameter documentation, but not about the absence of
|
|
@@ -587,8 +622,9 @@ INPUT_ENCODING = UTF-8
|
|
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
|
|
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
|
|
# and *.h) to filter out the source-files in the directories. If left
|
|
# and *.h) to filter out the source-files in the directories. If left
|
|
# blank the following patterns are tested:
|
|
# blank the following patterns are tested:
|
|
-# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
|
|
|
|
-# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
|
|
|
|
|
|
+# *.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 *.for *.vhd *.vhdl
|
|
|
|
|
|
FILE_PATTERNS = *.c \
|
|
FILE_PATTERNS = *.c \
|
|
*.cc \
|
|
*.cc \
|
|
@@ -664,7 +700,7 @@ EXCLUDE = @CTK_BINARY_DIR@ \
|
|
@CTK_SOURCE_DIR@/Utilities
|
|
@CTK_SOURCE_DIR@/Utilities
|
|
|
|
|
|
# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
|
|
# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
|
|
-# directories that are symbolic links (a Unix filesystem feature) are excluded
|
|
|
|
|
|
+# directories that are symbolic links (a Unix file system feature) are excluded
|
|
# from the input.
|
|
# from the input.
|
|
|
|
|
|
EXCLUDE_SYMLINKS = NO
|
|
EXCLUDE_SYMLINKS = NO
|
|
@@ -696,7 +732,7 @@ EXCLUDE_SYMBOLS =
|
|
# directories that contain example code fragments that are included (see
|
|
# directories that contain example code fragments that are included (see
|
|
# the \include command).
|
|
# the \include command).
|
|
|
|
|
|
-EXAMPLE_PATH =
|
|
|
|
|
|
+EXAMPLE_PATH =
|
|
|
|
|
|
# If the value of the EXAMPLE_PATH tag contains directories, you can use the
|
|
# 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
|
|
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
|
|
@@ -716,24 +752,27 @@ EXAMPLE_RECURSIVE = YES
|
|
# directories that contain image that are included in the documentation (see
|
|
# directories that contain image that are included in the documentation (see
|
|
# the \image command).
|
|
# the \image command).
|
|
|
|
|
|
-IMAGE_PATH =
|
|
|
|
|
|
+IMAGE_PATH =
|
|
|
|
|
|
# The INPUT_FILTER tag can be used to specify a program that doxygen should
|
|
# 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
|
|
# invoke to filter for each input file. Doxygen will invoke the filter program
|
|
# by executing (via popen()) the command <filter> <input-file>, where <filter>
|
|
# by executing (via popen()) the command <filter> <input-file>, where <filter>
|
|
# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
|
|
# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
|
|
# input file. Doxygen will then use the output that the filter program writes
|
|
# input file. Doxygen will then use the output that the filter program writes
|
|
-# to standard output. If FILTER_PATTERNS is specified, this tag will be
|
|
|
|
|
|
+# to standard output.
|
|
|
|
+# If FILTER_PATTERNS is specified, this tag will be
|
|
# ignored.
|
|
# ignored.
|
|
|
|
|
|
INPUT_FILTER =
|
|
INPUT_FILTER =
|
|
|
|
|
|
# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
|
|
# 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
|
|
|
|
-# filter if there is a match. The filters are a list of the form:
|
|
|
|
|
|
+# basis.
|
|
|
|
+# Doxygen will compare the file name with each pattern and apply the
|
|
|
|
+# 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
|
|
# 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 =
|
|
FILTER_PATTERNS =
|
|
|
|
|
|
@@ -743,6 +782,14 @@ FILTER_PATTERNS =
|
|
|
|
|
|
FILTER_SOURCE_FILES = NO
|
|
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
|
|
# configuration options related to source browsing
|
|
#---------------------------------------------------------------------------
|
|
#---------------------------------------------------------------------------
|
|
@@ -780,7 +827,8 @@ REFERENCES_RELATION = NO
|
|
# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
|
|
# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
|
|
# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
|
|
# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
|
|
# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
|
|
# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
|
|
-# link to the source code. Otherwise they will link to the documentation.
|
|
|
|
|
|
+# link to the source code.
|
|
|
|
+# Otherwise they will link to the documentation.
|
|
|
|
|
|
REFERENCES_LINK_SOURCE = YES
|
|
REFERENCES_LINK_SOURCE = YES
|
|
|
|
|
|
@@ -861,7 +909,38 @@ HTML_FOOTER =
|
|
# the style sheet file to the HTML output directory, so don't put your own
|
|
# the style sheet file to the HTML output directory, so don't put your own
|
|
# stylesheet in the HTML output directory as well, or it will be erased!
|
|
# stylesheet in the HTML output directory as well, or it will be erased!
|
|
|
|
|
|
-HTML_STYLESHEET =
|
|
|
|
|
|
+HTML_STYLESHEET =
|
|
|
|
+
|
|
|
|
+# 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,
|
|
|
|
+# see http://en.wikipedia.org/wiki/Hue for more information.
|
|
|
|
+# For instance the value 0 represents red, 60 is yellow, 120 is green,
|
|
|
|
+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
|
|
|
|
+# The allowed range is 0 to 359.
|
|
|
|
+
|
|
|
|
+HTML_COLORSTYLE_HUE = 220
|
|
|
|
+
|
|
|
|
+# 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 value of 255 will produce the most vivid colors.
|
|
|
|
+
|
|
|
|
+HTML_COLORSTYLE_SAT = 100
|
|
|
|
+
|
|
|
|
+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
|
|
|
|
+# the luminance component of the colors in the HTML output. Values below
|
|
|
|
+# 100 gradually make the output lighter, whereas values above 100 make
|
|
|
|
+# the output darker. The value divided by 100 is the actual gamma applied,
|
|
|
|
+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
|
|
|
|
+# and 100 does not change the gamma.
|
|
|
|
+
|
|
|
|
+HTML_COLORSTYLE_GAMMA = 80
|
|
|
|
+
|
|
|
|
+# 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 NO can help when comparing the output of multiple runs.
|
|
|
|
+
|
|
|
|
+HTML_TIMESTAMP = YES
|
|
|
|
|
|
# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
|
|
# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
|
|
# files or namespaces will be aligned in HTML using tables. If set to
|
|
# files or namespaces will be aligned in HTML using tables. If set to
|
|
@@ -885,7 +964,8 @@ HTML_DYNAMIC_SECTIONS = NO
|
|
# directory and running "make install" will install the docset in
|
|
# directory and running "make install" will install the docset in
|
|
# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
|
|
# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
|
|
# it at startup.
|
|
# it at startup.
|
|
-# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.
|
|
|
|
|
|
+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
|
|
|
|
+# for more information.
|
|
|
|
|
|
GENERATE_DOCSET = NO
|
|
GENERATE_DOCSET = NO
|
|
|
|
|
|
@@ -903,6 +983,16 @@ DOCSET_FEEDNAME = "Doxygen generated docs"
|
|
|
|
|
|
DOCSET_BUNDLE_ID = org.doxygen.Project
|
|
DOCSET_BUNDLE_ID = org.doxygen.Project
|
|
|
|
|
|
|
|
+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
|
|
|
|
+# the documentation publisher. This should be a reverse domain-name style
|
|
|
|
+# string, e.g. com.mycompany.MyDocSet.documentation.
|
|
|
|
+
|
|
|
|
+DOCSET_PUBLISHER_ID = org.doxygen.Publisher
|
|
|
|
+
|
|
|
|
+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
|
|
|
|
+
|
|
|
|
+DOCSET_PUBLISHER_NAME = Publisher
|
|
|
|
+
|
|
# If the GENERATE_HTMLHELP tag is set to YES, additional index files
|
|
# If the GENERATE_HTMLHELP tag is set to YES, additional index files
|
|
# will be generated that can be used as input for tools like the
|
|
# will be generated that can be used as input for tools like the
|
|
# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
|
|
# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
|
|
@@ -947,10 +1037,10 @@ BINARY_TOC = NO
|
|
|
|
|
|
TOC_EXPAND = NO
|
|
TOC_EXPAND = NO
|
|
|
|
|
|
-# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER
|
|
|
|
-# are set, an additional index file will be generated that can be used as input for
|
|
|
|
-# Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated
|
|
|
|
-# HTML documentation.
|
|
|
|
|
|
+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
|
|
|
|
+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
|
|
|
|
+# that can be used as input for Qt's qhelpgenerator to generate a
|
|
|
|
+# Qt Compressed Help (.qch) of the generated HTML documentation.
|
|
|
|
|
|
GENERATE_QHP = NO
|
|
GENERATE_QHP = NO
|
|
|
|
|
|
@@ -972,20 +1062,24 @@ QHP_NAMESPACE = org.doxygen.Project
|
|
|
|
|
|
QHP_VIRTUAL_FOLDER = doc
|
|
QHP_VIRTUAL_FOLDER = doc
|
|
|
|
|
|
-# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add.
|
|
|
|
-# For more information please see
|
|
|
|
|
|
+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
|
|
|
|
+# add. For more information please see
|
|
# http://doc.trolltech.com/qthelpproject.html#custom-filters
|
|
# http://doc.trolltech.com/qthelpproject.html#custom-filters
|
|
|
|
|
|
QHP_CUST_FILTER_NAME =
|
|
QHP_CUST_FILTER_NAME =
|
|
|
|
|
|
-# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see
|
|
|
|
-# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.
|
|
|
|
|
|
+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
|
|
|
|
+# custom filter to add. For more information please see
|
|
|
|
+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
|
|
|
|
+# Qt Help Project / Custom Filters</a>.
|
|
|
|
|
|
QHP_CUST_FILTER_ATTRS =
|
|
QHP_CUST_FILTER_ATTRS =
|
|
|
|
|
|
-# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's
|
|
|
|
|
|
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
|
|
|
|
+# project's
|
|
# filter section matches.
|
|
# filter section matches.
|
|
-# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.
|
|
|
|
|
|
+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
|
|
|
|
+# Qt Help Project / Filter Attributes</a>.
|
|
|
|
|
|
QHP_SECT_FILTER_ATTRS =
|
|
QHP_SECT_FILTER_ATTRS =
|
|
|
|
|
|
@@ -996,40 +1090,61 @@ QHP_SECT_FILTER_ATTRS =
|
|
|
|
|
|
QHG_LOCATION =
|
|
QHG_LOCATION =
|
|
|
|
|
|
|
|
+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
|
|
|
|
+# will be generated, which together with the HTML files, form an Eclipse help
|
|
|
|
+# plugin. To install this plugin and make it available under the help contents
|
|
|
|
+# menu in Eclipse, the contents of the directory containing the HTML and XML
|
|
|
|
+# files needs to be copied into the plugins directory of eclipse. The name of
|
|
|
|
+# the directory within the plugins directory should be the same as
|
|
|
|
+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
|
|
|
|
+# the help appears.
|
|
|
|
+
|
|
|
|
+GENERATE_ECLIPSEHELP = NO
|
|
|
|
+
|
|
|
|
+# A unique identifier for the eclipse help plugin. When installing the plugin
|
|
|
|
+# the directory name containing the HTML and XML files should also have
|
|
|
|
+# this name.
|
|
|
|
+
|
|
|
|
+ECLIPSE_DOC_ID = org.doxygen.Project
|
|
|
|
+
|
|
# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
|
|
# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
|
|
# top of each HTML page. The value NO (the default) enables the index and
|
|
# top of each HTML page. The value NO (the default) enables the index and
|
|
# the value YES disables it.
|
|
# the value YES disables it.
|
|
|
|
|
|
DISABLE_INDEX = NO
|
|
DISABLE_INDEX = NO
|
|
|
|
|
|
-# This tag can be used to set the number of enum values (range [1..20])
|
|
|
|
|
|
+# 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.
|
|
# 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
|
|
ENUM_VALUES_PER_LINE = 4
|
|
|
|
|
|
# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
|
|
# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
|
|
# structure should be generated to display hierarchical information.
|
|
# structure should be generated to display hierarchical information.
|
|
-# If the tag value is set to FRAME, a side panel will be generated
|
|
|
|
|
|
+# If the tag value is set to YES, a side panel will be generated
|
|
# containing a tree-like index structure (just like the one that
|
|
# containing a tree-like index structure (just like the one that
|
|
# is generated for HTML Help). For this to work a browser that supports
|
|
# is generated for HTML Help). For this to work a browser that supports
|
|
-# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
|
|
|
|
-# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
|
|
|
|
-# probably better off using the HTML help feature. Other possible values
|
|
|
|
-# for this tag are: HIERARCHIES, which will generate the Groups, Directories,
|
|
|
|
-# and Class Hierarchy pages using a tree view instead of an ordered list;
|
|
|
|
-# ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which
|
|
|
|
-# disables this behavior completely. For backwards compatibility with previous
|
|
|
|
-# releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE
|
|
|
|
-# respectively.
|
|
|
|
|
|
+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
|
|
|
|
+# Windows users are probably better off using the HTML help feature.
|
|
|
|
|
|
GENERATE_TREEVIEW = NONE
|
|
GENERATE_TREEVIEW = NONE
|
|
|
|
|
|
|
|
+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
|
|
|
|
+# and Class Hierarchy pages using a tree view instead of an ordered list.
|
|
|
|
+
|
|
|
|
+USE_INLINE_TREES = NO
|
|
|
|
+
|
|
# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
|
|
# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
|
|
# used to set the initial width (in pixels) of the frame in which the tree
|
|
# used to set the initial width (in pixels) of the frame in which the tree
|
|
# is shown.
|
|
# is shown.
|
|
|
|
|
|
TREEVIEW_WIDTH = 250
|
|
TREEVIEW_WIDTH = 250
|
|
|
|
|
|
|
|
+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
|
|
|
|
+# links to external symbols imported via tag files in a separate window.
|
|
|
|
+
|
|
|
|
+EXT_LINKS_IN_WINDOW = NO
|
|
|
|
+
|
|
# Use this tag to change the font size of Latex formulas included
|
|
# Use this tag to change the font size of Latex formulas included
|
|
# as images in the HTML documentation. The default is 10. Note that
|
|
# as images in the HTML documentation. The default is 10. Note that
|
|
# when you change the font size after a successful doxygen run you need
|
|
# when you change the font size after a successful doxygen run you need
|
|
@@ -1038,6 +1153,53 @@ TREEVIEW_WIDTH = 250
|
|
|
|
|
|
FORMULA_FONTSIZE = 10
|
|
FORMULA_FONTSIZE = 10
|
|
|
|
|
|
|
|
+# Use the FORMULA_TRANPARENT tag to determine whether or not the images
|
|
|
|
+# generated for formulas are transparent PNGs. Transparent PNGs are
|
|
|
|
+# not supported properly for IE 6.0, but are supported on all modern browsers.
|
|
|
|
+# Note that when changing this option you need to delete any form_*.png files
|
|
|
|
+# in the HTML output before the changes have effect.
|
|
|
|
+
|
|
|
|
+FORMULA_TRANSPARENT = YES
|
|
|
|
+
|
|
|
|
+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
|
|
|
|
+# (see http://www.mathjax.org) which uses client side Javascript for the
|
|
|
|
+# rendering instead of using prerendered bitmaps. Use this if you do not
|
|
|
|
+# have LaTeX installed or if you want to formulas look prettier in the HTML
|
|
|
|
+# output. When enabled you also need to install MathJax separately and
|
|
|
|
+# configure the path to it using the MATHJAX_RELPATH option.
|
|
|
|
+
|
|
|
|
+USE_MATHJAX = NO
|
|
|
|
+
|
|
|
|
+# When MathJax is enabled you need to specify the location relative to the
|
|
|
|
+# 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, but it is strongly recommended to install a local copy of MathJax
|
|
|
|
+# before deployment.
|
|
|
|
+
|
|
|
|
+MATHJAX_RELPATH = http://www.mathjax.org/mathjax
|
|
|
|
+
|
|
|
|
+# 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
|
|
|
|
+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
|
|
|
|
+# (GENERATE_DOCSET) there is already a search function so this one should
|
|
|
|
+# typically be disabled. For large projects the javascript based search engine
|
|
|
|
+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
|
|
|
|
+
|
|
|
|
+SEARCHENGINE = YES
|
|
|
|
+
|
|
|
|
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
|
|
|
|
+# implemented using a PHP enabled web server instead of at the web client
|
|
|
|
+# using Javascript. Doxygen will generate the search PHP script and index
|
|
|
|
+# file to put on the web server. The advantage of the server
|
|
|
|
+# based approach is that it scales better to large projects and allows
|
|
|
|
+# full text search. The disadvantages are that it is more difficult to setup
|
|
|
|
+# and does not have live searching capabilities.
|
|
|
|
+
|
|
|
|
+SERVER_BASED_SEARCH = NO
|
|
|
|
+
|
|
#---------------------------------------------------------------------------
|
|
#---------------------------------------------------------------------------
|
|
# configuration options related to the LaTeX output
|
|
# configuration options related to the LaTeX output
|
|
#---------------------------------------------------------------------------
|
|
#---------------------------------------------------------------------------
|
|
@@ -1055,6 +1217,9 @@ LATEX_OUTPUT = latex
|
|
|
|
|
|
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
|
|
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
|
|
# invoked. If left blank `latex' will be used as the default command name.
|
|
# invoked. If left blank `latex' will be used as the default command name.
|
|
|
|
+# 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.
|
|
|
|
|
|
LATEX_CMD_NAME = latex
|
|
LATEX_CMD_NAME = latex
|
|
|
|
|
|
@@ -1071,7 +1236,7 @@ MAKEINDEX_CMD_NAME = makeindex
|
|
COMPACT_LATEX = NO
|
|
COMPACT_LATEX = NO
|
|
|
|
|
|
# The PAPER_TYPE tag can be used to set the paper type that is used
|
|
# The PAPER_TYPE tag can be used to set the paper type that is used
|
|
-# by the printer. Possible values are: a4, a4wide, letter, legal and
|
|
|
|
|
|
+# by the printer. Possible values are: a4, letter, legal and
|
|
# executive. If left blank a4wide will be used.
|
|
# executive. If left blank a4wide will be used.
|
|
|
|
|
|
PAPER_TYPE = a4wide
|
|
PAPER_TYPE = a4wide
|
|
@@ -1114,6 +1279,13 @@ LATEX_BATCHMODE = NO
|
|
|
|
|
|
LATEX_HIDE_INDICES = NO
|
|
LATEX_HIDE_INDICES = NO
|
|
|
|
|
|
|
|
+# If LATEX_SOURCE_CODE is set to YES then doxygen will include
|
|
|
|
+# source code with syntax highlighting in the LaTeX output.
|
|
|
|
+# Note that which sources are shown also depends on other settings
|
|
|
|
+# such as SOURCE_BROWSER.
|
|
|
|
+
|
|
|
|
+LATEX_SOURCE_CODE = NO
|
|
|
|
+
|
|
#---------------------------------------------------------------------------
|
|
#---------------------------------------------------------------------------
|
|
# configuration options related to the RTF output
|
|
# configuration options related to the RTF output
|
|
#---------------------------------------------------------------------------
|
|
#---------------------------------------------------------------------------
|
|
@@ -1250,8 +1422,10 @@ GENERATE_PERLMOD = NO
|
|
PERLMOD_LATEX = NO
|
|
PERLMOD_LATEX = NO
|
|
|
|
|
|
# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
|
|
# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
|
|
-# nicely formatted so it can be parsed by a human reader. This is useful
|
|
|
|
-# if you want to understand what is going on. On the other hand, if this
|
|
|
|
|
|
+# nicely formatted so it can be parsed by a human reader.
|
|
|
|
+# This is useful
|
|
|
|
+# if you want to understand what is going on.
|
|
|
|
+# On the other hand, if this
|
|
# tag is set to NO the size of the Perl module output will be much smaller
|
|
# tag is set to NO the size of the Perl module output will be much smaller
|
|
# and Perl will parse it just the same.
|
|
# and Perl will parse it just the same.
|
|
|
|
|
|
@@ -1318,15 +1492,14 @@ PREDEFINED = DOXYGEN_SHOULD_SKIP_THIS
|
|
# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
|
|
# 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.
|
|
# 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.
|
|
# 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 =
|
|
EXPAND_AS_DEFINED =
|
|
|
|
|
|
# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
|
|
# 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
|
|
SKIP_FUNCTION_MACROS = YES
|
|
|
|
|
|
@@ -1338,9 +1511,11 @@ SKIP_FUNCTION_MACROS = YES
|
|
# Optionally an initial location of the external documentation
|
|
# Optionally an initial location of the external documentation
|
|
# can be added for each tagfile. The format of a tag file without
|
|
# can be added for each tagfile. The format of a tag file without
|
|
# this location is as follows:
|
|
# this location is as follows:
|
|
-# TAGFILES = file1 file2 ...
|
|
|
|
|
|
+#
|
|
|
|
+# TAGFILES = file1 file2 ...
|
|
# Adding location for the tag files is done as follows:
|
|
# Adding location for the tag files is done as follows:
|
|
-# TAGFILES = file1=loc1 "file2 = loc2" ...
|
|
|
|
|
|
+#
|
|
|
|
+# TAGFILES = file1=loc1 "file2 = loc2" ...
|
|
# where "loc1" and "loc2" can be relative or absolute paths or
|
|
# where "loc1" and "loc2" can be relative or absolute paths or
|
|
# URLs. If a location is present for each tag, the installdox tool
|
|
# URLs. If a location is present for each tag, the installdox tool
|
|
# does not have to be run to correct the links.
|
|
# does not have to be run to correct the links.
|
|
@@ -1351,7 +1526,6 @@ SKIP_FUNCTION_MACROS = YES
|
|
|
|
|
|
TAGFILES =
|
|
TAGFILES =
|
|
|
|
|
|
-#
|
|
|
|
# When a file name is specified after GENERATE_TAGFILE, doxygen will create
|
|
# When a file name is specified after GENERATE_TAGFILE, doxygen will create
|
|
# a tag file that is based on the input files it reads.
|
|
# a tag file that is based on the input files it reads.
|
|
|
|
|
|
@@ -1381,9 +1555,8 @@ PERL_PATH = /usr/bin/perl
|
|
# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
|
|
# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
|
|
# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
|
|
# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
|
|
# or super classes. Setting the tag to NO turns the diagrams off. Note that
|
|
# or super classes. Setting the tag to NO turns the diagrams off. Note that
|
|
-# this option is superseded by the HAVE_DOT option below. This is only a
|
|
|
|
-# fallback. It is recommended to install and use dot, since it yields more
|
|
|
|
-# powerful graphs.
|
|
|
|
|
|
+# this option also works with HAVE_DOT disabled, but it is recommended to
|
|
|
|
+# install and use dot, since it yields more powerful graphs.
|
|
|
|
|
|
CLASS_DIAGRAMS = YES
|
|
CLASS_DIAGRAMS = YES
|
|
|
|
|
|
@@ -1409,11 +1582,20 @@ HIDE_UNDOC_RELATIONS = YES
|
|
|
|
|
|
HAVE_DOT = YES
|
|
HAVE_DOT = YES
|
|
|
|
|
|
-# 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,
|
|
|
|
|
|
+# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is
|
|
|
|
+# allowed to run in parallel. When set to 0 (the default) doxygen will
|
|
|
|
+# base this on the number of processors available in the system. You can set it
|
|
|
|
+# explicitly to a value larger than 0 to get control over the balance
|
|
|
|
+# between CPU load and processing speed.
|
|
|
|
+
|
|
|
|
+# Note: Specify 1 to avoid crash with doxygen 1.7.3
|
|
|
|
+
|
|
|
|
+DOT_NUM_THREADS = 1
|
|
|
|
+
|
|
|
|
+# By default doxygen will write a font called Helvetica to the output
|
|
|
|
+# directory and reference it in 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
|
|
# 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
|
|
# DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
|
|
# containing the font.
|
|
# containing the font.
|
|
@@ -1493,7 +1675,7 @@ CALL_GRAPH = NO
|
|
CALLER_GRAPH = NO
|
|
CALLER_GRAPH = NO
|
|
|
|
|
|
# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
|
|
# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
|
|
-# will graphical hierarchy of all classes instead of a textual one.
|
|
|
|
|
|
+# will generate a graphical hierarchy of all classes instead of a textual one.
|
|
|
|
|
|
GRAPHICAL_HIERARCHY = YES
|
|
GRAPHICAL_HIERARCHY = YES
|
|
|
|
|
|
@@ -1505,7 +1687,7 @@ GRAPHICAL_HIERARCHY = YES
|
|
DIRECTORY_GRAPH = YES
|
|
DIRECTORY_GRAPH = YES
|
|
|
|
|
|
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
|
|
# 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
|
|
|
|
|
|
+# generated by dot. Possible values are png, svg, gif or svg.
|
|
# If left blank png will be used.
|
|
# If left blank png will be used.
|
|
|
|
|
|
DOT_IMAGE_FORMAT = png
|
|
DOT_IMAGE_FORMAT = png
|
|
@@ -1521,6 +1703,12 @@ DOT_PATH =
|
|
|
|
|
|
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 =
|
|
|
|
+
|
|
# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
|
|
# 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
|
|
# nodes that will be shown in the graph. If the number of nodes in a graph
|
|
# becomes larger than this value, doxygen will truncate the graph, which is
|
|
# becomes larger than this value, doxygen will truncate the graph, which is
|
|
@@ -1567,12 +1755,3 @@ GENERATE_LEGEND = YES
|
|
# the various graphs.
|
|
# the various graphs.
|
|
|
|
|
|
DOT_CLEANUP = YES
|
|
DOT_CLEANUP = YES
|
|
-
|
|
|
|
-#---------------------------------------------------------------------------
|
|
|
|
-# Options related to the search engine
|
|
|
|
-#---------------------------------------------------------------------------
|
|
|
|
-
|
|
|
|
-# The SEARCHENGINE tag specifies whether or not a search engine should be
|
|
|
|
-# used. If set to NO the values of all tags below this one will be ignored.
|
|
|
|
-
|
|
|
|
-SEARCHENGINE = YES
|
|
|