You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1154 lines
41 KiB
Plaintext
1154 lines
41 KiB
Plaintext
# Doxyfile 1.7.6.1
|
|
|
|
# This file describes the settings to be used by the documentation system
|
|
# doxygen (www.doxygen.org) for a project.
|
|
#
|
|
# All text after a hash (#) is considered a comment and will be ignored.
|
|
# The format is:
|
|
# TAG = value [value, ...]
|
|
# For lists items can also be appended using:
|
|
# TAG += value [value, ...]
|
|
# Values that contain spaces should be placed between quotes (" ").
|
|
|
|
#---------------------------------------------------------------------------
|
|
# Project related configuration options
|
|
#---------------------------------------------------------------------------
|
|
|
|
DOXYFILE_ENCODING = UTF-8
|
|
|
|
PROJECT_NAME = "libIEC61850"
|
|
|
|
PROJECT_NUMBER = 0.9.1
|
|
|
|
PROJECT_BRIEF = "Open-source IEC 61850 MMS/GOOSE server and client library"
|
|
|
|
# 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
|
|
# where doxygen was started. If left blank the current directory will be used.
|
|
|
|
OUTPUT_DIRECTORY = ../doxydoc
|
|
|
|
CREATE_SUBDIRS = NO
|
|
|
|
OUTPUT_LANGUAGE = English
|
|
|
|
BRIEF_MEMBER_DESC = YES
|
|
|
|
REPEAT_BRIEF = YES
|
|
|
|
ABBREVIATE_BRIEF =
|
|
|
|
ALWAYS_DETAILED_SEC = NO
|
|
|
|
INLINE_INHERITED_MEMB = NO
|
|
|
|
FULL_PATH_NAMES = YES
|
|
|
|
STRIP_FROM_PATH =
|
|
|
|
STRIP_FROM_INC_PATH =
|
|
|
|
SHORT_NAMES = NO
|
|
|
|
JAVADOC_AUTOBRIEF = NO
|
|
|
|
QT_AUTOBRIEF = NO
|
|
|
|
MULTILINE_CPP_IS_BRIEF = NO
|
|
|
|
INHERIT_DOCS = YES
|
|
|
|
SEPARATE_MEMBER_PAGES = NO
|
|
|
|
TAB_SIZE = 8
|
|
|
|
ALIASES =
|
|
|
|
TCL_SUBST =
|
|
|
|
OPTIMIZE_OUTPUT_FOR_C = YES.
|
|
|
|
OPTIMIZE_OUTPUT_JAVA = NO
|
|
|
|
OPTIMIZE_FOR_FORTRAN = NO
|
|
|
|
OPTIMIZE_OUTPUT_VHDL = NO
|
|
|
|
EXTENSION_MAPPING =
|
|
|
|
BUILTIN_STL_SUPPORT = NO
|
|
|
|
CPP_CLI_SUPPORT = NO
|
|
|
|
SIP_SUPPORT = NO
|
|
|
|
IDL_PROPERTY_SUPPORT = YES
|
|
|
|
DISTRIBUTE_GROUP_DOC = NO
|
|
|
|
SUBGROUPING = YES
|
|
|
|
INLINE_GROUPED_CLASSES = NO
|
|
|
|
INLINE_SIMPLE_STRUCTS = NO
|
|
|
|
TYPEDEF_HIDES_STRUCT = YES
|
|
|
|
SYMBOL_CACHE_SIZE = 0
|
|
|
|
LOOKUP_CACHE_SIZE = 0
|
|
|
|
#---------------------------------------------------------------------------
|
|
# Build related configuration options
|
|
#---------------------------------------------------------------------------
|
|
|
|
EXTRACT_ALL = YES
|
|
|
|
EXTRACT_PRIVATE = NO
|
|
|
|
EXTRACT_STATIC = NO
|
|
|
|
EXTRACT_LOCAL_CLASSES = YES
|
|
|
|
EXTRACT_LOCAL_METHODS = NO
|
|
|
|
EXTRACT_ANON_NSPACES = NO
|
|
|
|
HIDE_UNDOC_MEMBERS = NO
|
|
|
|
HIDE_UNDOC_CLASSES = NO
|
|
|
|
HIDE_FRIEND_COMPOUNDS = NO
|
|
|
|
HIDE_IN_BODY_DOCS = NO
|
|
|
|
INTERNAL_DOCS = NO
|
|
|
|
CASE_SENSE_NAMES = YES
|
|
|
|
HIDE_SCOPE_NAMES = NO
|
|
|
|
SHOW_INCLUDE_FILES = YES
|
|
|
|
FORCE_LOCAL_INCLUDES = NO
|
|
|
|
INLINE_INFO = YES
|
|
|
|
SORT_MEMBER_DOCS = YES
|
|
|
|
SORT_BRIEF_DOCS = NO
|
|
|
|
SORT_MEMBERS_CTORS_1ST = NO
|
|
|
|
SORT_GROUP_NAMES = NO
|
|
|
|
SORT_BY_SCOPE_NAME = NO
|
|
|
|
STRICT_PROTO_MATCHING = NO
|
|
|
|
GENERATE_TODOLIST = YES
|
|
|
|
GENERATE_TESTLIST = YES
|
|
|
|
GENERATE_BUGLIST = YES
|
|
|
|
GENERATE_DEPRECATEDLIST= YES
|
|
|
|
ENABLED_SECTIONS =
|
|
|
|
MAX_INITIALIZER_LINES = 30
|
|
|
|
SHOW_USED_FILES = YES
|
|
|
|
SHOW_DIRECTORIES = NO
|
|
|
|
SHOW_FILES = YES
|
|
|
|
SHOW_NAMESPACES = YES
|
|
|
|
FILE_VERSION_FILTER =
|
|
|
|
LAYOUT_FILE = doxygen/DoxygenLayout.xml
|
|
|
|
CITE_BIB_FILES =
|
|
|
|
#---------------------------------------------------------------------------
|
|
# configuration options related to warning and progress messages
|
|
#---------------------------------------------------------------------------
|
|
|
|
QUIET = NO
|
|
|
|
WARNINGS = YES
|
|
|
|
WARN_IF_UNDOCUMENTED = YES
|
|
|
|
WARN_IF_DOC_ERROR = YES
|
|
|
|
WARN_NO_PARAMDOC = NO
|
|
|
|
WARN_FORMAT = "$file:$line: $text"
|
|
|
|
WARN_LOGFILE =
|
|
|
|
#---------------------------------------------------------------------------
|
|
# configuration options related to the input files
|
|
#---------------------------------------------------------------------------
|
|
|
|
# The INPUT tag can be 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.
|
|
|
|
INPUT = "iec61850/inc/iec61850_client.h"
|
|
INPUT += "mms/inc/mms_value.h"
|
|
INPUT += "common/inc/linked_list.h"
|
|
INPUT += "doxygen/mainpage.doxygen"
|
|
INPUT += "iec61850/inc/iec61850_server.h"
|
|
INPUT += "iec61850/inc/iec61850_common.h"
|
|
INPUT += "iec61850/inc/iec61850_model.h"
|
|
INPUT += "iec61850/inc/iec61850_dynamic_model.h"
|
|
INPUT += "iec61850/inc/iec61850_config_file_parser.h"
|
|
INPUT += "iec61850/inc/iec61850_cdc.h"
|
|
INPUT += "goose/goose_subscriber.h"
|
|
INPUT += "goose/goose_receiver.h"
|
|
INPUT += "sampled_values/sv_subscriber.h"
|
|
INPUT += "sampled_values/sv_receiver.h"
|
|
INPUT += "sampled_values/sv_subscriber.h"
|
|
INPUT += "mms/inc/mms_device_model.h"
|
|
INPUT += "mms/inc/mms_types.h"
|
|
INPUT += "mms/inc/mms_common.h"
|
|
INPUT += "mms/inc/mms_server.h"
|
|
INPUT += "mms/inc/iso_server.h"
|
|
INPUT += "mms/inc/mms_named_variable_list.h"
|
|
INPUT += "mms/inc/mms_type_spec.h"
|
|
INPUT += "mms/inc/mms_types.h"
|
|
INPUT += "mms/inc/mms_client_connection.h"
|
|
INPUT += "mms/inc/iso_connection_parameters.h"
|
|
INPUT += "hal/inc/hal_socket.h"
|
|
INPUT += "hal/inc/hal_thread.h"
|
|
INPUT += "hal/inc/hal_ethernet.h"
|
|
INPUT += "hal/inc/hal_filesystem.h"
|
|
INPUT += "hal/inc/hal_time.h"
|
|
|
|
INPUT_ENCODING = UTF-8
|
|
|
|
# If the value of the INPUT tag contains directories, you can use the
|
|
# 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
|
|
# 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 *.for *.vhd *.vhdl
|
|
|
|
FILE_PATTERNS =
|
|
|
|
RECURSIVE = NO
|
|
|
|
EXCLUDE =
|
|
|
|
EXCLUDE_SYMLINKS = NO
|
|
|
|
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
|
|
# output. The symbol name can be a fully qualified name, a word, or if the
|
|
# wildcard * is used, a substring. Examples: ANamespace, AClass,
|
|
# AClass::ANamespace, ANamespace::*Test
|
|
|
|
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 =
|
|
|
|
# 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 =
|
|
|
|
# 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 irrespective of the value of the RECURSIVE tag.
|
|
# Possible values are YES and NO. If left blank NO is used.
|
|
|
|
EXAMPLE_RECURSIVE = NO
|
|
|
|
# The IMAGE_PATH tag can be used to specify one or more files or
|
|
# directories that contain image that are included in the documentation (see
|
|
# the \image command).
|
|
|
|
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
|
|
# 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
|
|
# 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
|
|
# ignored.
|
|
|
|
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
|
|
# 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 or if
|
|
# non of the patterns match the file name, INPUT_FILTER is applied.
|
|
|
|
FILTER_PATTERNS =
|
|
|
|
# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
|
|
# INPUT_FILTER) will be used to filter the input files when producing source
|
|
# files to browse (i.e. when SOURCE_BROWSER is set to YES).
|
|
|
|
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
|
|
#---------------------------------------------------------------------------
|
|
|
|
# If the SOURCE_BROWSER tag is set to YES then a list of source files will
|
|
# be generated. Documented entities will be cross-referenced with these sources.
|
|
# Note: To get rid of all source code in the generated output, make sure also
|
|
# VERBATIM_HEADERS is set to NO.
|
|
|
|
SOURCE_BROWSER = NO
|
|
|
|
# Setting the INLINE_SOURCES tag to YES will include the body
|
|
# of functions and classes directly in the documentation.
|
|
|
|
INLINE_SOURCES = NO
|
|
|
|
# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
|
|
# doxygen to hide any special comment blocks from generated source code
|
|
# fragments. Normal C and C++ comments will always remain visible.
|
|
|
|
STRIP_CODE_COMMENTS = YES
|
|
|
|
# If the REFERENCED_BY_RELATION tag is set to YES
|
|
# then for each documented function all documented
|
|
# functions referencing it will be listed.
|
|
|
|
REFERENCED_BY_RELATION = NO
|
|
|
|
# If the REFERENCES_RELATION tag is set to YES
|
|
# then for each documented function all documented entities
|
|
# called/used by that function will be listed.
|
|
|
|
REFERENCES_RELATION = NO
|
|
|
|
# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
|
|
# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
|
|
# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
|
|
# link to the source code.
|
|
# Otherwise they will link to the documentation.
|
|
|
|
REFERENCES_LINK_SOURCE = YES
|
|
|
|
# If the USE_HTAGS tag is set to YES then the references to source code
|
|
# will point to the HTML generated by the htags(1) tool instead of doxygen
|
|
# built-in source browser. The htags tool is part of GNU's global source
|
|
# tagging system (see http://www.gnu.org/software/global/global.html). You
|
|
# will need version 4.8.6 or higher.
|
|
|
|
USE_HTAGS = NO
|
|
|
|
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
|
|
# will generate a verbatim copy of the header file for each class for
|
|
# which an include is specified. Set to NO to disable this.
|
|
|
|
VERBATIM_HEADERS = YES
|
|
|
|
#---------------------------------------------------------------------------
|
|
# configuration options related to the alphabetical class index
|
|
#---------------------------------------------------------------------------
|
|
|
|
# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
|
|
# of all compounds will be generated. Enable this if the project
|
|
# contains a lot of classes, structs, unions or interfaces.
|
|
|
|
ALPHABETICAL_INDEX = YES
|
|
|
|
# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
|
|
# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
|
|
# in which this list will be split (can be a number in the range [1..20])
|
|
|
|
COLS_IN_ALPHA_INDEX = 5
|
|
|
|
# In case all classes in a project start with a common prefix, all
|
|
# classes will be put under the same header in the alphabetical index.
|
|
# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
|
|
# should be ignored while generating the index headers.
|
|
|
|
IGNORE_PREFIX =
|
|
|
|
#---------------------------------------------------------------------------
|
|
# configuration options related to the HTML output
|
|
#---------------------------------------------------------------------------
|
|
|
|
# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
|
|
# generate HTML output.
|
|
|
|
GENERATE_HTML = YES
|
|
|
|
# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
|
|
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
|
|
# put in front of it. If left blank `html' will be used as the default path.
|
|
|
|
HTML_OUTPUT = html
|
|
|
|
# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
|
|
# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
|
|
# doxygen will generate files with .html extension.
|
|
|
|
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. 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 advised 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 = doxygen/header.html
|
|
|
|
# The HTML_FOOTER tag can be used to specify a personal HTML footer for
|
|
# each generated HTML page. If it is left blank doxygen will generate a
|
|
# standard footer.
|
|
|
|
HTML_FOOTER = doxygen/footer.html
|
|
|
|
# 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 the HTML output. If the tag is left blank doxygen
|
|
# will generate a default style sheet. Note that doxygen will try to copy
|
|
# the style sheet file to the HTML output directory, so don't put your own
|
|
# style sheet in the HTML output directory as well, or it will be erased!
|
|
|
|
HTML_STYLESHEET = doxygen/doxygen.css
|
|
|
|
# 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 style sheet 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,
|
|
# files or namespaces will be aligned in HTML using tables. If set to
|
|
# NO a bullet list will be used.
|
|
|
|
HTML_ALIGN_MEMBERS = 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
|
|
# page has loaded. For this to work a browser that supports
|
|
# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
|
|
# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
|
|
|
|
HTML_DYNAMIC_SECTIONS = NO
|
|
|
|
# If the GENERATE_DOCSET tag is set to YES, additional index files
|
|
# will be generated that can be used as input for Apple's Xcode 3
|
|
# integrated development environment, introduced with OSX 10.5 (Leopard).
|
|
# To create a documentation set, doxygen will generate a Makefile in the
|
|
# HTML output directory. Running make will produce the docset in that
|
|
# directory and running "make install" will install the docset in
|
|
# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
|
|
# it at startup.
|
|
# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
|
|
# for more information.
|
|
|
|
GENERATE_DOCSET = NO
|
|
|
|
# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
|
|
# feed. A documentation feed provides an umbrella under which multiple
|
|
# documentation sets from a single provider (such as a company or product suite)
|
|
# can be grouped.
|
|
|
|
DOCSET_FEEDNAME = "Doxygen generated docs"
|
|
|
|
# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
|
|
# should uniquely identify the documentation set bundle. This should be a
|
|
# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
|
|
# will append .docset to the name.
|
|
|
|
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
|
|
# 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)
|
|
# of the generated HTML documentation.
|
|
|
|
GENERATE_HTMLHELP = NO
|
|
|
|
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
|
|
# be used to specify the file name of the resulting .chm file. You
|
|
# can add a path in front of the file if the result should not be
|
|
# written to the html output directory.
|
|
|
|
CHM_FILE =
|
|
|
|
# If the GENERATE_HTMLHELP tag is set to YES, 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 doxygen will try to run
|
|
# the HTML help compiler on the generated index.hhp.
|
|
|
|
HHC_LOCATION =
|
|
|
|
# If the GENERATE_HTMLHELP tag is set to YES, 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).
|
|
|
|
GENERATE_CHI = NO
|
|
|
|
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
|
|
# is used to encode HtmlHelp index (hhk), content (hhc) and project file
|
|
# content.
|
|
|
|
CHM_INDEX_ENCODING =
|
|
|
|
# If the GENERATE_HTMLHELP tag is set to YES, 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.
|
|
|
|
BINARY_TOC = NO
|
|
|
|
# The TOC_EXPAND flag can be set to YES to add extra items for group members
|
|
# to the contents of the HTML help documentation and to the tree view.
|
|
|
|
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.
|
|
|
|
GENERATE_QHP = NO
|
|
|
|
# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
|
|
# be used to specify the file name of the resulting .qch file.
|
|
# The path specified is relative to the HTML output folder.
|
|
|
|
QCH_FILE =
|
|
|
|
# The QHP_NAMESPACE tag specifies the namespace to use when generating
|
|
# Qt Help Project output. For more information please see
|
|
# http://doc.trolltech.com/qthelpproject.html#namespace
|
|
|
|
QHP_NAMESPACE = org.doxygen.Project
|
|
|
|
# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
|
|
# Qt Help Project output. For more information please see
|
|
# http://doc.trolltech.com/qthelpproject.html#virtual-folders
|
|
|
|
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
|
|
# http://doc.trolltech.com/qthelpproject.html#custom-filters
|
|
|
|
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>.
|
|
|
|
QHP_CUST_FILTER_ATTRS =
|
|
|
|
# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
|
|
# project's
|
|
# filter section matches.
|
|
# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
|
|
# Qt Help Project / Filter Attributes</a>.
|
|
|
|
QHP_SECT_FILTER_ATTRS =
|
|
|
|
# If the GENERATE_QHP tag is set to YES, 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.
|
|
|
|
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 (tabs)
|
|
# at top of each HTML page. The value NO (the default) enables the index and
|
|
# the value YES disables it. Since the tabs have the same information as the
|
|
# navigation tree you can set this option to NO if you already set
|
|
# GENERATE_TREEVIEW to YES.
|
|
|
|
DISABLE_INDEX = NO
|
|
|
|
# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
|
|
# structure should be generated to display hierarchical information.
|
|
# 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
|
|
# is generated for HTML Help). For this to work a browser that supports
|
|
# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
|
|
# Windows users are probably better off using the HTML help feature.
|
|
# Since the tree basically has the same information as the tab index you
|
|
# could consider to set DISABLE_INDEX to NO when enabling this option.
|
|
|
|
GENERATE_TREEVIEW = NO
|
|
|
|
# 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
|
|
|
|
# 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
|
|
# used to set the initial width (in pixels) of the frame in which the tree
|
|
# is shown.
|
|
|
|
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
|
|
# 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
|
|
# to manually remove any form_*.png images from the HTML output directory
|
|
# to force them to be regenerated.
|
|
|
|
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
|
|
|
|
# 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
|
|
# 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
|
|
#---------------------------------------------------------------------------
|
|
|
|
# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
|
|
# generate Latex output.
|
|
|
|
GENERATE_LATEX = YES
|
|
|
|
# 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 it. If left blank `latex' will be used as the default path.
|
|
|
|
LATEX_OUTPUT = latex
|
|
|
|
# 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.
|
|
# 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
|
|
|
|
# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
|
|
# generate index for LaTeX. If left blank `makeindex' will be used as the
|
|
# default command name.
|
|
|
|
MAKEINDEX_CMD_NAME = makeindex
|
|
|
|
# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
|
|
# LaTeX documents. This may be useful for small projects and may help to
|
|
# save some trees in general.
|
|
|
|
COMPACT_LATEX = NO
|
|
|
|
# The PAPER_TYPE tag can be used to set the paper type that is used
|
|
# by the printer. Possible values are: a4, letter, legal and
|
|
# executive. If left blank a4wide will be used.
|
|
|
|
PAPER_TYPE = a4
|
|
|
|
# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
|
|
# packages that should be included in the LaTeX output.
|
|
|
|
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 chapter. If it is left blank doxygen will generate a
|
|
# standard header. Notice: only use this tag if you know what you are doing!
|
|
|
|
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
|
|
# This makes the output suitable for online browsing using a pdf viewer.
|
|
|
|
PDF_HYPERLINKS = YES
|
|
|
|
# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
|
|
# plain latex in the generated Makefile. Set this option to YES to get a
|
|
# higher quality PDF documentation.
|
|
|
|
USE_PDFLATEX = YES
|
|
|
|
# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
|
|
# command to the generated LaTeX files. This will instruct LaTeX to keep
|
|
# running if errors occur, instead of asking the user for help.
|
|
# This option is also used when generating formulas in HTML.
|
|
|
|
LATEX_BATCHMODE = NO
|
|
|
|
# If LATEX_HIDE_INDICES is set to YES then doxygen will not
|
|
# include the index chapters (such as File Index, Compound Index, etc.)
|
|
# in the output.
|
|
|
|
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
|
|
|
|
# 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
|
|
#---------------------------------------------------------------------------
|
|
|
|
# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
|
|
# The RTF output is optimized for Word 97 and may not look very pretty with
|
|
# other RTF readers or editors.
|
|
|
|
GENERATE_RTF = NO
|
|
|
|
# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
|
|
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
|
|
# put in front of it. If left blank `rtf' will be used as the default path.
|
|
|
|
RTF_OUTPUT = rtf
|
|
|
|
# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
|
|
# RTF documents. This may be useful for small projects and may help to
|
|
# save some trees in general.
|
|
|
|
COMPACT_RTF = NO
|
|
|
|
# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
|
|
# will contain hyperlink fields. The RTF file will
|
|
# contain links (just like the HTML output) instead of page references.
|
|
# This makes the output suitable for online browsing using WORD or other
|
|
# programs which support those fields.
|
|
# Note: wordpad (write) and others do not support links.
|
|
|
|
RTF_HYPERLINKS = NO
|
|
|
|
# Load style sheet definitions from file. Syntax is similar to doxygen's
|
|
# config file, i.e. a series of assignments. You only have to provide
|
|
# replacements, missing definitions are set to their default value.
|
|
|
|
RTF_STYLESHEET_FILE =
|
|
|
|
# Set optional variables used in the generation of an rtf document.
|
|
# Syntax is similar to doxygen's config file.
|
|
|
|
RTF_EXTENSIONS_FILE =
|
|
|
|
#---------------------------------------------------------------------------
|
|
# configuration options related to the man page output
|
|
#---------------------------------------------------------------------------
|
|
|
|
# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
|
|
# generate man pages
|
|
|
|
GENERATE_MAN = NO
|
|
|
|
# The MAN_OUTPUT tag is used to specify where the man pages will be put.
|
|
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
|
|
# put in front of it. If left blank `man' will be used as the default path.
|
|
|
|
MAN_OUTPUT = man
|
|
|
|
# The MAN_EXTENSION tag determines the extension that is added to
|
|
# the generated man pages (default is the subroutine's section .3)
|
|
|
|
MAN_EXTENSION = .3
|
|
|
|
# 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 man page(s). These additional files
|
|
# only source the real man page, but without them the man command
|
|
# would be unable to find the correct page. The default is NO.
|
|
|
|
MAN_LINKS = NO
|
|
|
|
#---------------------------------------------------------------------------
|
|
# configuration options related to the XML output
|
|
#---------------------------------------------------------------------------
|
|
|
|
# If the GENERATE_XML tag is set to YES Doxygen will
|
|
# generate an XML file that captures the structure of
|
|
# the code including all documentation.
|
|
|
|
GENERATE_XML = NO
|
|
|
|
# The XML_OUTPUT tag is used to specify where the XML pages will be put.
|
|
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
|
|
# put in front of it. If left blank `xml' will be used as the default path.
|
|
|
|
XML_OUTPUT = xml
|
|
|
|
# The XML_SCHEMA tag can be used to specify an XML schema,
|
|
# which can be used by a validating XML parser to check the
|
|
# syntax of the XML files.
|
|
|
|
XML_SCHEMA =
|
|
|
|
# The XML_DTD tag can be used to specify an XML DTD,
|
|
# which can be used by a validating XML parser to check the
|
|
# syntax of the XML files.
|
|
|
|
XML_DTD =
|
|
|
|
# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
|
|
# dump the program listings (including syntax highlighting
|
|
# and cross-referencing information) to the XML output. Note that
|
|
# enabling this will significantly increase the size of the XML output.
|
|
|
|
XML_PROGRAMLISTING = YES
|
|
|
|
#---------------------------------------------------------------------------
|
|
# configuration options for the AutoGen Definitions output
|
|
#---------------------------------------------------------------------------
|
|
|
|
# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
|
|
# generate an AutoGen Definitions (see autogen.sf.net) file
|
|
# that captures the structure of the code including all
|
|
# documentation. Note that this feature is still experimental
|
|
# and incomplete at the moment.
|
|
|
|
GENERATE_AUTOGEN_DEF = NO
|
|
|
|
#---------------------------------------------------------------------------
|
|
# configuration options related to the Perl module output
|
|
#---------------------------------------------------------------------------
|
|
|
|
# If the GENERATE_PERLMOD tag is set to YES Doxygen will
|
|
# generate a Perl module file that captures the structure of
|
|
# the code including all documentation. Note that this
|
|
# feature is still experimental and incomplete at the
|
|
# moment.
|
|
|
|
GENERATE_PERLMOD = NO
|
|
|
|
# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
|
|
# the necessary Makefile rules, Perl scripts and LaTeX code to be able
|
|
# to generate PDF and DVI output from the Perl module output.
|
|
|
|
PERLMOD_LATEX = NO
|
|
|
|
# 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
|
|
# tag is set to NO the size of the Perl module output will be much smaller
|
|
# and Perl will parse it just the same.
|
|
|
|
PERLMOD_PRETTY = YES
|
|
|
|
# The names of the make variables in the generated doxyrules.make file
|
|
# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
|
|
# This is useful so different doxyrules.make files included by the same
|
|
# Makefile don't overwrite each other's variables.
|
|
|
|
PERLMOD_MAKEVAR_PREFIX =
|
|
|
|
#---------------------------------------------------------------------------
|
|
# Configuration options related to the preprocessor
|
|
#---------------------------------------------------------------------------
|
|
|
|
# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
|
|
# evaluate all C-preprocessor directives found in the sources and include
|
|
# files.
|
|
|
|
ENABLE_PREPROCESSING = YES
|
|
|
|
# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
|
|
# names in the source code. If set to NO (the default) only conditional
|
|
# compilation will be performed. Macro expansion can be done in a controlled
|
|
# way by setting EXPAND_ONLY_PREDEF to YES.
|
|
|
|
MACRO_EXPANSION = NO
|
|
|
|
# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
|
|
# then the macro expansion is limited to the macros specified with the
|
|
# PREDEFINED and EXPAND_AS_DEFINED tags.
|
|
|
|
EXPAND_ONLY_PREDEF = NO
|
|
|
|
# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
|
|
# pointed to by INCLUDE_PATH will be searched when a #include is found.
|
|
|
|
SEARCH_INCLUDES = YES
|
|
|
|
# The INCLUDE_PATH tag can be used to specify one or more directories that
|
|
# contain include files that are not input files but should be processed by
|
|
# the preprocessor.
|
|
|
|
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
|
|
# directories. If left blank, the patterns specified with FILE_PATTERNS will
|
|
# be used.
|
|
|
|
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
|
|
# gcc). The argument of the tag is a list of macros of the form: name
|
|
# or name=definition (no spaces). If the definition and the = are
|
|
# omitted =1 is assumed. To prevent a macro definition from being
|
|
# undefined via #undef or recursively expanded use the := operator
|
|
# instead of the = operator.
|
|
|
|
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 macro definition that is found in the sources will be used.
|
|
# 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 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
|
|
|
|
ALLEXTERNALS = NO
|
|
|
|
EXTERNAL_GROUPS = YES
|
|
|
|
PERL_PATH = /usr/bin/perl
|
|
|
|
#---------------------------------------------------------------------------
|
|
# Configuration options related to the dot tool
|
|
#---------------------------------------------------------------------------
|
|
|
|
CLASS_DIAGRAMS = YES
|
|
|
|
MSCGEN_PATH =
|
|
|
|
HIDE_UNDOC_RELATIONS = YES
|
|
|
|
HAVE_DOT = NO
|
|
|
|
DOT_NUM_THREADS = 0
|
|
|
|
DOT_FONTNAME = Helvetica
|
|
|
|
DOT_FONTSIZE = 10
|
|
|
|
DOT_FONTPATH =
|
|
|
|
CLASS_GRAPH = YES
|
|
|
|
COLLABORATION_GRAPH = YES
|
|
|
|
GROUP_GRAPHS = YES
|
|
|
|
UML_LOOK = NO
|
|
|
|
TEMPLATE_RELATIONS = NO
|
|
|
|
INCLUDE_GRAPH = YES
|
|
|
|
INCLUDED_BY_GRAPH = YES
|
|
|
|
CALL_GRAPH = NO
|
|
|
|
CALLER_GRAPH = NO
|
|
|
|
GRAPHICAL_HIERARCHY = YES
|
|
|
|
DIRECTORY_GRAPH = YES
|
|
|
|
DOT_IMAGE_FORMAT = png
|
|
|
|
INTERACTIVE_SVG = NO
|
|
|
|
DOT_PATH =
|
|
|
|
DOTFILE_DIRS =
|
|
|
|
MSCFILE_DIRS =
|
|
|
|
DOT_GRAPH_MAX_NODES = 50
|
|
|
|
MAX_DOT_GRAPH_DEPTH = 0
|
|
|
|
DOT_TRANSPARENT = NO
|
|
|
|
DOT_MULTI_TARGETS = YES
|
|
|
|
GENERATE_LEGEND = YES
|
|
|
|
DOT_CLEANUP = YES
|