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