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 double hash (##) is considered a comment and is placed in
7 # front of the TAG it is preceding.
9 # All text after a single hash (#) is considered a comment and will be ignored.
11 # TAG = value [value, ...]
12 # For lists, items can also be appended using:
13 # TAG += value [value, ...]
14 # Values that contain spaces should be placed between quotes (\" \").
16 #---------------------------------------------------------------------------
17 # Project related configuration options
18 #---------------------------------------------------------------------------
20 # This tag specifies the encoding used for all characters in the config file
21 # that follow. The default is UTF-8 which is also the encoding used for all text
22 # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23 # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24 # for the list of possible encodings.
25 # The default value is: UTF-8.
27 DOXYFILE_ENCODING = UTF-8
29 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
30 # double-quotes, unless you are using Doxywizard) that should identify the
31 # project for which the documentation is generated. This name is used in the
32 # title of most generated pages and in a few other places.
33 # The default value is: My Project.
37 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
38 # could be handy for archiving the generated documentation or if some version
39 # control system is used.
43 # Using the PROJECT_BRIEF tag one can provide an optional one line description
44 # for a project that appears at the top of each page and should give viewer a
45 # quick idea about the purpose of the project. Keep the description short.
49 # With the PROJECT_LOGO tag one can specify an logo or icon that is included in
50 # the documentation. The maximum height of the logo should not exceed 55 pixels
51 # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo
52 # to the output directory.
56 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path
57 # into which the generated documentation will be written. If a relative path is
58 # entered, it will be relative to the location where doxygen was started. If
59 # left blank the current directory will be used.
61 OUTPUT_DIRECTORY = @DOXYGEN_DOCS_DIR@/generated-internal
63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
64 # directories (in 2 levels) under the output directory of each output format and
65 # will distribute the generated files over these directories. Enabling this
66 # option can be useful when feeding doxygen a huge amount of source files, where
67 # putting all generated files in the same directory would otherwise causes
68 # performance problems for the file system.
69 # The default value is: NO.
73 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
74 # documentation generated by doxygen is written. Doxygen will use this
75 # information to generate all constant output in the proper language.
76 # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,
77 # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
78 # Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,
79 # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
80 # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
81 # Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,
82 # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
83 # Ukrainian and Vietnamese.
84 # The default value is: English.
86 OUTPUT_LANGUAGE = English
88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member
89 # descriptions after the members that are listed in the file and class
90 # documentation (similar to Javadoc). Set to NO to disable this.
91 # The default value is: YES.
93 BRIEF_MEMBER_DESC = YES
95 # If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief
96 # description of a member or function before the detailed description
98 # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
99 # brief descriptions will be completely suppressed.
100 # The default value is: YES.
104 # This tag implements a quasi-intelligent brief description abbreviator that is
105 # used to form the text in various listings. Each string in this list, if found
106 # as the leading text of the brief description, will be stripped from the text
107 # and the result, after processing the whole list, is used as the annotated
108 # text. Otherwise, the brief description is used as-is. If left blank, the
109 # following values are used ($name is automatically replaced with the name of
110 # the entity):The $name class, The $name widget, The $name file, is, provides,
111 # specifies, contains, represents, a, an and the.
113 ABBREVIATE_BRIEF = "The $name class" \
125 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
126 # doxygen will generate a detailed section even if there is only a brief
128 # The default value is: NO.
130 ALWAYS_DETAILED_SEC = NO
132 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
133 # inherited members of a class in the documentation of that class as if those
134 # members were ordinary class members. Constructors, destructors and assignment
135 # operators of the base classes will not be shown.
136 # The default value is: NO.
138 INLINE_INHERITED_MEMB = NO
140 # If the FULL_PATH_NAMES tag is set to YES doxygen will prepend the full path
141 # before files name in the file list and in the header files. If set to NO the
142 # shortest path that makes the file name unique will be used
143 # The default value is: YES.
145 FULL_PATH_NAMES = YES
147 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
148 # Stripping is only done if one of the specified strings matches the left-hand
149 # part of the path. The tag can be used to show relative paths in the file list.
150 # If left blank the directory from which doxygen is run is used as the path to
153 # Note that you can specify absolute paths here, but also relative paths, which
154 # will be relative from the directory where doxygen is started.
155 # This tag requires that the tag FULL_PATH_NAMES is set to YES.
159 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
160 # path mentioned in the documentation of a class, which tells the reader which
161 # header file to include in order to use a class. If left blank only the name of
162 # the header file containing the class definition is used. Otherwise one should
163 # specify the list of include paths that are normally passed to the compiler
166 STRIP_FROM_INC_PATH =
168 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but
169 # less readable) file names. This can be useful is your file systems doesn't
170 # support long names like on DOS, Mac, or CD-ROM.
171 # The default value is: NO.
175 # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the
176 # first line (until the first dot) of a Javadoc-style comment as the brief
177 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
178 # style comments (thus requiring an explicit @brief command for a brief
180 # The default value is: NO.
182 JAVADOC_AUTOBRIEF = YES
184 # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
185 # line (until the first dot) of a Qt-style comment as the brief description. If
186 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
187 # requiring an explicit \brief command for a brief description.)
188 # The default value is: NO.
192 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a
193 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
194 # a brief description. This used to be the default behavior. The new default is
195 # to treat a multi-line C++ comment block as a detailed description. Set this
196 # tag to YES if you prefer the old behavior instead.
198 # Note that setting this tag to YES also means that rational rose comments are
199 # not recognized any more.
200 # The default value is: NO.
202 MULTILINE_CPP_IS_BRIEF = NO
204 # If the DETAILS_AT_TOP tag is set to YES then Doxygen
205 # will output the detailed description near the top, like JavaDoc.
206 # If set to NO, the detailed description appears after the member
211 # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the
212 # documentation from any documented member that it re-implements.
213 # The default value is: YES.
217 # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce a
218 # new page for each member. If set to NO, the documentation of a member will be
219 # part of the file/class/namespace that contains it.
220 # The default value is: NO.
222 SEPARATE_MEMBER_PAGES = NO
224 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
225 # uses this value to replace tabs by spaces in code fragments.
226 # Minimum value: 1, maximum value: 16, default value: 4.
230 # This tag can be used to specify a number of aliases that act as commands in
231 # the documentation. An alias has the form:
234 # "sideeffect=@par Side Effects:\n"
235 # will allow you to put the command \sideeffect (or @sideeffect) in the
236 # documentation, which will result in a user-defined paragraph with heading
237 # "Side Effects:". You can put \n's in the value part of an alias to insert
241 # Clip alias inserts the specified file between two text markers.
242 # EG: @clip{"button.h",public,private}
243 # Shows all lines between public and private *inclusive*.
244 ALIASES += clip{3}="\dontinclude \1 \n \skip \2 \n \until \3"
246 # <DALi Doxygen Tagging Rule>
248 # Use @SINCE_1_0, @SINCE_1_1, ... instead of @since,
249 # and use @DEPRECATED_1_0, @DEPRECATED_1_1, ... instead of @deprecated.
250 # It enables integrated management of version tagging between
251 # the open source DALi API reference and Tizen API reference.
252 # Using those tags with different ALIASES settings in each doxygen config file allows us
253 # to generate two versions of "Since" and "Deprecated" generated output
254 # from one set of public header files.
256 # If you need a newer version number like @SINCE_1_5 or @SINCE_2_0, just add new ALIASES for it.
258 # ##################################################3
259 # # Guide for Open Source DALi API Reference
261 # ### @SINCE example:
262 # [some-public-header.h]
267 # void SomeFunction();
269 # [generated html file]
270 # void SomeFunction()
275 # ### @DEPRECATED example 1:
276 # [some-public-header.h]
278 # * @DEPRECATED_1_0.3
281 # void SomeFunction();
283 # [generated html file]
284 # void SomeFunction()
286 # Deprecated since 1.0.3
289 # ### @DEPRECATED example 2:
290 # [some-public-header.h]
293 # * @DEPRECATED_1_0.3. Use SomeFunction2() instead.
296 # void SomeFunction();
298 # [generated html file]
299 # void SomeFunction()
301 # Deprecated since 1.0.3. Use SomeFunction2() instead.
304 # ##################################################3
305 # # Guide for Tizen Native API Reference
307 # ### @SINCE example:
308 # [some-public-header.h]
313 # void SomeFunction();
315 # [generated html file]
316 # void SomeFunction()
319 # 2.4, DALi Version 1.0.1
321 # ### @DEPRECATED example 1:
322 # [some-public-header.h]
324 # * @DEPRECATED_1_0.3
327 # void SomeFunction();
329 # [generated html file]
330 # void SomeFunction()
332 # Deprecated since 3.0, DALi version 1.0.3
335 # ### @DEPRECATED example 2:
336 # [some-public-header.h]
339 # * @DEPRECATED_1_0.3. Use SomeFunction2() instead.
342 # void SomeFunction();
344 # [generated html file]
345 # void SomeFunction()
347 # Deprecated since 3.0, DALi version 1.0.3. Use SomeFunction2() instead.
350 ###########################################
351 # For Open Source DALi API Reference
352 ALIASES += SINCE_1_0="@since 1.0"
353 ALIASES += SINCE_1_1="@since 1.1"
354 ALIASES += SINCE_1_2="@since 1.2"
356 # Extra tags for Tizen 3.0
357 ALIASES += SINCE_1_2_2="@since 1.2.2"
358 ALIASES += SINCE_1_2_4="@since 1.2.4"
359 ALIASES += SINCE_1_2_5="@since 1.2.5"
360 ALIASES += SINCE_1_2_10="@since 1.2.10"
361 ALIASES += SINCE_1_2_14="@since 1.2.14"
362 ALIASES += SINCE_1_2_32="@since 1.2.32"
364 ALIASES += DEPRECATED_1_0="@deprecated Deprecated since 1.0"
365 ALIASES += DEPRECATED_1_1="@deprecated Deprecated since 1.1"
366 ALIASES += DEPRECATED_1_2_8="@deprecated Deprecated since 1.2.8"
367 ALIASES += DEPRECATED_1_2_10="@deprecated Deprecated since 1.2.10"
368 ALIASES += DEPRECATED_1_2="@deprecated Deprecated since 1.2"
370 ALIASES += PLATFORM=""
371 ALIASES += PRIVLEVEL_PLATFORM=""
372 ALIASES += PRIVLEVEL_PUBLIC=""
373 ALIASES += PRIVILEGE_KEYGRAB=""
374 ALIASES += PRIVILEGE_DISPLAY=""
375 ALIASES += REMARK_INTERNET=""
376 ALIASES += REMARK_STORAGE=""
378 ############################################
379 ## For Tizen Native API Reference
380 #ALIASES += SINCE_1_0="\par Since:\n 2.4, DALi version 1.0"
381 #ALIASES += SINCE_1_1="\par Since:\n 3.0, DALi version 1.1"
382 #ALIASES += SINCE_1_2="\par Since:\n 4.0, DALi version 1.2"
384 ## Extra tags for Tizen 3.0
385 #ALIASES += SINCE_1_2_2="\par Since:\n 3.0, DALi version 1.2.2"
386 #ALIASES += SINCE_1_2_4="\par Since:\n 3.0, DALi version 1.2.4"
387 #ALIASES += SINCE_1_2_5="\par Since:\n 3.0, DALi version 1.2.5"
388 #ALIASES += SINCE_1_2_10="\par Since:\n 3.0, DALi version 1.2.10"
389 #ALIASES += SINCE_1_2_14="\par Since:\n 3.0, DALi version 1.2.14"
390 #ALIASES += SINCE_1_2_32="\par Since:\n 3.0, DALi version 1.2.32"
392 ## DALi has no deprecated API in Tizen 2.4 because it's DALi's first release.
393 ## Thus deprecated APIs in DALi 1.0.xx will be deprecated in Tizen 3.0.
394 #ALIASES += DEPRECATED_1_0="@deprecated Deprecated since 3.0, DALi version 1.0"
395 #ALIASES += DEPRECATED_1_1="@deprecated Deprecated since 3.0, DALi version 1.1"
396 #ALIASES += DEPRECATED_1_2_8="@deprecated Deprecated since 3.0, DALi version 1.2.8"
397 #ALIASES += DEPRECATED_1_2_10="@deprecated Deprecated since 3.0, DALi version 1.2.10"
398 #ALIASES += DEPRECATED_1_2="@deprecated Deprecated since 4.0, DALi version 1.2"
400 #ALIASES += PLATFORM="@platform"
401 #ALIASES += PRIVLEVEL_PLATFORM="\par Privilege Level:\n platform"
402 #ALIASES += PRIVLEVEL_PUBLIC="\par Privilege Level:\n public"
403 #ALIASES += PRIVILEGE_KEYGRAB="\par Privilege:\n http://tizen.org/privilege/keygrab"
404 #ALIASES += PRIVILEGE_DISPLAY="\par Privilege:\n http://tizen.org/privilege/display"
405 #ALIASES += REMARK_INTERNET="@remarks %http://tizen.org/privilege/internet is needed if @a url is a http or https address."
406 #ALIASES += REMARK_STORAGE="@remarks %http://tizen.org/privilege/mediastorage is needed if @a url is relevant to media storage. @remarks %http://tizen.org/privilege/externalstorage is needed if @a url is relevant to external storage."
408 # This tag can be used to specify a number of word-keyword mappings (TCL only).
409 # A mapping has the form "name=value". For example adding "class=itcl::class"
410 # will allow you to use the command class in the itcl::class meaning.
414 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
415 # only. Doxygen will then generate output that is more tailored for C. For
416 # instance, some of the names that are used will be different. The list of all
417 # members will be omitted, etc.
418 # The default value is: NO.
420 OPTIMIZE_OUTPUT_FOR_C = NO
422 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
423 # Python sources only. Doxygen will then generate output that is more tailored
424 # for that language. For instance, namespaces will be presented as packages,
425 # qualified scopes will look different, etc.
426 # The default value is: NO.
428 OPTIMIZE_OUTPUT_JAVA = NO
430 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
431 # sources. Doxygen will then generate output that is tailored for Fortran.
432 # The default value is: NO.
434 OPTIMIZE_FOR_FORTRAN = NO
436 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
437 # sources. Doxygen will then generate output that is tailored for VHDL.
438 # The default value is: NO.
440 OPTIMIZE_OUTPUT_VHDL = NO
442 # Doxygen selects the parser to use depending on the extension of the files it
443 # parses. With this tag you can assign which parser to use for a given
444 # extension. Doxygen has a built-in mapping, but you can override or extend it
445 # using this tag. The format is ext=language, where ext is a file extension, and
446 # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
447 # C#, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL. For instance to make
448 # doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
449 # (default is Fortran), use: inc=Fortran f=C.
451 # Note For files without extension you can use no_extension as a placeholder.
453 # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
454 # the files are not read by doxygen.
458 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
459 # according to the Markdown format, which allows for more readable
460 # documentation. See http://daringfireball.net/projects/markdown/ for details.
461 # The output of markdown processing is further processed by doxygen, so you can
462 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
463 # case of backward compatibilities issues.
464 # The default value is: YES.
466 MARKDOWN_SUPPORT = YES
468 # When enabled doxygen tries to link words that correspond to documented
469 # classes, or namespaces to their corresponding documentation. Such a link can
470 # be prevented in individual cases by by putting a % sign in front of the word
471 # or globally by setting AUTOLINK_SUPPORT to NO.
472 # The default value is: YES.
474 AUTOLINK_SUPPORT = YES
476 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
477 # to include (a tag file for) the STL sources as input, then you should set this
478 # tag to YES in order to let doxygen match functions declarations and
479 # definitions whose arguments contain STL classes (e.g. func(std::string);
480 # versus func(std::string) {}). This also make the inheritance and collaboration
481 # diagrams that involve STL classes more complete and accurate.
482 # The default value is: NO.
484 BUILTIN_STL_SUPPORT = YES
486 # If you use Microsoft's C++/CLI language, you should set this option to YES to
487 # enable parsing support.
488 # The default value is: NO.
492 # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
493 # http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen
494 # will parse them like normal C++ but will assume all classes use public instead
495 # of private inheritance when no explicit protection keyword is present.
496 # The default value is: NO.
500 # For Microsoft's IDL there are propget and propput attributes to indicate
501 # getter and setter methods for a property. Setting this option to YES will make
502 # doxygen to replace the get and set methods by a property in the documentation.
503 # This will only work if the methods are indeed getting or setting a simple
504 # type. If this is not the case, or you want to show the methods anyway, you
505 # should set this option to NO.
506 # The default value is: YES.
508 IDL_PROPERTY_SUPPORT = YES
510 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
511 # tag is set to YES, then doxygen will reuse the documentation of the first
512 # member in the group (if any) for the other members of the group. By default
513 # all members of a group must be documented explicitly.
514 # The default value is: NO.
516 DISTRIBUTE_GROUP_DOC = NO
518 # Set the SUBGROUPING tag to YES to allow class member groups of the same type
519 # (for instance a group of public functions) to be put as a subgroup of that
520 # type (e.g. under the Public Functions section). Set it to NO to prevent
521 # subgrouping. Alternatively, this can be done per class using the
522 # \nosubgrouping command.
523 # The default value is: YES.
527 # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
528 # are shown inside the group in which they are included (e.g. using \ingroup)
529 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
532 # Note that this feature does not work in combination with
533 # SEPARATE_MEMBER_PAGES.
534 # The default value is: NO.
536 INLINE_GROUPED_CLASSES = NO
538 # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
539 # with only public data fields or simple typedef fields will be shown inline in
540 # the documentation of the scope in which they are defined (i.e. file,
541 # namespace, or group documentation), provided this scope is documented. If set
542 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
543 # Man pages) or section (for LaTeX and RTF).
544 # The default value is: NO.
546 INLINE_SIMPLE_STRUCTS = NO
548 # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
549 # enum is documented as struct, union, or enum with the name of the typedef. So
550 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
551 # with name TypeT. When disabled the typedef will appear as a member of a file,
552 # namespace, or class. And the struct will be named TypeS. This can typically be
553 # useful for C code in case the coding convention dictates that all compound
554 # types are typedef'ed and only the typedef is referenced, never the tag name.
555 # The default value is: NO.
557 TYPEDEF_HIDES_STRUCT = NO
559 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
560 # cache is used to resolve symbols given their name and scope. Since this can be
561 # an expensive process and often the same symbol appears multiple times in the
562 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
563 # doxygen will become slower. If the cache is too large, memory is wasted. The
564 # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
565 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
566 # symbols. At the end of a run doxygen will report the cache usage and suggest
567 # the optimal cache size from a speed point of view.
568 # Minimum value: 0, maximum value: 9, default value: 0.
570 LOOKUP_CACHE_SIZE = 0
572 #---------------------------------------------------------------------------
573 # Build related configuration options
574 #---------------------------------------------------------------------------
576 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
577 # documentation are documented, even if no documentation was available. Private
578 # class members and static file members will be hidden unless the
579 # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
580 # Note: This will also disable the warnings about undocumented members that are
581 # normally produced when WARNINGS is set to YES.
582 # The default value is: NO.
586 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class will
587 # be included in the documentation.
588 # The default value is: NO.
590 EXTRACT_PRIVATE = YES
592 # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
593 # scope will be included in the documentation.
594 # The default value is: NO.
598 # If the EXTRACT_STATIC tag is set to YES all static members of a file will be
599 # included in the documentation.
600 # The default value is: NO.
604 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) defined
605 # locally in source files will be included in the documentation. If set to NO
606 # only classes defined in header files are included. Does not have any effect
608 # The default value is: YES.
610 EXTRACT_LOCAL_CLASSES = YES
612 # This flag is only useful for Objective-C code. When set to YES local methods,
613 # which are defined in the implementation section but not in the interface are
614 # included in the documentation. If set to NO only methods in the interface are
616 # The default value is: NO.
618 EXTRACT_LOCAL_METHODS = NO
620 # If this flag is set to YES, the members of anonymous namespaces will be
621 # extracted and appear in the documentation as a namespace called
622 # 'anonymous_namespace{file}', where file will be replaced with the base name of
623 # the file that contains the anonymous namespace. By default anonymous namespace
625 # The default value is: NO.
627 EXTRACT_ANON_NSPACES = YES
629 # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
630 # undocumented members inside documented classes or files. If set to NO these
631 # members will be included in the various overviews, but no documentation
632 # section is generated. This option has no effect if EXTRACT_ALL is enabled.
633 # The default value is: NO.
635 HIDE_UNDOC_MEMBERS = NO
637 # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
638 # undocumented classes that are normally visible in the class hierarchy. If set
639 # to NO these classes will be included in the various overviews. This option has
640 # no effect if EXTRACT_ALL is enabled.
641 # The default value is: NO.
643 HIDE_UNDOC_CLASSES = NO
645 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
646 # (class|struct|union) declarations. If set to NO these declarations will be
647 # included in the documentation.
648 # The default value is: NO.
650 HIDE_FRIEND_COMPOUNDS = NO
652 # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
653 # documentation blocks found inside the body of a function. If set to NO these
654 # blocks will be appended to the function's detailed documentation block.
655 # The default value is: NO.
657 HIDE_IN_BODY_DOCS = NO
659 # The INTERNAL_DOCS tag determines if documentation that is typed after a
660 # \internal command is included. If the tag is set to NO then the documentation
661 # will be excluded. Set it to YES to include the internal documentation.
662 # The default value is: NO.
666 # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
667 # names in lower-case letters. If set to YES upper-case letters are also
668 # allowed. This is useful if you have classes or files whose names only differ
669 # in case and if your file system supports case sensitive file names. Windows
670 # and Mac users are advised to set this option to NO.
671 # The default value is: system dependent.
673 CASE_SENSE_NAMES = NO
675 # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
676 # their full class and namespace scopes in the documentation. If set to YES the
677 # scope will be hidden.
678 # The default value is: NO.
680 HIDE_SCOPE_NAMES = NO
682 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
683 # the files that are included by a file in the documentation of that file.
684 # The default value is: YES.
686 SHOW_INCLUDE_FILES = YES
688 # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
689 # grouped member an include statement to the documentation, telling the reader
690 # which file to include in order to use the member.
691 # The default value is: NO.
693 SHOW_GROUPED_MEMB_INC = NO
695 # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
696 # files with double quotes in the documentation rather than with sharp brackets.
697 # The default value is: NO.
699 FORCE_LOCAL_INCLUDES = NO
701 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
702 # documentation for inline members.
703 # The default value is: YES.
707 # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
708 # (detailed) documentation of file and class members alphabetically by member
709 # name. If set to NO the members will appear in declaration order.
710 # The default value is: YES.
712 SORT_MEMBER_DOCS = YES
714 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
715 # descriptions of file, namespace and class members alphabetically by member
716 # name. If set to NO the members will appear in declaration order. Note that
717 # this will also influence the order of the classes in the class list.
718 # The default value is: NO.
722 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
723 # (brief and detailed) documentation of class members so that constructors and
724 # destructors are listed first. If set to NO the constructors will appear in the
725 # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
726 # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
727 # member documentation.
728 # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
729 # detailed member documentation.
730 # The default value is: NO.
732 SORT_MEMBERS_CTORS_1ST = NO
734 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
735 # of group names into alphabetical order. If set to NO the group names will
736 # appear in their defined order.
737 # The default value is: NO.
739 SORT_GROUP_NAMES = NO
741 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
742 # fully-qualified names, including namespaces. If set to NO, the class list will
743 # be sorted only by class name, not including the namespace part.
744 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
745 # Note: This option applies only to the class list, not to the alphabetical
747 # The default value is: NO.
749 SORT_BY_SCOPE_NAME = NO
751 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
752 # type resolution of all parameters of a function it will reject a match between
753 # the prototype and the implementation of a member function even if there is
754 # only one candidate or it is obvious which candidate to choose by doing a
755 # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
756 # accept a match between prototype and implementation in such cases.
757 # The default value is: NO.
759 STRICT_PROTO_MATCHING = NO
761 # The GENERATE_TODOLIST tag can be used to enable ( YES) or disable ( NO) the
762 # todo list. This list is created by putting \todo commands in the
764 # The default value is: YES.
766 GENERATE_TODOLIST = NO
768 # The GENERATE_TESTLIST tag can be used to enable ( YES) or disable ( NO) the
769 # test list. This list is created by putting \test commands in the
771 # The default value is: YES.
773 GENERATE_TESTLIST = NO
775 # The GENERATE_BUGLIST tag can be used to enable ( YES) or disable ( NO) the bug
776 # list. This list is created by putting \bug commands in the documentation.
777 # The default value is: YES.
779 GENERATE_BUGLIST = NO
781 # The GENERATE_DEPRECATEDLIST tag can be used to enable ( YES) or disable ( NO)
782 # the deprecated list. This list is created by putting \deprecated commands in
784 # The default value is: YES.
786 GENERATE_DEPRECATEDLIST= YES
788 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
789 # sections, marked by \if <section_label> ... \endif and \cond <section_label>
790 # ... \endcond blocks.
794 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
795 # initial value of a variable or macro / define can have for it to appear in the
796 # documentation. If the initializer consists of more lines than specified here
797 # it will be hidden. Use a value of 0 to hide initializers completely. The
798 # appearance of the value of individual variables and macros / defines can be
799 # controlled using \showinitializer or \hideinitializer command in the
800 # documentation regardless of this setting.
801 # Minimum value: 0, maximum value: 10000, default value: 30.
803 MAX_INITIALIZER_LINES = 30
805 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
806 # the bottom of the documentation of classes and structs. If set to YES the list
807 # will mention the files that were used to generate the documentation.
808 # The default value is: YES.
810 SHOW_USED_FILES = YES
812 # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
813 # will remove the Files entry from the Quick Index and from the Folder Tree View
815 # The default value is: YES.
819 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
820 # page. This will remove the Namespaces entry from the Quick Index and from the
821 # Folder Tree View (if specified).
822 # The default value is: YES.
824 SHOW_NAMESPACES = YES
826 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
827 # doxygen should invoke to get the current version for each file (typically from
828 # the version control system). Doxygen will invoke the program by executing (via
829 # popen()) the command command input-file, where command is the value of the
830 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
831 # by doxygen. Whatever the program writes to standard output is used as the file
832 # version. For an example see the documentation.
834 FILE_VERSION_FILTER =
836 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
837 # by doxygen. The layout file controls the global structure of the generated
838 # output files in an output format independent way. To create the layout file
839 # that represents doxygen's defaults, run doxygen with the -l option. You can
840 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
841 # will be used as the name of the layout file.
843 # Note that if you run doxygen from a directory containing a file called
844 # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
847 LAYOUT_FILE = @DOXYGEN_DOCS_DIR@/DaliLayout.xml
849 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
850 # the reference definitions. This must be a list of .bib files. The .bib
851 # extension is automatically appended if omitted. This requires the bibtex tool
852 # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
853 # For LaTeX the style of the bibliography can be controlled using
854 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
855 # search path. Do not use file names with spaces, bibtex cannot handle them. See
856 # also \cite for info how to create references.
860 #---------------------------------------------------------------------------
861 # Configuration options related to warning and progress messages
862 #---------------------------------------------------------------------------
864 # The QUIET tag can be used to turn on/off the messages that are generated to
865 # standard output by doxygen. If QUIET is set to YES this implies that the
867 # The default value is: NO.
871 # The WARNINGS tag can be used to turn on/off the warning messages that are
872 # generated to standard error ( stderr) by doxygen. If WARNINGS is set to YES
873 # this implies that the warnings are on.
875 # Tip: Turn warnings on while writing the documentation.
876 # The default value is: YES.
880 # If the WARN_IF_UNDOCUMENTED tag is set to YES, then doxygen will generate
881 # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
882 # will automatically be disabled.
883 # The default value is: YES.
885 WARN_IF_UNDOCUMENTED = YES
887 # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
888 # potential errors in the documentation, such as not documenting some parameters
889 # in a documented function, or documenting parameters that don't exist or using
890 # markup commands wrongly.
891 # The default value is: YES.
893 WARN_IF_DOC_ERROR = YES
895 # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
896 # are documented, but have no documentation for their parameters or return
897 # value. If set to NO doxygen will only warn about wrong or incomplete parameter
898 # documentation, but not about the absence of documentation.
899 # The default value is: NO.
901 WARN_NO_PARAMDOC = YES
903 # The WARN_FORMAT tag determines the format of the warning messages that doxygen
904 # can produce. The string should contain the $file, $line, and $text tags, which
905 # will be replaced by the file and line number from which the warning originated
906 # and the warning text. Optionally the format may contain $version, which will
907 # be replaced by the version of the file (if it could be obtained via
908 # FILE_VERSION_FILTER)
909 # The default value is: $file:$line: $text.
911 WARN_FORMAT = "$file:$line: $text"
913 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
914 # messages should be written. If left blank the output is written to standard
919 #---------------------------------------------------------------------------
920 # configuration options related to the input files
921 #---------------------------------------------------------------------------
923 # The INPUT tag is used to specify the files and/or directories that contain
924 # documented source files. You may enter file names like myfile.cpp or
925 # directories like /usr/src/myproject. Separate the files or directories with
927 # Note: If this tag is empty the current directory is searched.
929 INPUT = @DOXYGEN_DOCS_DIR@content \
930 ../../../../dali-core/dali \
931 ../../../../dali-adaptor/adaptors/public-api \
932 ../../../../dali-adaptor/adaptors/devel-api
933 ../../../../dali-adaptor/adaptors/base \
934 ../../../../dali-adaptor/adaptors/common \
935 ../../../../dali-adaptor/adaptors/ecore \
936 ../../../../dali-adaptor/adaptors/integration-api
937 ../../../../dali-adaptor/adaptors/mobile \
938 ../../../../dali-adaptor/adaptors/tizen
939 ../../../../dali-adaptor/adaptors/x11
940 ../../../../dali-adaptor/plugins \
941 ../../../../dali-adaptor/platform-abstractions/interfaces \
942 ../../../../dali-adaptor/platform-abstractions/portable \
943 ../../../../dali-adaptor/platform-abstractions/tizen \
944 ../../../dali-toolkit/devel-api \
945 ../../../dali-toolkit/internal \
946 ../../../dali-toolkit/public-api
948 # This tag can be used to specify the character encoding of the source files
949 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
950 # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
951 # documentation (see: http://www.gnu.org/software/libiconv) for the list of
952 # possible encodings.
953 # The default value is: UTF-8.
955 INPUT_ENCODING = UTF-8
957 # If the value of the INPUT tag contains directories, you can use the
958 # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
959 # *.h) to filter out the source-files in the directories. If left blank the
960 # following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii,
961 # *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp,
962 # *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown,
963 # *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf,
964 # *.qsf, *.as and *.js.
966 FILE_PATTERNS = *.c \
999 # The RECURSIVE tag can be used to specify whether or not subdirectories should
1000 # be searched for input files as well.
1001 # The default value is: NO.
1005 # The EXCLUDE tag can be used to specify files and/or directories that should be
1006 # excluded from the INPUT source files. This way you can easily exclude a
1007 # subdirectory from a directory tree whose root is specified with the INPUT tag.
1009 # Note that relative paths are relative to the directory from which doxygen is
1014 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
1015 # directories that are symbolic links (a Unix file system feature) are excluded
1017 # The default value is: NO.
1019 EXCLUDE_SYMLINKS = NO
1021 # If the value of the INPUT tag contains directories, you can use the
1022 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
1023 # certain files from those directories.
1025 # Note that the wildcards are matched against the file with absolute path, so to
1026 # exclude all test directories for example use the pattern */test/*
1030 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
1031 # (namespaces, classes, functions, etc.) that should be excluded from the
1032 # output. The symbol name can be a fully qualified name, a word, or if the
1033 # wildcard * is used, a substring. Examples: ANamespace, AClass,
1034 # AClass::ANamespace, ANamespace::*Test
1036 # Note that the wildcards are matched against the file with absolute path, so to
1037 # exclude all test directories use the pattern */test/*
1041 # The EXAMPLE_PATH tag can be used to specify one or more files or directories
1042 # that contain example code fragments that are included (see the \include
1045 EXAMPLE_PATH = ../../../docs/../
1047 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
1048 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
1049 # *.h) to filter out the source-files in the directories. If left blank all
1050 # files are included.
1052 EXAMPLE_PATTERNS = *
1054 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
1055 # searched for input files to be used with the \include or \dontinclude commands
1056 # irrespective of the value of the RECURSIVE tag.
1057 # The default value is: NO.
1059 EXAMPLE_RECURSIVE = YES
1061 # The IMAGE_PATH tag can be used to specify one or more files or directories
1062 # that contain images that are to be included in the documentation (see the
1065 IMAGE_PATH = ../../../docs/content/images
1067 # The INPUT_FILTER tag can be used to specify a program that doxygen should
1068 # invoke to filter for each input file. Doxygen will invoke the filter program
1069 # by executing (via popen()) the command:
1071 # <filter> <input-file>
1073 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
1074 # name of an input file. Doxygen will then use the output that the filter
1075 # program writes to standard output. If FILTER_PATTERNS is specified, this tag
1078 # Note that the filter must not add or remove lines; it is applied before the
1079 # code is scanned, but not when the output code is generated. If lines are added
1080 # or removed, the anchors will not be placed correctly.
1084 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
1085 # basis. Doxygen will compare the file name with each pattern and apply the
1086 # filter if there is a match. The filters are a list of the form: pattern=filter
1087 # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
1088 # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
1089 # patterns match the file name, INPUT_FILTER is applied.
1093 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
1094 # INPUT_FILTER ) will also be used to filter the input files that are used for
1095 # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
1096 # The default value is: NO.
1098 FILTER_SOURCE_FILES = NO
1100 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
1101 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
1102 # it is also possible to disable source filtering for a specific pattern using
1103 # *.ext= (so without naming a filter).
1104 # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
1106 FILTER_SOURCE_PATTERNS =
1108 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
1109 # is part of the input, its contents will be placed on the main page
1110 # (index.html). This can be useful if you have a project on for instance GitHub
1111 # and want to reuse the introduction page also for the doxygen output.
1113 USE_MDFILE_AS_MAINPAGE = main.md
1115 #---------------------------------------------------------------------------
1116 # Configuration options related to source browsing
1117 #---------------------------------------------------------------------------
1119 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
1120 # generated. Documented entities will be cross-referenced with these sources.
1122 # Note: To get rid of all source code in the generated output, make sure that
1123 # also VERBATIM_HEADERS is set to NO.
1124 # The default value is: NO.
1126 SOURCE_BROWSER = YES
1128 # Setting the INLINE_SOURCES tag to YES will include the body of functions,
1129 # classes and enums directly into the documentation.
1130 # The default value is: NO.
1134 # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
1135 # special comment blocks from generated source code fragments. Normal C, C++ and
1136 # Fortran comments will always remain visible.
1137 # The default value is: YES.
1139 STRIP_CODE_COMMENTS = YES
1141 # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
1142 # function all documented functions referencing it will be listed.
1143 # The default value is: NO.
1145 REFERENCED_BY_RELATION = NO
1147 # If the REFERENCES_RELATION tag is set to YES then for each documented function
1148 # all documented entities called/used by that function will be listed.
1149 # The default value is: NO.
1151 REFERENCES_RELATION = NO
1153 # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
1154 # to YES, then the hyperlinks from functions in REFERENCES_RELATION and
1155 # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
1156 # link to the documentation.
1157 # The default value is: YES.
1159 REFERENCES_LINK_SOURCE = YES
1161 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1162 # source code will show a tooltip with additional information such as prototype,
1163 # brief description and links to the definition and documentation. Since this
1164 # will make the HTML file larger and loading of large files a bit slower, you
1165 # can opt to disable this feature.
1166 # The default value is: YES.
1167 # This tag requires that the tag SOURCE_BROWSER is set to YES.
1169 SOURCE_TOOLTIPS = NO
1171 # If the USE_HTAGS tag is set to YES then the references to source code will
1172 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1173 # source browser. The htags tool is part of GNU's global source tagging system
1174 # (see http://www.gnu.org/software/global/global.html). You will need version
1177 # To use it do the following:
1178 # - Install the latest version of global
1179 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
1180 # - Make sure the INPUT points to the root of the source tree
1181 # - Run doxygen as normal
1183 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
1184 # tools must be available from the command line (i.e. in the search path).
1186 # The result: instead of the source browser generated by doxygen, the links to
1187 # source code will now point to the output of htags.
1188 # The default value is: NO.
1189 # This tag requires that the tag SOURCE_BROWSER is set to YES.
1193 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
1194 # verbatim copy of the header file for each class for which an include is
1195 # specified. Set to NO to disable this.
1196 # See also: Section \class.
1197 # The default value is: YES.
1199 VERBATIM_HEADERS = YES
1201 #---------------------------------------------------------------------------
1202 # Configuration options related to the alphabetical class index
1203 #---------------------------------------------------------------------------
1205 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
1206 # compounds will be generated. Enable this if the project contains a lot of
1207 # classes, structs, unions or interfaces.
1208 # The default value is: YES.
1210 ALPHABETICAL_INDEX = NO
1212 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
1213 # which the alphabetical index list will be split.
1214 # Minimum value: 1, maximum value: 20, default value: 5.
1215 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1217 COLS_IN_ALPHA_INDEX = 5
1219 # In case all classes in a project start with a common prefix, all classes will
1220 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1221 # can be used to specify a prefix (or a list of prefixes) that should be ignored
1222 # while generating the index headers.
1223 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1227 #---------------------------------------------------------------------------
1228 # Configuration options related to the HTML output
1229 #---------------------------------------------------------------------------
1231 # If the GENERATE_HTML tag is set to YES doxygen will generate HTML output
1232 # The default value is: YES.
1236 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1237 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1239 # The default directory is: html.
1240 # This tag requires that the tag GENERATE_HTML is set to YES.
1244 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1245 # generated HTML page (for example: .htm, .php, .asp).
1246 # The default value is: .html.
1247 # This tag requires that the tag GENERATE_HTML is set to YES.
1249 HTML_FILE_EXTENSION = .html
1251 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1252 # each generated HTML page. If the tag is left blank doxygen will generate a
1255 # To get valid HTML the header file that includes any scripts and style sheets
1256 # that doxygen needs, which is dependent on the configuration options used (e.g.
1257 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1258 # default header using
1259 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1261 # and then modify the file new_header.html. See also section "Doxygen usage"
1262 # for information on how to generate the default header that doxygen normally
1264 # Note: The header is subject to change so you typically have to regenerate the
1265 # default header when upgrading to a newer version of doxygen. For a description
1266 # of the possible markers and block names see the documentation.
1267 # This tag requires that the tag GENERATE_HTML is set to YES.
1271 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1272 # generated HTML page. If the tag is left blank doxygen will generate a standard
1273 # footer. See HTML_HEADER for more information on how to generate a default
1274 # footer and what special commands can be used inside the footer. See also
1275 # section "Doxygen usage" for information on how to generate the default footer
1276 # that doxygen normally uses.
1277 # This tag requires that the tag GENERATE_HTML is set to YES.
1281 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1282 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1283 # the HTML output. If left blank doxygen will generate a default style sheet.
1284 # See also section "Doxygen usage" for information on how to generate the style
1285 # sheet that doxygen normally uses.
1286 # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
1287 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1289 # This tag requires that the tag GENERATE_HTML is set to YES.
1293 # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
1294 # defined cascading style sheet that is included after the standard style sheets
1295 # created by doxygen. Using this option one can overrule certain style aspects.
1296 # This is preferred over using HTML_STYLESHEET since it does not replace the
1297 # standard style sheet and is therefor more robust against future updates.
1298 # Doxygen will copy the style sheet file to the output directory. For an example
1299 # see the documentation.
1300 # This tag requires that the tag GENERATE_HTML is set to YES.
1302 HTML_EXTRA_STYLESHEET = dali_doxygen.css
1304 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1305 # other source files which should be copied to the HTML output directory. Note
1306 # that these files will be copied to the base HTML output directory. Use the
1307 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1308 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1309 # files will be copied as-is; there are no commands or markers available.
1310 # This tag requires that the tag GENERATE_HTML is set to YES.
1314 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1315 # will adjust the colors in the stylesheet and background images according to
1316 # this color. Hue is specified as an angle on a colorwheel, see
1317 # http://en.wikipedia.org/wiki/Hue for more information. For instance the value
1318 # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
1319 # purple, and 360 is red again.
1320 # Minimum value: 0, maximum value: 359, default value: 220.
1321 # This tag requires that the tag GENERATE_HTML is set to YES.
1323 HTML_COLORSTYLE_HUE = 220
1325 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
1326 # in the HTML output. For a value of 0 the output will use grayscales only. A
1327 # value of 255 will produce the most vivid colors.
1328 # Minimum value: 0, maximum value: 255, default value: 100.
1329 # This tag requires that the tag GENERATE_HTML is set to YES.
1331 HTML_COLORSTYLE_SAT = 100
1333 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
1334 # luminance component of the colors in the HTML output. Values below 100
1335 # gradually make the output lighter, whereas values above 100 make the output
1336 # darker. The value divided by 100 is the actual gamma applied, so 80 represents
1337 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1339 # Minimum value: 40, maximum value: 240, default value: 80.
1340 # This tag requires that the tag GENERATE_HTML is set to YES.
1342 HTML_COLORSTYLE_GAMMA = 80
1344 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
1345 # page will contain the date and time when the page was generated. Setting this
1346 # to NO can help when comparing the output of multiple runs.
1347 # The default value is: YES.
1348 # This tag requires that the tag GENERATE_HTML is set to YES.
1350 HTML_TIMESTAMP = YES
1352 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1353 # documentation will contain sections that can be hidden and shown after the
1355 # The default value is: NO.
1356 # This tag requires that the tag GENERATE_HTML is set to YES.
1358 HTML_DYNAMIC_SECTIONS = NO
1360 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
1361 # shown in the various tree structured indices initially; the user can expand
1362 # and collapse entries dynamically later on. Doxygen will expand the tree to
1363 # such a level that at most the specified number of entries are visible (unless
1364 # a fully collapsed tree already exceeds this amount). So setting the number of
1365 # entries 1 will produce a full collapsed tree by default. 0 is a special value
1366 # representing an infinite number of entries and will result in a full expanded
1368 # Minimum value: 0, maximum value: 9999, default value: 100.
1369 # This tag requires that the tag GENERATE_HTML is set to YES.
1371 HTML_INDEX_NUM_ENTRIES = 100
1373 # If the GENERATE_DOCSET tag is set to YES, additional index files will be
1374 # generated that can be used as input for Apple's Xcode 3 integrated development
1375 # environment (see: http://developer.apple.com/tools/xcode/), introduced with
1376 # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1377 # Makefile in the HTML output directory. Running make will produce the docset in
1378 # that directory and running make install will install the docset in
1379 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1380 # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
1381 # for more information.
1382 # The default value is: NO.
1383 # This tag requires that the tag GENERATE_HTML is set to YES.
1385 GENERATE_DOCSET = NO
1387 # This tag determines the name of the docset feed. A documentation feed provides
1388 # an umbrella under which multiple documentation sets from a single provider
1389 # (such as a company or product suite) can be grouped.
1390 # The default value is: Doxygen generated docs.
1391 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1393 DOCSET_FEEDNAME = "Doxygen generated docs"
1395 # This tag specifies a string that should uniquely identify the documentation
1396 # set bundle. This should be a reverse domain-name style string, e.g.
1397 # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
1398 # The default value is: org.doxygen.Project.
1399 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1401 DOCSET_BUNDLE_ID = org.doxygen.Project
1403 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1404 # the documentation publisher. This should be a reverse domain-name style
1405 # string, e.g. com.mycompany.MyDocSet.documentation.
1406 # The default value is: org.doxygen.Publisher.
1407 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1409 DOCSET_PUBLISHER_ID = org.doxygen.Publisher
1411 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1412 # The default value is: Publisher.
1413 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1415 DOCSET_PUBLISHER_NAME = Publisher
1417 # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1418 # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1419 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1420 # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1423 # The HTML Help Workshop contains a compiler that can convert all HTML output
1424 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1425 # files are now used as the Windows 98 help format, and will replace the old
1426 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1427 # HTML files also contain an index, a table of contents, and you can search for
1428 # words in the documentation. The HTML workshop also contains a viewer for
1429 # compressed HTML files.
1430 # The default value is: NO.
1431 # This tag requires that the tag GENERATE_HTML is set to YES.
1433 GENERATE_HTMLHELP = YES
1435 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1436 # file. You can add a path in front of the file if the result should not be
1437 # written to the html output directory.
1438 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1442 # The HHC_LOCATION tag can be used to specify the location (absolute path
1443 # including file name) of the HTML help compiler ( hhc.exe). If non-empty
1444 # doxygen will try to run the HTML help compiler on the generated index.hhp.
1445 # The file has to be specified with full path.
1446 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1450 # The GENERATE_CHI flag controls if a separate .chi index file is generated (
1451 # YES) or that it should be included in the master .chm file ( NO).
1452 # The default value is: NO.
1453 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1457 # The CHM_INDEX_ENCODING is used to encode HtmlHelp index ( hhk), content ( hhc)
1458 # and project file content.
1459 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1461 CHM_INDEX_ENCODING =
1463 # The BINARY_TOC flag controls whether a binary table of contents is generated (
1464 # YES) or a normal table of contents ( NO) in the .chm file.
1465 # The default value is: NO.
1466 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1470 # The TOC_EXPAND flag can be set to YES to add extra items for group members to
1471 # the table of contents of the HTML help documentation and to the tree view.
1472 # The default value is: NO.
1473 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1477 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1478 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1479 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1480 # (.qch) of the generated HTML documentation.
1481 # The default value is: NO.
1482 # This tag requires that the tag GENERATE_HTML is set to YES.
1486 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
1487 # the file name of the resulting .qch file. The path specified is relative to
1488 # the HTML output folder.
1489 # This tag requires that the tag GENERATE_QHP is set to YES.
1491 QCH_FILE = "Dali.qch"
1493 # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1494 # Project output. For more information please see Qt Help Project / Namespace
1495 # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1496 # The default value is: org.doxygen.Project.
1497 # This tag requires that the tag GENERATE_QHP is set to YES.
1499 QHP_NAMESPACE = "Dali"
1501 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
1502 # Help Project output. For more information please see Qt Help Project / Virtual
1503 # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1505 # The default value is: doc.
1506 # This tag requires that the tag GENERATE_QHP is set to YES.
1508 QHP_VIRTUAL_FOLDER = Dali
1510 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1511 # filter to add. For more information please see Qt Help Project / Custom
1512 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1514 # This tag requires that the tag GENERATE_QHP is set to YES.
1516 QHP_CUST_FILTER_NAME =
1518 # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1519 # custom filter to add. For more information please see Qt Help Project / Custom
1520 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1522 # This tag requires that the tag GENERATE_QHP is set to YES.
1524 QHP_CUST_FILTER_ATTRS =
1526 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1527 # project's filter section matches. Qt Help Project / Filter Attributes (see:
1528 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1529 # This tag requires that the tag GENERATE_QHP is set to YES.
1531 QHP_SECT_FILTER_ATTRS =
1533 # The QHG_LOCATION tag can be used to specify the location of Qt's
1534 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1535 # generated .qhp file.
1536 # This tag requires that the tag GENERATE_QHP is set to YES.
1538 # Setting this works, but leaving empty to match public doxygen config.
1541 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1542 # generated, together with the HTML files, they form an Eclipse help plugin. To
1543 # install this plugin and make it available under the help contents menu in
1544 # Eclipse, the contents of the directory containing the HTML and XML files needs
1545 # to be copied into the plugins directory of eclipse. The name of the directory
1546 # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
1547 # After copying Eclipse needs to be restarted before the help appears.
1548 # The default value is: NO.
1549 # This tag requires that the tag GENERATE_HTML is set to YES.
1551 GENERATE_ECLIPSEHELP = NO
1553 # A unique identifier for the Eclipse help plugin. When installing the plugin
1554 # the directory name containing the HTML and XML files should also have this
1555 # name. Each documentation set should have its own identifier.
1556 # The default value is: org.doxygen.Project.
1557 # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
1559 ECLIPSE_DOC_ID = org.doxygen.Project
1561 # If you want full control over the layout of the generated HTML pages it might
1562 # be necessary to disable the index and replace it with your own. The
1563 # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
1564 # of each HTML page. A value of NO enables the index and the value YES disables
1565 # it. Since the tabs in the index contain the same information as the navigation
1566 # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
1567 # The default value is: NO.
1568 # This tag requires that the tag GENERATE_HTML is set to YES.
1572 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1573 # structure should be generated to display hierarchical information. If the tag
1574 # value is set to YES, a side panel will be generated containing a tree-like
1575 # index structure (just like the one that is generated for HTML Help). For this
1576 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
1577 # (i.e. any modern browser). Windows users are probably better off using the
1578 # HTML help feature. Via custom stylesheets (see HTML_EXTRA_STYLESHEET) one can
1579 # further fine-tune the look of the index. As an example, the default style
1580 # sheet generated by doxygen has an example that shows how to put an image at
1581 # the root of the tree instead of the PROJECT_NAME. Since the tree basically has
1582 # the same information as the tab index, you could consider setting
1583 # DISABLE_INDEX to YES when enabling this option.
1584 # The default value is: NO.
1585 # This tag requires that the tag GENERATE_HTML is set to YES.
1587 GENERATE_TREEVIEW = NONE
1589 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
1590 # doxygen will group on one line in the generated HTML documentation.
1592 # Note that a value of 0 will completely suppress the enum values from appearing
1593 # in the overview section.
1594 # Minimum value: 0, maximum value: 20, default value: 4.
1595 # This tag requires that the tag GENERATE_HTML is set to YES.
1597 ENUM_VALUES_PER_LINE = 4
1599 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
1600 # to set the initial width (in pixels) of the frame in which the tree is shown.
1601 # Minimum value: 0, maximum value: 1500, default value: 250.
1602 # This tag requires that the tag GENERATE_HTML is set to YES.
1604 TREEVIEW_WIDTH = 250
1606 # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open links to
1607 # external symbols imported via tag files in a separate window.
1608 # The default value is: NO.
1609 # This tag requires that the tag GENERATE_HTML is set to YES.
1611 EXT_LINKS_IN_WINDOW = NO
1613 # Use this tag to change the font size of LaTeX formulas included as images in
1614 # the HTML documentation. When you change the font size after a successful
1615 # doxygen run you need to manually remove any form_*.png images from the HTML
1616 # output directory to force them to be regenerated.
1617 # Minimum value: 8, maximum value: 50, default value: 10.
1618 # This tag requires that the tag GENERATE_HTML is set to YES.
1620 FORMULA_FONTSIZE = 10
1622 # Use the FORMULA_TRANPARENT tag to determine whether or not the images
1623 # generated for formulas are transparent PNGs. Transparent PNGs are not
1624 # supported properly for IE 6.0, but are supported on all modern browsers.
1626 # Note that when changing this option you need to delete any form_*.png files in
1627 # the HTML output directory before the changes have effect.
1628 # The default value is: YES.
1629 # This tag requires that the tag GENERATE_HTML is set to YES.
1631 FORMULA_TRANSPARENT = YES
1633 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1634 # http://www.mathjax.org) which uses client side Javascript for the rendering
1635 # instead of using prerendered bitmaps. Use this if you do not have LaTeX
1636 # installed or if you want to formulas look prettier in the HTML output. When
1637 # enabled you may also need to install MathJax separately and configure the path
1638 # to it using the MATHJAX_RELPATH option.
1639 # The default value is: NO.
1640 # This tag requires that the tag GENERATE_HTML is set to YES.
1644 # When MathJax is enabled you can set the default output format to be used for
1645 # the MathJax output. See the MathJax site (see:
1646 # http://docs.mathjax.org/en/latest/output.html) for more details.
1647 # Possible values are: HTML-CSS (which is slower, but has the best
1648 # compatibility), NativeMML (i.e. MathML) and SVG.
1649 # The default value is: HTML-CSS.
1650 # This tag requires that the tag USE_MATHJAX is set to YES.
1652 MATHJAX_FORMAT = HTML-CSS
1654 # When MathJax is enabled you need to specify the location relative to the HTML
1655 # output directory using the MATHJAX_RELPATH option. The destination directory
1656 # should contain the MathJax.js script. For instance, if the mathjax directory
1657 # is located at the same level as the HTML output directory, then
1658 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1659 # Content Delivery Network so you can quickly see the result without installing
1660 # MathJax. However, it is strongly recommended to install a local copy of
1661 # MathJax from http://www.mathjax.org before deployment.
1662 # The default value is: http://cdn.mathjax.org/mathjax/latest.
1663 # This tag requires that the tag USE_MATHJAX is set to YES.
1665 MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest
1667 # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
1668 # extension names that should be enabled during MathJax rendering. For example
1669 # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
1670 # This tag requires that the tag USE_MATHJAX is set to YES.
1672 MATHJAX_EXTENSIONS =
1674 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1675 # of code that will be used on startup of the MathJax code. See the MathJax site
1676 # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
1677 # example see the documentation.
1678 # This tag requires that the tag USE_MATHJAX is set to YES.
1682 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1683 # the HTML output. The underlying search engine uses javascript and DHTML and
1684 # should work on any modern browser. Note that when using HTML help
1685 # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
1686 # there is already a search function so this one should typically be disabled.
1687 # For large projects the javascript based search engine can be slow, then
1688 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1689 # search using the keyboard; to jump to the search box use <access key> + S
1690 # (what the <access key> is depends on the OS and browser, but it is typically
1691 # <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
1692 # key> to jump into the search results window, the results can be navigated
1693 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1694 # the search. The filter options can be selected when the cursor is inside the
1695 # search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
1696 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1698 # The default value is: YES.
1699 # This tag requires that the tag GENERATE_HTML is set to YES.
1703 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1704 # implemented using a web server instead of a web client using Javascript. There
1705 # are two flavours of web server based searching depending on the
1706 # EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for
1707 # searching and an index file used by the script. When EXTERNAL_SEARCH is
1708 # enabled the indexing and searching needs to be provided by external tools. See
1709 # the section "External Indexing and Searching" for details.
1710 # The default value is: NO.
1711 # This tag requires that the tag SEARCHENGINE is set to YES.
1713 SERVER_BASED_SEARCH = NO
1715 # When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
1716 # script for searching. Instead the search results are written to an XML file
1717 # which needs to be processed by an external indexer. Doxygen will invoke an
1718 # external search engine pointed to by the SEARCHENGINE_URL option to obtain the
1721 # Doxygen ships with an example indexer ( doxyindexer) and search engine
1722 # (doxysearch.cgi) which are based on the open source search engine library
1723 # Xapian (see: http://xapian.org/).
1725 # See the section "External Indexing and Searching" for details.
1726 # The default value is: NO.
1727 # This tag requires that the tag SEARCHENGINE is set to YES.
1729 EXTERNAL_SEARCH = NO
1731 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
1732 # which will return the search results when EXTERNAL_SEARCH is enabled.
1734 # Doxygen ships with an example indexer ( doxyindexer) and search engine
1735 # (doxysearch.cgi) which are based on the open source search engine library
1736 # Xapian (see: http://xapian.org/). See the section "External Indexing and
1737 # Searching" for details.
1738 # This tag requires that the tag SEARCHENGINE is set to YES.
1742 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
1743 # search data is written to a file for indexing by an external tool. With the
1744 # SEARCHDATA_FILE tag the name of this file can be specified.
1745 # The default file is: searchdata.xml.
1746 # This tag requires that the tag SEARCHENGINE is set to YES.
1748 SEARCHDATA_FILE = searchdata.xml
1750 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
1751 # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
1752 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1753 # projects and redirect the results back to the right project.
1754 # This tag requires that the tag SEARCHENGINE is set to YES.
1756 EXTERNAL_SEARCH_ID =
1758 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1759 # projects other than the one defined by this configuration file, but that are
1760 # all added to the same external search index. Each project needs to have a
1761 # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
1762 # to a relative location where the documentation can be found. The format is:
1763 # EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
1764 # This tag requires that the tag SEARCHENGINE is set to YES.
1766 EXTRA_SEARCH_MAPPINGS =
1768 #---------------------------------------------------------------------------
1769 # Configuration options related to the LaTeX output
1770 #---------------------------------------------------------------------------
1772 # If the GENERATE_LATEX tag is set to YES doxygen will generate LaTeX output.
1773 # The default value is: YES.
1777 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1778 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1780 # The default directory is: latex.
1781 # This tag requires that the tag GENERATE_LATEX is set to YES.
1783 LATEX_OUTPUT = latex
1785 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1788 # Note that when enabling USE_PDFLATEX this option is only used for generating
1789 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1790 # written to the output directory.
1791 # The default file is: latex.
1792 # This tag requires that the tag GENERATE_LATEX is set to YES.
1794 LATEX_CMD_NAME = latex
1796 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
1798 # The default file is: makeindex.
1799 # This tag requires that the tag GENERATE_LATEX is set to YES.
1801 MAKEINDEX_CMD_NAME = makeindex
1803 # If the COMPACT_LATEX tag is set to YES doxygen generates more compact LaTeX
1804 # documents. This may be useful for small projects and may help to save some
1806 # The default value is: NO.
1807 # This tag requires that the tag GENERATE_LATEX is set to YES.
1811 # The PAPER_TYPE tag can be used to set the paper type that is used by the
1813 # Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
1814 # 14 inches) and executive (7.25 x 10.5 inches).
1815 # The default value is: a4.
1816 # This tag requires that the tag GENERATE_LATEX is set to YES.
1820 # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
1821 # that should be included in the LaTeX output. To get the times font for
1822 # instance you can specify
1823 # EXTRA_PACKAGES=times
1824 # If left blank no extra packages will be included.
1825 # This tag requires that the tag GENERATE_LATEX is set to YES.
1829 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1830 # generated LaTeX document. The header should contain everything until the first
1831 # chapter. If it is left blank doxygen will generate a standard header. See
1832 # section "Doxygen usage" for information on how to let doxygen write the
1833 # default header to a separate file.
1835 # Note: Only use a user-defined header if you know what you are doing! The
1836 # following commands have a special meaning inside the header: $title,
1837 # $datetime, $date, $doxygenversion, $projectname, $projectnumber. Doxygen will
1838 # replace them by respectively the title of the page, the current date and time,
1839 # only the current date, the version number of doxygen, the project name (see
1840 # PROJECT_NAME), or the project number (see PROJECT_NUMBER).
1841 # This tag requires that the tag GENERATE_LATEX is set to YES.
1845 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1846 # generated LaTeX document. The footer should contain everything after the last
1847 # chapter. If it is left blank doxygen will generate a standard footer.
1849 # Note: Only use a user-defined footer if you know what you are doing!
1850 # This tag requires that the tag GENERATE_LATEX is set to YES.
1854 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1855 # other source files which should be copied to the LATEX_OUTPUT output
1856 # directory. Note that the files will be copied as-is; there are no commands or
1857 # markers available.
1858 # This tag requires that the tag GENERATE_LATEX is set to YES.
1862 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
1863 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
1864 # contain links (just like the HTML output) instead of page references. This
1865 # makes the output suitable for online browsing using a PDF viewer.
1866 # The default value is: YES.
1867 # This tag requires that the tag GENERATE_LATEX is set to YES.
1869 PDF_HYPERLINKS = YES
1871 # If the LATEX_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
1872 # the PDF file directly from the LaTeX files. Set this option to YES to get a
1873 # higher quality PDF documentation.
1874 # The default value is: YES.
1875 # This tag requires that the tag GENERATE_LATEX is set to YES.
1879 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
1880 # command to the generated LaTeX files. This will instruct LaTeX to keep running
1881 # if errors occur, instead of asking the user for help. This option is also used
1882 # when generating formulas in HTML.
1883 # The default value is: NO.
1884 # This tag requires that the tag GENERATE_LATEX is set to YES.
1886 LATEX_BATCHMODE = NO
1888 # If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
1889 # index chapters (such as File Index, Compound Index, etc.) in the output.
1890 # The default value is: NO.
1891 # This tag requires that the tag GENERATE_LATEX is set to YES.
1893 LATEX_HIDE_INDICES = NO
1895 # If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
1896 # code with syntax highlighting in the LaTeX output.
1898 # Note that which sources are shown also depends on other settings such as
1900 # The default value is: NO.
1901 # This tag requires that the tag GENERATE_LATEX is set to YES.
1903 LATEX_SOURCE_CODE = NO
1905 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1906 # bibliography, e.g. plainnat, or ieeetr. See
1907 # http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
1908 # The default value is: plain.
1909 # This tag requires that the tag GENERATE_LATEX is set to YES.
1911 LATEX_BIB_STYLE = plain
1913 #---------------------------------------------------------------------------
1914 # Configuration options related to the RTF output
1915 #---------------------------------------------------------------------------
1917 # If the GENERATE_RTF tag is set to YES doxygen will generate RTF output. The
1918 # RTF output is optimized for Word 97 and may not look too pretty with other RTF
1920 # The default value is: NO.
1924 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
1925 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1927 # The default directory is: rtf.
1928 # This tag requires that the tag GENERATE_RTF is set to YES.
1932 # If the COMPACT_RTF tag is set to YES doxygen generates more compact RTF
1933 # documents. This may be useful for small projects and may help to save some
1935 # The default value is: NO.
1936 # This tag requires that the tag GENERATE_RTF is set to YES.
1940 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
1941 # contain hyperlink fields. The RTF file will contain links (just like the HTML
1942 # output) instead of page references. This makes the output suitable for online
1943 # browsing using Word or some other Word compatible readers that support those
1946 # Note: WordPad (write) and others do not support links.
1947 # The default value is: NO.
1948 # This tag requires that the tag GENERATE_RTF is set to YES.
1952 # Load stylesheet definitions from file. Syntax is similar to doxygen's config
1953 # file, i.e. a series of assignments. You only have to provide replacements,
1954 # missing definitions are set to their default value.
1956 # See also section "Doxygen usage" for information on how to generate the
1957 # default style sheet that doxygen normally uses.
1958 # This tag requires that the tag GENERATE_RTF is set to YES.
1960 RTF_STYLESHEET_FILE =
1962 # Set optional variables used in the generation of an RTF document. Syntax is
1963 # similar to doxygen's config file. A template extensions file can be generated
1964 # using doxygen -e rtf extensionFile.
1965 # This tag requires that the tag GENERATE_RTF is set to YES.
1967 RTF_EXTENSIONS_FILE =
1969 #---------------------------------------------------------------------------
1970 # Configuration options related to the man page output
1971 #---------------------------------------------------------------------------
1973 # If the GENERATE_MAN tag is set to YES doxygen will generate man pages for
1974 # classes and files.
1975 # The default value is: NO.
1979 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
1980 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1981 # it. A directory man3 will be created inside the directory specified by
1983 # The default directory is: man.
1984 # This tag requires that the tag GENERATE_MAN is set to YES.
1988 # The MAN_EXTENSION tag determines the extension that is added to the generated
1989 # man pages. In case the manual section does not start with a number, the number
1990 # 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
1992 # The default value is: .3.
1993 # This tag requires that the tag GENERATE_MAN is set to YES.
1997 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
1998 # will generate one additional man file for each entity documented in the real
1999 # man page(s). These additional files only source the real man page, but without
2000 # them the man command would be unable to find the correct page.
2001 # The default value is: NO.
2002 # This tag requires that the tag GENERATE_MAN is set to YES.
2006 #---------------------------------------------------------------------------
2007 # Configuration options related to the XML output
2008 #---------------------------------------------------------------------------
2010 # If the GENERATE_XML tag is set to YES doxygen will generate an XML file that
2011 # captures the structure of the code including all documentation.
2012 # The default value is: NO.
2016 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
2017 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2019 # The default directory is: xml.
2020 # This tag requires that the tag GENERATE_XML is set to YES.
2024 # The XML_SCHEMA tag can be used to specify a XML schema, which can be used by a
2025 # validating XML parser to check the syntax of the XML files.
2026 # This tag requires that the tag GENERATE_XML is set to YES.
2030 # The XML_DTD tag can be used to specify a XML DTD, which can be used by a
2031 # validating XML parser to check the syntax of the XML files.
2032 # This tag requires that the tag GENERATE_XML is set to YES.
2036 # If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program
2037 # listings (including syntax highlighting and cross-referencing information) to
2038 # the XML output. Note that enabling this will significantly increase the size
2039 # of the XML output.
2040 # The default value is: YES.
2041 # This tag requires that the tag GENERATE_XML is set to YES.
2043 XML_PROGRAMLISTING = YES
2045 #---------------------------------------------------------------------------
2046 # Configuration options related to the DOCBOOK output
2047 #---------------------------------------------------------------------------
2049 # If the GENERATE_DOCBOOK tag is set to YES doxygen will generate Docbook files
2050 # that can be used to generate PDF.
2051 # The default value is: NO.
2053 GENERATE_DOCBOOK = NO
2055 # The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
2056 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
2058 # The default directory is: docbook.
2059 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
2061 DOCBOOK_OUTPUT = docbook
2063 #---------------------------------------------------------------------------
2064 # Configuration options for the AutoGen Definitions output
2065 #---------------------------------------------------------------------------
2067 # If the GENERATE_AUTOGEN_DEF tag is set to YES doxygen will generate an AutoGen
2068 # Definitions (see http://autogen.sf.net) file that captures the structure of
2069 # the code including all documentation. Note that this feature is still
2070 # experimental and incomplete at the moment.
2071 # The default value is: NO.
2073 GENERATE_AUTOGEN_DEF = NO
2075 #---------------------------------------------------------------------------
2076 # Configuration options related to the Perl module output
2077 #---------------------------------------------------------------------------
2079 # If the GENERATE_PERLMOD tag is set to YES doxygen will generate a Perl module
2080 # file that captures the structure of the code including all documentation.
2082 # Note that this feature is still experimental and incomplete at the moment.
2083 # The default value is: NO.
2085 GENERATE_PERLMOD = NO
2087 # If the PERLMOD_LATEX tag is set to YES doxygen will generate the necessary
2088 # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
2089 # output from the Perl module output.
2090 # The default value is: NO.
2091 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2095 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be nicely
2096 # formatted so it can be parsed by a human reader. This is useful if you want to
2097 # understand what is going on. On the other hand, if this tag is set to NO the
2098 # size of the Perl module output will be much smaller and Perl will parse it
2100 # The default value is: YES.
2101 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2103 PERLMOD_PRETTY = YES
2105 # The names of the make variables in the generated doxyrules.make file are
2106 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
2107 # so different doxyrules.make files included by the same Makefile don't
2108 # overwrite each other's variables.
2109 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2111 PERLMOD_MAKEVAR_PREFIX =
2113 #---------------------------------------------------------------------------
2114 # Configuration options related to the preprocessor
2115 #---------------------------------------------------------------------------
2117 # If the ENABLE_PREPROCESSING tag is set to YES doxygen will evaluate all
2118 # C-preprocessor directives found in the sources and include files.
2119 # The default value is: YES.
2121 ENABLE_PREPROCESSING = YES
2123 # If the MACRO_EXPANSION tag is set to YES doxygen will expand all macro names
2124 # in the source code. If set to NO only conditional compilation will be
2125 # performed. Macro expansion can be done in a controlled way by setting
2126 # EXPAND_ONLY_PREDEF to YES.
2127 # The default value is: NO.
2128 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2130 MACRO_EXPANSION = YES
2132 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
2133 # the macro expansion is limited to the macros specified with the PREDEFINED and
2134 # EXPAND_AS_DEFINED tags.
2135 # The default value is: NO.
2136 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2138 EXPAND_ONLY_PREDEF = YES
2140 # If the SEARCH_INCLUDES tag is set to YES the includes files in the
2141 # INCLUDE_PATH will be searched if a #include is found.
2142 # The default value is: YES.
2143 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2145 SEARCH_INCLUDES = YES
2147 # The INCLUDE_PATH tag can be used to specify one or more directories that
2148 # contain include files that are not input files but should be processed by the
2150 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
2152 INCLUDE_PATH = ../../../../dali/dali \
2153 ../../../../dali-adaptor/adaptors \
2154 ../../../../dali-adaptor/plugins \
2155 ../../../../dali-adaptor/platform-abstractions \
2156 ../../../texture-atlas-exporter/dali-exporter \
2157 ../../../dali-toolkit
2159 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
2160 # patterns (like *.h and *.hpp) to filter out the header-files in the
2161 # directories. If left blank, the patterns specified with FILE_PATTERNS will be
2163 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2165 INCLUDE_FILE_PATTERNS =
2167 # The PREDEFINED tag can be used to specify one or more macro names that are
2168 # defined before the preprocessor is started (similar to the -D option of e.g.
2169 # gcc). The argument of the tag is a list of macros of the form: name or
2170 # name=definition (no spaces). If the definition and the "=" are omitted, "=1"
2171 # is assumed. To prevent a macro definition from being undefined via #undef or
2172 # recursively expanded use the := operator instead of the = operator.
2173 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2175 PREDEFINED = DALI_IMPORT_API \
2184 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
2185 # tag can be used to specify a list of macro names that should be expanded. The
2186 # macro definition that is found in the sources will be used. Use the PREDEFINED
2187 # tag if you want to use a different macro definition that overrules the
2188 # definition found in the source code.
2189 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2193 # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
2194 # remove all refrences to function-like macros that are alone on a line, have an
2195 # all uppercase name, and do not end with a semicolon. Such function macros are
2196 # typically used for boiler-plate code, and will confuse the parser if not
2198 # The default value is: YES.
2199 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2201 SKIP_FUNCTION_MACROS = YES
2203 #---------------------------------------------------------------------------
2204 # Configuration options related to external references
2205 #---------------------------------------------------------------------------
2207 # The TAGFILES tag can be used to specify one or more tag files. For each tag
2208 # file the location of the external documentation should be added. The format of
2209 # a tag file without this location is as follows:
2210 # TAGFILES = file1 file2 ...
2211 # Adding location for the tag files is done as follows:
2212 # TAGFILES = file1=loc1 "file2 = loc2" ...
2213 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
2214 # section "Linking to external documentation" for more information about the use
2216 # Note: Each tag file must have an unique name (where the name does NOT include
2217 # the path). If a tag file is not located in the directory in which doxygen is
2218 # run, you must also specify the path to the tagfile here.
2222 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2223 # tag file that is based on the input files it reads. See section "Linking to
2224 # external documentation" for more information about the usage of tag files.
2228 # If the ALLEXTERNALS tag is set to YES all external class will be listed in the
2229 # class index. If set to NO only the inherited external classes will be listed.
2230 # The default value is: NO.
2234 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed in
2235 # the modules index. If set to NO, only the current project's groups will be
2237 # The default value is: YES.
2239 EXTERNAL_GROUPS = YES
2241 # If the EXTERNAL_PAGES tag is set to YES all external pages will be listed in
2242 # the related pages index. If set to NO, only the current project's pages will
2244 # The default value is: YES.
2246 EXTERNAL_PAGES = YES
2248 # The PERL_PATH should be the absolute path and name of the perl script
2249 # interpreter (i.e. the result of 'which perl').
2250 # The default file (with absolute path) is: /usr/bin/perl.
2252 PERL_PATH = /usr/bin/perl
2254 #---------------------------------------------------------------------------
2255 # Configuration options related to the dot tool
2256 #---------------------------------------------------------------------------
2258 # If the CLASS_DIAGRAMS tag is set to YES doxygen will generate a class diagram
2259 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2260 # NO turns the diagrams off. Note that this option also works with HAVE_DOT
2261 # disabled, but it is recommended to install and use dot, since it yields more
2263 # The default value is: YES.
2265 CLASS_DIAGRAMS = YES
2267 # You can define message sequence charts within doxygen comments using the \msc
2268 # command. Doxygen will then run the mscgen tool (see:
2269 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2270 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
2271 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2272 # default search path.
2276 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2277 # then run dia to produce the diagram and insert it in the documentation. The
2278 # DIA_PATH tag allows you to specify the directory where the dia binary resides.
2279 # If left empty dia is assumed to be found in the default search path.
2283 # If set to YES, the inheritance and collaboration graphs will hide inheritance
2284 # and usage relations if the target is undocumented or is not a class.
2285 # The default value is: YES.
2287 HIDE_UNDOC_RELATIONS = YES
2289 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
2290 # available from the path. This tool is part of Graphviz (see:
2291 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2292 # Bell Labs. The other options in this section have no effect if this option is
2294 # The default value is: NO.
2298 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
2299 # to run in parallel. When set to 0 doxygen will base this on the number of
2300 # processors available in the system. You can set it explicitly to a value
2301 # larger than 0 to get control over the balance between CPU load and processing
2303 # Minimum value: 0, maximum value: 32, default value: 0.
2304 # This tag requires that the tag HAVE_DOT is set to YES.
2308 # When you want a differently looking font n the dot files that doxygen
2309 # generates you can specify the font name using DOT_FONTNAME. You need to make
2310 # sure dot is able to find the font, which can be done by putting it in a
2311 # standard location or by setting the DOTFONTPATH environment variable or by
2312 # setting DOT_FONTPATH to the directory containing the font.
2313 # The default value is: Helvetica.
2314 # This tag requires that the tag HAVE_DOT is set to YES.
2318 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2320 # Minimum value: 4, maximum value: 24, default value: 10.
2321 # This tag requires that the tag HAVE_DOT is set to YES.
2325 # By default doxygen will tell dot to use the default font as specified with
2326 # DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
2327 # the path where dot can find it using this tag.
2328 # This tag requires that the tag HAVE_DOT is set to YES.
2332 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2333 # each documented class showing the direct and indirect inheritance relations.
2334 # Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
2335 # The default value is: YES.
2336 # This tag requires that the tag HAVE_DOT is set to YES.
2340 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
2341 # graph for each documented class showing the direct and indirect implementation
2342 # dependencies (inheritance, containment, and class references variables) of the
2343 # class with other documented classes.
2344 # The default value is: YES.
2345 # This tag requires that the tag HAVE_DOT is set to YES.
2347 COLLABORATION_GRAPH = YES
2349 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2350 # groups, showing the direct groups dependencies.
2351 # The default value is: YES.
2352 # This tag requires that the tag HAVE_DOT is set to YES.
2356 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
2357 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2359 # The default value is: NO.
2360 # This tag requires that the tag HAVE_DOT is set to YES.
2364 # If the UML_LOOK tag is enabled, the fields and methods are shown inside the
2365 # class node. If there are many fields or methods and many nodes the graph may
2366 # become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
2367 # number of items for each type to make the size more manageable. Set this to 0
2368 # for no limit. Note that the threshold may be exceeded by 50% before the limit
2369 # is enforced. So when you set the threshold to 10, up to 15 fields may appear,
2370 # but if the number exceeds 15, the total amount of fields shown is limited to
2372 # Minimum value: 0, maximum value: 100, default value: 10.
2373 # This tag requires that the tag HAVE_DOT is set to YES.
2375 UML_LIMIT_NUM_FIELDS = 10
2377 # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
2378 # collaboration graphs will show the relations between templates and their
2380 # The default value is: NO.
2381 # This tag requires that the tag HAVE_DOT is set to YES.
2383 TEMPLATE_RELATIONS = NO
2385 # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
2386 # YES then doxygen will generate a graph for each documented file showing the
2387 # direct and indirect include dependencies of the file with other documented
2389 # The default value is: YES.
2390 # This tag requires that the tag HAVE_DOT is set to YES.
2394 # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
2395 # set to YES then doxygen will generate a graph for each documented file showing
2396 # the direct and indirect include dependencies of the file with other documented
2398 # The default value is: YES.
2399 # This tag requires that the tag HAVE_DOT is set to YES.
2401 INCLUDED_BY_GRAPH = YES
2403 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
2404 # dependency graph for every global function or class method.
2406 # Note that enabling this option will significantly increase the time of a run.
2407 # So in most cases it will be better to enable call graphs for selected
2408 # functions only using the \callgraph command.
2409 # The default value is: NO.
2410 # This tag requires that the tag HAVE_DOT is set to YES.
2414 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
2415 # dependency graph for every global function or class method.
2417 # Note that enabling this option will significantly increase the time of a run.
2418 # So in most cases it will be better to enable caller graphs for selected
2419 # functions only using the \callergraph command.
2420 # The default value is: NO.
2421 # This tag requires that the tag HAVE_DOT is set to YES.
2425 # If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
2426 # hierarchy of all classes instead of a textual one.
2427 # The default value is: YES.
2428 # This tag requires that the tag HAVE_DOT is set to YES.
2430 GRAPHICAL_HIERARCHY = YES
2432 # If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
2433 # dependencies a directory has on other directories in a graphical way. The
2434 # dependency relations are determined by the #include relations between the
2435 # files in the directories.
2436 # The default value is: YES.
2437 # This tag requires that the tag HAVE_DOT is set to YES.
2439 DIRECTORY_GRAPH = YES
2441 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
2443 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2444 # to make the SVG files visible in IE 9+ (other browsers do not have this
2446 # Possible values are: png, jpg, gif and svg.
2447 # The default value is: png.
2448 # This tag requires that the tag HAVE_DOT is set to YES.
2450 DOT_IMAGE_FORMAT = png
2452 # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
2453 # enable generation of interactive SVG images that allow zooming and panning.
2455 # Note that this requires a modern browser other than Internet Explorer. Tested
2456 # and working are Firefox, Chrome, Safari, and Opera.
2457 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2458 # the SVG files visible. Older versions of IE do not have SVG support.
2459 # The default value is: NO.
2460 # This tag requires that the tag HAVE_DOT is set to YES.
2462 INTERACTIVE_SVG = NO
2464 # The DOT_PATH tag can be used to specify the path where the dot tool can be
2465 # found. If left blank, it is assumed the dot tool can be found in the path.
2466 # This tag requires that the tag HAVE_DOT is set to YES.
2470 # The DOTFILE_DIRS tag can be used to specify one or more directories that
2471 # contain dot files that are included in the documentation (see the \dotfile
2473 # This tag requires that the tag HAVE_DOT is set to YES.
2477 # The MSCFILE_DIRS tag can be used to specify one or more directories that
2478 # contain msc files that are included in the documentation (see the \mscfile
2483 # The DIAFILE_DIRS tag can be used to specify one or more directories that
2484 # contain dia files that are included in the documentation (see the \diafile
2489 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2490 # that will be shown in the graph. If the number of nodes in a graph becomes
2491 # larger than this value, doxygen will truncate the graph, which is visualized
2492 # by representing a node as a red box. Note that doxygen if the number of direct
2493 # children of the root node in a graph is already larger than
2494 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
2495 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2496 # Minimum value: 0, maximum value: 10000, default value: 50.
2497 # This tag requires that the tag HAVE_DOT is set to YES.
2499 DOT_GRAPH_MAX_NODES = 50
2501 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
2502 # generated by dot. A depth value of 3 means that only nodes reachable from the
2503 # root by following a path via at most 3 edges will be shown. Nodes that lay
2504 # further from the root node will be omitted. Note that setting this option to 1
2505 # or 2 may greatly reduce the computation time needed for large code bases. Also
2506 # note that the size of a graph can be further restricted by
2507 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
2508 # Minimum value: 0, maximum value: 1000, default value: 0.
2509 # This tag requires that the tag HAVE_DOT is set to YES.
2511 MAX_DOT_GRAPH_DEPTH = 3
2513 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
2514 # background. This is disabled by default, because dot on Windows does not seem
2515 # to support this out of the box.
2517 # Warning: Depending on the platform used, enabling this option may lead to
2518 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2520 # The default value is: NO.
2521 # This tag requires that the tag HAVE_DOT is set to YES.
2523 DOT_TRANSPARENT = NO
2525 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
2526 # files in one run (i.e. multiple -o and -T options on the command line). This
2527 # makes dot run faster, but since only newer versions of dot (>1.8.10) support
2528 # this, this feature is disabled by default.
2529 # The default value is: NO.
2530 # This tag requires that the tag HAVE_DOT is set to YES.
2532 DOT_MULTI_TARGETS = YES
2534 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
2535 # explaining the meaning of the various boxes and arrows in the dot generated
2537 # The default value is: YES.
2538 # This tag requires that the tag HAVE_DOT is set to YES.
2540 GENERATE_LEGEND = YES
2542 # If the DOT_CLEANUP tag is set to YES doxygen will remove the intermediate dot
2543 # files that are used to generate the various graphs.
2544 # The default value is: YES.
2545 # This tag requires that the tag HAVE_DOT is set to YES.
2549 #---------------------------------------------------------------------------
2550 # Configuration::additions related to the search engine
2551 #---------------------------------------------------------------------------
2553 # The SEARCHENGINE tag specifies whether or not a search engine should be
2554 # used. If set to NO the values of all tags below this one will be ignored.