comparison Resources/OrthancPlugin.doxygen @ 2224:87c71bfb4e8a

upgrade doxygen configuration
author Sebastien Jodogne <s.jodogne@gmail.com>
date Tue, 13 Dec 2016 15:49:03 +0100
parents 86089e777691
children 40e0d031424c
comparison
equal deleted inserted replaced
2223:29689b30f9ae 2224:87c71bfb4e8a
1 # Doxyfile 1.8.1.2 1 # Doxyfile 1.8.7
2 2
3 # This file describes the settings to be used by the documentation system 3 # This file describes the settings to be used by the documentation system
4 # doxygen (www.doxygen.org) for a project. 4 # doxygen (www.doxygen.org) for a project.
5 # 5 #
6 # All text after a hash (#) is considered a comment and will be ignored. 6 # All text after a double hash (##) is considered a comment and is placed in
7 # front of the TAG it is preceding.
8 #
9 # All text after a single hash (#) is considered a comment and will be ignored.
7 # The format is: 10 # The format is:
8 # TAG = value [value, ...] 11 # TAG = value [value, ...]
9 # For lists items can also be appended using: 12 # For lists, items can also be appended using:
10 # TAG += value [value, ...] 13 # TAG += value [value, ...]
11 # Values that contain spaces should be placed between quotes (" "). 14 # Values that contain spaces should be placed between quotes (\" \").
12 15
13 #--------------------------------------------------------------------------- 16 #---------------------------------------------------------------------------
14 # Project related configuration options 17 # Project related configuration options
15 #--------------------------------------------------------------------------- 18 #---------------------------------------------------------------------------
16 19
17 # This tag specifies the encoding used for all characters in the config file 20 # This tag specifies the encoding used for all characters in the config file
18 # that follow. The default is UTF-8 which is also the encoding used for all 21 # that follow. The default is UTF-8 which is also the encoding used for all text
19 # text before the first occurrence of this tag. Doxygen uses libiconv (or the 22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
20 # iconv built into libc) for the transcoding. See 23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
21 # http://www.gnu.org/software/libiconv for the list of possible encodings. 24 # for the list of possible encodings.
25 # The default value is: UTF-8.
22 26
23 DOXYFILE_ENCODING = UTF-8 27 DOXYFILE_ENCODING = UTF-8
24 28
25 # The PROJECT_NAME tag is a single word (or sequence of words) that should 29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
26 # identify the project. Note that if you do not use Doxywizard you need 30 # double-quotes, unless you are using Doxywizard) that should identify the
27 # to put quotes around the project name if it contains spaces. 31 # project for which the documentation is generated. This name is used in the
32 # title of most generated pages and in a few other places.
33 # The default value is: My Project.
28 34
29 PROJECT_NAME = "Orthanc Plugin SDK" 35 PROJECT_NAME = "Orthanc Plugin SDK"
30 36
31 # The PROJECT_NUMBER tag can be used to enter a project or revision number. 37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
32 # This could be handy for archiving the generated documentation or 38 # could be handy for archiving the generated documentation or if some version
33 # if some version control system is used. 39 # control system is used.
34 40
35 PROJECT_NUMBER = @ORTHANC_VERSION@ 41 PROJECT_NUMBER = @ORTHANC_VERSION@
36 42
37 # Using the PROJECT_BRIEF tag one can provide an optional one line description 43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
38 # for a project that appears at the top of each page and should give viewer 44 # for a project that appears at the top of each page and should give viewer a
39 # a quick idea about the purpose of the project. Keep the description short. 45 # quick idea about the purpose of the project. Keep the description short.
40 46
41 PROJECT_BRIEF = "Documentation of the plugin interface of Orthanc" 47 PROJECT_BRIEF = "Documentation of the plugin interface of Orthanc"
42 48
43 # With the PROJECT_LOGO tag one can specify an logo or icon that is 49 # With the PROJECT_LOGO tag one can specify an logo or icon that is included in
44 # included in the documentation. The maximum height of the logo should not 50 # the documentation. The maximum height of the logo should not exceed 55 pixels
45 # exceed 55 pixels and the maximum width should not exceed 200 pixels. 51 # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo
46 # Doxygen will copy the logo to the output directory. 52 # to the output directory.
47 53
48 PROJECT_LOGO = @CMAKE_SOURCE_DIR@/Resources/OrthancLogoDocumentation.png 54 PROJECT_LOGO = @CMAKE_SOURCE_DIR@/Resources/OrthancLogoDocumentation.png
49 55
50 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
51 # base path where the generated documentation will be put. 57 # into which the generated documentation will be written. If a relative path is
52 # If a relative path is entered, it will be relative to the location 58 # entered, it will be relative to the location where doxygen was started. If
53 # where doxygen was started. If left blank the current directory will be used. 59 # left blank the current directory will be used.
54 60
55 OUTPUT_DIRECTORY = OrthancPluginDocumentation 61 OUTPUT_DIRECTORY = OrthancPluginDocumentation
56 62
57 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
58 # 4096 sub-directories (in 2 levels) under the output directory of each output 64 # directories (in 2 levels) under the output directory of each output format and
59 # format and will distribute the generated files over these directories. 65 # will distribute the generated files over these directories. Enabling this
60 # Enabling this option can be useful when feeding doxygen a huge amount of 66 # option can be useful when feeding doxygen a huge amount of source files, where
61 # source files, where putting all generated files in the same directory would 67 # putting all generated files in the same directory would otherwise causes
62 # otherwise cause performance problems for the file system. 68 # performance problems for the file system.
69 # The default value is: NO.
63 70
64 CREATE_SUBDIRS = NO 71 CREATE_SUBDIRS = NO
72
73 # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
75 # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
76 # U+3044.
77 # The default value is: NO.
78
79 ALLOW_UNICODE_NAMES = NO
65 80
66 # The OUTPUT_LANGUAGE tag is used to specify the language in which all 81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
67 # documentation generated by doxygen is written. Doxygen will use this 82 # documentation generated by doxygen is written. Doxygen will use this
68 # information to generate all constant output in the proper language. 83 # information to generate all constant output in the proper language.
69 # The default language is English, other supported languages are: 84 # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
70 # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 85 # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
71 # Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 86 # Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,
72 # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 87 # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
73 # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, 88 # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
74 # Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, 89 # Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,
75 # Slovene, Spanish, Swedish, Ukrainian, and Vietnamese. 90 # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
91 # Ukrainian and Vietnamese.
92 # The default value is: English.
76 93
77 OUTPUT_LANGUAGE = English 94 OUTPUT_LANGUAGE = English
78 95
79 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 96 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member
80 # include brief member descriptions after the members that are listed in 97 # descriptions after the members that are listed in the file and class
81 # the file and class documentation (similar to JavaDoc). 98 # documentation (similar to Javadoc). Set to NO to disable this.
82 # Set to NO to disable this. 99 # The default value is: YES.
83 100
84 BRIEF_MEMBER_DESC = YES 101 BRIEF_MEMBER_DESC = YES
85 102
86 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 103 # If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief
87 # the brief description of a member or function before the detailed description. 104 # description of a member or function before the detailed description
88 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 105 #
106 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
89 # brief descriptions will be completely suppressed. 107 # brief descriptions will be completely suppressed.
108 # The default value is: YES.
90 109
91 REPEAT_BRIEF = NO 110 REPEAT_BRIEF = NO
92 111
93 # This tag implements a quasi-intelligent brief description abbreviator 112 # This tag implements a quasi-intelligent brief description abbreviator that is
94 # that is used to form the text in various listings. Each string 113 # used to form the text in various listings. Each string in this list, if found
95 # in this list, if found as the leading text of the brief description, will be 114 # as the leading text of the brief description, will be stripped from the text
96 # stripped from the text and the result after processing the whole list, is 115 # and the result, after processing the whole list, is used as the annotated
97 # used as the annotated text. Otherwise, the brief description is used as-is. 116 # text. Otherwise, the brief description is used as-is. If left blank, the
98 # If left blank, the following values are used ("$name" is automatically 117 # following values are used ($name is automatically replaced with the name of
99 # replaced with the name of the entity): "The $name class" "The $name widget" 118 # the entity):The $name class, The $name widget, The $name file, is, provides,
100 # "The $name file" "is" "provides" "specifies" "contains" 119 # specifies, contains, represents, a, an and the.
101 # "represents" "a" "an" "the"
102 120
103 ABBREVIATE_BRIEF = 121 ABBREVIATE_BRIEF =
104 122
105 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 123 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
106 # Doxygen will generate a detailed section even if there is only a brief 124 # doxygen will generate a detailed section even if there is only a brief
107 # description. 125 # description.
126 # The default value is: NO.
108 127
109 ALWAYS_DETAILED_SEC = NO 128 ALWAYS_DETAILED_SEC = NO
110 129
111 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 130 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
112 # inherited members of a class in the documentation of that class as if those 131 # inherited members of a class in the documentation of that class as if those
113 # members were ordinary class members. Constructors, destructors and assignment 132 # members were ordinary class members. Constructors, destructors and assignment
114 # operators of the base classes will not be shown. 133 # operators of the base classes will not be shown.
134 # The default value is: NO.
115 135
116 INLINE_INHERITED_MEMB = NO 136 INLINE_INHERITED_MEMB = NO
117 137
118 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 138 # If the FULL_PATH_NAMES tag is set to YES doxygen will prepend the full path
119 # path before files name in the file list and in the header files. If set 139 # before files name in the file list and in the header files. If set to NO the
120 # to NO the shortest path that makes the file name unique will be used. 140 # shortest path that makes the file name unique will be used
141 # The default value is: YES.
121 142
122 FULL_PATH_NAMES = NO 143 FULL_PATH_NAMES = NO
123 144
124 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 145 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
125 # can be used to strip a user-defined part of the path. Stripping is 146 # Stripping is only done if one of the specified strings matches the left-hand
126 # only done if one of the specified strings matches the left-hand part of 147 # part of the path. The tag can be used to show relative paths in the file list.
127 # the path. The tag can be used to show relative paths in the file list. 148 # If left blank the directory from which doxygen is run is used as the path to
128 # If left blank the directory from which doxygen is run is used as the 149 # strip.
129 # path to strip. 150 #
151 # Note that you can specify absolute paths here, but also relative paths, which
152 # will be relative from the directory where doxygen is started.
153 # This tag requires that the tag FULL_PATH_NAMES is set to YES.
130 154
131 STRIP_FROM_PATH = 155 STRIP_FROM_PATH =
132 156
133 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 157 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
134 # the path mentioned in the documentation of a class, which tells 158 # path mentioned in the documentation of a class, which tells the reader which
135 # the reader which header file to include in order to use a class. 159 # header file to include in order to use a class. If left blank only the name of
136 # If left blank only the name of the header file containing the class 160 # the header file containing the class definition is used. Otherwise one should
137 # definition is used. Otherwise one should specify the include paths that 161 # specify the list of include paths that are normally passed to the compiler
138 # are normally passed to the compiler using the -I flag. 162 # using the -I flag.
139 163
140 STRIP_FROM_INC_PATH = 164 STRIP_FROM_INC_PATH =
141 165
142 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 166 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
143 # (but less readable) file names. This can be useful if your file system 167 # less readable) file names. This can be useful is your file systems doesn't
144 # doesn't support long names like on DOS, Mac, or CD-ROM. 168 # support long names like on DOS, Mac, or CD-ROM.
169 # The default value is: NO.
145 170
146 SHORT_NAMES = NO 171 SHORT_NAMES = NO
147 172
148 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 173 # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
149 # will interpret the first line (until the first dot) of a JavaDoc-style 174 # first line (until the first dot) of a Javadoc-style comment as the brief
150 # comment as the brief description. If set to NO, the JavaDoc 175 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
151 # comments will behave just like regular Qt-style comments 176 # style comments (thus requiring an explicit @brief command for a brief
152 # (thus requiring an explicit @brief command for a brief description.) 177 # description.)
178 # The default value is: NO.
153 179
154 JAVADOC_AUTOBRIEF = NO 180 JAVADOC_AUTOBRIEF = NO
155 181
156 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will 182 # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
157 # interpret the first line (until the first dot) of a Qt-style 183 # line (until the first dot) of a Qt-style comment as the brief description. If
158 # comment as the brief description. If set to NO, the comments 184 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
159 # will behave just like regular Qt-style comments (thus requiring 185 # requiring an explicit \brief command for a brief description.)
160 # an explicit \brief command for a brief description.) 186 # The default value is: NO.
161 187
162 QT_AUTOBRIEF = NO 188 QT_AUTOBRIEF = NO
163 189
164 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 190 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
165 # treat a multi-line C++ special comment block (i.e. a block of //! or /// 191 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
166 # comments) as a brief description. This used to be the default behaviour. 192 # a brief description. This used to be the default behavior. The new default is
167 # The new default is to treat a multi-line C++ comment block as a detailed 193 # to treat a multi-line C++ comment block as a detailed description. Set this
168 # description. Set this tag to YES if you prefer the old behaviour instead. 194 # tag to YES if you prefer the old behavior instead.
195 #
196 # Note that setting this tag to YES also means that rational rose comments are
197 # not recognized any more.
198 # The default value is: NO.
169 199
170 MULTILINE_CPP_IS_BRIEF = NO 200 MULTILINE_CPP_IS_BRIEF = NO
171 201
172 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 202 # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
173 # member inherits the documentation from any documented member that it 203 # documentation from any documented member that it re-implements.
174 # re-implements. 204 # The default value is: YES.
175 205
176 INHERIT_DOCS = YES 206 INHERIT_DOCS = YES
177 207
178 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 208 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce a
179 # a new page for each member. If set to NO, the documentation of a member will 209 # new page for each member. If set to NO, the documentation of a member will be
180 # be part of the file/class/namespace that contains it. 210 # part of the file/class/namespace that contains it.
211 # The default value is: NO.
181 212
182 SEPARATE_MEMBER_PAGES = NO 213 SEPARATE_MEMBER_PAGES = NO
183 214
184 # The TAB_SIZE tag can be used to set the number of spaces in a tab. 215 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
185 # Doxygen uses this value to replace tabs by spaces in code fragments. 216 # uses this value to replace tabs by spaces in code fragments.
217 # Minimum value: 1, maximum value: 16, default value: 4.
186 218
187 TAB_SIZE = 8 219 TAB_SIZE = 8
188 220
189 # This tag can be used to specify a number of aliases that acts 221 # This tag can be used to specify a number of aliases that act as commands in
190 # as commands in the documentation. An alias has the form "name=value". 222 # the documentation. An alias has the form:
191 # For example adding "sideeffect=\par Side Effects:\n" will allow you to 223 # name=value
192 # put the command \sideeffect (or @sideeffect) in the documentation, which 224 # For example adding
193 # will result in a user-defined paragraph with heading "Side Effects:". 225 # "sideeffect=@par Side Effects:\n"
194 # You can put \n's in the value part of an alias to insert newlines. 226 # will allow you to put the command \sideeffect (or @sideeffect) in the
227 # documentation, which will result in a user-defined paragraph with heading
228 # "Side Effects:". You can put \n's in the value part of an alias to insert
229 # newlines.
195 230
196 ALIASES = 231 ALIASES =
197 232
198 # This tag can be used to specify a number of word-keyword mappings (TCL only). 233 # This tag can be used to specify a number of word-keyword mappings (TCL only).
199 # A mapping has the form "name=value". For example adding 234 # A mapping has the form "name=value". For example adding "class=itcl::class"
200 # "class=itcl::class" will allow you to use the command class in the 235 # will allow you to use the command class in the itcl::class meaning.
201 # itcl::class meaning.
202 236
203 TCL_SUBST = 237 TCL_SUBST =
204 238
205 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 239 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
206 # sources only. Doxygen will then generate output that is more tailored for C. 240 # only. Doxygen will then generate output that is more tailored for C. For
207 # For instance, some of the names that are used will be different. The list 241 # instance, some of the names that are used will be different. The list of all
208 # of all members will be omitted, etc. 242 # members will be omitted, etc.
243 # The default value is: NO.
209 244
210 OPTIMIZE_OUTPUT_FOR_C = NO 245 OPTIMIZE_OUTPUT_FOR_C = NO
211 246
212 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 247 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
213 # sources only. Doxygen will then generate output that is more tailored for 248 # Python sources only. Doxygen will then generate output that is more tailored
214 # Java. For instance, namespaces will be presented as packages, qualified 249 # for that language. For instance, namespaces will be presented as packages,
215 # scopes will look different, etc. 250 # qualified scopes will look different, etc.
251 # The default value is: NO.
216 252
217 OPTIMIZE_OUTPUT_JAVA = NO 253 OPTIMIZE_OUTPUT_JAVA = NO
218 254
219 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 255 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
220 # sources only. Doxygen will then generate output that is more tailored for 256 # sources. Doxygen will then generate output that is tailored for Fortran.
221 # Fortran. 257 # The default value is: NO.
222 258
223 OPTIMIZE_FOR_FORTRAN = NO 259 OPTIMIZE_FOR_FORTRAN = NO
224 260
225 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 261 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
226 # sources. Doxygen will then generate output that is tailored for 262 # sources. Doxygen will then generate output that is tailored for VHDL.
227 # VHDL. 263 # The default value is: NO.
228 264
229 OPTIMIZE_OUTPUT_VHDL = NO 265 OPTIMIZE_OUTPUT_VHDL = NO
230 266
231 # Doxygen selects the parser to use depending on the extension of the files it 267 # Doxygen selects the parser to use depending on the extension of the files it
232 # parses. With this tag you can assign which parser to use for a given extension. 268 # parses. With this tag you can assign which parser to use for a given
233 # Doxygen has a built-in mapping, but you can override or extend it using this 269 # extension. Doxygen has a built-in mapping, but you can override or extend it
234 # tag. The format is ext=language, where ext is a file extension, and language 270 # using this tag. The format is ext=language, where ext is a file extension, and
235 # is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C, 271 # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
236 # C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make 272 # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
237 # doxygen treat .inc files as Fortran files (default is PHP), and .f files as C 273 # FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:
238 # (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions 274 # Fortran. In the later case the parser tries to guess whether the code is fixed
239 # you also need to set FILE_PATTERNS otherwise the files are not read by doxygen. 275 # or free formatted code, this is the default for Fortran type files), VHDL. For
276 # instance to make doxygen treat .inc files as Fortran files (default is PHP),
277 # and .f files as C (default is Fortran), use: inc=Fortran f=C.
278 #
279 # Note For files without extension you can use no_extension as a placeholder.
280 #
281 # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
282 # the files are not read by doxygen.
240 283
241 EXTENSION_MAPPING = 284 EXTENSION_MAPPING =
242 285
243 # If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all 286 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
244 # comments according to the Markdown format, which allows for more readable 287 # according to the Markdown format, which allows for more readable
245 # documentation. See http://daringfireball.net/projects/markdown/ for details. 288 # documentation. See http://daringfireball.net/projects/markdown/ for details.
246 # The output of markdown processing is further processed by doxygen, so you 289 # The output of markdown processing is further processed by doxygen, so you can
247 # can mix doxygen, HTML, and XML commands with Markdown formatting. 290 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
248 # Disable only in case of backward compatibilities issues. 291 # case of backward compatibilities issues.
292 # The default value is: YES.
249 293
250 MARKDOWN_SUPPORT = YES 294 MARKDOWN_SUPPORT = YES
251 295
296 # When enabled doxygen tries to link words that correspond to documented
297 # classes, or namespaces to their corresponding documentation. Such a link can
298 # be prevented in individual cases by by putting a % sign in front of the word
299 # or globally by setting AUTOLINK_SUPPORT to NO.
300 # The default value is: YES.
301
302 AUTOLINK_SUPPORT = YES
303
252 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 304 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
253 # to include (a tag file for) the STL sources as input, then you should 305 # to include (a tag file for) the STL sources as input, then you should set this
254 # set this tag to YES in order to let doxygen match functions declarations and 306 # tag to YES in order to let doxygen match functions declarations and
255 # definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 307 # definitions whose arguments contain STL classes (e.g. func(std::string);
256 # func(std::string) {}). This also makes the inheritance and collaboration 308 # versus func(std::string) {}). This also make the inheritance and collaboration
257 # diagrams that involve STL classes more complete and accurate. 309 # diagrams that involve STL classes more complete and accurate.
310 # The default value is: NO.
258 311
259 BUILTIN_STL_SUPPORT = YES 312 BUILTIN_STL_SUPPORT = YES
260 313
261 # If you use Microsoft's C++/CLI language, you should set this option to YES to 314 # If you use Microsoft's C++/CLI language, you should set this option to YES to
262 # enable parsing support. 315 # enable parsing support.
316 # The default value is: NO.
263 317
264 CPP_CLI_SUPPORT = NO 318 CPP_CLI_SUPPORT = NO
265 319
266 # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 320 # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
267 # Doxygen will parse them like normal C++ but will assume all classes use public 321 # http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen
268 # instead of private inheritance when no explicit protection keyword is present. 322 # will parse them like normal C++ but will assume all classes use public instead
323 # of private inheritance when no explicit protection keyword is present.
324 # The default value is: NO.
269 325
270 SIP_SUPPORT = NO 326 SIP_SUPPORT = NO
271 327
272 # For Microsoft's IDL there are propget and propput attributes to indicate getter 328 # For Microsoft's IDL there are propget and propput attributes to indicate
273 # and setter methods for a property. Setting this option to YES (the default) 329 # getter and setter methods for a property. Setting this option to YES will make
274 # will make doxygen replace the get and set methods by a property in the 330 # doxygen to replace the get and set methods by a property in the documentation.
275 # documentation. This will only work if the methods are indeed getting or 331 # This will only work if the methods are indeed getting or setting a simple
276 # setting a simple type. If this is not the case, or you want to show the 332 # type. If this is not the case, or you want to show the methods anyway, you
277 # methods anyway, you should set this option to NO. 333 # should set this option to NO.
334 # The default value is: YES.
278 335
279 IDL_PROPERTY_SUPPORT = YES 336 IDL_PROPERTY_SUPPORT = YES
280 337
281 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 338 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
282 # tag is set to YES, then doxygen will reuse the documentation of the first 339 # tag is set to YES, then doxygen will reuse the documentation of the first
283 # member in the group (if any) for the other members of the group. By default 340 # member in the group (if any) for the other members of the group. By default
284 # all members of a group must be documented explicitly. 341 # all members of a group must be documented explicitly.
342 # The default value is: NO.
285 343
286 DISTRIBUTE_GROUP_DOC = NO 344 DISTRIBUTE_GROUP_DOC = NO
287 345
288 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of 346 # Set the SUBGROUPING tag to YES to allow class member groups of the same type
289 # the same type (for instance a group of public functions) to be put as a 347 # (for instance a group of public functions) to be put as a subgroup of that
290 # subgroup of that type (e.g. under the Public Functions section). Set it to 348 # type (e.g. under the Public Functions section). Set it to NO to prevent
291 # NO to prevent subgrouping. Alternatively, this can be done per class using 349 # subgrouping. Alternatively, this can be done per class using the
292 # the \nosubgrouping command. 350 # \nosubgrouping command.
351 # The default value is: YES.
293 352
294 SUBGROUPING = YES 353 SUBGROUPING = YES
295 354
296 # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and 355 # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
297 # unions are shown inside the group in which they are included (e.g. using 356 # are shown inside the group in which they are included (e.g. using \ingroup)
298 # @ingroup) instead of on a separate page (for HTML and Man pages) or 357 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
299 # section (for LaTeX and RTF). 358 # and RTF).
359 #
360 # Note that this feature does not work in combination with
361 # SEPARATE_MEMBER_PAGES.
362 # The default value is: NO.
300 363
301 INLINE_GROUPED_CLASSES = NO 364 INLINE_GROUPED_CLASSES = NO
302 365
303 # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and 366 # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
304 # unions with only public data fields will be shown inline in the documentation 367 # with only public data fields or simple typedef fields will be shown inline in
305 # of the scope in which they are defined (i.e. file, namespace, or group 368 # the documentation of the scope in which they are defined (i.e. file,
306 # documentation), provided this scope is documented. If set to NO (the default), 369 # namespace, or group documentation), provided this scope is documented. If set
307 # structs, classes, and unions are shown on a separate page (for HTML and Man 370 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
308 # pages) or section (for LaTeX and RTF). 371 # Man pages) or section (for LaTeX and RTF).
372 # The default value is: NO.
309 373
310 INLINE_SIMPLE_STRUCTS = NO 374 INLINE_SIMPLE_STRUCTS = NO
311 375
312 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 376 # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
313 # is documented as struct, union, or enum with the name of the typedef. So 377 # enum is documented as struct, union, or enum with the name of the typedef. So
314 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct 378 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
315 # with name TypeT. When disabled the typedef will appear as a member of a file, 379 # with name TypeT. When disabled the typedef will appear as a member of a file,
316 # namespace, or class. And the struct will be named TypeS. This can typically 380 # namespace, or class. And the struct will be named TypeS. This can typically be
317 # be useful for C code in case the coding convention dictates that all compound 381 # useful for C code in case the coding convention dictates that all compound
318 # types are typedef'ed and only the typedef is referenced, never the tag name. 382 # types are typedef'ed and only the typedef is referenced, never the tag name.
383 # The default value is: NO.
319 384
320 TYPEDEF_HIDES_STRUCT = NO 385 TYPEDEF_HIDES_STRUCT = NO
321 386
322 # The SYMBOL_CACHE_SIZE determines the size of the internal cache use to 387 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
323 # determine which symbols to keep in memory and which to flush to disk. 388 # cache is used to resolve symbols given their name and scope. Since this can be
324 # When the cache is full, less often used symbols will be written to disk. 389 # an expensive process and often the same symbol appears multiple times in the
325 # For small to medium size projects (<1000 input files) the default value is 390 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
326 # probably good enough. For larger projects a too small cache size can cause 391 # doxygen will become slower. If the cache is too large, memory is wasted. The
327 # doxygen to be busy swapping symbols to and from disk most of the time 392 # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
328 # causing a significant performance penalty. 393 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
329 # If the system has enough physical memory increasing the cache will improve the 394 # symbols. At the end of a run doxygen will report the cache usage and suggest
330 # performance by keeping more symbols in memory. Note that the value works on 395 # the optimal cache size from a speed point of view.
331 # a logarithmic scale so increasing the size by one will roughly double the 396 # Minimum value: 0, maximum value: 9, default value: 0.
332 # memory usage. The cache size is given by this formula:
333 # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
334 # corresponding to a cache size of 2^16 = 65536 symbols.
335
336 SYMBOL_CACHE_SIZE = 0
337
338 # Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be
339 # set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given
340 # their name and scope. Since this can be an expensive process and often the
341 # same symbol appear multiple times in the code, doxygen keeps a cache of
342 # pre-resolved symbols. If the cache is too small doxygen will become slower.
343 # If the cache is too large, memory is wasted. The cache size is given by this
344 # formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0,
345 # corresponding to a cache size of 2^16 = 65536 symbols.
346 397
347 LOOKUP_CACHE_SIZE = 0 398 LOOKUP_CACHE_SIZE = 0
348 399
349 #--------------------------------------------------------------------------- 400 #---------------------------------------------------------------------------
350 # Build related configuration options 401 # Build related configuration options
351 #--------------------------------------------------------------------------- 402 #---------------------------------------------------------------------------
352 403
353 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 404 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
354 # documentation are documented, even if no documentation was available. 405 # documentation are documented, even if no documentation was available. Private
355 # Private class members and static file members will be hidden unless 406 # class members and static file members will be hidden unless the
356 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES 407 # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
408 # Note: This will also disable the warnings about undocumented members that are
409 # normally produced when WARNINGS is set to YES.
410 # The default value is: NO.
357 411
358 EXTRACT_ALL = NO 412 EXTRACT_ALL = NO
359 413
360 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class 414 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class will
361 # will be included in the documentation. 415 # be included in the documentation.
416 # The default value is: NO.
362 417
363 EXTRACT_PRIVATE = NO 418 EXTRACT_PRIVATE = NO
364 419
365 # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal scope will be included in the documentation. 420 # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
421 # scope will be included in the documentation.
422 # The default value is: NO.
366 423
367 EXTRACT_PACKAGE = NO 424 EXTRACT_PACKAGE = NO
368 425
369 # If the EXTRACT_STATIC tag is set to YES all static members of a file 426 # If the EXTRACT_STATIC tag is set to YES all static members of a file will be
370 # will be included in the documentation. 427 # included in the documentation.
428 # The default value is: NO.
371 429
372 EXTRACT_STATIC = NO 430 EXTRACT_STATIC = NO
373 431
374 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 432 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) defined
375 # defined locally in source files will be included in the documentation. 433 # locally in source files will be included in the documentation. If set to NO
376 # If set to NO only classes defined in header files are included. 434 # only classes defined in header files are included. Does not have any effect
435 # for Java sources.
436 # The default value is: YES.
377 437
378 EXTRACT_LOCAL_CLASSES = YES 438 EXTRACT_LOCAL_CLASSES = YES
379 439
380 # This flag is only useful for Objective-C code. When set to YES local 440 # This flag is only useful for Objective-C code. When set to YES local methods,
381 # methods, which are defined in the implementation section but not in 441 # which are defined in the implementation section but not in the interface are
382 # the interface are included in the documentation. 442 # included in the documentation. If set to NO only methods in the interface are
383 # If set to NO (the default) only methods in the interface are included. 443 # included.
444 # The default value is: NO.
384 445
385 EXTRACT_LOCAL_METHODS = NO 446 EXTRACT_LOCAL_METHODS = NO
386 447
387 # If this flag is set to YES, the members of anonymous namespaces will be 448 # If this flag is set to YES, the members of anonymous namespaces will be
388 # extracted and appear in the documentation as a namespace called 449 # extracted and appear in the documentation as a namespace called
389 # 'anonymous_namespace{file}', where file will be replaced with the base 450 # 'anonymous_namespace{file}', where file will be replaced with the base name of
390 # name of the file that contains the anonymous namespace. By default 451 # the file that contains the anonymous namespace. By default anonymous namespace
391 # anonymous namespaces are hidden. 452 # are hidden.
453 # The default value is: NO.
392 454
393 EXTRACT_ANON_NSPACES = NO 455 EXTRACT_ANON_NSPACES = NO
394 456
395 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 457 # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
396 # undocumented members of documented classes, files or namespaces. 458 # undocumented members inside documented classes or files. If set to NO these
397 # If set to NO (the default) these members will be included in the 459 # members will be included in the various overviews, but no documentation
398 # various overviews, but no documentation section is generated. 460 # section is generated. This option has no effect if EXTRACT_ALL is enabled.
399 # This option has no effect if EXTRACT_ALL is enabled. 461 # The default value is: NO.
400 462
401 HIDE_UNDOC_MEMBERS = NO 463 HIDE_UNDOC_MEMBERS = NO
402 464
403 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 465 # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
404 # undocumented classes that are normally visible in the class hierarchy. 466 # undocumented classes that are normally visible in the class hierarchy. If set
405 # If set to NO (the default) these classes will be included in the various 467 # to NO these classes will be included in the various overviews. This option has
406 # overviews. This option has no effect if EXTRACT_ALL is enabled. 468 # no effect if EXTRACT_ALL is enabled.
469 # The default value is: NO.
407 470
408 HIDE_UNDOC_CLASSES = NO 471 HIDE_UNDOC_CLASSES = NO
409 472
410 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 473 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
411 # friend (class|struct|union) declarations. 474 # (class|struct|union) declarations. If set to NO these declarations will be
412 # If set to NO (the default) these declarations will be included in the 475 # included in the documentation.
413 # documentation. 476 # The default value is: NO.
414 477
415 HIDE_FRIEND_COMPOUNDS = YES 478 HIDE_FRIEND_COMPOUNDS = YES
416 479
417 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 480 # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
418 # documentation blocks found inside the body of a function. 481 # documentation blocks found inside the body of a function. If set to NO these
419 # If set to NO (the default) these blocks will be appended to the 482 # blocks will be appended to the function's detailed documentation block.
420 # function's detailed documentation block. 483 # The default value is: NO.
421 484
422 HIDE_IN_BODY_DOCS = NO 485 HIDE_IN_BODY_DOCS = NO
423 486
424 # The INTERNAL_DOCS tag determines if documentation 487 # The INTERNAL_DOCS tag determines if documentation that is typed after a
425 # that is typed after a \internal command is included. If the tag is set 488 # \internal command is included. If the tag is set to NO then the documentation
426 # to NO (the default) then the documentation will be excluded. 489 # will be excluded. Set it to YES to include the internal documentation.
427 # Set it to YES to include the internal documentation. 490 # The default value is: NO.
428 491
429 INTERNAL_DOCS = NO 492 INTERNAL_DOCS = NO
430 493
431 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 494 # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
432 # file names in lower-case letters. If set to YES upper-case letters are also 495 # names in lower-case letters. If set to YES upper-case letters are also
433 # allowed. This is useful if you have classes or files whose names only differ 496 # allowed. This is useful if you have classes or files whose names only differ
434 # in case and if your file system supports case sensitive file names. Windows 497 # in case and if your file system supports case sensitive file names. Windows
435 # and Mac users are advised to set this option to NO. 498 # and Mac users are advised to set this option to NO.
499 # The default value is: system dependent.
436 500
437 CASE_SENSE_NAMES = YES 501 CASE_SENSE_NAMES = YES
438 502
439 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 503 # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
440 # will show members with their full class and namespace scopes in the 504 # their full class and namespace scopes in the documentation. If set to YES the
441 # documentation. If set to YES the scope will be hidden. 505 # scope will be hidden.
506 # The default value is: NO.
442 507
443 HIDE_SCOPE_NAMES = NO 508 HIDE_SCOPE_NAMES = NO
444 509
445 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 510 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
446 # will put a list of the files that are included by a file in the documentation 511 # the files that are included by a file in the documentation of that file.
447 # of that file. 512 # The default value is: YES.
448 513
449 SHOW_INCLUDE_FILES = YES 514 SHOW_INCLUDE_FILES = YES
450 515
451 # If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen 516 # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
452 # will list include files with double quotes in the documentation 517 # grouped member an include statement to the documentation, telling the reader
453 # rather than with sharp brackets. 518 # which file to include in order to use the member.
519 # The default value is: NO.
520
521 SHOW_GROUPED_MEMB_INC = NO
522
523 # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
524 # files with double quotes in the documentation rather than with sharp brackets.
525 # The default value is: NO.
454 526
455 FORCE_LOCAL_INCLUDES = NO 527 FORCE_LOCAL_INCLUDES = NO
456 528
457 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 529 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
458 # is inserted in the documentation for inline members. 530 # documentation for inline members.
531 # The default value is: YES.
459 532
460 INLINE_INFO = YES 533 INLINE_INFO = YES
461 534
462 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 535 # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
463 # will sort the (detailed) documentation of file and class members 536 # (detailed) documentation of file and class members alphabetically by member
464 # alphabetically by member name. If set to NO the members will appear in 537 # name. If set to NO the members will appear in declaration order.
465 # declaration order. 538 # The default value is: YES.
466 539
467 SORT_MEMBER_DOCS = YES 540 SORT_MEMBER_DOCS = YES
468 541
469 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 542 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
470 # brief documentation of file, namespace and class members alphabetically 543 # descriptions of file, namespace and class members alphabetically by member
471 # by member name. If set to NO (the default) the members will appear in 544 # name. If set to NO the members will appear in declaration order. Note that
472 # declaration order. 545 # this will also influence the order of the classes in the class list.
546 # The default value is: NO.
473 547
474 SORT_BRIEF_DOCS = NO 548 SORT_BRIEF_DOCS = NO
475 549
476 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen 550 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
477 # will sort the (brief and detailed) documentation of class members so that 551 # (brief and detailed) documentation of class members so that constructors and
478 # constructors and destructors are listed first. If set to NO (the default) 552 # destructors are listed first. If set to NO the constructors will appear in the
479 # the constructors will appear in the respective orders defined by 553 # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
480 # SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. 554 # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
481 # This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO 555 # member documentation.
482 # and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO. 556 # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
557 # detailed member documentation.
558 # The default value is: NO.
483 559
484 SORT_MEMBERS_CTORS_1ST = NO 560 SORT_MEMBERS_CTORS_1ST = NO
485 561
486 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 562 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
487 # hierarchy of group names into alphabetical order. If set to NO (the default) 563 # of group names into alphabetical order. If set to NO the group names will
488 # the group names will appear in their defined order. 564 # appear in their defined order.
565 # The default value is: NO.
489 566
490 SORT_GROUP_NAMES = NO 567 SORT_GROUP_NAMES = NO
491 568
492 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 569 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
493 # sorted by fully-qualified names, including namespaces. If set to 570 # fully-qualified names, including namespaces. If set to NO, the class list will
494 # NO (the default), the class list will be sorted only by class name, 571 # be sorted only by class name, not including the namespace part.
495 # not including the namespace part.
496 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 572 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
497 # Note: This option applies only to the class list, not to the 573 # Note: This option applies only to the class list, not to the alphabetical
498 # alphabetical list. 574 # list.
575 # The default value is: NO.
499 576
500 SORT_BY_SCOPE_NAME = NO 577 SORT_BY_SCOPE_NAME = NO
501 578
502 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to 579 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
503 # do proper type resolution of all parameters of a function it will reject a 580 # type resolution of all parameters of a function it will reject a match between
504 # match between the prototype and the implementation of a member function even 581 # the prototype and the implementation of a member function even if there is
505 # if there is only one candidate or it is obvious which candidate to choose 582 # only one candidate or it is obvious which candidate to choose by doing a
506 # by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen 583 # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
507 # will still accept a match between prototype and implementation in such cases. 584 # accept a match between prototype and implementation in such cases.
585 # The default value is: NO.
508 586
509 STRICT_PROTO_MATCHING = NO 587 STRICT_PROTO_MATCHING = NO
510 588
511 # The GENERATE_TODOLIST tag can be used to enable (YES) or 589 # The GENERATE_TODOLIST tag can be used to enable ( YES) or disable ( NO) the
512 # disable (NO) the todo list. This list is created by putting \todo 590 # todo list. This list is created by putting \todo commands in the
513 # commands in the documentation. 591 # documentation.
592 # The default value is: YES.
514 593
515 GENERATE_TODOLIST = YES 594 GENERATE_TODOLIST = YES
516 595
517 # The GENERATE_TESTLIST tag can be used to enable (YES) or 596 # The GENERATE_TESTLIST tag can be used to enable ( YES) or disable ( NO) the
518 # disable (NO) the test list. This list is created by putting \test 597 # test list. This list is created by putting \test commands in the
519 # commands in the documentation. 598 # documentation.
599 # The default value is: YES.
520 600
521 GENERATE_TESTLIST = YES 601 GENERATE_TESTLIST = YES
522 602
523 # The GENERATE_BUGLIST tag can be used to enable (YES) or 603 # The GENERATE_BUGLIST tag can be used to enable ( YES) or disable ( NO) the bug
524 # disable (NO) the bug list. This list is created by putting \bug 604 # list. This list is created by putting \bug commands in the documentation.
525 # commands in the documentation. 605 # The default value is: YES.
526 606
527 GENERATE_BUGLIST = YES 607 GENERATE_BUGLIST = YES
528 608
529 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 609 # The GENERATE_DEPRECATEDLIST tag can be used to enable ( YES) or disable ( NO)
530 # disable (NO) the deprecated list. This list is created by putting 610 # the deprecated list. This list is created by putting \deprecated commands in
531 # \deprecated commands in the documentation. 611 # the documentation.
612 # The default value is: YES.
532 613
533 GENERATE_DEPRECATEDLIST= YES 614 GENERATE_DEPRECATEDLIST= YES
534 615
535 # The ENABLED_SECTIONS tag can be used to enable conditional 616 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
536 # documentation sections, marked by \if sectionname ... \endif. 617 # sections, marked by \if <section_label> ... \endif and \cond <section_label>
618 # ... \endcond blocks.
537 619
538 ENABLED_SECTIONS = 620 ENABLED_SECTIONS =
539 621
540 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines 622 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
541 # the initial value of a variable or macro consists of for it to appear in 623 # initial value of a variable or macro / define can have for it to appear in the
542 # the documentation. If the initializer consists of more lines than specified 624 # documentation. If the initializer consists of more lines than specified here
543 # here it will be hidden. Use a value of 0 to hide initializers completely. 625 # it will be hidden. Use a value of 0 to hide initializers completely. The
544 # The appearance of the initializer of individual variables and macros in the 626 # appearance of the value of individual variables and macros / defines can be
545 # documentation can be controlled using \showinitializer or \hideinitializer 627 # controlled using \showinitializer or \hideinitializer command in the
546 # command in the documentation regardless of this setting. 628 # documentation regardless of this setting.
629 # Minimum value: 0, maximum value: 10000, default value: 30.
547 630
548 MAX_INITIALIZER_LINES = 0 631 MAX_INITIALIZER_LINES = 0
549 632
550 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated 633 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
551 # at the bottom of the documentation of classes and structs. If set to YES the 634 # the bottom of the documentation of classes and structs. If set to YES the list
552 # list will mention the files that were used to generate the documentation. 635 # will mention the files that were used to generate the documentation.
636 # The default value is: YES.
553 637
554 SHOW_USED_FILES = YES 638 SHOW_USED_FILES = YES
555 639
556 # Set the SHOW_FILES tag to NO to disable the generation of the Files page. 640 # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
557 # This will remove the Files entry from the Quick Index and from the 641 # will remove the Files entry from the Quick Index and from the Folder Tree View
558 # Folder Tree View (if specified). The default is YES. 642 # (if specified).
643 # The default value is: YES.
559 644
560 SHOW_FILES = YES 645 SHOW_FILES = YES
561 646
562 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the 647 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
563 # Namespaces page. 648 # page. This will remove the Namespaces entry from the Quick Index and from the
564 # This will remove the Namespaces entry from the Quick Index 649 # Folder Tree View (if specified).
565 # and from the Folder Tree View (if specified). The default is YES. 650 # The default value is: YES.
566 651
567 SHOW_NAMESPACES = YES 652 SHOW_NAMESPACES = YES
568 653
569 # The FILE_VERSION_FILTER tag can be used to specify a program or script that 654 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
570 # doxygen should invoke to get the current version for each file (typically from 655 # doxygen should invoke to get the current version for each file (typically from
571 # the version control system). Doxygen will invoke the program by executing (via 656 # the version control system). Doxygen will invoke the program by executing (via
572 # popen()) the command <command> <input-file>, where <command> is the value of 657 # popen()) the command command input-file, where command is the value of the
573 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 658 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
574 # provided by doxygen. Whatever the program writes to standard output 659 # by doxygen. Whatever the program writes to standard output is used as the file
575 # is used as the file version. See the manual for examples. 660 # version. For an example see the documentation.
576 661
577 FILE_VERSION_FILTER = 662 FILE_VERSION_FILTER =
578 663
579 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed 664 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
580 # by doxygen. The layout file controls the global structure of the generated 665 # by doxygen. The layout file controls the global structure of the generated
581 # output files in an output format independent way. To create the layout file 666 # output files in an output format independent way. To create the layout file
582 # that represents doxygen's defaults, run doxygen with the -l option. 667 # that represents doxygen's defaults, run doxygen with the -l option. You can
583 # You can optionally specify a file name after the option, if omitted 668 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
584 # DoxygenLayout.xml will be used as the name of the layout file. 669 # will be used as the name of the layout file.
670 #
671 # Note that if you run doxygen from a directory containing a file called
672 # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
673 # tag is left empty.
585 674
586 LAYOUT_FILE = 675 LAYOUT_FILE =
587 676
588 # The CITE_BIB_FILES tag can be used to specify one or more bib files 677 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
589 # containing the references data. This must be a list of .bib files. The 678 # the reference definitions. This must be a list of .bib files. The .bib
590 # .bib extension is automatically appended if omitted. Using this command 679 # extension is automatically appended if omitted. This requires the bibtex tool
591 # requires the bibtex tool to be installed. See also 680 # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
592 # http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style 681 # For LaTeX the style of the bibliography can be controlled using
593 # of the bibliography can be controlled using LATEX_BIB_STYLE. To use this 682 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
594 # feature you need bibtex and perl available in the search path. 683 # search path. Do not use file names with spaces, bibtex cannot handle them. See
684 # also \cite for info how to create references.
595 685
596 CITE_BIB_FILES = 686 CITE_BIB_FILES =
597 687
598 #--------------------------------------------------------------------------- 688 #---------------------------------------------------------------------------
599 # configuration options related to warning and progress messages 689 # Configuration options related to warning and progress messages
600 #--------------------------------------------------------------------------- 690 #---------------------------------------------------------------------------
601 691
602 # The QUIET tag can be used to turn on/off the messages that are generated 692 # The QUIET tag can be used to turn on/off the messages that are generated to
603 # by doxygen. Possible values are YES and NO. If left blank NO is used. 693 # standard output by doxygen. If QUIET is set to YES this implies that the
694 # messages are off.
695 # The default value is: NO.
604 696
605 QUIET = NO 697 QUIET = NO
606 698
607 # The WARNINGS tag can be used to turn on/off the warning messages that are 699 # The WARNINGS tag can be used to turn on/off the warning messages that are
608 # generated by doxygen. Possible values are YES and NO. If left blank 700 # generated to standard error ( stderr) by doxygen. If WARNINGS is set to YES
609 # NO is used. 701 # this implies that the warnings are on.
702 #
703 # Tip: Turn warnings on while writing the documentation.
704 # The default value is: YES.
610 705
611 WARNINGS = YES 706 WARNINGS = YES
612 707
613 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 708 # If the WARN_IF_UNDOCUMENTED tag is set to YES, then doxygen will generate
614 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will 709 # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
615 # automatically be disabled. 710 # will automatically be disabled.
711 # The default value is: YES.
616 712
617 WARN_IF_UNDOCUMENTED = YES 713 WARN_IF_UNDOCUMENTED = YES
618 714
619 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 715 # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
620 # potential errors in the documentation, such as not documenting some 716 # potential errors in the documentation, such as not documenting some parameters
621 # parameters in a documented function, or documenting parameters that 717 # in a documented function, or documenting parameters that don't exist or using
622 # don't exist or using markup commands wrongly. 718 # markup commands wrongly.
719 # The default value is: YES.
623 720
624 WARN_IF_DOC_ERROR = YES 721 WARN_IF_DOC_ERROR = YES
625 722
626 # The WARN_NO_PARAMDOC option can be enabled to get warnings for 723 # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
627 # functions that are documented, but have no documentation for their parameters 724 # are documented, but have no documentation for their parameters or return
628 # or return value. If set to NO (the default) doxygen will only warn about 725 # value. If set to NO doxygen will only warn about wrong or incomplete parameter
629 # wrong or incomplete parameter documentation, but not about the absence of 726 # documentation, but not about the absence of documentation.
630 # documentation. 727 # The default value is: NO.
631 728
632 WARN_NO_PARAMDOC = YES 729 WARN_NO_PARAMDOC = YES
633 730
634 # The WARN_FORMAT tag determines the format of the warning messages that 731 # The WARN_FORMAT tag determines the format of the warning messages that doxygen
635 # doxygen can produce. The string should contain the $file, $line, and $text 732 # can produce. The string should contain the $file, $line, and $text tags, which
636 # tags, which will be replaced by the file and line number from which the 733 # will be replaced by the file and line number from which the warning originated
637 # warning originated and the warning text. Optionally the format may contain 734 # and the warning text. Optionally the format may contain $version, which will
638 # $version, which will be replaced by the version of the file (if it could 735 # be replaced by the version of the file (if it could be obtained via
639 # be obtained via FILE_VERSION_FILTER) 736 # FILE_VERSION_FILTER)
737 # The default value is: $file:$line: $text.
640 738
641 WARN_FORMAT = "$file:$line: $text" 739 WARN_FORMAT = "$file:$line: $text"
642 740
643 # The WARN_LOGFILE tag can be used to specify a file to which warning 741 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
644 # and error messages should be written. If left blank the output is written 742 # messages should be written. If left blank the output is written to standard
645 # to stderr. 743 # error (stderr).
646 744
647 WARN_LOGFILE = 745 WARN_LOGFILE =
648 746
649 #--------------------------------------------------------------------------- 747 #---------------------------------------------------------------------------
650 # configuration options related to the input files 748 # Configuration options related to the input files
651 #--------------------------------------------------------------------------- 749 #---------------------------------------------------------------------------
652 750
653 # The INPUT tag can be used to specify the files and/or directories that contain 751 # The INPUT tag is used to specify the files and/or directories that contain
654 # documented source files. You may enter file names like "myfile.cpp" or 752 # documented source files. You may enter file names like myfile.cpp or
655 # directories like "/usr/src/myproject". Separate the files or directories 753 # directories like /usr/src/myproject. Separate the files or directories with
656 # with spaces. 754 # spaces.
755 # Note: If this tag is empty the current directory is searched.
657 756
658 INPUT = @CMAKE_SOURCE_DIR@/Plugins/Include/orthanc/OrthancCPlugin.h \ 757 INPUT = @CMAKE_SOURCE_DIR@/Plugins/Include/orthanc/OrthancCPlugin.h \
659 @CMAKE_SOURCE_DIR@/Plugins/Include/orthanc/OrthancCDatabasePlugin.h \ 758 @CMAKE_SOURCE_DIR@/Plugins/Include/orthanc/OrthancCDatabasePlugin.h \
660 @CMAKE_SOURCE_DIR@/Plugins/Include/orthanc/OrthancCppDatabasePlugin.h 759 @CMAKE_SOURCE_DIR@/Plugins/Include/orthanc/OrthancCppDatabasePlugin.h
661 760
662 # This tag can be used to specify the character encoding of the source files 761 # This tag can be used to specify the character encoding of the source files
663 # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is 762 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
664 # also the default input encoding. Doxygen uses libiconv (or the iconv built 763 # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
665 # into libc) for the transcoding. See http://www.gnu.org/software/libiconv for 764 # documentation (see: http://www.gnu.org/software/libiconv) for the list of
666 # the list of possible encodings. 765 # possible encodings.
766 # The default value is: UTF-8.
667 767
668 INPUT_ENCODING = UTF-8 768 INPUT_ENCODING = UTF-8
669 769
670 # If the value of the INPUT tag contains directories, you can use the 770 # If the value of the INPUT tag contains directories, you can use the
671 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 771 # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
672 # and *.h) to filter out the source-files in the directories. If left 772 # *.h) to filter out the source-files in the directories. If left blank the
673 # blank the following patterns are tested: 773 # following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii,
674 # *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh 774 # *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp,
675 # *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py 775 # *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown,
676 # *.f90 *.f *.for *.vhd *.vhdl 776 # *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf,
777 # *.qsf, *.as and *.js.
677 778
678 FILE_PATTERNS = *.h 779 FILE_PATTERNS = *.h
679 780
680 # The RECURSIVE tag can be used to turn specify whether or not subdirectories 781 # The RECURSIVE tag can be used to specify whether or not subdirectories should
681 # should be searched for input files as well. Possible values are YES and NO. 782 # be searched for input files as well.
682 # If left blank NO is used. 783 # The default value is: NO.
683 784
684 RECURSIVE = YES 785 RECURSIVE = YES
685 786
686 # The EXCLUDE tag can be used to specify files and/or directories that should be 787 # The EXCLUDE tag can be used to specify files and/or directories that should be
687 # excluded from the INPUT source files. This way you can easily exclude a 788 # excluded from the INPUT source files. This way you can easily exclude a
688 # subdirectory from a directory tree whose root is specified with the INPUT tag. 789 # subdirectory from a directory tree whose root is specified with the INPUT tag.
790 #
689 # Note that relative paths are relative to the directory from which doxygen is 791 # Note that relative paths are relative to the directory from which doxygen is
690 # run. 792 # run.
691 793
692 EXCLUDE = 794 EXCLUDE =
693 795
694 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or 796 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
695 # directories that are symbolic links (a Unix file system feature) are excluded 797 # directories that are symbolic links (a Unix file system feature) are excluded
696 # from the input. 798 # from the input.
799 # The default value is: NO.
697 800
698 EXCLUDE_SYMLINKS = NO 801 EXCLUDE_SYMLINKS = NO
699 802
700 # If the value of the INPUT tag contains directories, you can use the 803 # If the value of the INPUT tag contains directories, you can use the
701 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 804 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
702 # certain files from those directories. Note that the wildcards are matched 805 # certain files from those directories.
703 # against the file with absolute path, so to exclude all test directories 806 #
704 # for example use the pattern */test/* 807 # Note that the wildcards are matched against the file with absolute path, so to
808 # exclude all test directories for example use the pattern */test/*
705 809
706 EXCLUDE_PATTERNS = 810 EXCLUDE_PATTERNS =
707 811
708 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 812 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
709 # (namespaces, classes, functions, etc.) that should be excluded from the 813 # (namespaces, classes, functions, etc.) that should be excluded from the
710 # output. The symbol name can be a fully qualified name, a word, or if the 814 # output. The symbol name can be a fully qualified name, a word, or if the
711 # wildcard * is used, a substring. Examples: ANamespace, AClass, 815 # wildcard * is used, a substring. Examples: ANamespace, AClass,
712 # AClass::ANamespace, ANamespace::*Test 816 # AClass::ANamespace, ANamespace::*Test
713 817 #
714 EXCLUDE_SYMBOLS = _OrthancPlugin* OrthancPluginGetName 818 # Note that the wildcards are matched against the file with absolute path, so to
715 819 # exclude all test directories use the pattern */test/*
716 # The EXAMPLE_PATH tag can be used to specify one or more files or 820
717 # directories that contain example code fragments that are included (see 821 EXCLUDE_SYMBOLS = _OrthancPlugin* \
718 # the \include command). 822 OrthancPluginGetName
823
824 # The EXAMPLE_PATH tag can be used to specify one or more files or directories
825 # that contain example code fragments that are included (see the \include
826 # command).
719 827
720 EXAMPLE_PATH = 828 EXAMPLE_PATH =
721 829
722 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 830 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
723 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 831 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
724 # and *.h) to filter out the source-files in the directories. If left 832 # *.h) to filter out the source-files in the directories. If left blank all
725 # blank all files are included. 833 # files are included.
726 834
727 EXAMPLE_PATTERNS = 835 EXAMPLE_PATTERNS =
728 836
729 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 837 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
730 # searched for input files to be used with the \include or \dontinclude 838 # searched for input files to be used with the \include or \dontinclude commands
731 # commands irrespective of the value of the RECURSIVE tag. 839 # irrespective of the value of the RECURSIVE tag.
732 # Possible values are YES and NO. If left blank NO is used. 840 # The default value is: NO.
733 841
734 EXAMPLE_RECURSIVE = NO 842 EXAMPLE_RECURSIVE = NO
735 843
736 # The IMAGE_PATH tag can be used to specify one or more files or 844 # The IMAGE_PATH tag can be used to specify one or more files or directories
737 # directories that contain image that are included in the documentation (see 845 # that contain images that are to be included in the documentation (see the
738 # the \image command). 846 # \image command).
739 847
740 IMAGE_PATH = 848 IMAGE_PATH =
741 849
742 # The INPUT_FILTER tag can be used to specify a program that doxygen should 850 # The INPUT_FILTER tag can be used to specify a program that doxygen should
743 # invoke to filter for each input file. Doxygen will invoke the filter program 851 # invoke to filter for each input file. Doxygen will invoke the filter program
744 # by executing (via popen()) the command <filter> <input-file>, where <filter> 852 # by executing (via popen()) the command:
745 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an 853 #
746 # input file. Doxygen will then use the output that the filter program writes 854 # <filter> <input-file>
747 # to standard output. 855 #
748 # If FILTER_PATTERNS is specified, this tag will be 856 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
749 # ignored. 857 # name of an input file. Doxygen will then use the output that the filter
858 # program writes to standard output. If FILTER_PATTERNS is specified, this tag
859 # will be ignored.
860 #
861 # Note that the filter must not add or remove lines; it is applied before the
862 # code is scanned, but not when the output code is generated. If lines are added
863 # or removed, the anchors will not be placed correctly.
750 864
751 INPUT_FILTER = 865 INPUT_FILTER =
752 866
753 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 867 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
754 # basis. 868 # basis. Doxygen will compare the file name with each pattern and apply the
755 # Doxygen will compare the file name with each pattern and apply the 869 # filter if there is a match. The filters are a list of the form: pattern=filter
756 # filter if there is a match. 870 # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
757 # The filters are a list of the form: 871 # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
758 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 872 # patterns match the file name, INPUT_FILTER is applied.
759 # info on how filters are used. If FILTER_PATTERNS is empty or if
760 # non of the patterns match the file name, INPUT_FILTER is applied.
761 873
762 FILTER_PATTERNS = 874 FILTER_PATTERNS =
763 875
764 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 876 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
765 # INPUT_FILTER) will be used to filter the input files when producing source 877 # INPUT_FILTER ) will also be used to filter the input files that are used for
766 # files to browse (i.e. when SOURCE_BROWSER is set to YES). 878 # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
879 # The default value is: NO.
767 880
768 FILTER_SOURCE_FILES = NO 881 FILTER_SOURCE_FILES = NO
769 882
770 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file 883 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
771 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) 884 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
772 # and it is also possible to disable source filtering for a specific pattern 885 # it is also possible to disable source filtering for a specific pattern using
773 # using *.ext= (so without naming a filter). This option only has effect when 886 # *.ext= (so without naming a filter).
774 # FILTER_SOURCE_FILES is enabled. 887 # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
775 888
776 FILTER_SOURCE_PATTERNS = 889 FILTER_SOURCE_PATTERNS =
777 890
778 #--------------------------------------------------------------------------- 891 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
779 # configuration options related to source browsing 892 # is part of the input, its contents will be placed on the main page
780 #--------------------------------------------------------------------------- 893 # (index.html). This can be useful if you have a project on for instance GitHub
781 894 # and want to reuse the introduction page also for the doxygen output.
782 # If the SOURCE_BROWSER tag is set to YES then a list of source files will 895
783 # be generated. Documented entities will be cross-referenced with these sources. 896 USE_MDFILE_AS_MAINPAGE =
784 # Note: To get rid of all source code in the generated output, make sure also 897
785 # VERBATIM_HEADERS is set to NO. 898 #---------------------------------------------------------------------------
899 # Configuration options related to source browsing
900 #---------------------------------------------------------------------------
901
902 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
903 # generated. Documented entities will be cross-referenced with these sources.
904 #
905 # Note: To get rid of all source code in the generated output, make sure that
906 # also VERBATIM_HEADERS is set to NO.
907 # The default value is: NO.
786 908
787 SOURCE_BROWSER = NO 909 SOURCE_BROWSER = NO
788 910
789 # Setting the INLINE_SOURCES tag to YES will include the body 911 # Setting the INLINE_SOURCES tag to YES will include the body of functions,
790 # of functions and classes directly in the documentation. 912 # classes and enums directly into the documentation.
913 # The default value is: NO.
791 914
792 INLINE_SOURCES = NO 915 INLINE_SOURCES = NO
793 916
794 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 917 # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
795 # doxygen to hide any special comment blocks from generated source code 918 # special comment blocks from generated source code fragments. Normal C, C++ and
796 # fragments. Normal C, C++ and Fortran comments will always remain visible. 919 # Fortran comments will always remain visible.
920 # The default value is: YES.
797 921
798 STRIP_CODE_COMMENTS = YES 922 STRIP_CODE_COMMENTS = YES
799 923
800 # If the REFERENCED_BY_RELATION tag is set to YES 924 # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
801 # then for each documented function all documented 925 # function all documented functions referencing it will be listed.
802 # functions referencing it will be listed. 926 # The default value is: NO.
803 927
804 REFERENCED_BY_RELATION = NO 928 REFERENCED_BY_RELATION = NO
805 929
806 # If the REFERENCES_RELATION tag is set to YES 930 # If the REFERENCES_RELATION tag is set to YES then for each documented function
807 # then for each documented function all documented entities 931 # all documented entities called/used by that function will be listed.
808 # called/used by that function will be listed. 932 # The default value is: NO.
809 933
810 REFERENCES_RELATION = NO 934 REFERENCES_RELATION = NO
811 935
812 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 936 # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
813 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 937 # to YES, then the hyperlinks from functions in REFERENCES_RELATION and
814 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 938 # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
815 # link to the source code. 939 # link to the documentation.
816 # Otherwise they will link to the documentation. 940 # The default value is: YES.
817 941
818 REFERENCES_LINK_SOURCE = YES 942 REFERENCES_LINK_SOURCE = YES
819 943
820 # If the USE_HTAGS tag is set to YES then the references to source code 944 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
821 # will point to the HTML generated by the htags(1) tool instead of doxygen 945 # source code will show a tooltip with additional information such as prototype,
822 # built-in source browser. The htags tool is part of GNU's global source 946 # brief description and links to the definition and documentation. Since this
823 # tagging system (see http://www.gnu.org/software/global/global.html). You 947 # will make the HTML file larger and loading of large files a bit slower, you
824 # will need version 4.8.6 or higher. 948 # can opt to disable this feature.
949 # The default value is: YES.
950 # This tag requires that the tag SOURCE_BROWSER is set to YES.
951
952 SOURCE_TOOLTIPS = YES
953
954 # If the USE_HTAGS tag is set to YES then the references to source code will
955 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
956 # source browser. The htags tool is part of GNU's global source tagging system
957 # (see http://www.gnu.org/software/global/global.html). You will need version
958 # 4.8.6 or higher.
959 #
960 # To use it do the following:
961 # - Install the latest version of global
962 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
963 # - Make sure the INPUT points to the root of the source tree
964 # - Run doxygen as normal
965 #
966 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
967 # tools must be available from the command line (i.e. in the search path).
968 #
969 # The result: instead of the source browser generated by doxygen, the links to
970 # source code will now point to the output of htags.
971 # The default value is: NO.
972 # This tag requires that the tag SOURCE_BROWSER is set to YES.
825 973
826 USE_HTAGS = NO 974 USE_HTAGS = NO
827 975
828 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 976 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
829 # will generate a verbatim copy of the header file for each class for 977 # verbatim copy of the header file for each class for which an include is
830 # which an include is specified. Set to NO to disable this. 978 # specified. Set to NO to disable this.
979 # See also: Section \class.
980 # The default value is: YES.
831 981
832 VERBATIM_HEADERS = YES 982 VERBATIM_HEADERS = YES
833 983
834 #--------------------------------------------------------------------------- 984 #---------------------------------------------------------------------------
835 # configuration options related to the alphabetical class index 985 # Configuration options related to the alphabetical class index
836 #--------------------------------------------------------------------------- 986 #---------------------------------------------------------------------------
837 987
838 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 988 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
839 # of all compounds will be generated. Enable this if the project 989 # compounds will be generated. Enable this if the project contains a lot of
840 # contains a lot of classes, structs, unions or interfaces. 990 # classes, structs, unions or interfaces.
991 # The default value is: YES.
841 992
842 ALPHABETICAL_INDEX = YES 993 ALPHABETICAL_INDEX = YES
843 994
844 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 995 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
845 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 996 # which the alphabetical index list will be split.
846 # in which this list will be split (can be a number in the range [1..20]) 997 # Minimum value: 1, maximum value: 20, default value: 5.
998 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
847 999
848 COLS_IN_ALPHA_INDEX = 5 1000 COLS_IN_ALPHA_INDEX = 5
849 1001
850 # In case all classes in a project start with a common prefix, all 1002 # In case all classes in a project start with a common prefix, all classes will
851 # classes will be put under the same header in the alphabetical index. 1003 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
852 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that 1004 # can be used to specify a prefix (or a list of prefixes) that should be ignored
853 # should be ignored while generating the index headers. 1005 # while generating the index headers.
1006 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
854 1007
855 IGNORE_PREFIX = 1008 IGNORE_PREFIX =
856 1009
857 #--------------------------------------------------------------------------- 1010 #---------------------------------------------------------------------------
858 # configuration options related to the HTML output 1011 # Configuration options related to the HTML output
859 #--------------------------------------------------------------------------- 1012 #---------------------------------------------------------------------------
860 1013
861 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will 1014 # If the GENERATE_HTML tag is set to YES doxygen will generate HTML output
862 # generate HTML output. 1015 # The default value is: YES.
863 1016
864 GENERATE_HTML = YES 1017 GENERATE_HTML = YES
865 1018
866 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 1019 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
867 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1020 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
868 # put in front of it. If left blank `html' will be used as the default path. 1021 # it.
1022 # The default directory is: html.
1023 # This tag requires that the tag GENERATE_HTML is set to YES.
869 1024
870 HTML_OUTPUT = doc 1025 HTML_OUTPUT = doc
871 1026
872 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for 1027 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
873 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank 1028 # generated HTML page (for example: .htm, .php, .asp).
874 # doxygen will generate files with .html extension. 1029 # The default value is: .html.
1030 # This tag requires that the tag GENERATE_HTML is set to YES.
875 1031
876 HTML_FILE_EXTENSION = .html 1032 HTML_FILE_EXTENSION = .html
877 1033
878 # The HTML_HEADER tag can be used to specify a personal HTML header for 1034 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
879 # each generated HTML page. If it is left blank doxygen will generate a 1035 # each generated HTML page. If the tag is left blank doxygen will generate a
880 # standard header. Note that when using a custom header you are responsible 1036 # standard header.
881 # for the proper inclusion of any scripts and style sheets that doxygen 1037 #
882 # needs, which is dependent on the configuration options used. 1038 # To get valid HTML the header file that includes any scripts and style sheets
883 # It is advised to generate a default header using "doxygen -w html 1039 # that doxygen needs, which is dependent on the configuration options used (e.g.
884 # header.html footer.html stylesheet.css YourConfigFile" and then modify 1040 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
885 # that header. Note that the header is subject to change so you typically 1041 # default header using
886 # have to redo this when upgrading to a newer version of doxygen or when 1042 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
887 # changing the value of configuration settings such as GENERATE_TREEVIEW! 1043 # YourConfigFile
1044 # and then modify the file new_header.html. See also section "Doxygen usage"
1045 # for information on how to generate the default header that doxygen normally
1046 # uses.
1047 # Note: The header is subject to change so you typically have to regenerate the
1048 # default header when upgrading to a newer version of doxygen. For a description
1049 # of the possible markers and block names see the documentation.
1050 # This tag requires that the tag GENERATE_HTML is set to YES.
888 1051
889 HTML_HEADER = 1052 HTML_HEADER =
890 1053
891 # The HTML_FOOTER tag can be used to specify a personal HTML footer for 1054 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
892 # each generated HTML page. If it is left blank doxygen will generate a 1055 # generated HTML page. If the tag is left blank doxygen will generate a standard
893 # standard footer. 1056 # footer. See HTML_HEADER for more information on how to generate a default
1057 # footer and what special commands can be used inside the footer. See also
1058 # section "Doxygen usage" for information on how to generate the default footer
1059 # that doxygen normally uses.
1060 # This tag requires that the tag GENERATE_HTML is set to YES.
894 1061
895 HTML_FOOTER = 1062 HTML_FOOTER =
896 1063
897 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading 1064 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
898 # style sheet that is used by each HTML page. It can be used to 1065 # sheet that is used by each HTML page. It can be used to fine-tune the look of
899 # fine-tune the look of the HTML output. If the tag is left blank doxygen 1066 # the HTML output. If left blank doxygen will generate a default style sheet.
900 # will generate a default style sheet. Note that doxygen will try to copy 1067 # See also section "Doxygen usage" for information on how to generate the style
901 # the style sheet file to the HTML output directory, so don't put your own 1068 # sheet that doxygen normally uses.
902 # style sheet in the HTML output directory as well, or it will be erased! 1069 # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
1070 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1071 # obsolete.
1072 # This tag requires that the tag GENERATE_HTML is set to YES.
903 1073
904 HTML_STYLESHEET = 1074 HTML_STYLESHEET =
1075
1076 # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
1077 # defined cascading style sheet that is included after the standard style sheets
1078 # created by doxygen. Using this option one can overrule certain style aspects.
1079 # This is preferred over using HTML_STYLESHEET since it does not replace the
1080 # standard style sheet and is therefor more robust against future updates.
1081 # Doxygen will copy the style sheet file to the output directory. For an example
1082 # see the documentation.
1083 # This tag requires that the tag GENERATE_HTML is set to YES.
1084
1085 HTML_EXTRA_STYLESHEET =
905 1086
906 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or 1087 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
907 # other source files which should be copied to the HTML output directory. Note 1088 # other source files which should be copied to the HTML output directory. Note
908 # that these files will be copied to the base HTML output directory. Use the 1089 # that these files will be copied to the base HTML output directory. Use the
909 # $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these 1090 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
910 # files. In the HTML_STYLESHEET file, use the file name only. Also note that 1091 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
911 # the files will be copied as-is; there are no commands or markers available. 1092 # files will be copied as-is; there are no commands or markers available.
1093 # This tag requires that the tag GENERATE_HTML is set to YES.
912 1094
913 HTML_EXTRA_FILES = 1095 HTML_EXTRA_FILES =
914 1096
915 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. 1097 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
916 # Doxygen will adjust the colors in the style sheet and background images 1098 # will adjust the colors in the stylesheet and background images according to
917 # according to this color. Hue is specified as an angle on a colorwheel, 1099 # this color. Hue is specified as an angle on a colorwheel, see
918 # see http://en.wikipedia.org/wiki/Hue for more information. 1100 # http://en.wikipedia.org/wiki/Hue for more information. For instance the value
919 # For instance the value 0 represents red, 60 is yellow, 120 is green, 1101 # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
920 # 180 is cyan, 240 is blue, 300 purple, and 360 is red again. 1102 # purple, and 360 is red again.
921 # The allowed range is 0 to 359. 1103 # Minimum value: 0, maximum value: 359, default value: 220.
1104 # This tag requires that the tag GENERATE_HTML is set to YES.
922 1105
923 HTML_COLORSTYLE_HUE = 220 1106 HTML_COLORSTYLE_HUE = 220
924 1107
925 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of 1108 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
926 # the colors in the HTML output. For a value of 0 the output will use 1109 # in the HTML output. For a value of 0 the output will use grayscales only. A
927 # grayscales only. A value of 255 will produce the most vivid colors. 1110 # value of 255 will produce the most vivid colors.
1111 # Minimum value: 0, maximum value: 255, default value: 100.
1112 # This tag requires that the tag GENERATE_HTML is set to YES.
928 1113
929 HTML_COLORSTYLE_SAT = 100 1114 HTML_COLORSTYLE_SAT = 100
930 1115
931 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to 1116 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
932 # the luminance component of the colors in the HTML output. Values below 1117 # luminance component of the colors in the HTML output. Values below 100
933 # 100 gradually make the output lighter, whereas values above 100 make 1118 # gradually make the output lighter, whereas values above 100 make the output
934 # the output darker. The value divided by 100 is the actual gamma applied, 1119 # darker. The value divided by 100 is the actual gamma applied, so 80 represents
935 # so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, 1120 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
936 # and 100 does not change the gamma. 1121 # change the gamma.
1122 # Minimum value: 40, maximum value: 240, default value: 80.
1123 # This tag requires that the tag GENERATE_HTML is set to YES.
937 1124
938 HTML_COLORSTYLE_GAMMA = 80 1125 HTML_COLORSTYLE_GAMMA = 80
939 1126
940 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML 1127 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
941 # page will contain the date and time when the page was generated. Setting 1128 # page will contain the date and time when the page was generated. Setting this
942 # this to NO can help when comparing the output of multiple runs. 1129 # to NO can help when comparing the output of multiple runs.
1130 # The default value is: YES.
1131 # This tag requires that the tag GENERATE_HTML is set to YES.
943 1132
944 HTML_TIMESTAMP = NO 1133 HTML_TIMESTAMP = NO
945 1134
946 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 1135 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
947 # documentation will contain sections that can be hidden and shown after the 1136 # documentation will contain sections that can be hidden and shown after the
948 # page has loaded. 1137 # page has loaded.
1138 # The default value is: NO.
1139 # This tag requires that the tag GENERATE_HTML is set to YES.
949 1140
950 HTML_DYNAMIC_SECTIONS = NO 1141 HTML_DYNAMIC_SECTIONS = NO
951 1142
952 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of 1143 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
953 # entries shown in the various tree structured indices initially; the user 1144 # shown in the various tree structured indices initially; the user can expand
954 # can expand and collapse entries dynamically later on. Doxygen will expand 1145 # and collapse entries dynamically later on. Doxygen will expand the tree to
955 # the tree to such a level that at most the specified number of entries are 1146 # such a level that at most the specified number of entries are visible (unless
956 # visible (unless a fully collapsed tree already exceeds this amount). 1147 # a fully collapsed tree already exceeds this amount). So setting the number of
957 # So setting the number of entries 1 will produce a full collapsed tree by 1148 # entries 1 will produce a full collapsed tree by default. 0 is a special value
958 # default. 0 is a special value representing an infinite number of entries 1149 # representing an infinite number of entries and will result in a full expanded
959 # and will result in a full expanded tree by default. 1150 # tree by default.
1151 # Minimum value: 0, maximum value: 9999, default value: 100.
1152 # This tag requires that the tag GENERATE_HTML is set to YES.
960 1153
961 HTML_INDEX_NUM_ENTRIES = 100 1154 HTML_INDEX_NUM_ENTRIES = 100
962 1155
963 # If the GENERATE_DOCSET tag is set to YES, additional index files 1156 # If the GENERATE_DOCSET tag is set to YES, additional index files will be
964 # will be generated that can be used as input for Apple's Xcode 3 1157 # generated that can be used as input for Apple's Xcode 3 integrated development
965 # integrated development environment, introduced with OSX 10.5 (Leopard). 1158 # environment (see: http://developer.apple.com/tools/xcode/), introduced with
966 # To create a documentation set, doxygen will generate a Makefile in the 1159 # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
967 # HTML output directory. Running make will produce the docset in that 1160 # Makefile in the HTML output directory. Running make will produce the docset in
968 # directory and running "make install" will install the docset in 1161 # that directory and running make install will install the docset in
969 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 1162 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
970 # it at startup. 1163 # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
971 # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
972 # for more information. 1164 # for more information.
1165 # The default value is: NO.
1166 # This tag requires that the tag GENERATE_HTML is set to YES.
973 1167
974 GENERATE_DOCSET = NO 1168 GENERATE_DOCSET = NO
975 1169
976 # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 1170 # This tag determines the name of the docset feed. A documentation feed provides
977 # feed. A documentation feed provides an umbrella under which multiple 1171 # an umbrella under which multiple documentation sets from a single provider
978 # documentation sets from a single provider (such as a company or product suite) 1172 # (such as a company or product suite) can be grouped.
979 # can be grouped. 1173 # The default value is: Doxygen generated docs.
1174 # This tag requires that the tag GENERATE_DOCSET is set to YES.
980 1175
981 DOCSET_FEEDNAME = "Doxygen generated docs" 1176 DOCSET_FEEDNAME = "Doxygen generated docs"
982 1177
983 # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 1178 # This tag specifies a string that should uniquely identify the documentation
984 # should uniquely identify the documentation set bundle. This should be a 1179 # set bundle. This should be a reverse domain-name style string, e.g.
985 # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 1180 # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
986 # will append .docset to the name. 1181 # The default value is: org.doxygen.Project.
1182 # This tag requires that the tag GENERATE_DOCSET is set to YES.
987 1183
988 DOCSET_BUNDLE_ID = org.doxygen.Project 1184 DOCSET_BUNDLE_ID = org.doxygen.Project
989 1185
990 # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify 1186 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
991 # the documentation publisher. This should be a reverse domain-name style 1187 # the documentation publisher. This should be a reverse domain-name style
992 # string, e.g. com.mycompany.MyDocSet.documentation. 1188 # string, e.g. com.mycompany.MyDocSet.documentation.
1189 # The default value is: org.doxygen.Publisher.
1190 # This tag requires that the tag GENERATE_DOCSET is set to YES.
993 1191
994 DOCSET_PUBLISHER_ID = org.doxygen.Publisher 1192 DOCSET_PUBLISHER_ID = org.doxygen.Publisher
995 1193
996 # The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher. 1194 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1195 # The default value is: Publisher.
1196 # This tag requires that the tag GENERATE_DOCSET is set to YES.
997 1197
998 DOCSET_PUBLISHER_NAME = Publisher 1198 DOCSET_PUBLISHER_NAME = Publisher
999 1199
1000 # If the GENERATE_HTMLHELP tag is set to YES, additional index files 1200 # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1001 # will be generated that can be used as input for tools like the 1201 # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1002 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 1202 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1003 # of the generated HTML documentation. 1203 # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1204 # Windows.
1205 #
1206 # The HTML Help Workshop contains a compiler that can convert all HTML output
1207 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1208 # files are now used as the Windows 98 help format, and will replace the old
1209 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1210 # HTML files also contain an index, a table of contents, and you can search for
1211 # words in the documentation. The HTML workshop also contains a viewer for
1212 # compressed HTML files.
1213 # The default value is: NO.
1214 # This tag requires that the tag GENERATE_HTML is set to YES.
1004 1215
1005 GENERATE_HTMLHELP = NO 1216 GENERATE_HTMLHELP = NO
1006 1217
1007 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 1218 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1008 # be used to specify the file name of the resulting .chm file. You 1219 # file. You can add a path in front of the file if the result should not be
1009 # can add a path in front of the file if the result should not be
1010 # written to the html output directory. 1220 # written to the html output directory.
1221 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1011 1222
1012 CHM_FILE = 1223 CHM_FILE =
1013 1224
1014 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 1225 # The HHC_LOCATION tag can be used to specify the location (absolute path
1015 # be used to specify the location (absolute path including file name) of 1226 # including file name) of the HTML help compiler ( hhc.exe). If non-empty
1016 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 1227 # doxygen will try to run the HTML help compiler on the generated index.hhp.
1017 # the HTML help compiler on the generated index.hhp. 1228 # The file has to be specified with full path.
1229 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1018 1230
1019 HHC_LOCATION = 1231 HHC_LOCATION =
1020 1232
1021 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 1233 # The GENERATE_CHI flag controls if a separate .chi index file is generated (
1022 # controls if a separate .chi index file is generated (YES) or that 1234 # YES) or that it should be included in the master .chm file ( NO).
1023 # it should be included in the master .chm file (NO). 1235 # The default value is: NO.
1236 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1024 1237
1025 GENERATE_CHI = NO 1238 GENERATE_CHI = NO
1026 1239
1027 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 1240 # The CHM_INDEX_ENCODING is used to encode HtmlHelp index ( hhk), content ( hhc)
1028 # is used to encode HtmlHelp index (hhk), content (hhc) and project file 1241 # and project file content.
1029 # content. 1242 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1030 1243
1031 CHM_INDEX_ENCODING = 1244 CHM_INDEX_ENCODING =
1032 1245
1033 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 1246 # The BINARY_TOC flag controls whether a binary table of contents is generated (
1034 # controls whether a binary table of contents is generated (YES) or a 1247 # YES) or a normal table of contents ( NO) in the .chm file. Furthermore it
1035 # normal table of contents (NO) in the .chm file. 1248 # enables the Previous and Next buttons.
1249 # The default value is: NO.
1250 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1036 1251
1037 BINARY_TOC = NO 1252 BINARY_TOC = NO
1038 1253
1039 # The TOC_EXPAND flag can be set to YES to add extra items for group members 1254 # The TOC_EXPAND flag can be set to YES to add extra items for group members to
1040 # to the contents of the HTML help documentation and to the tree view. 1255 # the table of contents of the HTML help documentation and to the tree view.
1256 # The default value is: NO.
1257 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1041 1258
1042 TOC_EXPAND = NO 1259 TOC_EXPAND = NO
1043 1260
1044 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and 1261 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1045 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated 1262 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1046 # that can be used as input for Qt's qhelpgenerator to generate a 1263 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1047 # Qt Compressed Help (.qch) of the generated HTML documentation. 1264 # (.qch) of the generated HTML documentation.
1265 # The default value is: NO.
1266 # This tag requires that the tag GENERATE_HTML is set to YES.
1048 1267
1049 GENERATE_QHP = NO 1268 GENERATE_QHP = NO
1050 1269
1051 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can 1270 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
1052 # be used to specify the file name of the resulting .qch file. 1271 # the file name of the resulting .qch file. The path specified is relative to
1053 # The path specified is relative to the HTML output folder. 1272 # the HTML output folder.
1273 # This tag requires that the tag GENERATE_QHP is set to YES.
1054 1274
1055 QCH_FILE = 1275 QCH_FILE =
1056 1276
1057 # The QHP_NAMESPACE tag specifies the namespace to use when generating 1277 # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1058 # Qt Help Project output. For more information please see 1278 # Project output. For more information please see Qt Help Project / Namespace
1059 # http://doc.trolltech.com/qthelpproject.html#namespace 1279 # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1280 # The default value is: org.doxygen.Project.
1281 # This tag requires that the tag GENERATE_QHP is set to YES.
1060 1282
1061 QHP_NAMESPACE = org.doxygen.Project 1283 QHP_NAMESPACE = org.doxygen.Project
1062 1284
1063 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 1285 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
1064 # Qt Help Project output. For more information please see 1286 # Help Project output. For more information please see Qt Help Project / Virtual
1065 # http://doc.trolltech.com/qthelpproject.html#virtual-folders 1287 # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1288 # folders).
1289 # The default value is: doc.
1290 # This tag requires that the tag GENERATE_QHP is set to YES.
1066 1291
1067 QHP_VIRTUAL_FOLDER = doc 1292 QHP_VIRTUAL_FOLDER = doc
1068 1293
1069 # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to 1294 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1070 # add. For more information please see 1295 # filter to add. For more information please see Qt Help Project / Custom
1071 # http://doc.trolltech.com/qthelpproject.html#custom-filters 1296 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1297 # filters).
1298 # This tag requires that the tag GENERATE_QHP is set to YES.
1072 1299
1073 QHP_CUST_FILTER_NAME = 1300 QHP_CUST_FILTER_NAME =
1074 1301
1075 # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the 1302 # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1076 # custom filter to add. For more information please see 1303 # custom filter to add. For more information please see Qt Help Project / Custom
1077 # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters"> 1304 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1078 # Qt Help Project / Custom Filters</a>. 1305 # filters).
1306 # This tag requires that the tag GENERATE_QHP is set to YES.
1079 1307
1080 QHP_CUST_FILTER_ATTRS = 1308 QHP_CUST_FILTER_ATTRS =
1081 1309
1082 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this 1310 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1083 # project's 1311 # project's filter section matches. Qt Help Project / Filter Attributes (see:
1084 # filter section matches. 1312 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1085 # <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes"> 1313 # This tag requires that the tag GENERATE_QHP is set to YES.
1086 # Qt Help Project / Filter Attributes</a>.
1087 1314
1088 QHP_SECT_FILTER_ATTRS = 1315 QHP_SECT_FILTER_ATTRS =
1089 1316
1090 # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 1317 # The QHG_LOCATION tag can be used to specify the location of Qt's
1091 # be used to specify the location of Qt's qhelpgenerator. 1318 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1092 # If non-empty doxygen will try to run qhelpgenerator on the generated 1319 # generated .qhp file.
1093 # .qhp file. 1320 # This tag requires that the tag GENERATE_QHP is set to YES.
1094 1321
1095 QHG_LOCATION = 1322 QHG_LOCATION =
1096 1323
1097 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files 1324 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1098 # will be generated, which together with the HTML files, form an Eclipse help 1325 # generated, together with the HTML files, they form an Eclipse help plugin. To
1099 # plugin. To install this plugin and make it available under the help contents 1326 # install this plugin and make it available under the help contents menu in
1100 # menu in Eclipse, the contents of the directory containing the HTML and XML 1327 # Eclipse, the contents of the directory containing the HTML and XML files needs
1101 # files needs to be copied into the plugins directory of eclipse. The name of 1328 # to be copied into the plugins directory of eclipse. The name of the directory
1102 # the directory within the plugins directory should be the same as 1329 # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
1103 # the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before 1330 # After copying Eclipse needs to be restarted before the help appears.
1104 # the help appears. 1331 # The default value is: NO.
1332 # This tag requires that the tag GENERATE_HTML is set to YES.
1105 1333
1106 GENERATE_ECLIPSEHELP = NO 1334 GENERATE_ECLIPSEHELP = NO
1107 1335
1108 # A unique identifier for the eclipse help plugin. When installing the plugin 1336 # A unique identifier for the Eclipse help plugin. When installing the plugin
1109 # the directory name containing the HTML and XML files should also have 1337 # the directory name containing the HTML and XML files should also have this
1110 # this name. 1338 # name. Each documentation set should have its own identifier.
1339 # The default value is: org.doxygen.Project.
1340 # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
1111 1341
1112 ECLIPSE_DOC_ID = org.doxygen.Project 1342 ECLIPSE_DOC_ID = org.doxygen.Project
1113 1343
1114 # The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) 1344 # If you want full control over the layout of the generated HTML pages it might
1115 # at top of each HTML page. The value NO (the default) enables the index and 1345 # be necessary to disable the index and replace it with your own. The
1116 # the value YES disables it. Since the tabs have the same information as the 1346 # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
1117 # navigation tree you can set this option to NO if you already set 1347 # of each HTML page. A value of NO enables the index and the value YES disables
1118 # GENERATE_TREEVIEW to YES. 1348 # it. Since the tabs in the index contain the same information as the navigation
1349 # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
1350 # The default value is: NO.
1351 # This tag requires that the tag GENERATE_HTML is set to YES.
1119 1352
1120 DISABLE_INDEX = NO 1353 DISABLE_INDEX = NO
1121 1354
1122 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 1355 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1123 # structure should be generated to display hierarchical information. 1356 # structure should be generated to display hierarchical information. If the tag
1124 # If the tag value is set to YES, a side panel will be generated 1357 # value is set to YES, a side panel will be generated containing a tree-like
1125 # containing a tree-like index structure (just like the one that 1358 # index structure (just like the one that is generated for HTML Help). For this
1126 # is generated for HTML Help). For this to work a browser that supports 1359 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
1127 # JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). 1360 # (i.e. any modern browser). Windows users are probably better off using the
1128 # Windows users are probably better off using the HTML help feature. 1361 # HTML help feature. Via custom stylesheets (see HTML_EXTRA_STYLESHEET) one can
1129 # Since the tree basically has the same information as the tab index you 1362 # further fine-tune the look of the index. As an example, the default style
1130 # could consider to set DISABLE_INDEX to NO when enabling this option. 1363 # sheet generated by doxygen has an example that shows how to put an image at
1364 # the root of the tree instead of the PROJECT_NAME. Since the tree basically has
1365 # the same information as the tab index, you could consider setting
1366 # DISABLE_INDEX to YES when enabling this option.
1367 # The default value is: NO.
1368 # This tag requires that the tag GENERATE_HTML is set to YES.
1131 1369
1132 GENERATE_TREEVIEW = NO 1370 GENERATE_TREEVIEW = NO
1133 1371
1134 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values 1372 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
1135 # (range [0,1..20]) that doxygen will group on one line in the generated HTML 1373 # doxygen will group on one line in the generated HTML documentation.
1136 # documentation. Note that a value of 0 will completely suppress the enum 1374 #
1137 # values from appearing in the overview section. 1375 # Note that a value of 0 will completely suppress the enum values from appearing
1376 # in the overview section.
1377 # Minimum value: 0, maximum value: 20, default value: 4.
1378 # This tag requires that the tag GENERATE_HTML is set to YES.
1138 1379
1139 ENUM_VALUES_PER_LINE = 1 1380 ENUM_VALUES_PER_LINE = 1
1140 1381
1141 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 1382 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
1142 # used to set the initial width (in pixels) of the frame in which the tree 1383 # to set the initial width (in pixels) of the frame in which the tree is shown.
1143 # is shown. 1384 # Minimum value: 0, maximum value: 1500, default value: 250.
1385 # This tag requires that the tag GENERATE_HTML is set to YES.
1144 1386
1145 TREEVIEW_WIDTH = 250 1387 TREEVIEW_WIDTH = 250
1146 1388
1147 # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open 1389 # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open links to
1148 # links to external symbols imported via tag files in a separate window. 1390 # external symbols imported via tag files in a separate window.
1391 # The default value is: NO.
1392 # This tag requires that the tag GENERATE_HTML is set to YES.
1149 1393
1150 EXT_LINKS_IN_WINDOW = NO 1394 EXT_LINKS_IN_WINDOW = NO
1151 1395
1152 # Use this tag to change the font size of Latex formulas included 1396 # Use this tag to change the font size of LaTeX formulas included as images in
1153 # as images in the HTML documentation. The default is 10. Note that 1397 # the HTML documentation. When you change the font size after a successful
1154 # when you change the font size after a successful doxygen run you need 1398 # doxygen run you need to manually remove any form_*.png images from the HTML
1155 # to manually remove any form_*.png images from the HTML output directory 1399 # output directory to force them to be regenerated.
1156 # to force them to be regenerated. 1400 # Minimum value: 8, maximum value: 50, default value: 10.
1401 # This tag requires that the tag GENERATE_HTML is set to YES.
1157 1402
1158 FORMULA_FONTSIZE = 10 1403 FORMULA_FONTSIZE = 10
1159 1404
1160 # Use the FORMULA_TRANPARENT tag to determine whether or not the images 1405 # Use the FORMULA_TRANPARENT tag to determine whether or not the images
1161 # generated for formulas are transparent PNGs. Transparent PNGs are 1406 # generated for formulas are transparent PNGs. Transparent PNGs are not
1162 # not supported properly for IE 6.0, but are supported on all modern browsers. 1407 # supported properly for IE 6.0, but are supported on all modern browsers.
1163 # Note that when changing this option you need to delete any form_*.png files 1408 #
1164 # in the HTML output before the changes have effect. 1409 # Note that when changing this option you need to delete any form_*.png files in
1410 # the HTML output directory before the changes have effect.
1411 # The default value is: YES.
1412 # This tag requires that the tag GENERATE_HTML is set to YES.
1165 1413
1166 FORMULA_TRANSPARENT = YES 1414 FORMULA_TRANSPARENT = YES
1167 1415
1168 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax 1416 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1169 # (see http://www.mathjax.org) which uses client side Javascript for the 1417 # http://www.mathjax.org) which uses client side Javascript for the rendering
1170 # rendering instead of using prerendered bitmaps. Use this if you do not 1418 # instead of using prerendered bitmaps. Use this if you do not have LaTeX
1171 # have LaTeX installed or if you want to formulas look prettier in the HTML 1419 # installed or if you want to formulas look prettier in the HTML output. When
1172 # output. When enabled you may also need to install MathJax separately and 1420 # enabled you may also need to install MathJax separately and configure the path
1173 # configure the path to it using the MATHJAX_RELPATH option. 1421 # to it using the MATHJAX_RELPATH option.
1422 # The default value is: NO.
1423 # This tag requires that the tag GENERATE_HTML is set to YES.
1174 1424
1175 USE_MATHJAX = NO 1425 USE_MATHJAX = NO
1176 1426
1177 # When MathJax is enabled you need to specify the location relative to the 1427 # When MathJax is enabled you can set the default output format to be used for
1178 # HTML output directory using the MATHJAX_RELPATH option. The destination 1428 # the MathJax output. See the MathJax site (see:
1179 # directory should contain the MathJax.js script. For instance, if the mathjax 1429 # http://docs.mathjax.org/en/latest/output.html) for more details.
1180 # directory is located at the same level as the HTML output directory, then 1430 # Possible values are: HTML-CSS (which is slower, but has the best
1181 # MATHJAX_RELPATH should be ../mathjax. The default value points to 1431 # compatibility), NativeMML (i.e. MathML) and SVG.
1182 # the MathJax Content Delivery Network so you can quickly see the result without 1432 # The default value is: HTML-CSS.
1183 # installing MathJax. 1433 # This tag requires that the tag USE_MATHJAX is set to YES.
1184 # However, it is strongly recommended to install a local 1434
1185 # copy of MathJax from http://www.mathjax.org before deployment. 1435 MATHJAX_FORMAT = HTML-CSS
1436
1437 # When MathJax is enabled you need to specify the location relative to the HTML
1438 # output directory using the MATHJAX_RELPATH option. The destination directory
1439 # should contain the MathJax.js script. For instance, if the mathjax directory
1440 # is located at the same level as the HTML output directory, then
1441 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1442 # Content Delivery Network so you can quickly see the result without installing
1443 # MathJax. However, it is strongly recommended to install a local copy of
1444 # MathJax from http://www.mathjax.org before deployment.
1445 # The default value is: http://cdn.mathjax.org/mathjax/latest.
1446 # This tag requires that the tag USE_MATHJAX is set to YES.
1186 1447
1187 MATHJAX_RELPATH = http://www.mathjax.org/mathjax 1448 MATHJAX_RELPATH = http://www.mathjax.org/mathjax
1188 1449
1189 # The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension 1450 # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
1190 # names that should be enabled during MathJax rendering. 1451 # extension names that should be enabled during MathJax rendering. For example
1452 # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
1453 # This tag requires that the tag USE_MATHJAX is set to YES.
1191 1454
1192 MATHJAX_EXTENSIONS = 1455 MATHJAX_EXTENSIONS =
1193 1456
1194 # When the SEARCHENGINE tag is enabled doxygen will generate a search box 1457 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1195 # for the HTML output. The underlying search engine uses javascript 1458 # of code that will be used on startup of the MathJax code. See the MathJax site
1196 # and DHTML and should work on any modern browser. Note that when using 1459 # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
1197 # HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets 1460 # example see the documentation.
1198 # (GENERATE_DOCSET) there is already a search function so this one should 1461 # This tag requires that the tag USE_MATHJAX is set to YES.
1199 # typically be disabled. For large projects the javascript based search engine 1462
1200 # can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution. 1463 MATHJAX_CODEFILE =
1464
1465 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1466 # the HTML output. The underlying search engine uses javascript and DHTML and
1467 # should work on any modern browser. Note that when using HTML help
1468 # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
1469 # there is already a search function so this one should typically be disabled.
1470 # For large projects the javascript based search engine can be slow, then
1471 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1472 # search using the keyboard; to jump to the search box use <access key> + S
1473 # (what the <access key> is depends on the OS and browser, but it is typically
1474 # <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
1475 # key> to jump into the search results window, the results can be navigated
1476 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1477 # the search. The filter options can be selected when the cursor is inside the
1478 # search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
1479 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1480 # option.
1481 # The default value is: YES.
1482 # This tag requires that the tag GENERATE_HTML is set to YES.
1201 1483
1202 SEARCHENGINE = NO 1484 SEARCHENGINE = NO
1203 1485
1204 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be 1486 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1205 # implemented using a PHP enabled web server instead of at the web client 1487 # implemented using a web server instead of a web client using Javascript. There
1206 # using Javascript. Doxygen will generate the search PHP script and index 1488 # are two flavors of web server based searching depending on the EXTERNAL_SEARCH
1207 # file to put on the web server. The advantage of the server 1489 # setting. When disabled, doxygen will generate a PHP script for searching and
1208 # based approach is that it scales better to large projects and allows 1490 # an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
1209 # full text search. The disadvantages are that it is more difficult to setup 1491 # and searching needs to be provided by external tools. See the section
1210 # and does not have live searching capabilities. 1492 # "External Indexing and Searching" for details.
1493 # The default value is: NO.
1494 # This tag requires that the tag SEARCHENGINE is set to YES.
1211 1495
1212 SERVER_BASED_SEARCH = NO 1496 SERVER_BASED_SEARCH = NO
1213 1497
1214 #--------------------------------------------------------------------------- 1498 # When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
1215 # configuration options related to the LaTeX output 1499 # script for searching. Instead the search results are written to an XML file
1216 #--------------------------------------------------------------------------- 1500 # which needs to be processed by an external indexer. Doxygen will invoke an
1217 1501 # external search engine pointed to by the SEARCHENGINE_URL option to obtain the
1218 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 1502 # search results.
1219 # generate Latex output. 1503 #
1504 # Doxygen ships with an example indexer ( doxyindexer) and search engine
1505 # (doxysearch.cgi) which are based on the open source search engine library
1506 # Xapian (see: http://xapian.org/).
1507 #
1508 # See the section "External Indexing and Searching" for details.
1509 # The default value is: NO.
1510 # This tag requires that the tag SEARCHENGINE is set to YES.
1511
1512 EXTERNAL_SEARCH = NO
1513
1514 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
1515 # which will return the search results when EXTERNAL_SEARCH is enabled.
1516 #
1517 # Doxygen ships with an example indexer ( doxyindexer) and search engine
1518 # (doxysearch.cgi) which are based on the open source search engine library
1519 # Xapian (see: http://xapian.org/). See the section "External Indexing and
1520 # Searching" for details.
1521 # This tag requires that the tag SEARCHENGINE is set to YES.
1522
1523 SEARCHENGINE_URL =
1524
1525 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
1526 # search data is written to a file for indexing by an external tool. With the
1527 # SEARCHDATA_FILE tag the name of this file can be specified.
1528 # The default file is: searchdata.xml.
1529 # This tag requires that the tag SEARCHENGINE is set to YES.
1530
1531 SEARCHDATA_FILE = searchdata.xml
1532
1533 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
1534 # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
1535 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1536 # projects and redirect the results back to the right project.
1537 # This tag requires that the tag SEARCHENGINE is set to YES.
1538
1539 EXTERNAL_SEARCH_ID =
1540
1541 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1542 # projects other than the one defined by this configuration file, but that are
1543 # all added to the same external search index. Each project needs to have a
1544 # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
1545 # to a relative location where the documentation can be found. The format is:
1546 # EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
1547 # This tag requires that the tag SEARCHENGINE is set to YES.
1548
1549 EXTRA_SEARCH_MAPPINGS =
1550
1551 #---------------------------------------------------------------------------
1552 # Configuration options related to the LaTeX output
1553 #---------------------------------------------------------------------------
1554
1555 # If the GENERATE_LATEX tag is set to YES doxygen will generate LaTeX output.
1556 # The default value is: YES.
1220 1557
1221 GENERATE_LATEX = NO 1558 GENERATE_LATEX = NO
1222 1559
1223 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 1560 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1224 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1561 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1225 # put in front of it. If left blank `latex' will be used as the default path. 1562 # it.
1563 # The default directory is: latex.
1564 # This tag requires that the tag GENERATE_LATEX is set to YES.
1226 1565
1227 LATEX_OUTPUT = latex 1566 LATEX_OUTPUT = latex
1228 1567
1229 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 1568 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1230 # invoked. If left blank `latex' will be used as the default command name. 1569 # invoked.
1231 # Note that when enabling USE_PDFLATEX this option is only used for 1570 #
1232 # generating bitmaps for formulas in the HTML output, but not in the 1571 # Note that when enabling USE_PDFLATEX this option is only used for generating
1233 # Makefile that is written to the output directory. 1572 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1573 # written to the output directory.
1574 # The default file is: latex.
1575 # This tag requires that the tag GENERATE_LATEX is set to YES.
1234 1576
1235 LATEX_CMD_NAME = latex 1577 LATEX_CMD_NAME = latex
1236 1578
1237 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 1579 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
1238 # generate index for LaTeX. If left blank `makeindex' will be used as the 1580 # index for LaTeX.
1239 # default command name. 1581 # The default file is: makeindex.
1582 # This tag requires that the tag GENERATE_LATEX is set to YES.
1240 1583
1241 MAKEINDEX_CMD_NAME = makeindex 1584 MAKEINDEX_CMD_NAME = makeindex
1242 1585
1243 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 1586 # If the COMPACT_LATEX tag is set to YES doxygen generates more compact LaTeX
1244 # LaTeX documents. This may be useful for small projects and may help to 1587 # documents. This may be useful for small projects and may help to save some
1245 # save some trees in general. 1588 # trees in general.
1589 # The default value is: NO.
1590 # This tag requires that the tag GENERATE_LATEX is set to YES.
1246 1591
1247 COMPACT_LATEX = NO 1592 COMPACT_LATEX = NO
1248 1593
1249 # The PAPER_TYPE tag can be used to set the paper type that is used 1594 # The PAPER_TYPE tag can be used to set the paper type that is used by the
1250 # by the printer. Possible values are: a4, letter, legal and 1595 # printer.
1251 # executive. If left blank a4wide will be used. 1596 # Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
1597 # 14 inches) and executive (7.25 x 10.5 inches).
1598 # The default value is: a4.
1599 # This tag requires that the tag GENERATE_LATEX is set to YES.
1252 1600
1253 PAPER_TYPE = a4 1601 PAPER_TYPE = a4
1254 1602
1255 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 1603 # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
1256 # packages that should be included in the LaTeX output. 1604 # that should be included in the LaTeX output. To get the times font for
1605 # instance you can specify
1606 # EXTRA_PACKAGES=times
1607 # If left blank no extra packages will be included.
1608 # This tag requires that the tag GENERATE_LATEX is set to YES.
1257 1609
1258 EXTRA_PACKAGES = 1610 EXTRA_PACKAGES =
1259 1611
1260 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for 1612 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1261 # the generated latex document. The header should contain everything until 1613 # generated LaTeX document. The header should contain everything until the first
1262 # the first chapter. If it is left blank doxygen will generate a 1614 # chapter. If it is left blank doxygen will generate a standard header. See
1263 # standard header. Notice: only use this tag if you know what you are doing! 1615 # section "Doxygen usage" for information on how to let doxygen write the
1616 # default header to a separate file.
1617 #
1618 # Note: Only use a user-defined header if you know what you are doing! The
1619 # following commands have a special meaning inside the header: $title,
1620 # $datetime, $date, $doxygenversion, $projectname, $projectnumber. Doxygen will
1621 # replace them by respectively the title of the page, the current date and time,
1622 # only the current date, the version number of doxygen, the project name (see
1623 # PROJECT_NAME), or the project number (see PROJECT_NUMBER).
1624 # This tag requires that the tag GENERATE_LATEX is set to YES.
1264 1625
1265 LATEX_HEADER = 1626 LATEX_HEADER =
1266 1627
1267 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for 1628 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1268 # the generated latex document. The footer should contain everything after 1629 # generated LaTeX document. The footer should contain everything after the last
1269 # the last chapter. If it is left blank doxygen will generate a 1630 # chapter. If it is left blank doxygen will generate a standard footer.
1270 # standard footer. Notice: only use this tag if you know what you are doing! 1631 #
1632 # Note: Only use a user-defined footer if you know what you are doing!
1633 # This tag requires that the tag GENERATE_LATEX is set to YES.
1271 1634
1272 LATEX_FOOTER = 1635 LATEX_FOOTER =
1273 1636
1274 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 1637 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1275 # is prepared for conversion to pdf (using ps2pdf). The pdf file will 1638 # other source files which should be copied to the LATEX_OUTPUT output
1276 # contain links (just like the HTML output) instead of page references 1639 # directory. Note that the files will be copied as-is; there are no commands or
1277 # This makes the output suitable for online browsing using a pdf viewer. 1640 # markers available.
1641 # This tag requires that the tag GENERATE_LATEX is set to YES.
1642
1643 LATEX_EXTRA_FILES =
1644
1645 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
1646 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
1647 # contain links (just like the HTML output) instead of page references. This
1648 # makes the output suitable for online browsing using a PDF viewer.
1649 # The default value is: YES.
1650 # This tag requires that the tag GENERATE_LATEX is set to YES.
1278 1651
1279 PDF_HYPERLINKS = YES 1652 PDF_HYPERLINKS = YES
1280 1653
1281 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 1654 # If the LATEX_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
1282 # plain latex in the generated Makefile. Set this option to YES to get a 1655 # the PDF file directly from the LaTeX files. Set this option to YES to get a
1283 # higher quality PDF documentation. 1656 # higher quality PDF documentation.
1657 # The default value is: YES.
1658 # This tag requires that the tag GENERATE_LATEX is set to YES.
1284 1659
1285 USE_PDFLATEX = YES 1660 USE_PDFLATEX = YES
1286 1661
1287 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 1662 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
1288 # command to the generated LaTeX files. This will instruct LaTeX to keep 1663 # command to the generated LaTeX files. This will instruct LaTeX to keep running
1289 # running if errors occur, instead of asking the user for help. 1664 # if errors occur, instead of asking the user for help. This option is also used
1290 # This option is also used when generating formulas in HTML. 1665 # when generating formulas in HTML.
1666 # The default value is: NO.
1667 # This tag requires that the tag GENERATE_LATEX is set to YES.
1291 1668
1292 LATEX_BATCHMODE = NO 1669 LATEX_BATCHMODE = NO
1293 1670
1294 # If LATEX_HIDE_INDICES is set to YES then doxygen will not 1671 # If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
1295 # include the index chapters (such as File Index, Compound Index, etc.) 1672 # index chapters (such as File Index, Compound Index, etc.) in the output.
1296 # in the output. 1673 # The default value is: NO.
1674 # This tag requires that the tag GENERATE_LATEX is set to YES.
1297 1675
1298 LATEX_HIDE_INDICES = NO 1676 LATEX_HIDE_INDICES = NO
1299 1677
1300 # If LATEX_SOURCE_CODE is set to YES then doxygen will include 1678 # If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
1301 # source code with syntax highlighting in the LaTeX output. 1679 # code with syntax highlighting in the LaTeX output.
1302 # Note that which sources are shown also depends on other settings 1680 #
1303 # such as SOURCE_BROWSER. 1681 # Note that which sources are shown also depends on other settings such as
1682 # SOURCE_BROWSER.
1683 # The default value is: NO.
1684 # This tag requires that the tag GENERATE_LATEX is set to YES.
1304 1685
1305 LATEX_SOURCE_CODE = NO 1686 LATEX_SOURCE_CODE = NO
1306 1687
1307 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the 1688 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1308 # bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See 1689 # bibliography, e.g. plainnat, or ieeetr. See
1309 # http://en.wikipedia.org/wiki/BibTeX for more info. 1690 # http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
1691 # The default value is: plain.
1692 # This tag requires that the tag GENERATE_LATEX is set to YES.
1310 1693
1311 LATEX_BIB_STYLE = plain 1694 LATEX_BIB_STYLE = plain
1312 1695
1313 #--------------------------------------------------------------------------- 1696 #---------------------------------------------------------------------------
1314 # configuration options related to the RTF output 1697 # Configuration options related to the RTF output
1315 #--------------------------------------------------------------------------- 1698 #---------------------------------------------------------------------------
1316 1699
1317 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 1700 # If the GENERATE_RTF tag is set to YES doxygen will generate RTF output. The
1318 # The RTF output is optimized for Word 97 and may not look very pretty with 1701 # RTF output is optimized for Word 97 and may not look too pretty with other RTF
1319 # other RTF readers or editors. 1702 # readers/editors.
1703 # The default value is: NO.
1320 1704
1321 GENERATE_RTF = NO 1705 GENERATE_RTF = NO
1322 1706
1323 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 1707 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
1324 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1708 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1325 # put in front of it. If left blank `rtf' will be used as the default path. 1709 # it.
1710 # The default directory is: rtf.
1711 # This tag requires that the tag GENERATE_RTF is set to YES.
1326 1712
1327 RTF_OUTPUT = rtf 1713 RTF_OUTPUT = rtf
1328 1714
1329 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact 1715 # If the COMPACT_RTF tag is set to YES doxygen generates more compact RTF
1330 # RTF documents. This may be useful for small projects and may help to 1716 # documents. This may be useful for small projects and may help to save some
1331 # save some trees in general. 1717 # trees in general.
1718 # The default value is: NO.
1719 # This tag requires that the tag GENERATE_RTF is set to YES.
1332 1720
1333 COMPACT_RTF = NO 1721 COMPACT_RTF = NO
1334 1722
1335 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 1723 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
1336 # will contain hyperlink fields. The RTF file will 1724 # contain hyperlink fields. The RTF file will contain links (just like the HTML
1337 # contain links (just like the HTML output) instead of page references. 1725 # output) instead of page references. This makes the output suitable for online
1338 # This makes the output suitable for online browsing using WORD or other 1726 # browsing using Word or some other Word compatible readers that support those
1339 # programs which support those fields. 1727 # fields.
1340 # Note: wordpad (write) and others do not support links. 1728 #
1729 # Note: WordPad (write) and others do not support links.
1730 # The default value is: NO.
1731 # This tag requires that the tag GENERATE_RTF is set to YES.
1341 1732
1342 RTF_HYPERLINKS = NO 1733 RTF_HYPERLINKS = NO
1343 1734
1344 # Load style sheet definitions from file. Syntax is similar to doxygen's 1735 # Load stylesheet definitions from file. Syntax is similar to doxygen's config
1345 # config file, i.e. a series of assignments. You only have to provide 1736 # file, i.e. a series of assignments. You only have to provide replacements,
1346 # replacements, missing definitions are set to their default value. 1737 # missing definitions are set to their default value.
1738 #
1739 # See also section "Doxygen usage" for information on how to generate the
1740 # default style sheet that doxygen normally uses.
1741 # This tag requires that the tag GENERATE_RTF is set to YES.
1347 1742
1348 RTF_STYLESHEET_FILE = 1743 RTF_STYLESHEET_FILE =
1349 1744
1350 # Set optional variables used in the generation of an rtf document. 1745 # Set optional variables used in the generation of an RTF document. Syntax is
1351 # Syntax is similar to doxygen's config file. 1746 # similar to doxygen's config file. A template extensions file can be generated
1747 # using doxygen -e rtf extensionFile.
1748 # This tag requires that the tag GENERATE_RTF is set to YES.
1352 1749
1353 RTF_EXTENSIONS_FILE = 1750 RTF_EXTENSIONS_FILE =
1354 1751
1355 #--------------------------------------------------------------------------- 1752 #---------------------------------------------------------------------------
1356 # configuration options related to the man page output 1753 # Configuration options related to the man page output
1357 #--------------------------------------------------------------------------- 1754 #---------------------------------------------------------------------------
1358 1755
1359 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will 1756 # If the GENERATE_MAN tag is set to YES doxygen will generate man pages for
1360 # generate man pages 1757 # classes and files.
1758 # The default value is: NO.
1361 1759
1362 GENERATE_MAN = NO 1760 GENERATE_MAN = NO
1363 1761
1364 # The MAN_OUTPUT tag is used to specify where the man pages will be put. 1762 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
1365 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1763 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1366 # put in front of it. If left blank `man' will be used as the default path. 1764 # it. A directory man3 will be created inside the directory specified by
1765 # MAN_OUTPUT.
1766 # The default directory is: man.
1767 # This tag requires that the tag GENERATE_MAN is set to YES.
1367 1768
1368 MAN_OUTPUT = man 1769 MAN_OUTPUT = man
1369 1770
1370 # The MAN_EXTENSION tag determines the extension that is added to 1771 # The MAN_EXTENSION tag determines the extension that is added to the generated
1371 # the generated man pages (default is the subroutine's section .3) 1772 # man pages. In case the manual section does not start with a number, the number
1773 # 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
1774 # optional.
1775 # The default value is: .3.
1776 # This tag requires that the tag GENERATE_MAN is set to YES.
1372 1777
1373 MAN_EXTENSION = .3 1778 MAN_EXTENSION = .3
1374 1779
1375 # If the MAN_LINKS tag is set to YES and Doxygen generates man output, 1780 # The MAN_SUBDIR tag determines the name of the directory created within
1376 # then it will generate one additional man file for each entity 1781 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
1377 # documented in the real man page(s). These additional files 1782 # MAN_EXTENSION with the initial . removed.
1378 # only source the real man page, but without them the man command 1783 # This tag requires that the tag GENERATE_MAN is set to YES.
1379 # would be unable to find the correct page. The default is NO. 1784
1785 MAN_SUBDIR =
1786
1787 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
1788 # will generate one additional man file for each entity documented in the real
1789 # man page(s). These additional files only source the real man page, but without
1790 # them the man command would be unable to find the correct page.
1791 # The default value is: NO.
1792 # This tag requires that the tag GENERATE_MAN is set to YES.
1380 1793
1381 MAN_LINKS = NO 1794 MAN_LINKS = NO
1382 1795
1383 #--------------------------------------------------------------------------- 1796 #---------------------------------------------------------------------------
1384 # configuration options related to the XML output 1797 # Configuration options related to the XML output
1385 #--------------------------------------------------------------------------- 1798 #---------------------------------------------------------------------------
1386 1799
1387 # If the GENERATE_XML tag is set to YES Doxygen will 1800 # If the GENERATE_XML tag is set to YES doxygen will generate an XML file that
1388 # generate an XML file that captures the structure of 1801 # captures the structure of the code including all documentation.
1389 # the code including all documentation. 1802 # The default value is: NO.
1390 1803
1391 GENERATE_XML = NO 1804 GENERATE_XML = NO
1392 1805
1393 # The XML_OUTPUT tag is used to specify where the XML pages will be put. 1806 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
1394 # If a relative path is entered the value of OUTPUT_DIRECTORY will be 1807 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1395 # put in front of it. If left blank `xml' will be used as the default path. 1808 # it.
1809 # The default directory is: xml.
1810 # This tag requires that the tag GENERATE_XML is set to YES.
1396 1811
1397 XML_OUTPUT = xml 1812 XML_OUTPUT = xml
1398 1813
1399 # The XML_SCHEMA tag can be used to specify an XML schema, 1814 # If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program
1400 # which can be used by a validating XML parser to check the 1815 # listings (including syntax highlighting and cross-referencing information) to
1401 # syntax of the XML files. 1816 # the XML output. Note that enabling this will significantly increase the size
1402 1817 # of the XML output.
1403 XML_SCHEMA = 1818 # The default value is: YES.
1404 1819 # This tag requires that the tag GENERATE_XML is set to YES.
1405 # The XML_DTD tag can be used to specify an XML DTD,
1406 # which can be used by a validating XML parser to check the
1407 # syntax of the XML files.
1408
1409 XML_DTD =
1410
1411 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1412 # dump the program listings (including syntax highlighting
1413 # and cross-referencing information) to the XML output. Note that
1414 # enabling this will significantly increase the size of the XML output.
1415 1820
1416 XML_PROGRAMLISTING = YES 1821 XML_PROGRAMLISTING = YES
1417 1822
1418 #--------------------------------------------------------------------------- 1823 #---------------------------------------------------------------------------
1419 # configuration options for the AutoGen Definitions output 1824 # Configuration options related to the DOCBOOK output
1420 #--------------------------------------------------------------------------- 1825 #---------------------------------------------------------------------------
1421 1826
1422 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 1827 # If the GENERATE_DOCBOOK tag is set to YES doxygen will generate Docbook files
1423 # generate an AutoGen Definitions (see autogen.sf.net) file 1828 # that can be used to generate PDF.
1424 # that captures the structure of the code including all 1829 # The default value is: NO.
1425 # documentation. Note that this feature is still experimental 1830
1426 # and incomplete at the moment. 1831 GENERATE_DOCBOOK = NO
1832
1833 # The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
1834 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1835 # front of it.
1836 # The default directory is: docbook.
1837 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
1838
1839 DOCBOOK_OUTPUT = docbook
1840
1841 #---------------------------------------------------------------------------
1842 # Configuration options for the AutoGen Definitions output
1843 #---------------------------------------------------------------------------
1844
1845 # If the GENERATE_AUTOGEN_DEF tag is set to YES doxygen will generate an AutoGen
1846 # Definitions (see http://autogen.sf.net) file that captures the structure of
1847 # the code including all documentation. Note that this feature is still
1848 # experimental and incomplete at the moment.
1849 # The default value is: NO.
1427 1850
1428 GENERATE_AUTOGEN_DEF = NO 1851 GENERATE_AUTOGEN_DEF = NO
1429 1852
1430 #--------------------------------------------------------------------------- 1853 #---------------------------------------------------------------------------
1431 # configuration options related to the Perl module output 1854 # Configuration options related to the Perl module output
1432 #--------------------------------------------------------------------------- 1855 #---------------------------------------------------------------------------
1433 1856
1434 # If the GENERATE_PERLMOD tag is set to YES Doxygen will 1857 # If the GENERATE_PERLMOD tag is set to YES doxygen will generate a Perl module
1435 # generate a Perl module file that captures the structure of 1858 # file that captures the structure of the code including all documentation.
1436 # the code including all documentation. Note that this 1859 #
1437 # feature is still experimental and incomplete at the 1860 # Note that this feature is still experimental and incomplete at the moment.
1438 # moment. 1861 # The default value is: NO.
1439 1862
1440 GENERATE_PERLMOD = NO 1863 GENERATE_PERLMOD = NO
1441 1864
1442 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate 1865 # If the PERLMOD_LATEX tag is set to YES doxygen will generate the necessary
1443 # the necessary Makefile rules, Perl scripts and LaTeX code to be able 1866 # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
1444 # to generate PDF and DVI output from the Perl module output. 1867 # output from the Perl module output.
1868 # The default value is: NO.
1869 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
1445 1870
1446 PERLMOD_LATEX = NO 1871 PERLMOD_LATEX = NO
1447 1872
1448 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 1873 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be nicely
1449 # nicely formatted so it can be parsed by a human reader. 1874 # formatted so it can be parsed by a human reader. This is useful if you want to
1450 # This is useful 1875 # understand what is going on. On the other hand, if this tag is set to NO the
1451 # if you want to understand what is going on. 1876 # size of the Perl module output will be much smaller and Perl will parse it
1452 # On the other hand, if this 1877 # just the same.
1453 # tag is set to NO the size of the Perl module output will be much smaller 1878 # The default value is: YES.
1454 # and Perl will parse it just the same. 1879 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
1455 1880
1456 PERLMOD_PRETTY = YES 1881 PERLMOD_PRETTY = YES
1457 1882
1458 # The names of the make variables in the generated doxyrules.make file 1883 # The names of the make variables in the generated doxyrules.make file are
1459 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 1884 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
1460 # This is useful so different doxyrules.make files included by the same 1885 # so different doxyrules.make files included by the same Makefile don't
1461 # Makefile don't overwrite each other's variables. 1886 # overwrite each other's variables.
1887 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
1462 1888
1463 PERLMOD_MAKEVAR_PREFIX = 1889 PERLMOD_MAKEVAR_PREFIX =
1464 1890
1465 #--------------------------------------------------------------------------- 1891 #---------------------------------------------------------------------------
1466 # Configuration options related to the preprocessor 1892 # Configuration options related to the preprocessor
1467 #--------------------------------------------------------------------------- 1893 #---------------------------------------------------------------------------
1468 1894
1469 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 1895 # If the ENABLE_PREPROCESSING tag is set to YES doxygen will evaluate all
1470 # evaluate all C-preprocessor directives found in the sources and include 1896 # C-preprocessor directives found in the sources and include files.
1471 # files. 1897 # The default value is: YES.
1472 1898
1473 ENABLE_PREPROCESSING = YES 1899 ENABLE_PREPROCESSING = YES
1474 1900
1475 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 1901 # If the MACRO_EXPANSION tag is set to YES doxygen will expand all macro names
1476 # names in the source code. If set to NO (the default) only conditional 1902 # in the source code. If set to NO only conditional compilation will be
1477 # compilation will be performed. Macro expansion can be done in a controlled 1903 # performed. Macro expansion can be done in a controlled way by setting
1478 # way by setting EXPAND_ONLY_PREDEF to YES. 1904 # EXPAND_ONLY_PREDEF to YES.
1905 # The default value is: NO.
1906 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1479 1907
1480 MACRO_EXPANSION = YES 1908 MACRO_EXPANSION = YES
1481 1909
1482 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 1910 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
1483 # then the macro expansion is limited to the macros specified with the 1911 # the macro expansion is limited to the macros specified with the PREDEFINED and
1484 # PREDEFINED and EXPAND_AS_DEFINED tags. 1912 # EXPAND_AS_DEFINED tags.
1913 # The default value is: NO.
1914 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1485 1915
1486 EXPAND_ONLY_PREDEF = YES 1916 EXPAND_ONLY_PREDEF = YES
1487 1917
1488 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 1918 # If the SEARCH_INCLUDES tag is set to YES the includes files in the
1489 # pointed to by INCLUDE_PATH will be searched when a #include is found. 1919 # INCLUDE_PATH will be searched if a #include is found.
1920 # The default value is: YES.
1921 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1490 1922
1491 SEARCH_INCLUDES = YES 1923 SEARCH_INCLUDES = YES
1492 1924
1493 # The INCLUDE_PATH tag can be used to specify one or more directories that 1925 # The INCLUDE_PATH tag can be used to specify one or more directories that
1494 # contain include files that are not input files but should be processed by 1926 # contain include files that are not input files but should be processed by the
1495 # the preprocessor. 1927 # preprocessor.
1928 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
1496 1929
1497 INCLUDE_PATH = 1930 INCLUDE_PATH =
1498 1931
1499 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 1932 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1500 # patterns (like *.h and *.hpp) to filter out the header-files in the 1933 # patterns (like *.h and *.hpp) to filter out the header-files in the
1501 # directories. If left blank, the patterns specified with FILE_PATTERNS will 1934 # directories. If left blank, the patterns specified with FILE_PATTERNS will be
1502 # be used. 1935 # used.
1936 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1503 1937
1504 INCLUDE_FILE_PATTERNS = 1938 INCLUDE_FILE_PATTERNS =
1505 1939
1506 # The PREDEFINED tag can be used to specify one or more macro names that 1940 # The PREDEFINED tag can be used to specify one or more macro names that are
1507 # are defined before the preprocessor is started (similar to the -D option of 1941 # defined before the preprocessor is started (similar to the -D option of e.g.
1508 # gcc). The argument of the tag is a list of macros of the form: name 1942 # gcc). The argument of the tag is a list of macros of the form: name or
1509 # or name=definition (no spaces). If the definition and the = are 1943 # name=definition (no spaces). If the definition and the "=" are omitted, "=1"
1510 # omitted =1 is assumed. To prevent a macro definition from being 1944 # is assumed. To prevent a macro definition from being undefined via #undef or
1511 # undefined via #undef or recursively expanded use the := operator 1945 # recursively expanded use the := operator instead of the = operator.
1512 # instead of the = operator. 1946 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1513 1947
1514 PREDEFINED = ORTHANC_PLUGIN_INLINE= 1948 PREDEFINED = ORTHANC_PLUGIN_INLINE=
1515 1949
1516 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 1950 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
1517 # this tag can be used to specify a list of macro names that should be expanded. 1951 # tag can be used to specify a list of macro names that should be expanded. The
1518 # The macro definition that is found in the sources will be used. 1952 # macro definition that is found in the sources will be used. Use the PREDEFINED
1519 # Use the PREDEFINED tag if you want to use a different macro definition that 1953 # tag if you want to use a different macro definition that overrules the
1520 # overrules the definition found in the source code. 1954 # definition found in the source code.
1955 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1521 1956
1522 EXPAND_AS_DEFINED = 1957 EXPAND_AS_DEFINED =
1523 1958
1524 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 1959 # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
1525 # doxygen's preprocessor will remove all references to function-like macros 1960 # remove all references to function-like macros that are alone on a line, have
1526 # that are alone on a line, have an all uppercase name, and do not end with a 1961 # an all uppercase name, and do not end with a semicolon. Such function macros
1527 # semicolon, because these will confuse the parser if not removed. 1962 # are typically used for boiler-plate code, and will confuse the parser if not
1963 # removed.
1964 # The default value is: YES.
1965 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1528 1966
1529 SKIP_FUNCTION_MACROS = YES 1967 SKIP_FUNCTION_MACROS = YES
1530 1968
1531 #--------------------------------------------------------------------------- 1969 #---------------------------------------------------------------------------
1532 # Configuration::additions related to external references 1970 # Configuration options related to external references
1533 #--------------------------------------------------------------------------- 1971 #---------------------------------------------------------------------------
1534 1972
1535 # The TAGFILES option can be used to specify one or more tagfiles. For each 1973 # The TAGFILES tag can be used to specify one or more tag files. For each tag
1536 # tag file the location of the external documentation should be added. The 1974 # file the location of the external documentation should be added. The format of
1537 # format of a tag file without this location is as follows: 1975 # a tag file without this location is as follows:
1538 #
1539 # TAGFILES = file1 file2 ... 1976 # TAGFILES = file1 file2 ...
1540 # Adding location for the tag files is done as follows: 1977 # Adding location for the tag files is done as follows:
1541 #
1542 # TAGFILES = file1=loc1 "file2 = loc2" ... 1978 # TAGFILES = file1=loc1 "file2 = loc2" ...
1543 # where "loc1" and "loc2" can be relative or absolute paths 1979 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
1544 # or URLs. Note that each tag file must have a unique name (where the name does 1980 # section "Linking to external documentation" for more information about the use
1545 # NOT include the path). If a tag file is not located in the directory in which 1981 # of tag files.
1546 # doxygen is run, you must also specify the path to the tagfile here. 1982 # Note: Each tag file must have a unique name (where the name does NOT include
1983 # the path). If a tag file is not located in the directory in which doxygen is
1984 # run, you must also specify the path to the tagfile here.
1547 1985
1548 TAGFILES = 1986 TAGFILES =
1549 1987
1550 # When a file name is specified after GENERATE_TAGFILE, doxygen will create 1988 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
1551 # a tag file that is based on the input files it reads. 1989 # tag file that is based on the input files it reads. See section "Linking to
1990 # external documentation" for more information about the usage of tag files.
1552 1991
1553 GENERATE_TAGFILE = 1992 GENERATE_TAGFILE =
1554 1993
1555 # If the ALLEXTERNALS tag is set to YES all external classes will be listed 1994 # If the ALLEXTERNALS tag is set to YES all external class will be listed in the
1556 # in the class index. If set to NO only the inherited external classes 1995 # class index. If set to NO only the inherited external classes will be listed.
1557 # will be listed. 1996 # The default value is: NO.
1558 1997
1559 ALLEXTERNALS = NO 1998 ALLEXTERNALS = NO
1560 1999
1561 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 2000 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed in
1562 # in the modules index. If set to NO, only the current project's groups will 2001 # the modules index. If set to NO, only the current project's groups will be
2002 # listed.
2003 # The default value is: YES.
2004
2005 EXTERNAL_GROUPS = YES
2006
2007 # If the EXTERNAL_PAGES tag is set to YES all external pages will be listed in
2008 # the related pages index. If set to NO, only the current project's pages will
1563 # be listed. 2009 # be listed.
1564 2010 # The default value is: YES.
1565 EXTERNAL_GROUPS = YES 2011
2012 EXTERNAL_PAGES = YES
1566 2013
1567 # The PERL_PATH should be the absolute path and name of the perl script 2014 # The PERL_PATH should be the absolute path and name of the perl script
1568 # interpreter (i.e. the result of `which perl'). 2015 # interpreter (i.e. the result of 'which perl').
2016 # The default file (with absolute path) is: /usr/bin/perl.
1569 2017
1570 PERL_PATH = /usr/bin/perl 2018 PERL_PATH = /usr/bin/perl
1571 2019
1572 #--------------------------------------------------------------------------- 2020 #---------------------------------------------------------------------------
1573 # Configuration options related to the dot tool 2021 # Configuration options related to the dot tool
1574 #--------------------------------------------------------------------------- 2022 #---------------------------------------------------------------------------
1575 2023
1576 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 2024 # If the CLASS_DIAGRAMS tag is set to YES doxygen will generate a class diagram
1577 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 2025 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
1578 # or super classes. Setting the tag to NO turns the diagrams off. Note that 2026 # NO turns the diagrams off. Note that this option also works with HAVE_DOT
1579 # this option also works with HAVE_DOT disabled, but it is recommended to 2027 # disabled, but it is recommended to install and use dot, since it yields more
1580 # install and use dot, since it yields more powerful graphs. 2028 # powerful graphs.
2029 # The default value is: YES.
1581 2030
1582 CLASS_DIAGRAMS = YES 2031 CLASS_DIAGRAMS = YES
1583 2032
1584 # You can define message sequence charts within doxygen comments using the \msc 2033 # You can define message sequence charts within doxygen comments using the \msc
1585 # command. Doxygen will then run the mscgen tool (see 2034 # command. Doxygen will then run the mscgen tool (see:
1586 # http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the 2035 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
1587 # documentation. The MSCGEN_PATH tag allows you to specify the directory where 2036 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1588 # the mscgen tool resides. If left empty the tool is assumed to be found in the 2037 # the mscgen tool resides. If left empty the tool is assumed to be found in the
1589 # default search path. 2038 # default search path.
1590 2039
1591 MSCGEN_PATH = 2040 MSCGEN_PATH =
1592 2041
1593 # If set to YES, the inheritance and collaboration graphs will hide 2042 # You can include diagrams made with dia in doxygen documentation. Doxygen will
1594 # inheritance and usage relations if the target is undocumented 2043 # then run dia to produce the diagram and insert it in the documentation. The
1595 # or is not a class. 2044 # DIA_PATH tag allows you to specify the directory where the dia binary resides.
2045 # If left empty dia is assumed to be found in the default search path.
2046
2047 DIA_PATH =
2048
2049 # If set to YES, the inheritance and collaboration graphs will hide inheritance
2050 # and usage relations if the target is undocumented or is not a class.
2051 # The default value is: YES.
1596 2052
1597 HIDE_UNDOC_RELATIONS = YES 2053 HIDE_UNDOC_RELATIONS = YES
1598 2054
1599 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 2055 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1600 # available from the path. This tool is part of Graphviz, a graph visualization 2056 # available from the path. This tool is part of Graphviz (see:
1601 # toolkit from AT&T and Lucent Bell Labs. The other options in this section 2057 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
1602 # have no effect if this option is set to NO (the default) 2058 # Bell Labs. The other options in this section have no effect if this option is
2059 # set to NO
2060 # The default value is: YES.
1603 2061
1604 HAVE_DOT = NO 2062 HAVE_DOT = NO
1605 2063
1606 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is 2064 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
1607 # allowed to run in parallel. When set to 0 (the default) doxygen will 2065 # to run in parallel. When set to 0 doxygen will base this on the number of
1608 # base this on the number of processors available in the system. You can set it 2066 # processors available in the system. You can set it explicitly to a value
1609 # explicitly to a value larger than 0 to get control over the balance 2067 # larger than 0 to get control over the balance between CPU load and processing
1610 # between CPU load and processing speed. 2068 # speed.
2069 # Minimum value: 0, maximum value: 32, default value: 0.
2070 # This tag requires that the tag HAVE_DOT is set to YES.
1611 2071
1612 DOT_NUM_THREADS = 0 2072 DOT_NUM_THREADS = 0
1613 2073
1614 # By default doxygen will use the Helvetica font for all dot files that 2074 # When you want a differently looking font n the dot files that doxygen
1615 # doxygen generates. When you want a differently looking font you can specify 2075 # generates you can specify the font name using DOT_FONTNAME. You need to make
1616 # the font name using DOT_FONTNAME. You need to make sure dot is able to find 2076 # sure dot is able to find the font, which can be done by putting it in a
1617 # the font, which can be done by putting it in a standard location or by setting 2077 # standard location or by setting the DOTFONTPATH environment variable or by
1618 # the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the 2078 # setting DOT_FONTPATH to the directory containing the font.
1619 # directory containing the font. 2079 # The default value is: Helvetica.
2080 # This tag requires that the tag HAVE_DOT is set to YES.
1620 2081
1621 DOT_FONTNAME = Helvetica 2082 DOT_FONTNAME = Helvetica
1622 2083
1623 # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. 2084 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
1624 # The default size is 10pt. 2085 # dot graphs.
2086 # Minimum value: 4, maximum value: 24, default value: 10.
2087 # This tag requires that the tag HAVE_DOT is set to YES.
1625 2088
1626 DOT_FONTSIZE = 10 2089 DOT_FONTSIZE = 10
1627 2090
1628 # By default doxygen will tell dot to use the Helvetica font. 2091 # By default doxygen will tell dot to use the default font as specified with
1629 # If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to 2092 # DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
1630 # set the path where dot can find it. 2093 # the path where dot can find it using this tag.
2094 # This tag requires that the tag HAVE_DOT is set to YES.
1631 2095
1632 DOT_FONTPATH = 2096 DOT_FONTPATH =
1633 2097
1634 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 2098 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
1635 # will generate a graph for each documented class showing the direct and 2099 # each documented class showing the direct and indirect inheritance relations.
1636 # indirect inheritance relations. Setting this tag to YES will force the 2100 # Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
1637 # CLASS_DIAGRAMS tag to NO. 2101 # The default value is: YES.
2102 # This tag requires that the tag HAVE_DOT is set to YES.
1638 2103
1639 CLASS_GRAPH = YES 2104 CLASS_GRAPH = YES
1640 2105
1641 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 2106 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
1642 # will generate a graph for each documented class showing the direct and 2107 # graph for each documented class showing the direct and indirect implementation
1643 # indirect implementation dependencies (inheritance, containment, and 2108 # dependencies (inheritance, containment, and class references variables) of the
1644 # class references variables) of the class with other documented classes. 2109 # class with other documented classes.
2110 # The default value is: YES.
2111 # This tag requires that the tag HAVE_DOT is set to YES.
1645 2112
1646 COLLABORATION_GRAPH = YES 2113 COLLABORATION_GRAPH = YES
1647 2114
1648 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 2115 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
1649 # will generate a graph for groups, showing the direct groups dependencies 2116 # groups, showing the direct groups dependencies.
2117 # The default value is: YES.
2118 # This tag requires that the tag HAVE_DOT is set to YES.
1650 2119
1651 GROUP_GRAPHS = YES 2120 GROUP_GRAPHS = YES
1652 2121
1653 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and 2122 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1654 # collaboration diagrams in a style similar to the OMG's Unified Modeling 2123 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1655 # Language. 2124 # Language.
2125 # The default value is: NO.
2126 # This tag requires that the tag HAVE_DOT is set to YES.
1656 2127
1657 UML_LOOK = NO 2128 UML_LOOK = NO
1658 2129
1659 # If the UML_LOOK tag is enabled, the fields and methods are shown inside 2130 # If the UML_LOOK tag is enabled, the fields and methods are shown inside the
1660 # the class node. If there are many fields or methods and many nodes the 2131 # class node. If there are many fields or methods and many nodes the graph may
1661 # graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS 2132 # become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
1662 # threshold limits the number of items for each type to make the size more 2133 # number of items for each type to make the size more manageable. Set this to 0
1663 # managable. Set this to 0 for no limit. Note that the threshold may be 2134 # for no limit. Note that the threshold may be exceeded by 50% before the limit
1664 # exceeded by 50% before the limit is enforced. 2135 # is enforced. So when you set the threshold to 10, up to 15 fields may appear,
2136 # but if the number exceeds 15, the total amount of fields shown is limited to
2137 # 10.
2138 # Minimum value: 0, maximum value: 100, default value: 10.
2139 # This tag requires that the tag HAVE_DOT is set to YES.
1665 2140
1666 UML_LIMIT_NUM_FIELDS = 10 2141 UML_LIMIT_NUM_FIELDS = 10
1667 2142
1668 # If set to YES, the inheritance and collaboration graphs will show the 2143 # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
1669 # relations between templates and their instances. 2144 # collaboration graphs will show the relations between templates and their
2145 # instances.
2146 # The default value is: NO.
2147 # This tag requires that the tag HAVE_DOT is set to YES.
1670 2148
1671 TEMPLATE_RELATIONS = NO 2149 TEMPLATE_RELATIONS = NO
1672 2150
1673 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 2151 # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
1674 # tags are set to YES then doxygen will generate a graph for each documented 2152 # YES then doxygen will generate a graph for each documented file showing the
1675 # file showing the direct and indirect include dependencies of the file with 2153 # direct and indirect include dependencies of the file with other documented
1676 # other documented files. 2154 # files.
2155 # The default value is: YES.
2156 # This tag requires that the tag HAVE_DOT is set to YES.
1677 2157
1678 INCLUDE_GRAPH = YES 2158 INCLUDE_GRAPH = YES
1679 2159
1680 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 2160 # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
1681 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each 2161 # set to YES then doxygen will generate a graph for each documented file showing
1682 # documented header file showing the documented files that directly or 2162 # the direct and indirect include dependencies of the file with other documented
1683 # indirectly include this file. 2163 # files.
2164 # The default value is: YES.
2165 # This tag requires that the tag HAVE_DOT is set to YES.
1684 2166
1685 INCLUDED_BY_GRAPH = YES 2167 INCLUDED_BY_GRAPH = YES
1686 2168
1687 # If the CALL_GRAPH and HAVE_DOT options are set to YES then 2169 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
1688 # doxygen will generate a call dependency graph for every global function 2170 # dependency graph for every global function or class method.
1689 # or class method. Note that enabling this option will significantly increase 2171 #
1690 # the time of a run. So in most cases it will be better to enable call graphs 2172 # Note that enabling this option will significantly increase the time of a run.
1691 # for selected functions only using the \callgraph command. 2173 # So in most cases it will be better to enable call graphs for selected
2174 # functions only using the \callgraph command.
2175 # The default value is: NO.
2176 # This tag requires that the tag HAVE_DOT is set to YES.
1692 2177
1693 CALL_GRAPH = NO 2178 CALL_GRAPH = NO
1694 2179
1695 # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then 2180 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
1696 # doxygen will generate a caller dependency graph for every global function 2181 # dependency graph for every global function or class method.
1697 # or class method. Note that enabling this option will significantly increase 2182 #
1698 # the time of a run. So in most cases it will be better to enable caller 2183 # Note that enabling this option will significantly increase the time of a run.
1699 # graphs for selected functions only using the \callergraph command. 2184 # So in most cases it will be better to enable caller graphs for selected
2185 # functions only using the \callergraph command.
2186 # The default value is: NO.
2187 # This tag requires that the tag HAVE_DOT is set to YES.
1700 2188
1701 CALLER_GRAPH = NO 2189 CALLER_GRAPH = NO
1702 2190
1703 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 2191 # If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
1704 # will generate a graphical hierarchy of all classes instead of a textual one. 2192 # hierarchy of all classes instead of a textual one.
2193 # The default value is: YES.
2194 # This tag requires that the tag HAVE_DOT is set to YES.
1705 2195
1706 GRAPHICAL_HIERARCHY = YES 2196 GRAPHICAL_HIERARCHY = YES
1707 2197
1708 # If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES 2198 # If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
1709 # then doxygen will show the dependencies a directory has on other directories 2199 # dependencies a directory has on other directories in a graphical way. The
1710 # in a graphical way. The dependency relations are determined by the #include 2200 # dependency relations are determined by the #include relations between the
1711 # relations between the files in the directories. 2201 # files in the directories.
2202 # The default value is: YES.
2203 # This tag requires that the tag HAVE_DOT is set to YES.
1712 2204
1713 DIRECTORY_GRAPH = YES 2205 DIRECTORY_GRAPH = YES
1714 2206
1715 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 2207 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1716 # generated by dot. Possible values are svg, png, jpg, or gif. 2208 # generated by dot.
1717 # If left blank png will be used. If you choose svg you need to set 2209 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
1718 # HTML_FILE_EXTENSION to xhtml in order to make the SVG files 2210 # to make the SVG files visible in IE 9+ (other browsers do not have this
1719 # visible in IE 9+ (other browsers do not have this requirement). 2211 # requirement).
2212 # Possible values are: png, png:cairo, png:cairo:cairo, png:cairo:gd, png:gd,
2213 # png:gd:gd, jpg, jpg:cairo, jpg:cairo:gd, jpg:gd, jpg:gd:gd, gif, gif:cairo,
2214 # gif:cairo:gd, gif:gd, gif:gd:gd and svg.
2215 # The default value is: png.
2216 # This tag requires that the tag HAVE_DOT is set to YES.
1720 2217
1721 DOT_IMAGE_FORMAT = png 2218 DOT_IMAGE_FORMAT = png
1722 2219
1723 # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to 2220 # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
1724 # enable generation of interactive SVG images that allow zooming and panning. 2221 # enable generation of interactive SVG images that allow zooming and panning.
1725 # Note that this requires a modern browser other than Internet Explorer. 2222 #
1726 # Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you 2223 # Note that this requires a modern browser other than Internet Explorer. Tested
1727 # need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files 2224 # and working are Firefox, Chrome, Safari, and Opera.
1728 # visible. Older versions of IE do not have SVG support. 2225 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2226 # the SVG files visible. Older versions of IE do not have SVG support.
2227 # The default value is: NO.
2228 # This tag requires that the tag HAVE_DOT is set to YES.
1729 2229
1730 INTERACTIVE_SVG = NO 2230 INTERACTIVE_SVG = NO
1731 2231
1732 # The tag DOT_PATH can be used to specify the path where the dot tool can be 2232 # The DOT_PATH tag can be used to specify the path where the dot tool can be
1733 # found. If left blank, it is assumed the dot tool can be found in the path. 2233 # found. If left blank, it is assumed the dot tool can be found in the path.
2234 # This tag requires that the tag HAVE_DOT is set to YES.
1734 2235
1735 DOT_PATH = 2236 DOT_PATH =
1736 2237
1737 # The DOTFILE_DIRS tag can be used to specify one or more directories that 2238 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1738 # contain dot files that are included in the documentation (see the 2239 # contain dot files that are included in the documentation (see the \dotfile
1739 # \dotfile command). 2240 # command).
2241 # This tag requires that the tag HAVE_DOT is set to YES.
1740 2242
1741 DOTFILE_DIRS = 2243 DOTFILE_DIRS =
1742 2244
1743 # The MSCFILE_DIRS tag can be used to specify one or more directories that 2245 # The MSCFILE_DIRS tag can be used to specify one or more directories that
1744 # contain msc files that are included in the documentation (see the 2246 # contain msc files that are included in the documentation (see the \mscfile
1745 # \mscfile command). 2247 # command).
1746 2248
1747 MSCFILE_DIRS = 2249 MSCFILE_DIRS =
1748 2250
1749 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 2251 # The DIAFILE_DIRS tag can be used to specify one or more directories that
1750 # nodes that will be shown in the graph. If the number of nodes in a graph 2252 # contain dia files that are included in the documentation (see the \diafile
1751 # becomes larger than this value, doxygen will truncate the graph, which is 2253 # command).
1752 # visualized by representing a node as a red box. Note that doxygen if the 2254
1753 # number of direct children of the root node in a graph is already larger than 2255 DIAFILE_DIRS =
1754 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note 2256
1755 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. 2257 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2258 # that will be shown in the graph. If the number of nodes in a graph becomes
2259 # larger than this value, doxygen will truncate the graph, which is visualized
2260 # by representing a node as a red box. Note that doxygen if the number of direct
2261 # children of the root node in a graph is already larger than
2262 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
2263 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2264 # Minimum value: 0, maximum value: 10000, default value: 50.
2265 # This tag requires that the tag HAVE_DOT is set to YES.
1756 2266
1757 DOT_GRAPH_MAX_NODES = 50 2267 DOT_GRAPH_MAX_NODES = 50
1758 2268
1759 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 2269 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
1760 # graphs generated by dot. A depth value of 3 means that only nodes reachable 2270 # generated by dot. A depth value of 3 means that only nodes reachable from the
1761 # from the root by following a path via at most 3 edges will be shown. Nodes 2271 # root by following a path via at most 3 edges will be shown. Nodes that lay
1762 # that lay further from the root node will be omitted. Note that setting this 2272 # further from the root node will be omitted. Note that setting this option to 1
1763 # option to 1 or 2 may greatly reduce the computation time needed for large 2273 # or 2 may greatly reduce the computation time needed for large code bases. Also
1764 # code bases. Also note that the size of a graph can be further restricted by 2274 # note that the size of a graph can be further restricted by
1765 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. 2275 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
2276 # Minimum value: 0, maximum value: 1000, default value: 0.
2277 # This tag requires that the tag HAVE_DOT is set to YES.
1766 2278
1767 MAX_DOT_GRAPH_DEPTH = 0 2279 MAX_DOT_GRAPH_DEPTH = 0
1768 2280
1769 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 2281 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1770 # background. This is disabled by default, because dot on Windows does not 2282 # background. This is disabled by default, because dot on Windows does not seem
1771 # seem to support this out of the box. Warning: Depending on the platform used, 2283 # to support this out of the box.
1772 # enabling this option may lead to badly anti-aliased labels on the edges of 2284 #
1773 # a graph (i.e. they become hard to read). 2285 # Warning: Depending on the platform used, enabling this option may lead to
2286 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2287 # read).
2288 # The default value is: NO.
2289 # This tag requires that the tag HAVE_DOT is set to YES.
1774 2290
1775 DOT_TRANSPARENT = NO 2291 DOT_TRANSPARENT = NO
1776 2292
1777 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 2293 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1778 # files in one run (i.e. multiple -o and -T options on the command line). This 2294 # files in one run (i.e. multiple -o and -T options on the command line). This
1779 # makes dot run faster, but since only newer versions of dot (>1.8.10) 2295 # makes dot run faster, but since only newer versions of dot (>1.8.10) support
1780 # support this, this feature is disabled by default. 2296 # this, this feature is disabled by default.
2297 # The default value is: NO.
2298 # This tag requires that the tag HAVE_DOT is set to YES.
1781 2299
1782 DOT_MULTI_TARGETS = YES 2300 DOT_MULTI_TARGETS = YES
1783 2301
1784 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 2302 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
1785 # generate a legend page explaining the meaning of the various boxes and 2303 # explaining the meaning of the various boxes and arrows in the dot generated
1786 # arrows in the dot generated graphs. 2304 # graphs.
2305 # The default value is: YES.
2306 # This tag requires that the tag HAVE_DOT is set to YES.
1787 2307
1788 GENERATE_LEGEND = YES 2308 GENERATE_LEGEND = YES
1789 2309
1790 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 2310 # If the DOT_CLEANUP tag is set to YES doxygen will remove the intermediate dot
1791 # remove the intermediate dot files that are used to generate 2311 # files that are used to generate the various graphs.
1792 # the various graphs. 2312 # The default value is: YES.
2313 # This tag requires that the tag HAVE_DOT is set to YES.
1793 2314
1794 DOT_CLEANUP = YES 2315 DOT_CLEANUP = YES