soult / pca

A PHP5 cache abstraction layer supporting APC, database, filesystem and memcached

This URL has Read+Write access

pca / Doxyfile
raw normal view history
e327bdcf » soult 2009-03-18 Add documentation 1 # Doxyfile 1.5.6
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 hash (#) is considered a comment and will be ignored
7 # The format is:
8 # TAG = value [value, ...]
9 # For lists items can also be appended using:
10 # TAG += value [value, ...]
11 # Values that contain spaces should be placed between quotes (" ")
12
13 #---------------------------------------------------------------------------
14 # Project related configuration options
15 #---------------------------------------------------------------------------
16
17 # This tag specifies the encoding used for all characters in the config file
18 # that follow. The default is UTF-8 which is also the encoding used for all
19 # text before the first occurrence of this tag. Doxygen uses libiconv (or the
20 # iconv built into libc) for the transcoding. See
21 # http://www.gnu.org/software/libiconv for the list of possible encodings.
22
23 DOXYFILE_ENCODING = UTF-8
24
25 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
26 # by quotes) that should identify the project.
27
28 PROJECT_NAME = PCA
29
30 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
31 # This could be handy for archiving the generated documentation or
32 # if some version control system is used.
33
34 PROJECT_NUMBER =
35
36 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
37 # base path where the generated documentation will be put.
38 # If a relative path is entered, it will be relative to the location
39 # where doxygen was started. If left blank the current directory will be used.
40
41 OUTPUT_DIRECTORY =
42
43 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
44 # 4096 sub-directories (in 2 levels) under the output directory of each output
45 # format and will distribute the generated files over these directories.
46 # Enabling this option can be useful when feeding doxygen a huge amount of
47 # source files, where putting all generated files in the same directory would
48 # otherwise cause performance problems for the file system.
49
50 CREATE_SUBDIRS = NO
51
52 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
53 # documentation generated by doxygen is written. Doxygen will use this
54 # information to generate all constant output in the proper language.
55 # The default language is English, other supported languages are:
56 # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
57 # Croatian, Czech, Danish, Dutch, Farsi, Finnish, French, German, Greek,
58 # Hungarian, Italian, Japanese, Japanese-en (Japanese with English messages),
59 # Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian, Polish,
60 # Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish,
61 # and Ukrainian.
62
63 OUTPUT_LANGUAGE = English
64
65 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
66 # include brief member descriptions after the members that are listed in
67 # the file and class documentation (similar to JavaDoc).
68 # Set to NO to disable this.
69
70 BRIEF_MEMBER_DESC = YES
71
72 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
73 # the brief description of a member or function before the detailed description.
74 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
75 # brief descriptions will be completely suppressed.
76
77 REPEAT_BRIEF = NO
78
79 # This tag implements a quasi-intelligent brief description abbreviator
80 # that is used to form the text in various listings. Each string
81 # in this list, if found as the leading text of the brief description, will be
82 # stripped from the text and the result after processing the whole list, is
83 # used as the annotated text. Otherwise, the brief description is used as-is.
84 # If left blank, the following values are used ("$name" is automatically
85 # replaced with the name of the entity): "The $name class" "The $name widget"
86 # "The $name file" "is" "provides" "specifies" "contains"
87 # "represents" "a" "an" "the"
88
89 ABBREVIATE_BRIEF =
90
91 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
92 # Doxygen will generate a detailed section even if there is only a brief
93 # description.
94
95 ALWAYS_DETAILED_SEC = NO
96
97 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
98 # inherited members of a class in the documentation of that class as if those
99 # members were ordinary class members. Constructors, destructors and assignment
100 # operators of the base classes will not be shown.
101
102 INLINE_INHERITED_MEMB = NO
103
104 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
105 # path before files name in the file list and in the header files. If set
106 # to NO the shortest path that makes the file name unique will be used.
107
108 FULL_PATH_NAMES = YES
109
110 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
111 # can be used to strip a user-defined part of the path. Stripping is
112 # only done if one of the specified strings matches the left-hand part of
113 # the path. The tag can be used to show relative paths in the file list.
114 # If left blank the directory from which doxygen is run is used as the
115 # path to strip.
116
117 STRIP_FROM_PATH =
118
119 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
120 # the path mentioned in the documentation of a class, which tells
121 # the reader which header file to include in order to use a class.
122 # If left blank only the name of the header file containing the class
123 # definition is used. Otherwise one should specify the include paths that
124 # are normally passed to the compiler using the -I flag.
125
126 STRIP_FROM_INC_PATH =
127
128 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
129 # (but less readable) file names. This can be useful is your file systems
130 # doesn't support long names like on DOS, Mac, or CD-ROM.
131
132 SHORT_NAMES = NO
133
134 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
135 # will interpret the first line (until the first dot) of a JavaDoc-style
136 # comment as the brief description. If set to NO, the JavaDoc
137 # comments will behave just like regular Qt-style comments
138 # (thus requiring an explicit @brief command for a brief description.)
139
140 JAVADOC_AUTOBRIEF = NO
141
142 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will
143 # interpret the first line (until the first dot) of a Qt-style
144 # comment as the brief description. If set to NO, the comments
145 # will behave just like regular Qt-style comments (thus requiring
146 # an explicit \brief command for a brief description.)
147
148 QT_AUTOBRIEF = NO
149
150 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
151 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
152 # comments) as a brief description. This used to be the default behaviour.
153 # The new default is to treat a multi-line C++ comment block as a detailed
154 # description. Set this tag to YES if you prefer the old behaviour instead.
155
156 MULTILINE_CPP_IS_BRIEF = NO
157
158 # If the DETAILS_AT_TOP tag is set to YES then Doxygen
159 # will output the detailed description near the top, like JavaDoc.
160 # If set to NO, the detailed description appears after the member
161 # documentation.
162
163 DETAILS_AT_TOP = NO
164
165 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
166 # member inherits the documentation from any documented member that it
167 # re-implements.
168
169 INHERIT_DOCS = YES
170
171 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
172 # a new page for each member. If set to NO, the documentation of a member will
173 # be part of the file/class/namespace that contains it.
174
175 SEPARATE_MEMBER_PAGES = NO
176
177 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
178 # Doxygen uses this value to replace tabs by spaces in code fragments.
179
180 TAB_SIZE = 8
181
182 # This tag can be used to specify a number of aliases that acts
183 # as commands in the documentation. An alias has the form "name=value".
184 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
185 # put the command \sideeffect (or @sideeffect) in the documentation, which
186 # will result in a user-defined paragraph with heading "Side Effects:".
187 # You can put \n's in the value part of an alias to insert newlines.
188
189 ALIASES =
190
191 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
192 # sources only. Doxygen will then generate output that is more tailored for C.
193 # For instance, some of the names that are used will be different. The list
194 # of all members will be omitted, etc.
195
196 OPTIMIZE_OUTPUT_FOR_C = NO
197
198 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
199 # sources only. Doxygen will then generate output that is more tailored for
200 # Java. For instance, namespaces will be presented as packages, qualified
201 # scopes will look different, etc.
202
203 OPTIMIZE_OUTPUT_JAVA = NO
204
205 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
206 # sources only. Doxygen will then generate output that is more tailored for
207 # Fortran.
208
209 OPTIMIZE_FOR_FORTRAN = NO
210
211 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
212 # sources. Doxygen will then generate output that is tailored for
213 # VHDL.
214
215 OPTIMIZE_OUTPUT_VHDL = NO
216
217 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
218 # to include (a tag file for) the STL sources as input, then you should
219 # set this tag to YES in order to let doxygen match functions declarations and
220 # definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
221 # func(std::string) {}). This also make the inheritance and collaboration
222 # diagrams that involve STL classes more complete and accurate.
223
224 BUILTIN_STL_SUPPORT = NO
225
226 # If you use Microsoft's C++/CLI language, you should set this option to YES to
227 # enable parsing support.
228
229 CPP_CLI_SUPPORT = NO
230
231 # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
232 # Doxygen will parse them like normal C++ but will assume all classes use public
233 # instead of private inheritance when no explicit protection keyword is present.
234
235 SIP_SUPPORT = NO
236
237 # For Microsoft's IDL there are propget and propput attributes to indicate getter
238 # and setter methods for a property. Setting this option to YES (the default)
239 # will make doxygen to replace the get and set methods by a property in the
240 # documentation. This will only work if the methods are indeed getting or
241 # setting a simple type. If this is not the case, or you want to show the
242 # methods anyway, you should set this option to NO.
243
244 IDL_PROPERTY_SUPPORT = YES
245
246 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
247 # tag is set to YES, then doxygen will reuse the documentation of the first
248 # member in the group (if any) for the other members of the group. By default
249 # all members of a group must be documented explicitly.
250
251 DISTRIBUTE_GROUP_DOC = NO
252
253 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
254 # the same type (for instance a group of public functions) to be put as a
255 # subgroup of that type (e.g. under the Public Functions section). Set it to
256 # NO to prevent subgrouping. Alternatively, this can be done per class using
257 # the \nosubgrouping command.
258
259 SUBGROUPING = YES
260
261 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
262 # is documented as struct, union, or enum with the name of the typedef. So
263 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
264 # with name TypeT. When disabled the typedef will appear as a member of a file,
265 # namespace, or class. And the struct will be named TypeS. This can typically
266 # be useful for C code in case the coding convention dictates that all compound
267 # types are typedef'ed and only the typedef is referenced, never the tag name.
268
269 TYPEDEF_HIDES_STRUCT = NO
270
271 #---------------------------------------------------------------------------
272 # Build related configuration options
273 #---------------------------------------------------------------------------
274
275 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
276 # documentation are documented, even if no documentation was available.
277 # Private class members and static file members will be hidden unless
278 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
279
280 EXTRACT_ALL = NO
281
282 # will be included in the documentation.
283
284 EXTRACT_PRIVATE = NO
285
286 # If the EXTRACT_STATIC tag is set to YES all static members of a file
287 # will be included in the documentation.
288
289 EXTRACT_STATIC = NO
290
291 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
292 # defined locally in source files will be included in the documentation.
293 # If set to NO only classes defined in header files are included.
294
295 EXTRACT_LOCAL_CLASSES = YES
296
297 # This flag is only useful for Objective-C code. When set to YES local
298 # methods, which are defined in the implementation section but not in
299 # the interface are included in the documentation.
300 # If set to NO (the default) only methods in the interface are included.
301
302 EXTRACT_LOCAL_METHODS = NO
303
304 # If this flag is set to YES, the members of anonymous namespaces will be
305 # extracted and appear in the documentation as a namespace called
306 # 'anonymous_namespace{file}', where file will be replaced with the base
307 # name of the file that contains the anonymous namespace. By default
308 # anonymous namespace are hidden.
309
310 EXTRACT_ANON_NSPACES = NO
311
312 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
313 # undocumented members of documented classes, files or namespaces.
314 # If set to NO (the default) these members will be included in the
315 # various overviews, but no documentation section is generated.
316 # This option has no effect if EXTRACT_ALL is enabled.
317
318 HIDE_UNDOC_MEMBERS = NO
319
320 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
321 # undocumented classes that are normally visible in the class hierarchy.
322 # If set to NO (the default) these classes will be included in the various
323 # overviews. This option has no effect if EXTRACT_ALL is enabled.
324
325 HIDE_UNDOC_CLASSES = NO
326
327 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
328 # friend (class|struct|union) declarations.
329 # If set to NO (the default) these declarations will be included in the
330 # documentation.
331
332 HIDE_FRIEND_COMPOUNDS = NO
333
334 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
335 # documentation blocks found inside the body of a function.
336 # If set to NO (the default) these blocks will be appended to the
337 # function's detailed documentation block.
338
339 HIDE_IN_BODY_DOCS = NO
340
341 # The INTERNAL_DOCS tag determines if documentation
342 # that is typed after a \internal command is included. If the tag is set
343 # to NO (the default) then the documentation will be excluded.
344 # Set it to YES to include the internal documentation.
345
346 INTERNAL_DOCS = NO
347
348 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
349 # file names in lower-case letters. If set to YES upper-case letters are also
350 # allowed. This is useful if you have classes or files whose names only differ
351 # in case and if your file system supports case sensitive file names. Windows
352 # and Mac users are advised to set this option to NO.
353
354 CASE_SENSE_NAMES = YES
355
356 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
357 # will show members with their full class and namespace scopes in the
358 # documentation. If set to YES the scope will be hidden.
359
360 HIDE_SCOPE_NAMES = NO
361
362 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
363 # will put a list of the files that are included by a file in the documentation
364 # of that file.
365
366 SHOW_INCLUDE_FILES = YES
367
368 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
369 # is inserted in the documentation for inline members.
370
371 INLINE_INFO = YES
372
373 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
374 # will sort the (detailed) documentation of file and class members
375 # alphabetically by member name. If set to NO the members will appear in
376 # declaration order.
377
378 SORT_MEMBER_DOCS = YES
379
380 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
381 # brief documentation of file, namespace and class members alphabetically
382 # by member name. If set to NO (the default) the members will appear in
383 # declaration order.
384
385 SORT_BRIEF_DOCS = NO
386
387 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
388 # hierarchy of group names into alphabetical order. If set to NO (the default)
389 # the group names will appear in their defined order.
390
391 SORT_GROUP_NAMES = NO
392
393 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
394 # sorted by fully-qualified names, including namespaces. If set to
395 # NO (the default), the class list will be sorted only by class name,
396 # not including the namespace part.
397 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
398 # Note: This option applies only to the class list, not to the
399 # alphabetical list.
400
401 SORT_BY_SCOPE_NAME = NO
402
403 # The GENERATE_TODOLIST tag can be used to enable (YES) or
404 # disable (NO) the todo list. This list is created by putting \todo
405 # commands in the documentation.
406
407 GENERATE_TODOLIST = YES
408
409 # The GENERATE_TESTLIST tag can be used to enable (YES) or
410 # disable (NO) the test list. This list is created by putting \test
411 # commands in the documentation.
412
413 GENERATE_TESTLIST = YES
414
415 # The GENERATE_BUGLIST tag can be used to enable (YES) or
416 # disable (NO) the bug list. This list is created by putting \bug
417 # commands in the documentation.
418
419 GENERATE_BUGLIST = YES
420
421 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
422 # disable (NO) the deprecated list. This list is created by putting
423 # \deprecated commands in the documentation.
424
425 GENERATE_DEPRECATEDLIST= YES
426
427 # The ENABLED_SECTIONS tag can be used to enable conditional
428 # documentation sections, marked by \if sectionname ... \endif.
429
430 ENABLED_SECTIONS =
431
432 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
433 # the initial value of a variable or define consists of for it to appear in
434 # the documentation. If the initializer consists of more lines than specified
435 # here it will be hidden. Use a value of 0 to hide initializers completely.
436 # The appearance of the initializer of individual variables and defines in the
437 # documentation can be controlled using \showinitializer or \hideinitializer
438 # command in the documentation regardless of this setting.
439
440 MAX_INITIALIZER_LINES = 30
441
442 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
443 # at the bottom of the documentation of classes and structs. If set to YES the
444 # list will mention the files that were used to generate the documentation.
445
446 SHOW_USED_FILES = YES
447
448 # If the sources in your project are distributed over multiple directories
449 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
450 # in the documentation. The default is NO.
451
452 SHOW_DIRECTORIES = NO
453
454 # Set the SHOW_FILES tag to NO to disable the generation of the Files page.
455 # This will remove the Files entry from the Quick Index and from the
456 # Folder Tree View (if specified). The default is YES.
457
458 SHOW_FILES = YES
459
460 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the
461 # Namespaces page. This will remove the Namespaces entry from the Quick Index
462 # and from the Folder Tree View (if specified). The default is YES.
463
464 SHOW_NAMESPACES = YES
465
466 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
467 # doxygen should invoke to get the current version for each file (typically from
468 # the version control system). Doxygen will invoke the program by executing (via
469 # popen()) the command <command> <input-file>, where <command> is the value of
470 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
471 # provided by doxygen. Whatever the program writes to standard output
472 # is used as the file version. See the manual for examples.
473
474 FILE_VERSION_FILTER =
475
476 #---------------------------------------------------------------------------
477 # configuration options related to warning and progress messages
478 #---------------------------------------------------------------------------
479
480 # The QUIET tag can be used to turn on/off the messages that are generated
481 # by doxygen. Possible values are YES and NO. If left blank NO is used.
482
483 QUIET = NO
484
485 # The WARNINGS tag can be used to turn on/off the warning messages that are
486 # generated by doxygen. Possible values are YES and NO. If left blank
487 # NO is used.
488
489 WARNINGS = YES
490
491 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
492 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
493 # automatically be disabled.
494
495 WARN_IF_UNDOCUMENTED = YES
496
497 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
498 # potential errors in the documentation, such as not documenting some
499 # parameters in a documented function, or documenting parameters that
500 # don't exist or using markup commands wrongly.
501
502 WARN_IF_DOC_ERROR = YES
503
504 # This WARN_NO_PARAMDOC option can be abled to get warnings for
505 # functions that are documented, but have no documentation for their parameters
506 # or return value. If set to NO (the default) doxygen will only warn about
507 # wrong or incomplete parameter documentation, but not about the absence of
508 # documentation.
509
510 WARN_NO_PARAMDOC = NO
511
512 # The WARN_FORMAT tag determines the format of the warning messages that
513 # doxygen can produce. The string should contain the $file, $line, and $text
514 # tags, which will be replaced by the file and line number from which the
515 # warning originated and the warning text. Optionally the format may contain
516 # $version, which will be replaced by the version of the file (if it could
517 # be obtained via FILE_VERSION_FILTER)
518
519 WARN_FORMAT = "$file:$line: $text"
520
521 # The WARN_LOGFILE tag can be used to specify a file to which warning
522 # and error messages should be written. If left blank the output is written
523 # to stderr.
524
525 WARN_LOGFILE =
526
527 #---------------------------------------------------------------------------
528 # configuration options related to the input files
529 #---------------------------------------------------------------------------
530
531 # The INPUT tag can be used to specify the files and/or directories that contain
532 # documented source files. You may enter file names like "myfile.cpp" or
533 # directories like "/usr/src/myproject". Separate the files or directories
534 # with spaces.
535
536 INPUT =
537
538 # This tag can be used to specify the character encoding of the source files
539 # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
540 # also the default input encoding. Doxygen uses libiconv (or the iconv built
541 # into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
542 # the list of possible encodings.
543
544 INPUT_ENCODING = UTF-8
545
546 # If the value of the INPUT tag contains directories, you can use the
547 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
548 # and *.h) to filter out the source-files in the directories. If left
549 # blank the following patterns are tested:
550 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
551 # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
552
553 FILE_PATTERNS = *.php
554
555 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
556 # should be searched for input files as well. Possible values are YES and NO.
557 # If left blank NO is used.
558
559 RECURSIVE = YES
560
561 # The EXCLUDE tag can be used to specify files and/or directories that should
562 # excluded from the INPUT source files. This way you can easily exclude a
563 # subdirectory from a directory tree whose root is specified with the INPUT tag.
564
565 EXCLUDE =
566
567 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
568 # directories that are symbolic links (a Unix filesystem feature) are excluded
569 # from the input.
570
571 EXCLUDE_SYMLINKS = NO
572
573 # If the value of the INPUT tag contains directories, you can use the
574 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
575 # certain files from those directories. Note that the wildcards are matched
576 # against the file with absolute path, so to exclude all test directories
577 # for example use the pattern */test/*
578
579 EXCLUDE_PATTERNS = */tests/*
580
581 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
582 # (namespaces, classes, functions, etc.) that should be excluded from the
583 # output. The symbol name can be a fully qualified name, a word, or if the
584 # wildcard * is used, a substring. Examples: ANamespace, AClass,
585 # AClass::ANamespace, ANamespace::*Test
586
587 EXCLUDE_SYMBOLS =
588
589 # The EXAMPLE_PATH tag can be used to specify one or more files or
590 # directories that contain example code fragments that are included (see
591 # the \include command).
592
593 EXAMPLE_PATH =
594
595 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
596 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
597 # and *.h) to filter out the source-files in the directories. If left
598 # blank all files are included.
599
600 EXAMPLE_PATTERNS =
601
602 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
603 # searched for input files to be used with the \include or \dontinclude
604 # commands irrespective of the value of the RECURSIVE tag.
605 # Possible values are YES and NO. If left blank NO is used.
606
607 EXAMPLE_RECURSIVE = NO
608
609 # The IMAGE_PATH tag can be used to specify one or more files or
610 # directories that contain image that are included in the documentation (see
611 # the \image command).
612
613 IMAGE_PATH =
614
615 # The INPUT_FILTER tag can be used to specify a program that doxygen should
616 # invoke to filter for each input file. Doxygen will invoke the filter program
617 # by executing (via popen()) the command <filter> <input-file>, where <filter>
618 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
619 # input file. Doxygen will then use the output that the filter program writes
620 # to standard output. If FILTER_PATTERNS is specified, this tag will be
621 # ignored.
622
623 INPUT_FILTER =
624
625 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
626 # basis. Doxygen will compare the file name with each pattern and apply the
627 # filter if there is a match. The filters are a list of the form:
628 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
629 # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
630 # is applied to all files.
631
632 FILTER_PATTERNS =
633
634 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
635 # INPUT_FILTER) will be used to filter the input files when producing source
636 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
637
638 FILTER_SOURCE_FILES = NO
639
640 #---------------------------------------------------------------------------
641 # configuration options related to source browsing
642 #---------------------------------------------------------------------------
643
644 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
645 # be generated. Documented entities will be cross-referenced with these sources.
646 # Note: To get rid of all source code in the generated output, make sure also
647 # VERBATIM_HEADERS is set to NO.
648
649 SOURCE_BROWSER = NO
650
651 # Setting the INLINE_SOURCES tag to YES will include the body
652 # of functions and classes directly in the documentation.
653
654 INLINE_SOURCES = NO
655
656 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
657 # doxygen to hide any special comment blocks from generated source code
658 # fragments. Normal C and C++ comments will always remain visible.
659
660 STRIP_CODE_COMMENTS = YES
661
662 # If the REFERENCED_BY_RELATION tag is set to YES
663 # then for each documented function all documented
664 # functions referencing it will be listed.
665
666 REFERENCED_BY_RELATION = NO
667
668 # If the REFERENCES_RELATION tag is set to YES
669 # then for each documented function all documented entities
670 # called/used by that function will be listed.
671
672 REFERENCES_RELATION = NO
673
674 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
675 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
676 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
677 # link to the source code. Otherwise they will link to the documentstion.
678
679 REFERENCES_LINK_SOURCE = YES
680
681 # If the USE_HTAGS tag is set to YES then the references to source code
682 # will point to the HTML generated by the htags(1) tool instead of doxygen
683 # built-in source browser. The htags tool is part of GNU's global source
684 # tagging system (see http://www.gnu.org/software/global/global.html). You
685 # will need version 4.8.6 or higher.
686
687 USE_HTAGS = NO
688
689 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
690 # will generate a verbatim copy of the header file for each class for
691 # which an include is specified. Set to NO to disable this.
692
693 VERBATIM_HEADERS = YES
694
695 #---------------------------------------------------------------------------
696 # configuration options related to the alphabetical class index
697 #---------------------------------------------------------------------------
698
699 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
700 # of all compounds will be generated. Enable this if the project
701 # contains a lot of classes, structs, unions or interfaces.
702
703 ALPHABETICAL_INDEX = NO
704
705 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
706 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
707 # in which this list will be split (can be a number in the range [1..20])
708
709 COLS_IN_ALPHA_INDEX = 5
710
711 # In case all classes in a project start with a common prefix, all
712 # classes will be put under the same header in the alphabetical index.
713 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
714 # should be ignored while generating the index headers.
715
716 IGNORE_PREFIX =
717
718 #---------------------------------------------------------------------------
719 # configuration options related to the HTML output
720 #---------------------------------------------------------------------------
721
722 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
723 # generate HTML output.
724
725 GENERATE_HTML = YES
726
727 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
728 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
729 # put in front of it. If left blank `html' will be used as the default path.
730
731 HTML_OUTPUT = doc/
732
733 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
734 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
735 # doxygen will generate files with .html extension.
736
737 HTML_FILE_EXTENSION = .html
738
739 # The HTML_HEADER tag can be used to specify a personal HTML header for
740 # each generated HTML page. If it is left blank doxygen will generate a
741 # standard header.
742
743 HTML_HEADER =
744
745 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
746 # each generated HTML page. If it is left blank doxygen will generate a
747 # standard footer.
748
749 HTML_FOOTER =
750
751 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
752 # style sheet that is used by each HTML page. It can be used to
753 # fine-tune the look of the HTML output. If the tag is left blank doxygen
754 # will generate a default style sheet. Note that doxygen will try to copy
755 # the style sheet file to the HTML output directory, so don't put your own
756 # stylesheet in the HTML output directory as well, or it will be erased!
757
758 HTML_STYLESHEET =
759
760 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
761 # files or namespaces will be aligned in HTML using tables. If set to
762 # NO a bullet list will be used.
763
764 HTML_ALIGN_MEMBERS = YES
765
766 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
767 # will be generated that can be used as input for tools like the
768 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
769 # of the generated HTML documentation.
770
771 GENERATE_HTMLHELP = NO
772
773 # If the GENERATE_DOCSET tag is set to YES, additional index files
774 # will be generated that can be used as input for Apple's Xcode 3
775 # integrated development environment, introduced with OSX 10.5 (Leopard).
776 # To create a documentation set, doxygen will generate a Makefile in the
777 # HTML output directory. Running make will produce the docset in that
778 # directory and running "make install" will install the docset in
779 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
780 # it at startup.
781
782 GENERATE_DOCSET = NO
783
784 # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
785 # feed. A documentation feed provides an umbrella under which multiple
786 # documentation sets from a single provider (such as a company or product suite)
787 # can be grouped.
788
789 DOCSET_FEEDNAME = "Doxygen generated docs"
790
791 # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
792 # should uniquely identify the documentation set bundle. This should be a
793 # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
794 # will append .docset to the name.
795
796 DOCSET_BUNDLE_ID = org.doxygen.Project
797
798 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
799 # documentation will contain sections that can be hidden and shown after the
800 # page has loaded. For this to work a browser that supports
801 # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
802 # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
803
804 HTML_DYNAMIC_SECTIONS = NO
805
806 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
807 # be used to specify the file name of the resulting .chm file. You
808 # can add a path in front of the file if the result should not be
809 # written to the html output directory.
810
811 CHM_FILE =
812
813 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
814 # be used to specify the location (absolute path including file name) of
815 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
816 # the HTML help compiler on the generated index.hhp.
817
818 HHC_LOCATION =
819
820 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
821 # controls if a separate .chi index file is generated (YES) or that
822 # it should be included in the master .chm file (NO).
823
824 GENERATE_CHI = NO
825
826 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
827 # is used to encode HtmlHelp index (hhk), content (hhc) and project file
828 # content.
829
830 CHM_INDEX_ENCODING =
831
832 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
833 # controls whether a binary table of contents is generated (YES) or a
834 # normal table of contents (NO) in the .chm file.
835
836 BINARY_TOC = NO
837
838 # The TOC_EXPAND flag can be set to YES to add extra items for group members
839 # to the contents of the HTML help documentation and to the tree view.
840
841 TOC_EXPAND = NO
842
843 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
844 # top of each HTML page. The value NO (the default) enables the index and
845 # the value YES disables it.
846
847 DISABLE_INDEX = NO
848
849 # This tag can be used to set the number of enum values (range [1..20])
850 # that doxygen will group on one line in the generated HTML documentation.
851
852 ENUM_VALUES_PER_LINE = 4
853
854 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
855 # structure should be generated to display hierarchical information.
856 # If the tag value is set to FRAME, a side panel will be generated
857 # containing a tree-like index structure (just like the one that
858 # is generated for HTML Help). For this to work a browser that supports
859 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
860 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
861 # probably better off using the HTML help feature. Other possible values
862 # for this tag are: HIERARCHIES, which will generate the Groups, Directories,
863 # and Class Hiererachy pages using a tree view instead of an ordered list;
864 # ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which
865 # disables this behavior completely. For backwards compatibility with previous
866 # releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE
867 # respectively.
868
869 GENERATE_TREEVIEW = NONE
870
871 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
872 # used to set the initial width (in pixels) of the frame in which the tree
873 # is shown.
874
875 TREEVIEW_WIDTH = 250
876
877 # Use this tag to change the font size of Latex formulas included
878 # as images in the HTML documentation. The default is 10. Note that
879 # when you change the font size after a successful doxygen run you need
880 # to manually remove any form_*.png images from the HTML output directory
881 # to force them to be regenerated.
882
883 FORMULA_FONTSIZE = 10
884
885 #---------------------------------------------------------------------------
886 # configuration options related to the LaTeX output
887 #---------------------------------------------------------------------------
888
889 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
890 # generate Latex output.
891
892 GENERATE_LATEX = NO
893
894 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
895 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
896 # put in front of it. If left blank `latex' will be used as the default path.
897
898 LATEX_OUTPUT = latex
899
900 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
901 # invoked. If left blank `latex' will be used as the default command name.
902
903 LATEX_CMD_NAME = latex
904
905 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
906 # generate index for LaTeX. If left blank `makeindex' will be used as the
907 # default command name.
908
909 MAKEINDEX_CMD_NAME = makeindex
910
911 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
912 # LaTeX documents. This may be useful for small projects and may help to
913 # save some trees in general.
914
915 COMPACT_LATEX = NO
916
917 # The PAPER_TYPE tag can be used to set the paper type that is used
918 # by the printer. Possible values are: a4, a4wide, letter, legal and
919 # executive. If left blank a4wide will be used.
920
921 PAPER_TYPE = a4wide
922
923 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
924 # packages that should be included in the LaTeX output.
925
926 EXTRA_PACKAGES =
927
928 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
929 # the generated latex document. The header should contain everything until
930 # the first chapter. If it is left blank doxygen will generate a
931 # standard header. Notice: only use this tag if you know what you are doing!
932
933 LATEX_HEADER =
934
935 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
936 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
937 # contain links (just like the HTML output) instead of page references
938 # This makes the output suitable for online browsing using a pdf viewer.
939
940 PDF_HYPERLINKS = YES
941
942 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
943 # plain latex in the generated Makefile. Set this option to YES to get a
944 # higher quality PDF documentation.
945
946 USE_PDFLATEX = YES
947
948 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
949 # command to the generated LaTeX files. This will instruct LaTeX to keep
950 # running if errors occur, instead of asking the user for help.
951 # This option is also used when generating formulas in HTML.
952
953 LATEX_BATCHMODE = NO
954
955 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
956 # include the index chapters (such as File Index, Compound Index, etc.)
957 # in the output.
958
959 LATEX_HIDE_INDICES = NO
960
961 #---------------------------------------------------------------------------
962 # configuration options related to the RTF output
963 #---------------------------------------------------------------------------
964
965 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
966 # The RTF output is optimized for Word 97 and may not look very pretty with
967 # other RTF readers or editors.
968
969 GENERATE_RTF = NO
970
971 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
972 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
973 # put in front of it. If left blank `rtf' will be used as the default path.
974
975 RTF_OUTPUT = rtf
976
977 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
978 # RTF documents. This may be useful for small projects and may help to
979 # save some trees in general.
980
981 COMPACT_RTF = NO
982
983 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
984 # will contain hyperlink fields. The RTF file will
985 # contain links (just like the HTML output) instead of page references.
986 # This makes the output suitable for online browsing using WORD or other
987 # programs which support those fields.
988 # Note: wordpad (write) and others do not support links.
989
990 RTF_HYPERLINKS = NO
991
992 # Load stylesheet definitions from file. Syntax is similar to doxygen's
993 # config file, i.e. a series of assignments. You only have to provide
994 # replacements, missing definitions are set to their default value.
995
996 RTF_STYLESHEET_FILE =
997
998 # Set optional variables used in the generation of an rtf document.
999 # Syntax is similar to doxygen's config file.
1000
1001 RTF_EXTENSIONS_FILE =
1002
1003 #---------------------------------------------------------------------------
1004 # configuration options related to the man page output
1005 #---------------------------------------------------------------------------
1006
1007 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1008 # generate man pages
1009
1010 GENERATE_MAN = NO
1011
1012 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
1013 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1014 # put in front of it. If left blank `man' will be used as the default path.
1015
1016 MAN_OUTPUT = man
1017
1018 # The MAN_EXTENSION tag determines the extension that is added to
1019 # the generated man pages (default is the subroutine's section .3)
1020
1021 MAN_EXTENSION = .3
1022
1023 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1024 # then it will generate one additional man file for each entity
1025 # documented in the real man page(s). These additional files
1026 # only source the real man page, but without them the man command
1027 # would be unable to find the correct page. The default is NO.
1028
1029 MAN_LINKS = NO
1030
1031 #---------------------------------------------------------------------------
1032 # configuration options related to the XML output
1033 #---------------------------------------------------------------------------
1034
1035 # If the GENERATE_XML tag is set to YES Doxygen will
1036 # generate an XML file that captures the structure of
1037 # the code including all documentation.
1038
1039 GENERATE_XML = NO
1040
1041 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
1042 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1043 # put in front of it. If left blank `xml' will be used as the default path.
1044
1045 XML_OUTPUT = xml
1046
1047 # The XML_SCHEMA tag can be used to specify an XML schema,
1048 # which can be used by a validating XML parser to check the
1049 # syntax of the XML files.
1050
1051 XML_SCHEMA =
1052
1053 # The XML_DTD tag can be used to specify an XML DTD,
1054 # which can be used by a validating XML parser to check the
1055 # syntax of the XML files.
1056
1057 XML_DTD =
1058
1059 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1060 # dump the program listings (including syntax highlighting
1061 # and cross-referencing information) to the XML output. Note that
1062 # enabling this will significantly increase the size of the XML output.
1063
1064 XML_PROGRAMLISTING = YES
1065
1066 #---------------------------------------------------------------------------
1067 # configuration options for the AutoGen Definitions output
1068 #---------------------------------------------------------------------------
1069
1070 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1071 # generate an AutoGen Definitions (see autogen.sf.net) file
1072 # that captures the structure of the code including all
1073 # documentation. Note that this feature is still experimental
1074 # and incomplete at the moment.
1075
1076 GENERATE_AUTOGEN_DEF = NO
1077
1078 #---------------------------------------------------------------------------
1079 # configuration options related to the Perl module output
1080 #---------------------------------------------------------------------------
1081
1082 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
1083 # generate a Perl module file that captures the structure of
1084 # the code including all documentation. Note that this
1085 # feature is still experimental and incomplete at the
1086 # moment.
1087
1088 GENERATE_PERLMOD = NO
1089
1090 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1091 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
1092 # to generate PDF and DVI output from the Perl module output.
1093
1094 PERLMOD_LATEX = NO
1095
1096 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1097 # nicely formatted so it can be parsed by a human reader. This is useful
1098 # if you want to understand what is going on. On the other hand, if this
1099 # tag is set to NO the size of the Perl module output will be much smaller
1100 # and Perl will parse it just the same.
1101
1102 PERLMOD_PRETTY = YES
1103
1104 # The names of the make variables in the generated doxyrules.make file
1105 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1106 # This is useful so different doxyrules.make files included by the same
1107 # Makefile don't overwrite each other's variables.
1108
1109 PERLMOD_MAKEVAR_PREFIX =
1110
1111 #---------------------------------------------------------------------------
1112 # Configuration options related to the preprocessor
1113 #---------------------------------------------------------------------------
1114
1115 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1116 # evaluate all C-preprocessor directives found in the sources and include
1117 # files.
1118
1119 ENABLE_PREPROCESSING = YES
1120
1121 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1122 # names in the source code. If set to NO (the default) only conditional
1123 # compilation will be performed. Macro expansion can be done in a controlled
1124 # way by setting EXPAND_ONLY_PREDEF to YES.
1125
1126 MACRO_EXPANSION = NO
1127
1128 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1129 # then the macro expansion is limited to the macros specified with the
1130 # PREDEFINED and EXPAND_AS_DEFINED tags.
1131
1132 EXPAND_ONLY_PREDEF = NO
1133
1134 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1135 # in the INCLUDE_PATH (see below) will be search if a #include is found.
1136
1137 SEARCH_INCLUDES = YES
1138
1139 # The INCLUDE_PATH tag can be used to specify one or more directories that
1140 # contain include files that are not input files but should be processed by
1141 # the preprocessor.
1142
1143 INCLUDE_PATH =
1144
1145 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1146 # patterns (like *.h and *.hpp) to filter out the header-files in the
1147 # directories. If left blank, the patterns specified with FILE_PATTERNS will
1148 # be used.
1149
1150 INCLUDE_FILE_PATTERNS =
1151
1152 # The PREDEFINED tag can be used to specify one or more macro names that
1153 # are defined before the preprocessor is started (similar to the -D option of
1154 # gcc). The argument of the tag is a list of macros of the form: name
1155 # or name=definition (no spaces). If the definition and the = are
1156 # omitted =1 is assumed. To prevent a macro definition from being
1157 # undefined via #undef or recursively expanded use the := operator
1158 # instead of the = operator.
1159
1160 PREDEFINED =
1161
1162 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1163 # this tag can be used to specify a list of macro names that should be expanded.
1164 # The macro definition that is found in the sources will be used.
1165 # Use the PREDEFINED tag if you want to use a different macro definition.
1166
1167 EXPAND_AS_DEFINED =
1168
1169 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1170 # doxygen's preprocessor will remove all function-like macros that are alone
1171 # on a line, have an all uppercase name, and do not end with a semicolon. Such
1172 # function macros are typically used for boiler-plate code, and will confuse
1173 # the parser if not removed.
1174
1175 SKIP_FUNCTION_MACROS = YES
1176
1177 #---------------------------------------------------------------------------
1178 # Configuration::additions related to external references
1179 #---------------------------------------------------------------------------
1180
1181 # The TAGFILES option can be used to specify one or more tagfiles.
1182 # Optionally an initial location of the external documentation
1183 # can be added for each tagfile. The format of a tag file without
1184 # this location is as follows:
1185 # TAGFILES = file1 file2 ...
1186 # Adding location for the tag files is done as follows:
1187 # TAGFILES = file1=loc1 "file2 = loc2" ...
1188 # where "loc1" and "loc2" can be relative or absolute paths or
1189 # URLs. If a location is present for each tag, the installdox tool
1190 # does not have to be run to correct the links.
1191 # Note that each tag file must have a unique name
1192 # (where the name does NOT include the path)
1193 # If a tag file is not located in the directory in which doxygen
1194 # is run, you must also specify the path to the tagfile here.
1195
1196 TAGFILES =
1197
1198 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1199 # a tag file that is based on the input files it reads.
1200
1201 GENERATE_TAGFILE =
1202
1203 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1204 # in the class index. If set to NO only the inherited external classes
1205 # will be listed.
1206
1207 ALLEXTERNALS = NO
1208
1209 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1210 # in the modules index. If set to NO, only the current project's groups will
1211 # be listed.
1212
1213 EXTERNAL_GROUPS = YES
1214
1215 # The PERL_PATH should be the absolute path and name of the perl script
1216 # interpreter (i.e. the result of `which perl').
1217
1218 PERL_PATH = /usr/bin/perl
1219
1220 #---------------------------------------------------------------------------
1221 # Configuration options related to the dot tool
1222 #---------------------------------------------------------------------------
1223
1224 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1225 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1226 # or super classes. Setting the tag to NO turns the diagrams off. Note that
1227 # this option is superseded by the HAVE_DOT option below. This is only a
1228 # fallback. It is recommended to install and use dot, since it yields more
1229 # powerful graphs.
1230
1231 CLASS_DIAGRAMS = YES
1232
1233 # You can define message sequence charts within doxygen comments using the \msc
1234 # command. Doxygen will then run the mscgen tool (see
1235 # http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1236 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1237 # the mscgen tool resides. If left empty the tool is assumed to be found in the
1238 # default search path.
1239
1240 MSCGEN_PATH =
1241
1242 # If set to YES, the inheritance and collaboration graphs will hide
1243 # inheritance and usage relations if the target is undocumented
1244 # or is not a class.
1245
1246 HIDE_UNDOC_RELATIONS = YES
1247
1248 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1249 # available from the path. This tool is part of Graphviz, a graph visualization
1250 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
1251 # have no effect if this option is set to NO (the default)
1252
1253 HAVE_DOT = NO
1254
1255 # By default doxygen will write a font called FreeSans.ttf to the output
1256 # directory and reference it in all dot files that doxygen generates. This
1257 # font does not include all possible unicode characters however, so when you need
1258 # these (or just want a differently looking font) you can specify the font name
1259 # using DOT_FONTNAME. You need need to make sure dot is able to find the font,
1260 # which can be done by putting it in a standard location or by setting the
1261 # DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1262 # containing the font.
1263
1264 DOT_FONTNAME = FreeSans
1265
1266 # By default doxygen will tell dot to use the output directory to look for the
1267 # FreeSans.ttf font (which doxygen will put there itself). If you specify a
1268 # different font using DOT_FONTNAME you can set the path where dot
1269 # can find it using this tag.
1270
1271 DOT_FONTPATH =
1272
1273 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1274 # will generate a graph for each documented class showing the direct and
1275 # indirect inheritance relations. Setting this tag to YES will force the
1276 # the CLASS_DIAGRAMS tag to NO.
1277
1278 CLASS_GRAPH = YES
1279
1280 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1281 # will generate a graph for each documented class showing the direct and
1282 # indirect implementation dependencies (inheritance, containment, and
1283 # class references variables) of the class with other documented classes.
1284
1285 COLLABORATION_GRAPH = YES
1286
1287 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1288 # will generate a graph for groups, showing the direct groups dependencies
1289
1290 GROUP_GRAPHS = YES
1291
1292 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1293 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1294 # Language.
1295
1296 UML_LOOK = NO
1297
1298 # If set to YES, the inheritance and collaboration graphs will show the
1299 # relations between templates and their instances.
1300
1301 TEMPLATE_RELATIONS = NO
1302
1303 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1304 # tags are set to YES then doxygen will generate a graph for each documented
1305 # file showing the direct and indirect include dependencies of the file with
1306 # other documented files.
1307
1308 INCLUDE_GRAPH = YES
1309
1310 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1311 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1312 # documented header file showing the documented files that directly or
1313 # indirectly include this file.
1314
1315 INCLUDED_BY_GRAPH = YES
1316
1317 # If the CALL_GRAPH and HAVE_DOT options are set to YES then
1318 # doxygen will generate a call dependency graph for every global function
1319 # or class method. Note that enabling this option will significantly increase
1320 # the time of a run. So in most cases it will be better to enable call graphs
1321 # for selected functions only using the \callgraph command.
1322
1323 CALL_GRAPH = NO
1324
1325 # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1326 # doxygen will generate a caller dependency graph for every global function
1327 # or class method. Note that enabling this option will significantly increase
1328 # the time of a run. So in most cases it will be better to enable caller
1329 # graphs for selected functions only using the \callergraph command.
1330
1331 CALLER_GRAPH = NO
1332
1333 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1334 # will graphical hierarchy of all classes instead of a textual one.
1335
1336 GRAPHICAL_HIERARCHY = YES
1337
1338 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1339 # then doxygen will show the dependencies a directory has on other directories
1340 # in a graphical way. The dependency relations are determined by the #include
1341 # relations between the files in the directories.
1342
1343 DIRECTORY_GRAPH = YES
1344
1345 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1346 # generated by dot. Possible values are png, jpg, or gif
1347 # If left blank png will be used.
1348
1349 DOT_IMAGE_FORMAT = png
1350
1351 # The tag DOT_PATH can be used to specify the path where the dot tool can be
1352 # found. If left blank, it is assumed the dot tool can be found in the path.
1353
1354 DOT_PATH =
1355
1356 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1357 # contain dot files that are included in the documentation (see the
1358 # \dotfile command).
1359
1360 DOTFILE_DIRS =
1361
1362 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1363 # nodes that will be shown in the graph. If the number of nodes in a graph
1364 # becomes larger than this value, doxygen will truncate the graph, which is
1365 # visualized by representing a node as a red box. Note that doxygen if the
1366 # number of direct children of the root node in a graph is already larger than
1367 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1368 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1369
1370 DOT_GRAPH_MAX_NODES = 50
1371
1372 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1373 # graphs generated by dot. A depth value of 3 means that only nodes reachable
1374 # from the root by following a path via at most 3 edges will be shown. Nodes
1375 # that lay further from the root node will be omitted. Note that setting this
1376 # option to 1 or 2 may greatly reduce the computation time needed for large
1377 # code bases. Also note that the size of a graph can be further restricted by
1378 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1379
1380 MAX_DOT_GRAPH_DEPTH = 0
1381
1382 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1383 # background. This is enabled by default, which results in a transparent
1384 # background. Warning: Depending on the platform used, enabling this option
1385 # may lead to badly anti-aliased labels on the edges of a graph (i.e. they
1386 # become hard to read).
1387
1388 DOT_TRANSPARENT = YES
1389
1390 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1391 # files in one run (i.e. multiple -o and -T options on the command line). This
1392 # makes dot run faster, but since only newer versions of dot (>1.8.10)
1393 # support this, this feature is disabled by default.
1394
1395 DOT_MULTI_TARGETS = NO
1396
1397 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1398 # generate a legend page explaining the meaning of the various boxes and
1399 # arrows in the dot generated graphs.
1400
1401 GENERATE_LEGEND = YES
1402
1403 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1404 # remove the intermediate dot files that are used to generate
1405 # the various graphs.
1406
1407 DOT_CLEANUP = YES
1408
1409 #---------------------------------------------------------------------------
1410 # Configuration::additions related to the search engine
1411 #---------------------------------------------------------------------------
1412
1413 # The SEARCHENGINE tag specifies whether or not a search engine should be
1414 # used. If set to NO the values of all tags below this one will be ignored.
1415
1416 SEARCHENGINE = NO