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