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 # General configuration options
15 #---------------------------------------------------------------------------
17 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
18 # by quotes) that should identify the project.
20 PROJECT_NAME = "@PACKAGE_NAME@"
22 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
23 # This could be handy for archiving the generated documentation or
24 # if some version control system is used.
26 PROJECT_NUMBER = "@VERSION@"
28 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
29 # base path where the generated documentation will be put.
30 # If a relative path is entered, it will be relative to the location
31 # where doxygen was started. If left blank the current directory will be used.
35 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
36 # documentation generated by doxygen is written. Doxygen will use this
37 # information to generate all constant output in the proper language.
38 # The default language is English, other supported languages are:
39 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch,
40 # Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en
41 # (Japanese with English messages), Korean, Norwegian, Polish, Portuguese,
42 # Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
44 OUTPUT_LANGUAGE = English
46 # This tag can be used to specify the encoding used in the generated output.
47 # The encoding is not always determined by the language that is chosen,
48 # but also whether or not the output is meant for Windows or non-Windows users.
49 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
50 # forces the Windows encoding (this is the default for the Windows binary),
51 # whereas setting the tag to NO uses a Unix-style encoding (the default for
52 # all platforms other than Windows).
54 USE_WINDOWS_ENCODING = NO
56 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
57 # documentation are documented, even if no documentation was available.
58 # Private class members and static file members will be hidden unless
59 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
63 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
64 # will be included in the documentation.
68 # If the EXTRACT_STATIC tag is set to YES all static members of a file
69 # will be included in the documentation.
73 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
74 # defined locally in source files will be included in the documentation.
75 # If set to NO only classes defined in header files are included.
77 EXTRACT_LOCAL_CLASSES = NO
79 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
80 # undocumented members of documented classes, files or namespaces.
81 # If set to NO (the default) these members will be included in the
82 # various overviews, but no documentation section is generated.
83 # This option has no effect if EXTRACT_ALL is enabled.
85 HIDE_UNDOC_MEMBERS = YES
87 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
88 # undocumented classes that are normally visible in the class hierarchy.
89 # If set to NO (the default) these classes will be included in the various
90 # overviews. This option has no effect if EXTRACT_ALL is enabled.
92 HIDE_UNDOC_CLASSES = YES
94 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
95 # friend (class|struct|union) declarations.
96 # If set to NO (the default) these declarations will be included in the
99 HIDE_FRIEND_COMPOUNDS = NO
101 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
102 # documentation blocks found inside the body of a function.
103 # If set to NO (the default) these blocks will be appended to the
104 # function's detailed documentation block.
106 HIDE_IN_BODY_DOCS = NO
108 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
109 # include brief member descriptions after the members that are listed in
110 # the file and class documentation (similar to JavaDoc).
111 # Set to NO to disable this.
113 BRIEF_MEMBER_DESC = YES
115 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
116 # the brief description of a member or function before the detailed description.
117 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
118 # brief descriptions will be completely suppressed.
122 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
123 # Doxygen will generate a detailed section even if there is only a brief
126 ALWAYS_DETAILED_SEC = NO
128 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited
129 # members of a class in the documentation of that class as if those members were
130 # ordinary class members. Constructors, destructors and assignment operators of
131 # the base classes will not be shown.
133 INLINE_INHERITED_MEMB = NO
135 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
136 # path before files name in the file list and in the header files. If set
137 # to NO the shortest path that makes the file name unique will be used.
141 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
142 # can be used to strip a user-defined part of the path. Stripping is
143 # only done if one of the specified strings matches the left-hand part of
144 # the path. It is allowed to use relative paths in the argument list.
148 # The INTERNAL_DOCS tag determines if documentation
149 # that is typed after a \internal command is included. If the tag is set
150 # to NO (the default) then the documentation will be excluded.
151 # Set it to YES to include the internal documentation.
155 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
156 # file names in lower-case letters. If set to YES upper-case letters are also
157 # allowed. This is useful if you have classes or files whose names only differ
158 # in case and if your file system supports case sensitive file names. Windows
159 # users are advised to set this option to NO.
161 CASE_SENSE_NAMES = YES
163 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
164 # (but less readable) file names. This can be useful is your file systems
165 # doesn't support long names like on DOS, Mac, or CD-ROM.
169 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
170 # will show members with their full class and namespace scopes in the
171 # documentation. If set to YES the scope will be hidden.
173 HIDE_SCOPE_NAMES = NO
175 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
176 # will put a list of the files that are included by a file in the documentation
179 SHOW_INCLUDE_FILES = YES
181 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
182 # will interpret the first line (until the first dot) of a JavaDoc-style
183 # comment as the brief description. If set to NO, the JavaDoc
184 # comments will behave just like the Qt-style comments (thus requiring an
185 # explict @brief command for a brief description.
187 JAVADOC_AUTOBRIEF = YES
189 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
190 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
191 # comments) as a brief description. This used to be the default behaviour.
192 # The new default is to treat a multi-line C++ comment block as a detailed
193 # description. Set this tag to YES if you prefer the old behaviour instead.
195 MULTILINE_CPP_IS_BRIEF = NO
197 # If the DETAILS_AT_TOP tag is set to YES then Doxygen
198 # will output the detailed description near the top, like JavaDoc.
199 # If set to NO, the detailed description appears after the member
204 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
205 # member inherits the documentation from any documented member that it
210 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
211 # is inserted in the documentation for inline members.
215 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
216 # will sort the (detailed) documentation of file and class members
217 # alphabetically by member name. If set to NO the members will appear in
220 SORT_MEMBER_DOCS = YES
222 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
223 # tag is set to YES, then doxygen will reuse the documentation of the first
224 # member in the group (if any) for the other members of the group. By default
225 # all members of a group must be documented explicitly.
227 DISTRIBUTE_GROUP_DOC = NO
229 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
230 # Doxygen uses this value to replace tabs by spaces in code fragments.
234 # The GENERATE_TODOLIST tag can be used to enable (YES) or
235 # disable (NO) the todo list. This list is created by putting \todo
236 # commands in the documentation.
238 GENERATE_TODOLIST = YES
240 # The GENERATE_TESTLIST tag can be used to enable (YES) or
241 # disable (NO) the test list. This list is created by putting \test
242 # commands in the documentation.
244 GENERATE_TESTLIST = YES
246 # The GENERATE_BUGLIST tag can be used to enable (YES) or
247 # disable (NO) the bug list. This list is created by putting \bug
248 # commands in the documentation.
250 GENERATE_BUGLIST = YES
252 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
253 # disable (NO) the deprecated list. This list is created by putting
254 # \deprecated commands in the documentation.
256 GENERATE_DEPRECATEDLIST= YES
258 # This tag can be used to specify a number of aliases that acts
259 # as commands in the documentation. An alias has the form "name=value".
260 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
261 # put the command \sideeffect (or @sideeffect) in the documentation, which
262 # will result in a user-defined paragraph with heading "Side Effects:".
263 # You can put \n's in the value part of an alias to insert newlines.
267 # The ENABLED_SECTIONS tag can be used to enable conditional
268 # documentation sections, marked by \if sectionname ... \endif.
272 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
273 # the initial value of a variable or define consists of for it to appear in
274 # the documentation. If the initializer consists of more lines than specified
275 # here it will be hidden. Use a value of 0 to hide initializers completely.
276 # The appearance of the initializer of individual variables and defines in the
277 # documentation can be controlled using \showinitializer or \hideinitializer
278 # command in the documentation regardless of this setting.
280 MAX_INITIALIZER_LINES = 30
282 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
283 # only. Doxygen will then generate output that is more tailored for C.
284 # For instance, some of the names that are used will be different. The list
285 # of all members will be omitted, etc.
287 OPTIMIZE_OUTPUT_FOR_C = YES
289 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
290 # only. Doxygen will then generate output that is more tailored for Java.
291 # For instance, namespaces will be presented as packages, qualified scopes
292 # will look different, etc.
294 OPTIMIZE_OUTPUT_JAVA = NO
296 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
297 # at the bottom of the documentation of classes and structs. If set to YES the
298 # list will mention the files that were used to generate the documentation.
300 SHOW_USED_FILES = YES
302 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
303 # the same type (for instance a group of public functions) to be put as a
304 # subgroup of that type (e.g. under the Public Functions section). Set it to
305 # NO to prevent subgrouping. Alternatively, this can be done per class using
306 # the \nosubgrouping command.
310 #---------------------------------------------------------------------------
311 # configuration options related to warning and progress messages
312 #---------------------------------------------------------------------------
314 # The QUIET tag can be used to turn on/off the messages that are generated
315 # by doxygen. Possible values are YES and NO. If left blank NO is used.
319 # The WARNINGS tag can be used to turn on/off the warning messages that are
320 # generated by doxygen. Possible values are YES and NO. If left blank
325 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
326 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
327 # automatically be disabled.
329 WARN_IF_UNDOCUMENTED = YES
331 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
332 # potential errors in the documentation, such as not documenting some
333 # parameters in a documented function, or documenting parameters that
334 # don't exist or using markup commands wrongly.
336 WARN_IF_DOC_ERROR = YES
338 # The WARN_FORMAT tag determines the format of the warning messages that
339 # doxygen can produce. The string should contain the $file, $line, and $text
340 # tags, which will be replaced by the file and line number from which the
341 # warning originated and the warning text.
343 WARN_FORMAT = "$file:$line: $text"
345 # The WARN_LOGFILE tag can be used to specify a file to which warning
346 # and error messages should be written. If left blank the output is written
351 #---------------------------------------------------------------------------
352 # configuration options related to the input files
353 #---------------------------------------------------------------------------
355 # The INPUT tag can be used to specify the files and/or directories that contain
356 # documented source files. You may enter file names like "myfile.cpp" or
357 # directories like "/usr/src/myproject". Separate the files or directories
360 INPUT = @top_srcdir@/src/ccunit @top_srcdir@/src/tools \
363 # If the value of the INPUT tag contains directories, you can use the
364 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
365 # and *.h) to filter out the source-files in the directories. If left
366 # blank the following patterns are tested:
367 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
368 # *.h++ *.idl *.odl *.cs
370 FILE_PATTERNS = *.c *.h *.dox
372 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
373 # should be searched for input files as well. Possible values are YES and NO.
374 # If left blank NO is used.
378 # The EXCLUDE tag can be used to specify files and/or directories that should
379 # excluded from the INPUT source files. This way you can easily exclude a
380 # subdirectory from a directory tree whose root is specified with the INPUT tag.
384 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
385 # that are symbolic links (a Unix filesystem feature) are excluded from the input.
387 EXCLUDE_SYMLINKS = NO
389 # If the value of the INPUT tag contains directories, you can use the
390 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
391 # certain files from those directories.
393 EXCLUDE_PATTERNS = config.h
395 # The EXAMPLE_PATH tag can be used to specify one or more files or
396 # directories that contain example code fragments that are included (see
397 # the \include command).
399 EXAMPLE_PATH = @top_srcdir@/examples
401 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
402 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
403 # and *.h) to filter out the source-files in the directories. If left
404 # blank all files are included.
406 EXAMPLE_PATTERNS = *.c *.h
408 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
409 # searched for input files to be used with the \include or \dontinclude
410 # commands irrespective of the value of the RECURSIVE tag.
411 # Possible values are YES and NO. If left blank NO is used.
413 EXAMPLE_RECURSIVE = YES
415 # The IMAGE_PATH tag can be used to specify one or more files or
416 # directories that contain image that are included in the documentation (see
417 # the \image command).
419 IMAGE_PATH = @top_srcdir@/images
421 # The INPUT_FILTER tag can be used to specify a program that doxygen should
422 # invoke to filter for each input file. Doxygen will invoke the filter program
423 # by executing (via popen()) the command <filter> <input-file>, where <filter>
424 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
425 # input file. Doxygen will then use the output that the filter program writes
426 # to standard output.
430 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
431 # INPUT_FILTER) will be used to filter the input files when producing source
432 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
434 FILTER_SOURCE_FILES = NO
436 #---------------------------------------------------------------------------
437 # configuration options related to source browsing
438 #---------------------------------------------------------------------------
440 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
441 # be generated. Documented entities will be cross-referenced with these sources.
445 # Setting the INLINE_SOURCES tag to YES will include the body
446 # of functions and classes directly in the documentation.
450 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
451 # doxygen to hide any special comment blocks from generated source code
452 # fragments. Normal C and C++ comments will always remain visible.
454 STRIP_CODE_COMMENTS = YES
456 # If the REFERENCED_BY_RELATION tag is set to YES (the default)
457 # then for each documented function all documented
458 # functions referencing it will be listed.
460 REFERENCED_BY_RELATION = YES
462 # If the REFERENCES_RELATION tag is set to YES (the default)
463 # then for each documented function all documented entities
464 # called/used by that function will be listed.
466 REFERENCES_RELATION = YES
468 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
469 # will generate a verbatim copy of the header file for each class for
470 # which an include is specified. Set to NO to disable this.
472 VERBATIM_HEADERS = YES
474 #---------------------------------------------------------------------------
475 # configuration options related to the alphabetical class index
476 #---------------------------------------------------------------------------
478 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
479 # of all compounds will be generated. Enable this if the project
480 # contains a lot of classes, structs, unions or interfaces.
482 ALPHABETICAL_INDEX = NO
484 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
485 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
486 # in which this list will be split (can be a number in the range [1..20])
488 COLS_IN_ALPHA_INDEX = 5
490 # In case all classes in a project start with a common prefix, all
491 # classes will be put under the same header in the alphabetical index.
492 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
493 # should be ignored while generating the index headers.
495 IGNORE_PREFIX = _ccuint _CCUnit
497 #---------------------------------------------------------------------------
498 # configuration options related to the HTML output
499 #---------------------------------------------------------------------------
501 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
502 # generate HTML output.
506 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
507 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
508 # put in front of it. If left blank `html' will be used as the default path.
512 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
513 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
514 # doxygen will generate files with .html extension.
516 HTML_FILE_EXTENSION = .html
518 # The HTML_HEADER tag can be used to specify a personal HTML header for
519 # each generated HTML page. If it is left blank doxygen will generate a
522 HTML_HEADER = @srcdir@/header.html
524 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
525 # each generated HTML page. If it is left blank doxygen will generate a
528 HTML_FOOTER = @srcdir@/footer.html
530 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
531 # style sheet that is used by each HTML page. It can be used to
532 # fine-tune the look of the HTML output. If the tag is left blank doxygen
533 # will generate a default style sheet
537 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
538 # files or namespaces will be aligned in HTML using tables. If set to
539 # NO a bullet list will be used.
541 HTML_ALIGN_MEMBERS = YES
543 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
544 # will be generated that can be used as input for tools like the
545 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
546 # of the generated HTML documentation.
548 GENERATE_HTMLHELP = NO
550 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
551 # be used to specify the file name of the resulting .chm file. You
552 # can add a path in front of the file if the result should not be
553 # written to the html output dir.
557 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
558 # be used to specify the location (absolute path including file name) of
559 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
560 # the HTML help compiler on the generated index.hhp.
564 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
565 # controls if a separate .chi index file is generated (YES) or that
566 # it should be included in the master .chm file (NO).
570 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
571 # controls whether a binary table of contents is generated (YES) or a
572 # normal table of contents (NO) in the .chm file.
576 # The TOC_EXPAND flag can be set to YES to add extra items for group members
577 # to the contents of the HTML help documentation and to the tree view.
581 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
582 # top of each HTML page. The value NO (the default) enables the index and
583 # the value YES disables it.
587 # This tag can be used to set the number of enum values (range [1..20])
588 # that doxygen will group on one line in the generated HTML documentation.
590 ENUM_VALUES_PER_LINE = 4
592 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
593 # generated containing a tree-like index structure (just like the one that
594 # is generated for HTML Help). For this to work a browser that supports
595 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
596 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
597 # probably better off using the HTML help feature.
599 GENERATE_TREEVIEW = NO
601 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
602 # used to set the initial width (in pixels) of the frame in which the tree
607 #---------------------------------------------------------------------------
608 # configuration options related to the LaTeX output
609 #---------------------------------------------------------------------------
611 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
612 # generate Latex output.
614 GENERATE_LATEX = @enable_latex_docs@
616 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
617 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
618 # put in front of it. If left blank `latex' will be used as the default path.
622 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
623 # invoked. If left blank `latex' will be used as the default command name.
625 LATEX_CMD_NAME = latex
627 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
628 # generate index for LaTeX. If left blank `makeindex' will be used as the
629 # default command name.
631 MAKEINDEX_CMD_NAME = makeindex
633 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
634 # LaTeX documents. This may be useful for small projects and may help to
635 # save some trees in general.
639 # The PAPER_TYPE tag can be used to set the paper type that is used
640 # by the printer. Possible values are: a4, a4wide, letter, legal and
641 # executive. If left blank a4wide will be used.
645 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
646 # packages that should be included in the LaTeX output.
650 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
651 # the generated latex document. The header should contain everything until
652 # the first chapter. If it is left blank doxygen will generate a
653 # standard header. Notice: only use this tag if you know what you are doing!
657 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
658 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
659 # contain links (just like the HTML output) instead of page references
660 # This makes the output suitable for online browsing using a pdf viewer.
664 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
665 # plain latex in the generated Makefile. Set this option to YES to get a
666 # higher quality PDF documentation.
670 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
671 # command to the generated LaTeX files. This will instruct LaTeX to keep
672 # running if errors occur, instead of asking the user for help.
673 # This option is also used when generating formulas in HTML.
677 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
678 # include the index chapters (such as File Index, Compound Index, etc.)
681 LATEX_HIDE_INDICES = NO
683 #---------------------------------------------------------------------------
684 # configuration options related to the RTF output
685 #---------------------------------------------------------------------------
687 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
688 # The RTF output is optimised for Word 97 and may not look very pretty with
689 # other RTF readers or editors.
693 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
694 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
695 # put in front of it. If left blank `rtf' will be used as the default path.
699 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
700 # RTF documents. This may be useful for small projects and may help to
701 # save some trees in general.
705 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
706 # will contain hyperlink fields. The RTF file will
707 # contain links (just like the HTML output) instead of page references.
708 # This makes the output suitable for online browsing using WORD or other
709 # programs which support those fields.
710 # Note: wordpad (write) and others do not support links.
714 # Load stylesheet definitions from file. Syntax is similar to doxygen's
715 # config file, i.e. a series of assigments. You only have to provide
716 # replacements, missing definitions are set to their default value.
718 RTF_STYLESHEET_FILE =
720 # Set optional variables used in the generation of an rtf document.
721 # Syntax is similar to doxygen's config file.
723 RTF_EXTENSIONS_FILE =
725 #---------------------------------------------------------------------------
726 # configuration options related to the man page output
727 #---------------------------------------------------------------------------
729 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
734 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
735 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
736 # put in front of it. If left blank `man' will be used as the default path.
740 # The MAN_EXTENSION tag determines the extension that is added to
741 # the generated man pages (default is the subroutine's section .3)
745 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
746 # then it will generate one additional man file for each entity
747 # documented in the real man page(s). These additional files
748 # only source the real man page, but without them the man command
749 # would be unable to find the correct page. The default is NO.
753 #---------------------------------------------------------------------------
754 # configuration options related to the XML output
755 #---------------------------------------------------------------------------
757 # If the GENERATE_XML tag is set to YES Doxygen will
758 # generate an XML file that captures the structure of
759 # the code including all documentation. Note that this
760 # feature is still experimental and incomplete at the
765 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
766 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
767 # put in front of it. If left blank `xml' will be used as the default path.
771 # The XML_SCHEMA tag can be used to specify an XML schema,
772 # which can be used by a validating XML parser to check the
773 # syntax of the XML files.
777 # The XML_DTD tag can be used to specify an XML DTD,
778 # which can be used by a validating XML parser to check the
779 # syntax of the XML files.
783 #---------------------------------------------------------------------------
784 # configuration options for the AutoGen Definitions output
785 #---------------------------------------------------------------------------
787 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
788 # generate an AutoGen Definitions (see autogen.sf.net) file
789 # that captures the structure of the code including all
790 # documentation. Note that this feature is still experimental
791 # and incomplete at the moment.
793 GENERATE_AUTOGEN_DEF = NO
795 #---------------------------------------------------------------------------
796 # configuration options related to the Perl module output
797 #---------------------------------------------------------------------------
799 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
800 # generate a Perl module file that captures the structure of
801 # the code including all documentation. Note that this
802 # feature is still experimental and incomplete at the
805 GENERATE_PERLMOD = NO
807 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
808 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
809 # to generate PDF and DVI output from the Perl module output.
813 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
814 # nicely formatted so it can be parsed by a human reader. This is useful
815 # if you want to understand what is going on. On the other hand, if this
816 # tag is set to NO the size of the Perl module output will be much smaller
817 # and Perl will parse it just the same.
821 # The names of the make variables in the generated doxyrules.make file
822 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
823 # This is useful so different doxyrules.make files included by the same
824 # Makefile don't overwrite each other's variables.
826 PERLMOD_MAKEVAR_PREFIX =
828 #---------------------------------------------------------------------------
829 # Configuration options related to the preprocessor
830 #---------------------------------------------------------------------------
832 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
833 # evaluate all C-preprocessor directives found in the sources and include
836 ENABLE_PREPROCESSING = YES
838 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
839 # names in the source code. If set to NO (the default) only conditional
840 # compilation will be performed. Macro expansion can be done in a controlled
841 # way by setting EXPAND_ONLY_PREDEF to YES.
843 MACRO_EXPANSION = YES
845 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
846 # then the macro expansion is limited to the macros specified with the
847 # PREDEFINED and EXPAND_AS_PREDEFINED tags.
849 EXPAND_ONLY_PREDEF = YES
851 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
852 # in the INCLUDE_PATH (see below) will be search if a #include is found.
854 SEARCH_INCLUDES = YES
856 # The INCLUDE_PATH tag can be used to specify one or more directories that
857 # contain include files that are not input files but should be processed by
862 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
863 # patterns (like *.h and *.hpp) to filter out the header-files in the
864 # directories. If left blank, the patterns specified with FILE_PATTERNS will
867 INCLUDE_FILE_PATTERNS =
869 # The PREDEFINED tag can be used to specify one or more macro names that
870 # are defined before the preprocessor is started (similar to the -D option of
871 # gcc). The argument of the tag is a list of macros of the form: name
872 # or name=definition (no spaces). If the definition and the = are
873 # omitted =1 is assumed.
875 PREDEFINED = __attribute__(ATR)=/**/
877 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
878 # this tag can be used to specify a list of macro names that should be expanded.
879 # The macro definition that is found in the sources will be used.
880 # Use the PREDEFINED tag if you want to use a different macro definition.
884 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
885 # doxygen's preprocessor will remove all function-like macros that are alone
886 # on a line, have an all uppercase name, and do not end with a semicolon. Such
887 # function macros are typically used for boiler-plate code, and will confuse the
888 # parser if not removed.
890 SKIP_FUNCTION_MACROS = YES
892 #---------------------------------------------------------------------------
893 # Configuration::addtions related to external references
894 #---------------------------------------------------------------------------
896 # The TAGFILES option can be used to specify one or more tagfiles.
897 # Optionally an initial location of the external documentation
898 # can be added for each tagfile. The format of a tag file without
899 # this location is as follows:
900 # TAGFILES = file1 file2 ...
901 # Adding location for the tag files is done as follows:
902 # TAGFILES = file1=loc1 "file2 = loc2" ...
903 # where "loc1" and "loc2" can be relative or absolute paths or
904 # URLs. If a location is present for each tag, the installdox tool
905 # does not have to be run to correct the links.
906 # Note that each tag file must have a unique name
907 # (where the name does NOT include the path)
908 # If a tag file is not located in the directory in which doxygen
909 # is run, you must also specify the path to the tagfile here.
913 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
914 # a tag file that is based on the input files it reads.
918 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
919 # in the class index. If set to NO only the inherited external classes
924 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
925 # in the modules index. If set to NO, only the current project's groups will
928 EXTERNAL_GROUPS = YES
930 # The PERL_PATH should be the absolute path and name of the perl script
931 # interpreter (i.e. the result of `which perl').
933 PERL_PATH = /usr/bin/perl
935 #---------------------------------------------------------------------------
936 # Configuration options related to the dot tool
937 #---------------------------------------------------------------------------
939 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
940 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or
941 # super classes. Setting the tag to NO turns the diagrams off. Note that this
942 # option is superceded by the HAVE_DOT option below. This is only a fallback. It is
943 # recommended to install and use dot, since it yields more powerful graphs.
947 # If set to YES, the inheritance and collaboration graphs will hide
948 # inheritance and usage relations if the target is undocumented
951 HIDE_UNDOC_RELATIONS = YES
953 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
954 # available from the path. This tool is part of Graphviz, a graph visualization
955 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
956 # have no effect if this option is set to NO (the default)
958 HAVE_DOT = @enable_dot@
960 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
961 # will generate a graph for each documented class showing the direct and
962 # indirect inheritance relations. Setting this tag to YES will force the
963 # the CLASS_DIAGRAMS tag to NO.
967 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
968 # will generate a graph for each documented class showing the direct and
969 # indirect implementation dependencies (inheritance, containment, and
970 # class references variables) of the class with other documented classes.
972 COLLABORATION_GRAPH = YES
974 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
975 # collaboration diagrams in a style similiar to the OMG's Unified Modeling
980 # If set to YES, the inheritance and collaboration graphs will show the
981 # relations between templates and their instances.
983 TEMPLATE_RELATIONS = NO
985 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
986 # tags are set to YES then doxygen will generate a graph for each documented
987 # file showing the direct and indirect include dependencies of the file with
988 # other documented files.
992 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
993 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
994 # documented header file showing the documented files that directly or
995 # indirectly include this file.
997 INCLUDED_BY_GRAPH = YES
999 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1000 # generate a call dependency graph for every global function or class method.
1001 # Note that enabling this option will significantly increase the time of a run.
1002 # So in most cases it will be better to enable call graphs for selected
1003 # functions only using the \callgraph command.
1007 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1008 # will graphical hierarchy of all classes instead of a textual one.
1010 GRAPHICAL_HIERARCHY = YES
1012 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1013 # generated by dot. Possible values are png, jpg, or gif
1014 # If left blank png will be used.
1016 DOT_IMAGE_FORMAT = png
1018 # The tag DOT_PATH can be used to specify the path where the dot tool can be
1019 # found. If left blank, it is assumed the dot tool can be found on the path.
1021 DOT_PATH = @DOT_PATH@
1023 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1024 # contain dot files that are included in the documentation (see the
1025 # \dotfile command).
1029 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1030 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1031 # this value, doxygen will try to truncate the graph, so that it fits within
1032 # the specified constraint. Beware that most browsers cannot cope with very
1035 MAX_DOT_GRAPH_WIDTH = 1024
1037 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1038 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1039 # this value, doxygen will try to truncate the graph, so that it fits within
1040 # the specified constraint. Beware that most browsers cannot cope with very
1043 MAX_DOT_GRAPH_HEIGHT = 1024
1045 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1046 # graphs generated by dot. A depth value of 3 means that only nodes reachable
1047 # from the root by following a path via at most 3 edges will be shown. Nodes that
1048 # lay further from the root node will be omitted. Note that setting this option to
1049 # 1 or 2 may greatly reduce the computation time needed for large code bases. Also
1050 # note that a graph may be further truncated if the graph's image dimensions are
1051 # not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT).
1052 # If 0 is used for the depth value (the default), the graph is not depth-constrained.
1054 MAX_DOT_GRAPH_DEPTH = 0
1056 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1057 # generate a legend page explaining the meaning of the various boxes and
1058 # arrows in the dot generated graphs.
1060 GENERATE_LEGEND = YES
1062 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1063 # remove the intermediate dot files that are used to generate
1064 # the various graphs.
1068 #---------------------------------------------------------------------------
1069 # Configuration::addtions related to the search engine
1070 #---------------------------------------------------------------------------
1072 # The SEARCHENGINE tag specifies whether or not a search engine should be
1073 # used. If set to NO the values of all tags below this one will be ignored.
1077 # The CGI_NAME tag should be the name of the CGI script that
1078 # starts the search engine (doxysearch) with the correct parameters.
1079 # A script with this name will be generated by doxygen.
1081 CGI_NAME = search.cgi
1083 # The CGI_URL tag should be the absolute URL to the directory where the
1084 # cgi binaries are located. See the documentation of your http daemon for
1089 # The DOC_URL tag should be the absolute URL to the directory where the
1090 # documentation is located. If left blank the absolute path to the
1091 # documentation, with file:// prepended to it, will be used.
1095 # The DOC_ABSPATH tag should be the absolute path to the directory where the
1096 # documentation is located. If left blank the directory on the local machine
1101 # The BIN_ABSPATH tag must point to the directory where the doxysearch binary
1104 BIN_ABSPATH = /usr/local/bin/
1106 # The EXT_DOC_PATHS tag can be used to specify one or more paths to
1107 # documentation generated for other projects. This allows doxysearch to search
1108 # the documentation for these projects as well.