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 DOXYFILE_ENCODING = UTF-8
18 PROJECT_NAME = SLP-Developer Library
20 OUTPUT_DIRECTORY = ./doxygen_output
22 OUTPUT_LANGUAGE = English
23 BRIEF_MEMBER_DESC = YES
26 ALWAYS_DETAILED_SEC = YES
27 INLINE_INHERITED_MEMB = NO
32 JAVADOC_AUTOBRIEF = NO
33 MULTILINE_CPP_IS_BRIEF = NO
36 SEPARATE_MEMBER_PAGES = YES
39 OPTIMIZE_OUTPUT_FOR_C = NO
40 OPTIMIZE_OUTPUT_JAVA = NO
41 BUILTIN_STL_SUPPORT = NO
43 DISTRIBUTE_GROUP_DOC = NO
46 #---------------------------------------------------------------------------
47 # Build related configuration options
48 #---------------------------------------------------------------------------
53 EXTRACT_LOCAL_CLASSES = NO
54 EXTRACT_LOCAL_METHODS = YES
55 HIDE_UNDOC_MEMBERS = YES
56 HIDE_UNDOC_CLASSES = YES
57 HIDE_FRIEND_COMPOUNDS = YES
58 HIDE_IN_BODY_DOCS = NO
60 CASE_SENSE_NAMES = YES
62 SHOW_INCLUDE_FILES = YES
64 SORT_MEMBER_DOCS = YES
66 SORT_BY_SCOPE_NAME = YES
67 SORT_GROUP_NAMES = YES
68 GENERATE_TODOLIST = NO
71 HTML DYNAMIC SECTIONS = YES
72 GENERATE_TESTLIST = NO
74 GENERATE_DEPRECATEDLIST= NO
76 MAX_INITIALIZER_LINES = 30
81 #---------------------------------------------------------------------------
82 # configuration options related to warning and progress messages
83 #---------------------------------------------------------------------------
85 # The QUIET tag can be used to turn on/off the messages that are generated
86 # by doxygen. Possible values are YES and NO. If left blank NO is used.
90 # The WARNINGS tag can be used to turn on/off the warning messages that are
91 # generated by doxygen. Possible values are YES and NO. If left blank
96 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
97 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
98 # automatically be disabled.
100 WARN_IF_UNDOCUMENTED = YES
102 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
103 # potential errors in the documentation, such as not documenting some
104 # parameters in a documented function, or documenting parameters that
105 # don't exist or using markup commands wrongly.
107 WARN_IF_DOC_ERROR = YES
109 # This WARN_NO_PARAMDOC option can be abled to get warnings for
110 # functions that are documented, but have no documentation for their parameters
111 # or return value. If set to NO (the default) doxygen will only warn about
112 # wrong or incomplete parameter documentation, but not about the absence of
115 WARN_NO_PARAMDOC = NO
117 # The WARN_FORMAT tag determines the format of the warning messages that
118 # doxygen can produce. The string should contain the $file, $line, and $text
119 # tags, which will be replaced by the file and line number from which the
120 # warning originated and the warning text. Optionally the format may contain
121 # $version, which will be replaced by the version of the file (if it could
122 # be obtained via FILE_VERSION_FILTER)
124 WARN_FORMAT = "$file:$line: $text"
126 # The WARN_LOGFILE tag can be used to specify a file to which warning
127 # and error messages should be written. If left blank the output is written
132 #---------------------------------------------------------------------------
133 # configuration options related to the input files
134 #---------------------------------------------------------------------------
136 # The INPUT tag can be used to specify the files and/or directories that contain
137 # documented source files. You may enter file names like "myfile.cpp" or
138 # directories like "/usr/src/myproject". Separate the files or directories
142 INPUT = ../src/commonlib/include/net_nfc_typedef.h ../src/clientlib/include/net_nfc_target_info.h ../src/clientlib/include/net_nfc_llcp.h ../src/clientlib/include/net_nfc_exchanger.h ../src/clientlib/include/net_nfc_ndef_message.h ../src/clientlib/include/net_nfc_data.h ../src/clientlib/include/net_nfc_ndef_record.h ../src/clientlib/include/net_nfc_apdu.h ../src/clientlib/include/net_nfc_tag.h ../src/clientlib/include/net_nfc.h ../src/clientlib/include/net_nfc_ndef_message_handover.h ../src/clientlib/include/net_nfc_tag_felica.h ../src/clientlib/include/net_nfc_tag_jewel.h ../src/clientlib/include/net_nfc_tag_mifare.h
145 # This tag can be used to specify the character encoding of the source files that
146 # doxygen parses. Internally doxygen uses the UTF-8 encoding, which is also the default
147 # input encoding. Doxygen uses libiconv (or the iconv built into libc) for the transcoding.
148 # See http://www.gnu.org/software/libiconv for the list of possible encodings.
150 INPUT_ENCODING = UTF-8
151 FILE_PATTERNS = *.h \
155 EXCLUDE_SYMLINKS = NO
156 EXCLUDE_PATTERNS = */test/* \
167 EXAMPLE_RECURSIVE = NO
168 IMAGE_PATH = ../image
171 FILTER_SOURCE_FILES = NO
173 #---------------------------------------------------------------------------
174 # configuration options related to source browsing
175 #---------------------------------------------------------------------------
177 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
178 # be generated. Documented entities will be cross-referenced with these sources.
179 # Note: To get rid of all source code in the generated output, make sure also
180 # VERBATIM_HEADERS is set to NO.
184 # Setting the INLINE_SOURCES tag to YES will include the body
185 # of functions and classes directly in the documentation.
189 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
190 # doxygen to hide any special comment blocks from generated source code
191 # fragments. Normal C and C++ comments will always remain visible.
193 STRIP_CODE_COMMENTS = YES
195 # If the REFERENCED_BY_RELATION tag is set to YES (the default)
196 # then for each documented function all documented
197 # functions referencing it will be listed.
199 REFERENCED_BY_RELATION = YES
201 # If the REFERENCES_RELATION tag is set to YES (the default)
202 # then for each documented function all documented entities
203 # called/used by that function will be listed.
205 REFERENCES_RELATION = YES
207 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
208 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
209 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
210 # link to the source code. Otherwise they will link to the documentstion.
212 REFERENCES_LINK_SOURCE = YES
214 # If the USE_HTAGS tag is set to YES then the references to source code
215 # will point to the HTML generated by the htags(1) tool instead of doxygen
216 # built-in source browser. The htags tool is part of GNU's global source
217 # tagging system (see http://www.gnu.org/software/global/global.html). You
218 # will need version 4.8.6 or higher.
222 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
223 # will generate a verbatim copy of the header file for each class for
224 # which an include is specified. Set to NO to disable this.
226 VERBATIM_HEADERS = YES
228 #---------------------------------------------------------------------------
229 # configuration options related to the alphabetical class index
230 #---------------------------------------------------------------------------
232 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
233 # of all compounds will be generated. Enable this if the project
234 # contains a lot of classes, structs, unions or interfaces.
236 ALPHABETICAL_INDEX = YES
237 COLS_IN_ALPHA_INDEX = 10
240 #---------------------------------------------------------------------------
241 # configuration options related to the HTML output
242 #---------------------------------------------------------------------------
244 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
245 # generate HTML output.
249 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
250 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
251 # put in front of it. If left blank `html' will be used as the default path.
255 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
256 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
257 # doxygen will generate files with .html extension.
259 HTML_FILE_EXTENSION = .html
261 # The HTML_HEADER tag can be used to specify a personal HTML header for
262 # each generated HTML page. If it is left blank doxygen will generate a
267 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
268 # each generated HTML page. If it is left blank doxygen will generate a
273 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
274 # style sheet that is used by each HTML page. It can be used to
275 # fine-tune the look of the HTML output. If the tag is left blank doxygen
276 # will generate a default style sheet. Note that doxygen will try to copy
277 # the style sheet file to the HTML output directory, so don't put your own
278 # stylesheet in the HTML output directory as well, or it will be erased!
280 HTML_STYLESHEET =./slp_doxy.css
282 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
283 # files or namespaces will be aligned in HTML using tables. If set to
284 # NO a bullet list will be used.
286 HTML_ALIGN_MEMBERS = YES
288 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
289 # will be generated that can be used as input for tools like the
290 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
291 # of the generated HTML documentation.
293 GENERATE_HTMLHELP = YES
295 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
296 # be used to specify the file name of the resulting .chm file. You
297 # can add a path in front of the file if the result should not be
298 # written to the html output directory.
302 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
303 # be used to specify the location (absolute path including file name) of
304 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
305 # the HTML help compiler on the generated index.hhp.
309 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
310 # controls if a separate .chi index file is generated (YES) or that
311 # it should be included in the master .chm file (NO).
315 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
316 # controls whether a binary table of contents is generated (YES) or a
317 # normal table of contents (NO) in the .chm file.
321 # The TOC_EXPAND flag can be set to YES to add extra items for group members
322 # to the contents of the HTML help documentation and to the tree view.
326 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
327 # top of each HTML page. The value NO (the default) enables the index and
328 # the value YES disables it.
332 # This tag can be used to set the number of enum values (range [1..20])
333 # that doxygen will group on one line in the generated HTML documentation.
335 ENUM_VALUES_PER_LINE = 4
337 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
338 # generated containing a tree-like index structure (just like the one that
339 # is generated for HTML Help). For this to work a browser that supports
340 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
341 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
342 # probably better off using the HTML help feature.
344 GENERATE_TREEVIEW = YES
346 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
347 # used to set the initial width (in pixels) of the frame in which the tree
352 #---------------------------------------------------------------------------
353 # configuration options related to the LaTeX output
354 #---------------------------------------------------------------------------
356 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
357 # generate Latex output.
361 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
362 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
363 # put in front of it. If left blank `latex' will be used as the default path.
367 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
368 # invoked. If left blank `latex' will be used as the default command name.
370 LATEX_CMD_NAME = latex
372 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
373 # generate index for LaTeX. If left blank `makeindex' will be used as the
374 # default command name.
376 MAKEINDEX_CMD_NAME = makeindex
378 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
379 # LaTeX documents. This may be useful for small projects and may help to
380 # save some trees in general.
384 # The PAPER_TYPE tag can be used to set the paper type that is used
385 # by the printer. Possible values are: a4, a4wide, letter, legal and
386 # executive. If left blank a4wide will be used.
390 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
391 # packages that should be included in the LaTeX output.
395 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
396 # the generated latex document. The header should contain everything until
397 # the first chapter. If it is left blank doxygen will generate a
398 # standard header. Notice: only use this tag if you know what you are doing!
402 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
403 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
404 # contain links (just like the HTML output) instead of page references
405 # This makes the output suitable for online browsing using a pdf viewer.
409 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
410 # plain latex in the generated Makefile. Set this option to YES to get a
411 # higher quality PDF documentation.
415 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
416 # command to the generated LaTeX files. This will instruct LaTeX to keep
417 # running if errors occur, instead of asking the user for help.
418 # This option is also used when generating formulas in HTML.
422 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
423 # include the index chapters (such as File Index, Compound Index, etc.)
426 LATEX_HIDE_INDICES = NO
428 #---------------------------------------------------------------------------
429 # configuration options related to the RTF output
430 #---------------------------------------------------------------------------
432 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
433 # The RTF output is optimized for Word 97 and may not look very pretty with
434 # other RTF readers or editors.
438 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
439 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
440 # put in front of it. If left blank `rtf' will be used as the default path.
444 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
445 # RTF documents. This may be useful for small projects and may help to
446 # save some trees in general.
450 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
451 # will contain hyperlink fields. The RTF file will
452 # contain links (just like the HTML output) instead of page references.
453 # This makes the output suitable for online browsing using WORD or other
454 # programs which support those fields.
455 # Note: wordpad (write) and others do not support links.
459 # Load stylesheet definitions from file. Syntax is similar to doxygen's
460 # config file, i.e. a series of assignments. You only have to provide
461 # replacements, missing definitions are set to their default value.
463 RTF_STYLESHEET_FILE =
465 # Set optional variables used in the generation of an rtf document.
466 # Syntax is similar to doxygen's config file.
468 RTF_EXTENSIONS_FILE =
470 #---------------------------------------------------------------------------
471 # configuration options related to the man page output
472 #---------------------------------------------------------------------------
474 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
479 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
480 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
481 # put in front of it. If left blank `man' will be used as the default path.
485 # The MAN_EXTENSION tag determines the extension that is added to
486 # the generated man pages (default is the subroutine's section .3)
490 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
491 # then it will generate one additional man file for each entity
492 # documented in the real man page(s). These additional files
493 # only source the real man page, but without them the man command
494 # would be unable to find the correct page. The default is NO.
498 #---------------------------------------------------------------------------
499 # configuration options related to the XML output
500 #---------------------------------------------------------------------------
502 # If the GENERATE_XML tag is set to YES Doxygen will
503 # generate an XML file that captures the structure of
504 # the code including all documentation.
508 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
509 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
510 # put in front of it. If left blank `xml' will be used as the default path.
514 # The XML_SCHEMA tag can be used to specify an XML schema,
515 # which can be used by a validating XML parser to check the
516 # syntax of the XML files.
520 # The XML_DTD tag can be used to specify an XML DTD,
521 # which can be used by a validating XML parser to check the
522 # syntax of the XML files.
526 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
527 # dump the program listings (including syntax highlighting
528 # and cross-referencing information) to the XML output. Note that
529 # enabling this will significantly increase the size of the XML output.
531 XML_PROGRAMLISTING = YES
533 #---------------------------------------------------------------------------
534 # configuration options for the AutoGen Definitions output
535 #---------------------------------------------------------------------------
537 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
538 # generate an AutoGen Definitions (see autogen.sf.net) file
539 # that captures the structure of the code including all
540 # documentation. Note that this feature is still experimental
541 # and incomplete at the moment.
543 GENERATE_AUTOGEN_DEF = NO
545 #---------------------------------------------------------------------------
546 # configuration options related to the Perl module output
547 #---------------------------------------------------------------------------
549 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
550 # generate a Perl module file that captures the structure of
551 # the code including all documentation. Note that this
552 # feature is still experimental and incomplete at the
555 GENERATE_PERLMOD = NO
557 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
558 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
559 # to generate PDF and DVI output from the Perl module output.
563 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
564 # nicely formatted so it can be parsed by a human reader. This is useful
565 # if you want to understand what is going on. On the other hand, if this
566 # tag is set to NO the size of the Perl module output will be much smaller
567 # and Perl will parse it just the same.
571 # The names of the make variables in the generated doxyrules.make file
572 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
573 # This is useful so different doxyrules.make files included by the same
574 # Makefile don't overwrite each other's variables.
576 PERLMOD_MAKEVAR_PREFIX =
578 #---------------------------------------------------------------------------
579 # Configuration options related to the preprocessor
580 #---------------------------------------------------------------------------
582 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
583 # evaluate all C-preprocessor directives found in the sources and include
586 ENABLE_PREPROCESSING = YES
588 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
589 # names in the source code. If set to NO (the default) only conditional
590 # compilation will be performed. Macro expansion can be done in a controlled
591 # way by setting EXPAND_ONLY_PREDEF to YES.
595 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
596 # then the macro expansion is limited to the macros specified with the
597 # PREDEFINED and EXPAND_AS_DEFINED tags.
599 EXPAND_ONLY_PREDEF = NO
601 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
602 # in the INCLUDE_PATH (see below) will be search if a #include is found.
604 SEARCH_INCLUDES = YES
606 # The INCLUDE_PATH tag can be used to specify one or more directories that
607 # contain include files that are not input files but should be processed by
612 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
613 # patterns (like *.h and *.hpp) to filter out the header-files in the
614 # directories. If left blank, the patterns specified with FILE_PATTERNS will
617 INCLUDE_FILE_PATTERNS =
619 # The PREDEFINED tag can be used to specify one or more macro names that
620 # are defined before the preprocessor is started (similar to the -D option of
621 # gcc). The argument of the tag is a list of macros of the form: name
622 # or name=definition (no spaces). If the definition and the = are
623 # omitted =1 is assumed. To prevent a macro definition from being
624 # undefined via #undef or recursively expanded use the := operator
625 # instead of the = operator.
629 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
630 # this tag can be used to specify a list of macro names that should be expanded.
631 # The macro definition that is found in the sources will be used.
632 # Use the PREDEFINED tag if you want to use a different macro definition.
636 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
637 # doxygen's preprocessor will remove all function-like macros that are alone
638 # on a line, have an all uppercase name, and do not end with a semicolon. Such
639 # function macros are typically used for boiler-plate code, and will confuse
640 # the parser if not removed.
642 SKIP_FUNCTION_MACROS = YES
644 #---------------------------------------------------------------------------
645 # Configuration::additions related to external references
646 #---------------------------------------------------------------------------
648 # The TAGFILES option can be used to specify one or more tagfiles.
649 # Optionally an initial location of the external documentation
650 # can be added for each tagfile. The format of a tag file without
651 # this location is as follows:
652 # TAGFILES = file1 file2 ...
653 # Adding location for the tag files is done as follows:
654 # TAGFILES = file1=loc1 "file2 = loc2" ...
655 # where "loc1" and "loc2" can be relative or absolute paths or
656 # URLs. If a location is present for each tag, the installdox tool
657 # does not have to be run to correct the links.
658 # Note that each tag file must have a unique name
659 # (where the name does NOT include the path)
660 # If a tag file is not located in the directory in which doxygen
661 # is run, you must also specify the path to the tagfile here.
665 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
666 # a tag file that is based on the input files it reads.
670 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
671 # in the class index. If set to NO only the inherited external classes
676 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
677 # in the modules index. If set to NO, only the current project's groups will
680 EXTERNAL_GROUPS = YES
682 # The PERL_PATH should be the absolute path and name of the perl script
683 # interpreter (i.e. the result of `which perl').
685 PERL_PATH = /usr/bin/perl
687 #---------------------------------------------------------------------------
688 # Configuration options related to the dot tool
689 #---------------------------------------------------------------------------
691 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
692 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
693 # or super classes. Setting the tag to NO turns the diagrams off. Note that
694 # this option is superseded by the HAVE_DOT option below. This is only a
695 # fallback. It is recommended to install and use dot, since it yields more
700 # You can define message sequence charts within doxygen comments using the \msc
701 # command. Doxygen will then run the mscgen tool (see http://www.mcternan.me.uk/mscgen/) to
702 # produce the chart and insert it in the documentation. The MSCGEN_PATH tag allows you to
703 # specify the directory where the mscgen tool resides. If left empty the tool is assumed to
704 # be found in the default search path.
708 # If set to YES, the inheritance and collaboration graphs will hide
709 # inheritance and usage relations if the target is undocumented
712 HIDE_UNDOC_RELATIONS = YES
714 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
715 # available from the path. This tool is part of Graphviz, a graph visualization
716 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
717 # have no effect if this option is set to NO (the default)
721 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
722 # will generate a graph for each documented class showing the direct and
723 # indirect inheritance relations. Setting this tag to YES will force the
724 # the CLASS_DIAGRAMS tag to NO.
728 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
729 # will generate a graph for each documented class showing the direct and
730 # indirect implementation dependencies (inheritance, containment, and
731 # class references variables) of the class with other documented classes.
733 COLLABORATION_GRAPH = NO
735 # If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
736 # will generate a graph for groups, showing the direct groups dependencies
740 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
741 # collaboration diagrams in a style similar to the OMG's Unified Modeling
746 # If set to YES, the inheritance and collaboration graphs will show the
747 # relations between templates and their instances.
749 TEMPLATE_RELATIONS = NO
751 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
752 # tags are set to YES then doxygen will generate a graph for each documented
753 # file showing the direct and indirect include dependencies of the file with
754 # other documented files.
758 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
759 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
760 # documented header file showing the documented files that directly or
761 # indirectly include this file.
763 INCLUDED_BY_GRAPH = NO
765 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
766 # generate a call dependency graph for every global function or class method.
767 # Note that enabling this option will significantly increase the time of a run.
768 # So in most cases it will be better to enable call graphs for selected
769 # functions only using the \callgraph command.
773 # If the CALLER_GRAPH and HAVE_DOT tags are set to YES then doxygen will
774 # generate a caller dependency graph for every global function or class method.
775 # Note that enabling this option will significantly increase the time of a run.
776 # So in most cases it will be better to enable caller graphs for selected
777 # functions only using the \callergraph command.
781 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
782 # will graphical hierarchy of all classes instead of a textual one.
784 GRAPHICAL_HIERARCHY = NO
786 # If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
787 # then doxygen will show the dependencies a directory has on other directories
788 # in a graphical way. The dependency relations are determined by the #include
789 # relations between the files in the directories.
793 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
794 # generated by dot. Possible values are png, jpg, or gif
795 # If left blank png will be used.
797 DOT_IMAGE_FORMAT = jpg
799 # The tag DOT_PATH can be used to specify the path where the dot tool can be
800 # found. If left blank, it is assumed the dot tool can be found in the path.
804 # The DOTFILE_DIRS tag can be used to specify one or more directories that
805 # contain dot files that are included in the documentation (see the
810 # The MAX_DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
811 # nodes that will be shown in the graph. If the number of nodes in a graph
812 # becomes larger than this value, doxygen will truncate the graph, which is
813 # visualized by representing a node as a red box. Note that doxygen will always
814 # show the root nodes and its direct children regardless of this setting.
816 DOT_GRAPH_MAX_NODES = 50
818 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
819 # background. This is disabled by default, which results in a white background.
820 # Warning: Depending on the platform used, enabling this option may lead to
821 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
826 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
827 # files in one run (i.e. multiple -o and -T options on the command line). This
828 # makes dot run faster, but since only newer versions of dot (>1.8.10)
829 # support this, this feature is disabled by default.
831 DOT_MULTI_TARGETS = NO
833 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
834 # generate a legend page explaining the meaning of the various boxes and
835 # arrows in the dot generated graphs.
839 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
840 # remove the intermediate dot files that are used to generate
841 # the various graphs.
845 #---------------------------------------------------------------------------
846 # Configuration::additions related to the search engine
847 #---------------------------------------------------------------------------
849 # The SEARCHENGINE tag specifies whether or not a search engine should be
850 # used. If set to NO the values of all tags below this one will be ignored.