3 # This file describes the settings to be used by the documentation system
4 # doxygen (www.doxygen.org) for a project
6 # All text after a hash (#) is considered a comment and will be ignored
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 (" ")
13 #---------------------------------------------------------------------------
14 # Project related configuration options
15 #---------------------------------------------------------------------------
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.
23 DOXYFILE_ENCODING = UTF-8
25 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
26 # by quotes) that should identify the project.
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.
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.
41 OUTPUT_DIRECTORY = doc/offline-reference
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.
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, Esperanto, Farsi, Finnish, French, German,
58 # Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
59 # messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
60 # Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrilic, Slovak,
61 # Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
63 OUTPUT_LANGUAGE = English
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.
70 BRIEF_MEMBER_DESC = YES
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.
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"
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
95 ALWAYS_DETAILED_SEC = NO
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.
102 INLINE_INHERITED_MEMB = NO
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.
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
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.
126 STRIP_FROM_INC_PATH =
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.
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.)
140 JAVADOC_AUTOBRIEF = YES
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.)
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.
156 MULTILINE_CPP_IS_BRIEF = NO
158 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
159 # member inherits the documentation from any documented member that it
164 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
165 # a new page for each member. If set to NO, the documentation of a member will
166 # be part of the file/class/namespace that contains it.
168 SEPARATE_MEMBER_PAGES = NO
170 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
171 # Doxygen uses this value to replace tabs by spaces in code fragments.
175 # This tag can be used to specify a number of aliases that acts
176 # as commands in the documentation. An alias has the form "name=value".
177 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
178 # put the command \sideeffect (or @sideeffect) in the documentation, which
179 # will result in a user-defined paragraph with heading "Side Effects:".
180 # You can put \n's in the value part of an alias to insert newlines.
184 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
185 # sources only. Doxygen will then generate output that is more tailored for C.
186 # For instance, some of the names that are used will be different. The list
187 # of all members will be omitted, etc.
189 OPTIMIZE_OUTPUT_FOR_C = YES
191 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
192 # sources only. Doxygen will then generate output that is more tailored for
193 # Java. For instance, namespaces will be presented as packages, qualified
194 # scopes will look different, etc.
196 OPTIMIZE_OUTPUT_JAVA = NO
198 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
199 # sources only. Doxygen will then generate output that is more tailored for
202 OPTIMIZE_FOR_FORTRAN = NO
204 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
205 # sources. Doxygen will then generate output that is tailored for
208 OPTIMIZE_OUTPUT_VHDL = NO
210 # Doxygen selects the parser to use depending on the extension of the files it parses.
211 # With this tag you can assign which parser to use for a given extension.
212 # Doxygen has a built-in mapping, but you can override or extend it using this tag.
213 # The format is ext=language, where ext is a file extension, and language is one of
214 # the parsers supported by doxygen: IDL, Java, Javascript, C#, C, C++, D, PHP,
215 # Objective-C, Python, Fortran, VHDL, C, C++. For instance to make doxygen treat
216 # .inc files as Fortran files (default is PHP), and .f files as C (default is Fortran),
217 # use: inc=Fortran f=C. Note that for custom extensions you also need to set
218 # FILE_PATTERNS otherwise the files are not read by doxygen.
220 # commented, generates warnings with old version of doxygen
223 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
224 # to include (a tag file for) the STL sources as input, then you should
225 # set this tag to YES in order to let doxygen match functions declarations and
226 # definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
227 # func(std::string) {}). This also make the inheritance and collaboration
228 # diagrams that involve STL classes more complete and accurate.
230 BUILTIN_STL_SUPPORT = YES
232 # If you use Microsoft's C++/CLI language, you should set this option to YES to
233 # enable parsing support.
237 # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
238 # Doxygen will parse them like normal C++ but will assume all classes use public
239 # instead of private inheritance when no explicit protection keyword is present.
243 # For Microsoft's IDL there are propget and propput attributes to indicate getter
244 # and setter methods for a property. Setting this option to YES (the default)
245 # will make doxygen to replace the get and set methods by a property in the
246 # documentation. This will only work if the methods are indeed getting or
247 # setting a simple type. If this is not the case, or you want to show the
248 # methods anyway, you should set this option to NO.
250 IDL_PROPERTY_SUPPORT = YES
252 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
253 # tag is set to YES, then doxygen will reuse the documentation of the first
254 # member in the group (if any) for the other members of the group. By default
255 # all members of a group must be documented explicitly.
257 DISTRIBUTE_GROUP_DOC = NO
259 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
260 # the same type (for instance a group of public functions) to be put as a
261 # subgroup of that type (e.g. under the Public Functions section). Set it to
262 # NO to prevent subgrouping. Alternatively, this can be done per class using
263 # the \nosubgrouping command.
267 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
268 # is documented as struct, union, or enum with the name of the typedef. So
269 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
270 # with name TypeT. When disabled the typedef will appear as a member of a file,
271 # namespace, or class. And the struct will be named TypeS. This can typically
272 # be useful for C code in case the coding convention dictates that all compound
273 # types are typedef'ed and only the typedef is referenced, never the tag name.
275 TYPEDEF_HIDES_STRUCT = NO
277 # The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
278 # determine which symbols to keep in memory and which to flush to disk.
279 # When the cache is full, less often used symbols will be written to disk.
280 # For small to medium size projects (<1000 input files) the default value is
281 # probably good enough. For larger projects a too small cache size can cause
282 # doxygen to be busy swapping symbols to and from disk most of the time
283 # causing a significant performance penality.
284 # If the system has enough physical memory increasing the cache will improve the
285 # performance by keeping more symbols in memory. Note that the value works on
286 # a logarithmic scale so increasing the size by one will rougly double the
287 # memory usage. The cache size is given by this formula:
288 # 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
289 # corresponding to a cache size of 2^16 = 65536 symbols
291 SYMBOL_CACHE_SIZE = 0
293 #---------------------------------------------------------------------------
294 # Build related configuration options
295 #---------------------------------------------------------------------------
297 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
298 # documentation are documented, even if no documentation was available.
299 # Private class members and static file members will be hidden unless
300 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
304 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
305 # will be included in the documentation.
307 EXTRACT_PRIVATE = YES
309 # If the EXTRACT_STATIC tag is set to YES all static members of a file
310 # will be included in the documentation.
314 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
315 # defined locally in source files will be included in the documentation.
316 # If set to NO only classes defined in header files are included.
318 EXTRACT_LOCAL_CLASSES = YES
320 # This flag is only useful for Objective-C code. When set to YES local
321 # methods, which are defined in the implementation section but not in
322 # the interface are included in the documentation.
323 # If set to NO (the default) only methods in the interface are included.
325 EXTRACT_LOCAL_METHODS = NO
327 # If this flag is set to YES, the members of anonymous namespaces will be
328 # extracted and appear in the documentation as a namespace called
329 # 'anonymous_namespace{file}', where file will be replaced with the base
330 # name of the file that contains the anonymous namespace. By default
331 # anonymous namespace are hidden.
333 EXTRACT_ANON_NSPACES = NO
335 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
336 # undocumented members of documented classes, files or namespaces.
337 # If set to NO (the default) these members will be included in the
338 # various overviews, but no documentation section is generated.
339 # This option has no effect if EXTRACT_ALL is enabled.
341 HIDE_UNDOC_MEMBERS = YES
343 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
344 # undocumented classes that are normally visible in the class hierarchy.
345 # If set to NO (the default) these classes will be included in the various
346 # overviews. This option has no effect if EXTRACT_ALL is enabled.
348 HIDE_UNDOC_CLASSES = YES
350 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
351 # friend (class|struct|union) declarations.
352 # If set to NO (the default) these declarations will be included in the
355 HIDE_FRIEND_COMPOUNDS = NO
357 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
358 # documentation blocks found inside the body of a function.
359 # If set to NO (the default) these blocks will be appended to the
360 # function's detailed documentation block.
362 HIDE_IN_BODY_DOCS = NO
364 # The INTERNAL_DOCS tag determines if documentation
365 # that is typed after a \internal command is included. If the tag is set
366 # to NO (the default) then the documentation will be excluded.
367 # Set it to YES to include the internal documentation.
371 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
372 # file names in lower-case letters. If set to YES upper-case letters are also
373 # allowed. This is useful if you have classes or files whose names only differ
374 # in case and if your file system supports case sensitive file names. Windows
375 # and Mac users are advised to set this option to NO.
377 CASE_SENSE_NAMES = YES
379 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
380 # will show members with their full class and namespace scopes in the
381 # documentation. If set to YES the scope will be hidden.
383 HIDE_SCOPE_NAMES = NO
385 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
386 # will put a list of the files that are included by a file in the documentation
389 SHOW_INCLUDE_FILES = YES
391 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
392 # is inserted in the documentation for inline members.
396 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
397 # will sort the (detailed) documentation of file and class members
398 # alphabetically by member name. If set to NO the members will appear in
401 SORT_MEMBER_DOCS = YES
403 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
404 # brief documentation of file, namespace and class members alphabetically
405 # by member name. If set to NO (the default) the members will appear in
410 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
411 # hierarchy of group names into alphabetical order. If set to NO (the default)
412 # the group names will appear in their defined order.
414 SORT_GROUP_NAMES = NO
416 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
417 # sorted by fully-qualified names, including namespaces. If set to
418 # NO (the default), the class list will be sorted only by class name,
419 # not including the namespace part.
420 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
421 # Note: This option applies only to the class list, not to the
424 SORT_BY_SCOPE_NAME = NO
426 # The GENERATE_TODOLIST tag can be used to enable (YES) or
427 # disable (NO) the todo list. This list is created by putting \todo
428 # commands in the documentation.
430 GENERATE_TODOLIST = NO
432 # The GENERATE_TESTLIST tag can be used to enable (YES) or
433 # disable (NO) the test list. This list is created by putting \test
434 # commands in the documentation.
436 GENERATE_TESTLIST = NO
438 # The GENERATE_BUGLIST tag can be used to enable (YES) or
439 # disable (NO) the bug list. This list is created by putting \bug
440 # commands in the documentation.
442 GENERATE_BUGLIST = NO
444 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
445 # disable (NO) the deprecated list. This list is created by putting
446 # \deprecated commands in the documentation.
448 GENERATE_DEPRECATEDLIST= YES
450 # The ENABLED_SECTIONS tag can be used to enable conditional
451 # documentation sections, marked by \if sectionname ... \endif.
455 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
456 # the initial value of a variable or define consists of for it to appear in
457 # the documentation. If the initializer consists of more lines than specified
458 # here it will be hidden. Use a value of 0 to hide initializers completely.
459 # The appearance of the initializer of individual variables and defines in the
460 # documentation can be controlled using \showinitializer or \hideinitializer
461 # command in the documentation regardless of this setting.
463 MAX_INITIALIZER_LINES = 30
465 # If the sources in your project are distributed over multiple directories
466 # then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
467 # in the documentation. The default is NO.
469 SHOW_DIRECTORIES = YES
471 # Set the SHOW_FILES tag to NO to disable the generation of the Files page.
472 # This will remove the Files entry from the Quick Index and from the
473 # Folder Tree View (if specified). The default is YES.
477 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the
478 # Namespaces page. This will remove the Namespaces entry from the Quick Index
479 # and from the Folder Tree View (if specified). The default is YES.
483 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
484 # doxygen should invoke to get the current version for each file (typically from
485 # the version control system). Doxygen will invoke the program by executing (via
486 # popen()) the command <command> <input-file>, where <command> is the value of
487 # the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
488 # provided by doxygen. Whatever the program writes to standard output
489 # is used as the file version. See the manual for examples.
491 FILE_VERSION_FILTER =
493 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed by
494 # doxygen. The layout file controls the global structure of the generated output files
495 # in an output format independent way. The create the layout file that represents
496 # doxygen's defaults, run doxygen with the -l option. You can optionally specify a
497 # file name after the option, if omitted DoxygenLayout.xml will be used as the name
498 # of the layout file.
502 #---------------------------------------------------------------------------
503 # configuration options related to warning and progress messages
504 #---------------------------------------------------------------------------
506 # The QUIET tag can be used to turn on/off the messages that are generated
507 # by doxygen. Possible values are YES and NO. If left blank NO is used.
511 # The WARNINGS tag can be used to turn on/off the warning messages that are
512 # generated by doxygen. Possible values are YES and NO. If left blank
517 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
518 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
519 # automatically be disabled.
521 WARN_IF_UNDOCUMENTED = NO
523 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
524 # potential errors in the documentation, such as not documenting some
525 # parameters in a documented function, or documenting parameters that
526 # don't exist or using markup commands wrongly.
528 WARN_IF_DOC_ERROR = YES
530 # This WARN_NO_PARAMDOC option can be abled to get warnings for
531 # functions that are documented, but have no documentation for their parameters
532 # or return value. If set to NO (the default) doxygen will only warn about
533 # wrong or incomplete parameter documentation, but not about the absence of
536 WARN_NO_PARAMDOC = NO
538 # The WARN_FORMAT tag determines the format of the warning messages that
539 # doxygen can produce. The string should contain the $file, $line, and $text
540 # tags, which will be replaced by the file and line number from which the
541 # warning originated and the warning text. Optionally the format may contain
542 # $version, which will be replaced by the version of the file (if it could
543 # be obtained via FILE_VERSION_FILTER)
545 WARN_FORMAT = "$file:$line: $text"
547 # The WARN_LOGFILE tag can be used to specify a file to which warning
548 # and error messages should be written. If left blank the output is written
553 #---------------------------------------------------------------------------
554 # configuration options related to the input files
555 #---------------------------------------------------------------------------
557 # The INPUT tag can be used to specify the files and/or directories that contain
558 # documented source files. You may enter file names like "myfile.cpp" or
559 # directories like "/usr/src/myproject". Separate the files or directories
564 # This tag can be used to specify the character encoding of the source files
565 # that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
566 # also the default input encoding. Doxygen uses libiconv (or the iconv built
567 # into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
568 # the list of possible encodings.
570 INPUT_ENCODING = UTF-8
572 # If the value of the INPUT tag contains directories, you can use the
573 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
574 # and *.h) to filter out the source-files in the directories. If left
575 # blank the following patterns are tested:
576 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
577 # *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py *.f90
579 FILE_PATTERNS = *.h \
584 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
585 # should be searched for input files as well. Possible values are YES and NO.
586 # If left blank NO is used.
590 # The EXCLUDE tag can be used to specify files and/or directories that should
591 # excluded from the INPUT source files. This way you can easily exclude a
592 # subdirectory from a directory tree whose root is specified with the INPUT tag.
602 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or
603 # directories that are symbolic links (a Unix filesystem feature) are excluded
606 EXCLUDE_SYMLINKS = NO
608 # If the value of the INPUT tag contains directories, you can use the
609 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
610 # certain files from those directories. Note that the wildcards are matched
611 # against the file with absolute path, so to exclude all test directories
612 # for example use the pattern */test/*
614 EXCLUDE_PATTERNS = *_test.* \
617 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
618 # (namespaces, classes, functions, etc.) that should be excluded from the
619 # output. The symbol name can be a fully qualified name, a word, or if the
620 # wildcard * is used, a substring. Examples: ANamespace, AClass,
621 # AClass::ANamespace, ANamespace::*Test
625 # The EXAMPLE_PATH tag can be used to specify one or more files or
626 # directories that contain example code fragments that are included (see
627 # the \include command).
631 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
632 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
633 # and *.h) to filter out the source-files in the directories. If left
634 # blank all files are included.
638 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
639 # searched for input files to be used with the \include or \dontinclude
640 # commands irrespective of the value of the RECURSIVE tag.
641 # Possible values are YES and NO. If left blank NO is used.
643 EXAMPLE_RECURSIVE = NO
645 # The IMAGE_PATH tag can be used to specify one or more files or
646 # directories that contain image that are included in the documentation (see
647 # the \image command).
651 # The INPUT_FILTER tag can be used to specify a program that doxygen should
652 # invoke to filter for each input file. Doxygen will invoke the filter program
653 # by executing (via popen()) the command <filter> <input-file>, where <filter>
654 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
655 # input file. Doxygen will then use the output that the filter program writes
656 # to standard output. If FILTER_PATTERNS is specified, this tag will be
659 INPUT_FILTER = "python doc/tag-filter.py"
661 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
662 # basis. Doxygen will compare the file name with each pattern and apply the
663 # filter if there is a match. The filters are a list of the form:
664 # pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
665 # info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
666 # is applied to all files.
670 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
671 # INPUT_FILTER) will be used to filter the input files when producing source
672 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
674 FILTER_SOURCE_FILES = NO
676 #---------------------------------------------------------------------------
677 # configuration options related to source browsing
678 #---------------------------------------------------------------------------
680 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
681 # be generated. Documented entities will be cross-referenced with these sources.
682 # Note: To get rid of all source code in the generated output, make sure also
683 # VERBATIM_HEADERS is set to NO.
687 # Setting the INLINE_SOURCES tag to YES will include the body
688 # of functions and classes directly in the documentation.
692 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
693 # doxygen to hide any special comment blocks from generated source code
694 # fragments. Normal C and C++ comments will always remain visible.
696 STRIP_CODE_COMMENTS = YES
698 # If the REFERENCED_BY_RELATION tag is set to YES
699 # then for each documented function all documented
700 # functions referencing it will be listed.
702 REFERENCED_BY_RELATION = NO
704 # If the REFERENCES_RELATION tag is set to YES
705 # then for each documented function all documented entities
706 # called/used by that function will be listed.
708 REFERENCES_RELATION = NO
710 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
711 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
712 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
713 # link to the source code. Otherwise they will link to the documentation.
715 REFERENCES_LINK_SOURCE = YES
717 # If the USE_HTAGS tag is set to YES then the references to source code
718 # will point to the HTML generated by the htags(1) tool instead of doxygen
719 # built-in source browser. The htags tool is part of GNU's global source
720 # tagging system (see http://www.gnu.org/software/global/global.html). You
721 # will need version 4.8.6 or higher.
725 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
726 # will generate a verbatim copy of the header file for each class for
727 # which an include is specified. Set to NO to disable this.
729 VERBATIM_HEADERS = YES
731 #---------------------------------------------------------------------------
732 # configuration options related to the alphabetical class index
733 #---------------------------------------------------------------------------
735 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
736 # of all compounds will be generated. Enable this if the project
737 # contains a lot of classes, structs, unions or interfaces.
739 ALPHABETICAL_INDEX = YES
741 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
742 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
743 # in which this list will be split (can be a number in the range [1..20])
745 COLS_IN_ALPHA_INDEX = 1
747 # In case all classes in a project start with a common prefix, all
748 # classes will be put under the same header in the alphabetical index.
749 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
750 # should be ignored while generating the index headers.
754 #---------------------------------------------------------------------------
755 # configuration options related to the HTML output
756 #---------------------------------------------------------------------------
758 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
759 # generate HTML output.
763 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
764 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
765 # put in front of it. If left blank `html' will be used as the default path.
769 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
770 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
771 # doxygen will generate files with .html extension.
773 HTML_FILE_EXTENSION = .html
775 # The HTML_HEADER tag can be used to specify a personal HTML header for
776 # each generated HTML page. If it is left blank doxygen will generate a
781 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
782 # each generated HTML page. If it is left blank doxygen will generate a
785 HTML_FOOTER = doc/TracFooter.html
787 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
788 # style sheet that is used by each HTML page. It can be used to
789 # fine-tune the look of the HTML output. If the tag is left blank doxygen
790 # will generate a default style sheet. Note that doxygen will try to copy
791 # the style sheet file to the HTML output directory, so don't put your own
792 # stylesheet in the HTML output directory as well, or it will be erased!
794 HTML_STYLESHEET = doc/doxygen.css
796 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
797 # files or namespaces will be aligned in HTML using tables. If set to
798 # NO a bullet list will be used.
800 HTML_ALIGN_MEMBERS = YES
802 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
803 # documentation will contain sections that can be hidden and shown after the
804 # page has loaded. For this to work a browser that supports
805 # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
806 # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
808 HTML_DYNAMIC_SECTIONS = NO
810 # If the GENERATE_DOCSET tag is set to YES, additional index files
811 # will be generated that can be used as input for Apple's Xcode 3
812 # integrated development environment, introduced with OSX 10.5 (Leopard).
813 # To create a documentation set, doxygen will generate a Makefile in the
814 # HTML output directory. Running make will produce the docset in that
815 # directory and running "make install" will install the docset in
816 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
818 # See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html for more information.
822 # When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
823 # feed. A documentation feed provides an umbrella under which multiple
824 # documentation sets from a single provider (such as a company or product suite)
827 DOCSET_FEEDNAME = "Doxygen generated docs"
829 # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
830 # should uniquely identify the documentation set bundle. This should be a
831 # reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
832 # will append .docset to the name.
834 DOCSET_BUNDLE_ID = org.doxygen.Project
836 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
837 # will be generated that can be used as input for tools like the
838 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
839 # of the generated HTML documentation.
841 GENERATE_HTMLHELP = YES
843 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
844 # be used to specify the file name of the resulting .chm file. You
845 # can add a path in front of the file if the result should not be
846 # written to the html output directory.
848 CHM_FILE = bertos-doc.chm
850 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
851 # be used to specify the location (absolute path including file name) of
852 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
853 # the HTML help compiler on the generated index.hhp.
857 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
858 # controls if a separate .chi index file is generated (YES) or that
859 # it should be included in the master .chm file (NO).
863 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
864 # is used to encode HtmlHelp index (hhk), content (hhc) and project file
869 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
870 # controls whether a binary table of contents is generated (YES) or a
871 # normal table of contents (NO) in the .chm file.
875 # The TOC_EXPAND flag can be set to YES to add extra items for group members
876 # to the contents of the HTML help documentation and to the tree view.
880 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and QHP_VIRTUAL_FOLDER
881 # are set, an additional index file will be generated that can be used as input for
882 # Qt's qhelpgenerator to generate a Qt Compressed Help (.qch) of the generated
883 # HTML documentation.
887 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can
888 # be used to specify the file name of the resulting .qch file.
889 # The path specified is relative to the HTML output folder.
893 # The QHP_NAMESPACE tag specifies the namespace to use when generating
894 # Qt Help Project output. For more information please see
895 # http://doc.trolltech.com/qthelpproject.html#namespace
897 QHP_NAMESPACE = org.doxygen.Project
899 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
900 # Qt Help Project output. For more information please see
901 # http://doc.trolltech.com/qthelpproject.html#virtual-folders
903 QHP_VIRTUAL_FOLDER = doc
905 # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to add.
906 # For more information please see
907 # http://doc.trolltech.com/qthelpproject.html#custom-filters
909 # commented, generates warnings with old version of doxygen
910 #QHP_CUST_FILTER_NAME =
912 # The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the custom filter to add.For more information please see
913 # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">Qt Help Project / Custom Filters</a>.
915 # commented, generates warnings with old version of doxygen
916 #QHP_CUST_FILTER_ATTRS =
918 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this project's
919 # filter section matches.
920 # <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">Qt Help Project / Filter Attributes</a>.
922 # commented, generates warnings with old version of doxygen
923 #QHP_SECT_FILTER_ATTRS =
925 # If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
926 # be used to specify the location of Qt's qhelpgenerator.
927 # If non-empty doxygen will try to run qhelpgenerator on the generated
932 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
933 # top of each HTML page. The value NO (the default) enables the index and
934 # the value YES disables it.
938 # This tag can be used to set the number of enum values (range [1..20])
939 # that doxygen will group on one line in the generated HTML documentation.
941 ENUM_VALUES_PER_LINE = 4
943 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
944 # structure should be generated to display hierarchical information.
945 # If the tag value is set to FRAME, a side panel will be generated
946 # containing a tree-like index structure (just like the one that
947 # is generated for HTML Help). For this to work a browser that supports
948 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
949 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
950 # probably better off using the HTML help feature. Other possible values
951 # for this tag are: HIERARCHIES, which will generate the Groups, Directories,
952 # and Class Hierarchy pages using a tree view instead of an ordered list;
953 # ALL, which combines the behavior of FRAME and HIERARCHIES; and NONE, which
954 # disables this behavior completely. For backwards compatibility with previous
955 # releases of Doxygen, the values YES and NO are equivalent to FRAME and NONE
958 GENERATE_TREEVIEW = NONE
960 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
961 # used to set the initial width (in pixels) of the frame in which the tree
966 # Use this tag to change the font size of Latex formulas included
967 # as images in the HTML documentation. The default is 10. Note that
968 # when you change the font size after a successful doxygen run you need
969 # to manually remove any form_*.png images from the HTML output directory
970 # to force them to be regenerated.
972 FORMULA_FONTSIZE = 10
974 #---------------------------------------------------------------------------
975 # configuration options related to the LaTeX output
976 #---------------------------------------------------------------------------
978 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
979 # generate Latex output.
983 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
984 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
985 # put in front of it. If left blank `latex' will be used as the default path.
989 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
990 # invoked. If left blank `latex' will be used as the default command name.
992 LATEX_CMD_NAME = latex
994 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
995 # generate index for LaTeX. If left blank `makeindex' will be used as the
996 # default command name.
998 MAKEINDEX_CMD_NAME = makeindex
1000 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1001 # LaTeX documents. This may be useful for small projects and may help to
1002 # save some trees in general.
1006 # The PAPER_TYPE tag can be used to set the paper type that is used
1007 # by the printer. Possible values are: a4, a4wide, letter, legal and
1008 # executive. If left blank a4wide will be used.
1012 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1013 # packages that should be included in the LaTeX output.
1017 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1018 # the generated latex document. The header should contain everything until
1019 # the first chapter. If it is left blank doxygen will generate a
1020 # standard header. Notice: only use this tag if you know what you are doing!
1024 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1025 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
1026 # contain links (just like the HTML output) instead of page references
1027 # This makes the output suitable for online browsing using a pdf viewer.
1029 PDF_HYPERLINKS = YES
1031 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1032 # plain latex in the generated Makefile. Set this option to YES to get a
1033 # higher quality PDF documentation.
1037 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1038 # command to the generated LaTeX files. This will instruct LaTeX to keep
1039 # running if errors occur, instead of asking the user for help.
1040 # This option is also used when generating formulas in HTML.
1042 LATEX_BATCHMODE = YES
1044 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
1045 # include the index chapters (such as File Index, Compound Index, etc.)
1048 LATEX_HIDE_INDICES = NO
1050 # If LATEX_SOURCE_CODE is set to YES then doxygen will include
1051 # source code with syntax highlighting in the LaTeX output.
1052 # Note that which sources are shown also depends on other settings
1053 # such as SOURCE_BROWSER.
1055 # commented, generates warnings with old version of doxygen
1056 #LATEX_SOURCE_CODE = NO
1058 #---------------------------------------------------------------------------
1059 # configuration options related to the RTF output
1060 #---------------------------------------------------------------------------
1062 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
1063 # The RTF output is optimized for Word 97 and may not look very pretty with
1064 # other RTF readers or editors.
1068 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
1069 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1070 # put in front of it. If left blank `rtf' will be used as the default path.
1074 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
1075 # RTF documents. This may be useful for small projects and may help to
1076 # save some trees in general.
1080 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
1081 # will contain hyperlink fields. The RTF file will
1082 # contain links (just like the HTML output) instead of page references.
1083 # This makes the output suitable for online browsing using WORD or other
1084 # programs which support those fields.
1085 # Note: wordpad (write) and others do not support links.
1089 # Load stylesheet definitions from file. Syntax is similar to doxygen's
1090 # config file, i.e. a series of assignments. You only have to provide
1091 # replacements, missing definitions are set to their default value.
1093 RTF_STYLESHEET_FILE =
1095 # Set optional variables used in the generation of an rtf document.
1096 # Syntax is similar to doxygen's config file.
1098 RTF_EXTENSIONS_FILE =
1100 #---------------------------------------------------------------------------
1101 # configuration options related to the man page output
1102 #---------------------------------------------------------------------------
1104 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1105 # generate man pages
1109 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
1110 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1111 # put in front of it. If left blank `man' will be used as the default path.
1115 # The MAN_EXTENSION tag determines the extension that is added to
1116 # the generated man pages (default is the subroutine's section .3)
1120 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1121 # then it will generate one additional man file for each entity
1122 # documented in the real man page(s). These additional files
1123 # only source the real man page, but without them the man command
1124 # would be unable to find the correct page. The default is NO.
1128 #---------------------------------------------------------------------------
1129 # configuration options related to the XML output
1130 #---------------------------------------------------------------------------
1132 # If the GENERATE_XML tag is set to YES Doxygen will
1133 # generate an XML file that captures the structure of
1134 # the code including all documentation.
1138 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
1139 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1140 # put in front of it. If left blank `xml' will be used as the default path.
1144 # The XML_SCHEMA tag can be used to specify an XML schema,
1145 # which can be used by a validating XML parser to check the
1146 # syntax of the XML files.
1150 # The XML_DTD tag can be used to specify an XML DTD,
1151 # which can be used by a validating XML parser to check the
1152 # syntax of the XML files.
1156 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1157 # dump the program listings (including syntax highlighting
1158 # and cross-referencing information) to the XML output. Note that
1159 # enabling this will significantly increase the size of the XML output.
1161 XML_PROGRAMLISTING = YES
1163 #---------------------------------------------------------------------------
1164 # configuration options for the AutoGen Definitions output
1165 #---------------------------------------------------------------------------
1167 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1168 # generate an AutoGen Definitions (see autogen.sf.net) file
1169 # that captures the structure of the code including all
1170 # documentation. Note that this feature is still experimental
1171 # and incomplete at the moment.
1173 GENERATE_AUTOGEN_DEF = NO
1175 #---------------------------------------------------------------------------
1176 # configuration options related to the Perl module output
1177 #---------------------------------------------------------------------------
1179 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
1180 # generate a Perl module file that captures the structure of
1181 # the code including all documentation. Note that this
1182 # feature is still experimental and incomplete at the
1185 GENERATE_PERLMOD = NO
1187 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1188 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
1189 # to generate PDF and DVI output from the Perl module output.
1193 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1194 # nicely formatted so it can be parsed by a human reader. This is useful
1195 # if you want to understand what is going on. On the other hand, if this
1196 # tag is set to NO the size of the Perl module output will be much smaller
1197 # and Perl will parse it just the same.
1199 PERLMOD_PRETTY = YES
1201 # The names of the make variables in the generated doxyrules.make file
1202 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1203 # This is useful so different doxyrules.make files included by the same
1204 # Makefile don't overwrite each other's variables.
1206 PERLMOD_MAKEVAR_PREFIX =
1208 #---------------------------------------------------------------------------
1209 # Configuration options related to the preprocessor
1210 #---------------------------------------------------------------------------
1212 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1213 # evaluate all C-preprocessor directives found in the sources and include
1216 ENABLE_PREPROCESSING = YES
1218 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1219 # names in the source code. If set to NO (the default) only conditional
1220 # compilation will be performed. Macro expansion can be done in a controlled
1221 # way by setting EXPAND_ONLY_PREDEF to YES.
1223 MACRO_EXPANSION = YES
1225 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1226 # then the macro expansion is limited to the macros specified with the
1227 # PREDEFINED and EXPAND_AS_DEFINED tags.
1229 EXPAND_ONLY_PREDEF = YES
1231 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1232 # in the INCLUDE_PATH (see below) will be search if a #include is found.
1234 SEARCH_INCLUDES = YES
1236 # The INCLUDE_PATH tag can be used to specify one or more directories that
1237 # contain include files that are not input files but should be processed by
1242 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1243 # patterns (like *.h and *.hpp) to filter out the header-files in the
1244 # directories. If left blank, the patterns specified with FILE_PATTERNS will
1247 INCLUDE_FILE_PATTERNS =
1249 # The PREDEFINED tag can be used to specify one or more macro names that
1250 # are defined before the preprocessor is started (similar to the -D option of
1251 # gcc). The argument of the tag is a list of macros of the form: name
1252 # or name=definition (no spaces). If the definition and the = are
1253 # omitted =1 is assumed. To prevent a macro definition from being
1254 # undefined via #undef or recursively expanded use the := operator
1255 # instead of the = operator.
1257 PREDEFINED = __doxygen__ \
1266 CONFIG_FAT_DRIVES=1 \
1268 CONFIG_TIMER_EVENTS=1 \
1269 CONFIG_TIMER_UDELAY=1 \
1270 CONFIG_KERN_SIGNALS=1
1272 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1273 # this tag can be used to specify a list of macro names that should be expanded.
1274 # The macro definition that is found in the sources will be used.
1275 # Use the PREDEFINED tag if you want to use a different macro definition.
1279 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1280 # doxygen's preprocessor will remove all function-like macros that are alone
1281 # on a line, have an all uppercase name, and do not end with a semicolon. Such
1282 # function macros are typically used for boiler-plate code, and will confuse
1283 # the parser if not removed.
1285 SKIP_FUNCTION_MACROS = YES
1287 #---------------------------------------------------------------------------
1288 # Configuration::additions related to external references
1289 #---------------------------------------------------------------------------
1291 # The TAGFILES option can be used to specify one or more tagfiles.
1292 # Optionally an initial location of the external documentation
1293 # can be added for each tagfile. The format of a tag file without
1294 # this location is as follows:
1295 # TAGFILES = file1 file2 ...
1296 # Adding location for the tag files is done as follows:
1297 # TAGFILES = file1=loc1 "file2 = loc2" ...
1298 # where "loc1" and "loc2" can be relative or absolute paths or
1299 # URLs. If a location is present for each tag, the installdox tool
1300 # does not have to be run to correct the links.
1301 # Note that each tag file must have a unique name
1302 # (where the name does NOT include the path)
1303 # If a tag file is not located in the directory in which doxygen
1304 # is run, you must also specify the path to the tagfile here.
1308 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1309 # a tag file that is based on the input files it reads.
1313 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1314 # in the class index. If set to NO only the inherited external classes
1319 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1320 # in the modules index. If set to NO, only the current project's groups will
1323 EXTERNAL_GROUPS = YES
1325 # The PERL_PATH should be the absolute path and name of the perl script
1326 # interpreter (i.e. the result of `which perl').
1328 PERL_PATH = /usr/bin/perl
1330 #---------------------------------------------------------------------------
1331 # Configuration options related to the dot tool
1332 #---------------------------------------------------------------------------
1334 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1335 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1336 # or super classes. Setting the tag to NO turns the diagrams off. Note that
1337 # this option is superseded by the HAVE_DOT option below. This is only a
1338 # fallback. It is recommended to install and use dot, since it yields more
1343 # You can define message sequence charts within doxygen comments using the \msc
1344 # command. Doxygen will then run the mscgen tool (see
1345 # http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the
1346 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
1347 # the mscgen tool resides. If left empty the tool is assumed to be found in the
1348 # default search path.
1352 # If set to YES, the inheritance and collaboration graphs will hide
1353 # inheritance and usage relations if the target is undocumented
1354 # or is not a class.
1356 HIDE_UNDOC_RELATIONS = YES
1358 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1359 # available from the path. This tool is part of Graphviz, a graph visualization
1360 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
1361 # have no effect if this option is set to NO (the default)
1365 # By default doxygen will write a font called FreeSans.ttf to the output
1366 # directory and reference it in all dot files that doxygen generates. This
1367 # font does not include all possible unicode characters however, so when you need
1368 # these (or just want a differently looking font) you can specify the font name
1369 # using DOT_FONTNAME. You need need to make sure dot is able to find the font,
1370 # which can be done by putting it in a standard location or by setting the
1371 # DOTFONTPATH environment variable or by setting DOT_FONTPATH to the directory
1372 # containing the font.
1374 DOT_FONTNAME = FreeSans
1376 # The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs.
1377 # The default size is 10pt.
1381 # By default doxygen will tell dot to use the output directory to look for the
1382 # FreeSans.ttf font (which doxygen will put there itself). If you specify a
1383 # different font using DOT_FONTNAME you can set the path where dot
1384 # can find it using this tag.
1388 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1389 # will generate a graph for each documented class showing the direct and
1390 # indirect inheritance relations. Setting this tag to YES will force the
1391 # the CLASS_DIAGRAMS tag to NO.
1395 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1396 # will generate a graph for each documented class showing the direct and
1397 # indirect implementation dependencies (inheritance, containment, and
1398 # class references variables) of the class with other documented classes.
1400 COLLABORATION_GRAPH = YES
1402 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1403 # will generate a graph for groups, showing the direct groups dependencies
1407 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1408 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1413 # If set to YES, the inheritance and collaboration graphs will show the
1414 # relations between templates and their instances.
1416 TEMPLATE_RELATIONS = YES
1418 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1419 # tags are set to YES then doxygen will generate a graph for each documented
1420 # file showing the direct and indirect include dependencies of the file with
1421 # other documented files.
1425 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1426 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1427 # documented header file showing the documented files that directly or
1428 # indirectly include this file.
1430 INCLUDED_BY_GRAPH = NO
1432 # If the CALL_GRAPH and HAVE_DOT options are set to YES then
1433 # doxygen will generate a call dependency graph for every global function
1434 # or class method. Note that enabling this option will significantly increase
1435 # the time of a run. So in most cases it will be better to enable call graphs
1436 # for selected functions only using the \callgraph command.
1440 # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then
1441 # doxygen will generate a caller dependency graph for every global function
1442 # or class method. Note that enabling this option will significantly increase
1443 # the time of a run. So in most cases it will be better to enable caller
1444 # graphs for selected functions only using the \callergraph command.
1448 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1449 # will graphical hierarchy of all classes instead of a textual one.
1451 GRAPHICAL_HIERARCHY = YES
1453 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1454 # then doxygen will show the dependencies a directory has on other directories
1455 # in a graphical way. The dependency relations are determined by the #include
1456 # relations between the files in the directories.
1458 DIRECTORY_GRAPH = YES
1460 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1461 # generated by dot. Possible values are png, jpg, or gif
1462 # If left blank png will be used.
1464 DOT_IMAGE_FORMAT = png
1466 # The tag DOT_PATH can be used to specify the path where the dot tool can be
1467 # found. If left blank, it is assumed the dot tool can be found in the path.
1471 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1472 # contain dot files that are included in the documentation (see the
1473 # \dotfile command).
1477 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1478 # nodes that will be shown in the graph. If the number of nodes in a graph
1479 # becomes larger than this value, doxygen will truncate the graph, which is
1480 # visualized by representing a node as a red box. Note that doxygen if the
1481 # number of direct children of the root node in a graph is already larger than
1482 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note
1483 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1485 DOT_GRAPH_MAX_NODES = 50
1487 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1488 # graphs generated by dot. A depth value of 3 means that only nodes reachable
1489 # from the root by following a path via at most 3 edges will be shown. Nodes
1490 # that lay further from the root node will be omitted. Note that setting this
1491 # option to 1 or 2 may greatly reduce the computation time needed for large
1492 # code bases. Also note that the size of a graph can be further restricted by
1493 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1495 MAX_DOT_GRAPH_DEPTH = 0
1497 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1498 # background. This is disabled by default, because dot on Windows does not
1499 # seem to support this out of the box. Warning: Depending on the platform used,
1500 # enabling this option may lead to badly anti-aliased labels on the edges of
1501 # a graph (i.e. they become hard to read).
1503 DOT_TRANSPARENT = NO
1505 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1506 # files in one run (i.e. multiple -o and -T options on the command line). This
1507 # makes dot run faster, but since only newer versions of dot (>1.8.10)
1508 # support this, this feature is disabled by default.
1510 DOT_MULTI_TARGETS = NO
1512 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1513 # generate a legend page explaining the meaning of the various boxes and
1514 # arrows in the dot generated graphs.
1516 GENERATE_LEGEND = YES
1518 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1519 # remove the intermediate dot files that are used to generate
1520 # the various graphs.
1524 #---------------------------------------------------------------------------
1525 # Options related to the search engine
1526 #---------------------------------------------------------------------------
1528 # The SEARCHENGINE tag specifies whether or not a search engine should be
1529 # used. If set to NO the values of all tags below this one will be ignored.