33
33
OUTPUT_DIRECTORY = reference
35
# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
36
# 4096 sub-directories (in 2 levels) under the output directory of each output
37
# format and will distribute the generated files over these directories.
38
# Enabling this option can be useful when feeding doxygen a huge amount of
39
# source files, where putting all generated files in the same directory would
40
# otherwise cause performance problems for the file system.
35
44
# The OUTPUT_LANGUAGE tag is used to specify the language in which all
36
45
# documentation generated by doxygen is written. Doxygen will use this
37
46
# information to generate all constant output in the proper language.
38
47
# The default language is English, other supported languages are:
39
# Brazilian, Chinese, Croatian, Czech, Danish, Dutch, Finnish, French,
40
# German, Greek, Hungarian, Italian, Japanese, Korean, Norwegian, Polish,
41
# Portuguese, Romanian, Russian, Slovak, Slovene, Spanish and Swedish.
48
# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,
49
# Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,
50
# Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,
51
# Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,
52
# Swedish, and Ukrainian.
43
54
OUTPUT_LANGUAGE = English
56
# This tag can be used to specify the encoding used in the generated output.
57
# The encoding is not always determined by the language that is chosen,
58
# but also whether or not the output is meant for Windows or non-Windows users.
59
# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
60
# forces the Windows encoding (this is the default for the Windows binary),
61
# whereas setting the tag to NO uses a Unix-style encoding (the default for
62
# all platforms other than Windows).
64
USE_WINDOWS_ENCODING = NO
66
# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
67
# include brief member descriptions after the members that are listed in
68
# the file and class documentation (similar to JavaDoc).
69
# Set to NO to disable this.
71
BRIEF_MEMBER_DESC = YES
73
# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
74
# the brief description of a member or function before the detailed description.
75
# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
76
# brief descriptions will be completely suppressed.
80
# This tag implements a quasi-intelligent brief description abbreviator
81
# that is used to form the text in various listings. Each string
82
# in this list, if found as the leading text of the brief description, will be
83
# stripped from the text and the result after processing the whole list, is
84
# used as the annotated text. Otherwise, the brief description is used as-is.
85
# If left blank, the following values are used ("$name" is automatically
86
# replaced with the name of the entity): "The $name class" "The $name widget"
87
# "The $name file" "is" "provides" "specifies" "contains"
88
# "represents" "a" "an" "the"
92
# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
93
# Doxygen will generate a detailed section even if there is only a brief
96
ALWAYS_DETAILED_SEC = NO
98
# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
99
# inherited members of a class in the documentation of that class as if those
100
# members were ordinary class members. Constructors, destructors and assignment
101
# operators of the base classes will not be shown.
103
INLINE_INHERITED_MEMB = NO
105
# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
106
# path before files name in the file list and in the header files. If set
107
# to NO the shortest path that makes the file name unique will be used.
111
# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
112
# can be used to strip a user-defined part of the path. Stripping is
113
# only done if one of the specified strings matches the left-hand part of
114
# the path. The tag can be used to show relative paths in the file list.
115
# If left blank the directory from which doxygen is run is used as the
120
# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
121
# the path mentioned in the documentation of a class, which tells
122
# the reader which header file to include in order to use a class.
123
# If left blank only the name of the header file containing the class
124
# definition is used. Otherwise one should specify the include paths that
125
# are normally passed to the compiler using the -I flag.
127
STRIP_FROM_INC_PATH =
129
# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
130
# (but less readable) file names. This can be useful is your file systems
131
# doesn't support long names like on DOS, Mac, or CD-ROM.
135
# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
136
# will interpret the first line (until the first dot) of a JavaDoc-style
137
# comment as the brief description. If set to NO, the JavaDoc
138
# comments will behave just like the Qt-style comments (thus requiring an
139
# explicit @brief command for a brief description.
141
JAVADOC_AUTOBRIEF = NO
143
# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
144
# treat a multi-line C++ special comment block (i.e. a block of //! or ///
145
# comments) as a brief description. This used to be the default behaviour.
146
# The new default is to treat a multi-line C++ comment block as a detailed
147
# description. Set this tag to YES if you prefer the old behaviour instead.
149
MULTILINE_CPP_IS_BRIEF = NO
151
# If the DETAILS_AT_TOP tag is set to YES then Doxygen
152
# will output the detailed description near the top, like JavaDoc.
153
# If set to NO, the detailed description appears after the member
158
# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
159
# member inherits the documentation from any documented member that it
164
# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
165
# a new page for each member. If set to NO, the documentation of a member will
166
# be part of the file/class/namespace that contains it.
168
SEPARATE_MEMBER_PAGES = NO
170
# The TAB_SIZE tag can be used to set the number of spaces in a tab.
171
# Doxygen uses this value to replace tabs by spaces in code fragments.
175
# This tag can be used to specify a number of aliases that acts
176
# as commands in the documentation. An alias has the form "name=value".
177
# For example adding "sideeffect=\par Side Effects:\n" will allow you to
178
# put the command \sideeffect (or @sideeffect) in the documentation, which
179
# will result in a user-defined paragraph with heading "Side Effects:".
180
# You can put \n's in the value part of an alias to insert newlines.
184
# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
185
# sources only. Doxygen will then generate output that is more tailored for C.
186
# For instance, some of the names that are used will be different. The list
187
# of all members will be omitted, etc.
189
OPTIMIZE_OUTPUT_FOR_C = YES
191
# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
192
# sources only. Doxygen will then generate output that is more tailored for Java.
193
# For instance, namespaces will be presented as packages, qualified scopes
194
# will look different, etc.
196
OPTIMIZE_OUTPUT_JAVA = NO
198
# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want to
199
# include (a tag file for) the STL sources as input, then you should
200
# set this tag to YES in order to let doxygen match functions declarations and
201
# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
202
# func(std::string) {}). This also make the inheritance and collaboration
203
# diagrams that involve STL classes more complete and accurate.
205
BUILTIN_STL_SUPPORT = NO
207
# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
208
# tag is set to YES, then doxygen will reuse the documentation of the first
209
# member in the group (if any) for the other members of the group. By default
210
# all members of a group must be documented explicitly.
212
DISTRIBUTE_GROUP_DOC = NO
214
# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
215
# the same type (for instance a group of public functions) to be put as a
216
# subgroup of that type (e.g. under the Public Functions section). Set it to
217
# NO to prevent subgrouping. Alternatively, this can be done per class using
218
# the \nosubgrouping command.
222
#---------------------------------------------------------------------------
223
# Build related configuration options
224
#---------------------------------------------------------------------------
45
226
# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
46
227
# documentation are documented, even if no documentation was available.
47
228
# Private class members and static file members will be hidden unless
76
264
# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
77
265
# undocumented classes that are normally visible in the class hierarchy.
78
# If set to NO (the default) these class will be included in the various
266
# If set to NO (the default) these classes will be included in the various
79
267
# overviews. This option has no effect if EXTRACT_ALL is enabled.
81
269
HIDE_UNDOC_CLASSES = NO
83
# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
84
# include brief member descriptions after the members that are listed in
85
# the file and class documentation (similar to JavaDoc).
86
# Set to NO to disable this.
88
BRIEF_MEMBER_DESC = YES
90
# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
91
# the brief description of a member or function before the detailed description.
92
# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
93
# brief descriptions will be completely suppressed.
97
# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
98
# Doxygen will generate a detailed section even if there is only a brief
101
ALWAYS_DETAILED_SEC = NO
103
# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show
104
# all inherited members of a class in the documentation of that class as
105
# if those members were ordinary class members. Constructors, destructors
106
# and assignment operators of the base classes will not be shown.
108
INLINE_INHERITED_MEMB = NO
110
# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
111
# path before files name in the file list and in the header files. If set
112
# to NO the shortest path that makes the file name unique will be used.
116
# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
117
# can be used to strip a user defined part of the path. Stripping is
118
# only done if one of the specified strings matches the left-hand part of
119
# the path. It is allowed to use relative paths in the argument list.
271
# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
272
# friend (class|struct|union) declarations.
273
# If set to NO (the default) these declarations will be included in the
276
HIDE_FRIEND_COMPOUNDS = NO
278
# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
279
# documentation blocks found inside the body of a function.
280
# If set to NO (the default) these blocks will be appended to the
281
# function's detailed documentation block.
283
HIDE_IN_BODY_DOCS = NO
123
285
# The INTERNAL_DOCS tag determines if documentation
124
286
# that is typed after a \internal command is included. If the tag is set
128
290
INTERNAL_DOCS = NO
130
# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
131
# doxygen to hide any special comment blocks from generated source code
132
# fragments. Normal C and C++ comments will always remain visible.
134
STRIP_CODE_COMMENTS = YES
136
292
# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
137
# file names in lower case letters. If set to YES upper case letters are also
293
# file names in lower-case letters. If set to YES upper-case letters are also
138
294
# allowed. This is useful if you have classes or files whose names only differ
139
295
# in case and if your file system supports case sensitive file names. Windows
140
# users are adviced to set this option to NO.
296
# and Mac users are advised to set this option to NO.
142
298
CASE_SENSE_NAMES = YES
144
# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
145
# (but less readable) file names. This can be useful is your file systems
146
# doesn't support long names like on DOS, Mac, or CD-ROM.
150
300
# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
151
301
# will show members with their full class and namespace scopes in the
152
302
# documentation. If set to YES the scope will be hidden.
154
304
HIDE_SCOPE_NAMES = NO
156
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
157
# will generate a verbatim copy of the header file for each class for
158
# which an include is specified. Set to NO to disable this.
160
VERBATIM_HEADERS = YES
162
306
# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
163
# will put list of the files that are included by a file in the documentation
307
# will put a list of the files that are included by a file in the documentation
166
310
SHOW_INCLUDE_FILES = YES
168
# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
169
# will interpret the first line (until the first dot) of a JavaDoc-style
170
# comment as the brief description. If set to NO, the JavaDoc
171
# comments will behave just like the Qt-style comments (thus requiring an
172
# explict @brief command for a brief description.
174
JAVADOC_AUTOBRIEF = NO
176
# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
177
# member inherits the documentation from any documented member that it
182
312
# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
183
313
# is inserted in the documentation for inline members.