/[svn]/liblscp/trunk/doc/liblscp.doxygen.in
ViewVC logotype

Contents of /liblscp/trunk/doc/liblscp.doxygen.in

Parent Directory Parent Directory | Revision Log Revision Log


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

  ViewVC Help
Powered by ViewVC