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"
363 ALIASES += DEPRECATED_1_0="@deprecated Deprecated since 1.0"
364 ALIASES += DEPRECATED_1_1="@deprecated Deprecated since 1.1"
365 ALIASES += DEPRECATED_1_2_10="@deprecated Deprecated since 1.2.10"
366 ALIASES += DEPRECATED_1_2="@deprecated Deprecated since 1.2"
368 ALIASES += PLATFORM=""
369 ALIASES += PRIVLEVEL_PLATFORM=""
370 ALIASES += PRIVLEVEL_PUBLIC=""
371 ALIASES += PRIVILEGE_KEYGRAB=""
372 ALIASES += PRIVILEGE_DISPLAY=""
373 ALIASES += REMARK_INTERNET=""
374 ALIASES += REMARK_STORAGE=""
376 ############################################
377 ## For Tizen Native API Reference
378 #ALIASES += SINCE_1_0="\par Since:\n 2.4, DALi version 1.0"
379 #ALIASES += SINCE_1_1="\par Since:\n 3.0, DALi version 1.1"
380 #ALIASES += SINCE_1_2="\par Since:\n 4.0, DALi version 1.2"
382 ## Extra tags for Tizen 3.0
383 #ALIASES += SINCE_1_2_2="\par Since:\n 3.0, DALi version 1.2.2"
384 #ALIASES += SINCE_1_2_4="\par Since:\n 3.0, DALi version 1.2.4"
385 #ALIASES += SINCE_1_2_5="\par Since:\n 3.0, DALi version 1.2.5"
386 #ALIASES += SINCE_1_2_10="\par Since:\n 3.0, DALi version 1.2.10"
387 #ALIASES += SINCE_1_2_14="\par Since:\n 3.0, DALi version 1.2.14"
389 ## DALi has no deprecated API in Tizen 2.4 because it's DALi's first release.
390 ## Thus deprecated APIs in DALi 1.0.xx will be deprecated in Tizen 3.0.
391 #ALIASES += DEPRECATED_1_0="@deprecated Deprecated since 3.0, DALi version 1.0"
392 #ALIASES += DEPRECATED_1_1="@deprecated Deprecated since 3.0, DALi version 1.1"
393 #ALIASES += DEPRECATED_1_2_10="@deprecated Deprecated since 3.0, DALi version 1.2.10"
394 #ALIASES += DEPRECATED_1_2="@deprecated Deprecated since 4.0, DALi version 1.2"
396 #ALIASES += PLATFORM="@platform"
397 #ALIASES += PRIVLEVEL_PLATFORM="\par Privilege Level:\n platform"
398 #ALIASES += PRIVLEVEL_PUBLIC="\par Privilege Level:\n public"
399 #ALIASES += PRIVILEGE_KEYGRAB="\par Privilege:\n http://tizen.org/privilege/keygrab"
400 #ALIASES += PRIVILEGE_DISPLAY="\par Privilege:\n http://tizen.org/privilege/display"
401 #ALIASES += REMARK_INTERNET="@remarks %http://tizen.org/privilege/internet is needed if @a url is a http or https address."
402 #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."
404 # This tag can be used to specify a number of word-keyword mappings (TCL only).
405 # A mapping has the form "name=value". For example adding "class=itcl::class"
406 # will allow you to use the command class in the itcl::class meaning.
410 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
411 # only. Doxygen will then generate output that is more tailored for C. For
412 # instance, some of the names that are used will be different. The list of all
413 # members will be omitted, etc.
414 # The default value is: NO.
416 OPTIMIZE_OUTPUT_FOR_C = NO
418 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or
419 # Python sources only. Doxygen will then generate output that is more tailored
420 # for that language. For instance, namespaces will be presented as packages,
421 # qualified scopes will look different, etc.
422 # The default value is: NO.
424 OPTIMIZE_OUTPUT_JAVA = NO
426 # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
427 # sources. Doxygen will then generate output that is tailored for Fortran.
428 # The default value is: NO.
430 OPTIMIZE_FOR_FORTRAN = NO
432 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
433 # sources. Doxygen will then generate output that is tailored for VHDL.
434 # The default value is: NO.
436 OPTIMIZE_OUTPUT_VHDL = NO
438 # Doxygen selects the parser to use depending on the extension of the files it
439 # parses. With this tag you can assign which parser to use for a given
440 # extension. Doxygen has a built-in mapping, but you can override or extend it
441 # using this tag. The format is ext=language, where ext is a file extension, and
442 # language is one of the parsers supported by doxygen: IDL, Java, Javascript,
443 # C#, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL. For instance to make
444 # doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
445 # (default is Fortran), use: inc=Fortran f=C.
447 # Note For files without extension you can use no_extension as a placeholder.
449 # Note that for custom extensions you also need to set FILE_PATTERNS otherwise
450 # the files are not read by doxygen.
454 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
455 # according to the Markdown format, which allows for more readable
456 # documentation. See http://daringfireball.net/projects/markdown/ for details.
457 # The output of markdown processing is further processed by doxygen, so you can
458 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
459 # case of backward compatibilities issues.
460 # The default value is: YES.
462 MARKDOWN_SUPPORT = YES
464 # When enabled doxygen tries to link words that correspond to documented
465 # classes, or namespaces to their corresponding documentation. Such a link can
466 # be prevented in individual cases by by putting a % sign in front of the word
467 # or globally by setting AUTOLINK_SUPPORT to NO.
468 # The default value is: YES.
470 AUTOLINK_SUPPORT = YES
472 # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
473 # to include (a tag file for) the STL sources as input, then you should set this
474 # tag to YES in order to let doxygen match functions declarations and
475 # definitions whose arguments contain STL classes (e.g. func(std::string);
476 # versus func(std::string) {}). This also make the inheritance and collaboration
477 # diagrams that involve STL classes more complete and accurate.
478 # The default value is: NO.
480 BUILTIN_STL_SUPPORT = YES
482 # If you use Microsoft's C++/CLI language, you should set this option to YES to
483 # enable parsing support.
484 # The default value is: NO.
488 # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
489 # http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen
490 # will parse them like normal C++ but will assume all classes use public instead
491 # of private inheritance when no explicit protection keyword is present.
492 # The default value is: NO.
496 # For Microsoft's IDL there are propget and propput attributes to indicate
497 # getter and setter methods for a property. Setting this option to YES will make
498 # doxygen to replace the get and set methods by a property in the documentation.
499 # This will only work if the methods are indeed getting or setting a simple
500 # type. If this is not the case, or you want to show the methods anyway, you
501 # should set this option to NO.
502 # The default value is: YES.
504 IDL_PROPERTY_SUPPORT = YES
506 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
507 # tag is set to YES, then doxygen will reuse the documentation of the first
508 # member in the group (if any) for the other members of the group. By default
509 # all members of a group must be documented explicitly.
510 # The default value is: NO.
512 DISTRIBUTE_GROUP_DOC = NO
514 # Set the SUBGROUPING tag to YES to allow class member groups of the same type
515 # (for instance a group of public functions) to be put as a subgroup of that
516 # type (e.g. under the Public Functions section). Set it to NO to prevent
517 # subgrouping. Alternatively, this can be done per class using the
518 # \nosubgrouping command.
519 # The default value is: YES.
523 # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions
524 # are shown inside the group in which they are included (e.g. using \ingroup)
525 # instead of on a separate page (for HTML and Man pages) or section (for LaTeX
528 # Note that this feature does not work in combination with
529 # SEPARATE_MEMBER_PAGES.
530 # The default value is: NO.
532 INLINE_GROUPED_CLASSES = NO
534 # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions
535 # with only public data fields or simple typedef fields will be shown inline in
536 # the documentation of the scope in which they are defined (i.e. file,
537 # namespace, or group documentation), provided this scope is documented. If set
538 # to NO, structs, classes, and unions are shown on a separate page (for HTML and
539 # Man pages) or section (for LaTeX and RTF).
540 # The default value is: NO.
542 INLINE_SIMPLE_STRUCTS = NO
544 # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or
545 # enum is documented as struct, union, or enum with the name of the typedef. So
546 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
547 # with name TypeT. When disabled the typedef will appear as a member of a file,
548 # namespace, or class. And the struct will be named TypeS. This can typically be
549 # useful for C code in case the coding convention dictates that all compound
550 # types are typedef'ed and only the typedef is referenced, never the tag name.
551 # The default value is: NO.
553 TYPEDEF_HIDES_STRUCT = NO
555 # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This
556 # cache is used to resolve symbols given their name and scope. Since this can be
557 # an expensive process and often the same symbol appears multiple times in the
558 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
559 # doxygen will become slower. If the cache is too large, memory is wasted. The
560 # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range
561 # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536
562 # symbols. At the end of a run doxygen will report the cache usage and suggest
563 # the optimal cache size from a speed point of view.
564 # Minimum value: 0, maximum value: 9, default value: 0.
566 LOOKUP_CACHE_SIZE = 0
568 #---------------------------------------------------------------------------
569 # Build related configuration options
570 #---------------------------------------------------------------------------
572 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
573 # documentation are documented, even if no documentation was available. Private
574 # class members and static file members will be hidden unless the
575 # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
576 # Note: This will also disable the warnings about undocumented members that are
577 # normally produced when WARNINGS is set to YES.
578 # The default value is: NO.
582 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class will
583 # be included in the documentation.
584 # The default value is: NO.
586 EXTRACT_PRIVATE = YES
588 # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
589 # scope will be included in the documentation.
590 # The default value is: NO.
594 # If the EXTRACT_STATIC tag is set to YES all static members of a file will be
595 # included in the documentation.
596 # The default value is: NO.
600 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) defined
601 # locally in source files will be included in the documentation. If set to NO
602 # only classes defined in header files are included. Does not have any effect
604 # The default value is: YES.
606 EXTRACT_LOCAL_CLASSES = YES
608 # This flag is only useful for Objective-C code. When set to YES local methods,
609 # which are defined in the implementation section but not in the interface are
610 # included in the documentation. If set to NO only methods in the interface are
612 # The default value is: NO.
614 EXTRACT_LOCAL_METHODS = NO
616 # If this flag is set to YES, the members of anonymous namespaces will be
617 # extracted and appear in the documentation as a namespace called
618 # 'anonymous_namespace{file}', where file will be replaced with the base name of
619 # the file that contains the anonymous namespace. By default anonymous namespace
621 # The default value is: NO.
623 EXTRACT_ANON_NSPACES = YES
625 # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all
626 # undocumented members inside documented classes or files. If set to NO these
627 # members will be included in the various overviews, but no documentation
628 # section is generated. This option has no effect if EXTRACT_ALL is enabled.
629 # The default value is: NO.
631 HIDE_UNDOC_MEMBERS = NO
633 # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
634 # undocumented classes that are normally visible in the class hierarchy. If set
635 # to NO these classes will be included in the various overviews. This option has
636 # no effect if EXTRACT_ALL is enabled.
637 # The default value is: NO.
639 HIDE_UNDOC_CLASSES = NO
641 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
642 # (class|struct|union) declarations. If set to NO these declarations will be
643 # included in the documentation.
644 # The default value is: NO.
646 HIDE_FRIEND_COMPOUNDS = NO
648 # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
649 # documentation blocks found inside the body of a function. If set to NO these
650 # blocks will be appended to the function's detailed documentation block.
651 # The default value is: NO.
653 HIDE_IN_BODY_DOCS = NO
655 # The INTERNAL_DOCS tag determines if documentation that is typed after a
656 # \internal command is included. If the tag is set to NO then the documentation
657 # will be excluded. Set it to YES to include the internal documentation.
658 # The default value is: NO.
662 # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
663 # names in lower-case letters. If set to YES upper-case letters are also
664 # allowed. This is useful if you have classes or files whose names only differ
665 # in case and if your file system supports case sensitive file names. Windows
666 # and Mac users are advised to set this option to NO.
667 # The default value is: system dependent.
669 CASE_SENSE_NAMES = NO
671 # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
672 # their full class and namespace scopes in the documentation. If set to YES the
673 # scope will be hidden.
674 # The default value is: NO.
676 HIDE_SCOPE_NAMES = NO
678 # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
679 # the files that are included by a file in the documentation of that file.
680 # The default value is: YES.
682 SHOW_INCLUDE_FILES = YES
684 # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each
685 # grouped member an include statement to the documentation, telling the reader
686 # which file to include in order to use the member.
687 # The default value is: NO.
689 SHOW_GROUPED_MEMB_INC = NO
691 # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include
692 # files with double quotes in the documentation rather than with sharp brackets.
693 # The default value is: NO.
695 FORCE_LOCAL_INCLUDES = NO
697 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
698 # documentation for inline members.
699 # The default value is: YES.
703 # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
704 # (detailed) documentation of file and class members alphabetically by member
705 # name. If set to NO the members will appear in declaration order.
706 # The default value is: YES.
708 SORT_MEMBER_DOCS = YES
710 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
711 # descriptions of file, namespace and class members alphabetically by member
712 # name. If set to NO the members will appear in declaration order. Note that
713 # this will also influence the order of the classes in the class list.
714 # The default value is: NO.
718 # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the
719 # (brief and detailed) documentation of class members so that constructors and
720 # destructors are listed first. If set to NO the constructors will appear in the
721 # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS.
722 # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief
723 # member documentation.
724 # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting
725 # detailed member documentation.
726 # The default value is: NO.
728 SORT_MEMBERS_CTORS_1ST = NO
730 # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy
731 # of group names into alphabetical order. If set to NO the group names will
732 # appear in their defined order.
733 # The default value is: NO.
735 SORT_GROUP_NAMES = NO
737 # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by
738 # fully-qualified names, including namespaces. If set to NO, the class list will
739 # be sorted only by class name, not including the namespace part.
740 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
741 # Note: This option applies only to the class list, not to the alphabetical
743 # The default value is: NO.
745 SORT_BY_SCOPE_NAME = NO
747 # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper
748 # type resolution of all parameters of a function it will reject a match between
749 # the prototype and the implementation of a member function even if there is
750 # only one candidate or it is obvious which candidate to choose by doing a
751 # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still
752 # accept a match between prototype and implementation in such cases.
753 # The default value is: NO.
755 STRICT_PROTO_MATCHING = NO
757 # The GENERATE_TODOLIST tag can be used to enable ( YES) or disable ( NO) the
758 # todo list. This list is created by putting \todo commands in the
760 # The default value is: YES.
762 GENERATE_TODOLIST = NO
764 # The GENERATE_TESTLIST tag can be used to enable ( YES) or disable ( NO) the
765 # test list. This list is created by putting \test commands in the
767 # The default value is: YES.
769 GENERATE_TESTLIST = NO
771 # The GENERATE_BUGLIST tag can be used to enable ( YES) or disable ( NO) the bug
772 # list. This list is created by putting \bug commands in the documentation.
773 # The default value is: YES.
775 GENERATE_BUGLIST = NO
777 # The GENERATE_DEPRECATEDLIST tag can be used to enable ( YES) or disable ( NO)
778 # the deprecated list. This list is created by putting \deprecated commands in
780 # The default value is: YES.
782 GENERATE_DEPRECATEDLIST= YES
784 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
785 # sections, marked by \if <section_label> ... \endif and \cond <section_label>
786 # ... \endcond blocks.
790 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the
791 # initial value of a variable or macro / define can have for it to appear in the
792 # documentation. If the initializer consists of more lines than specified here
793 # it will be hidden. Use a value of 0 to hide initializers completely. The
794 # appearance of the value of individual variables and macros / defines can be
795 # controlled using \showinitializer or \hideinitializer command in the
796 # documentation regardless of this setting.
797 # Minimum value: 0, maximum value: 10000, default value: 30.
799 MAX_INITIALIZER_LINES = 30
801 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
802 # the bottom of the documentation of classes and structs. If set to YES the list
803 # will mention the files that were used to generate the documentation.
804 # The default value is: YES.
806 SHOW_USED_FILES = YES
808 # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This
809 # will remove the Files entry from the Quick Index and from the Folder Tree View
811 # The default value is: YES.
815 # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces
816 # page. This will remove the Namespaces entry from the Quick Index and from the
817 # Folder Tree View (if specified).
818 # The default value is: YES.
820 SHOW_NAMESPACES = YES
822 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
823 # doxygen should invoke to get the current version for each file (typically from
824 # the version control system). Doxygen will invoke the program by executing (via
825 # popen()) the command command input-file, where command is the value of the
826 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
827 # by doxygen. Whatever the program writes to standard output is used as the file
828 # version. For an example see the documentation.
830 FILE_VERSION_FILTER =
832 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
833 # by doxygen. The layout file controls the global structure of the generated
834 # output files in an output format independent way. To create the layout file
835 # that represents doxygen's defaults, run doxygen with the -l option. You can
836 # optionally specify a file name after the option, if omitted DoxygenLayout.xml
837 # will be used as the name of the layout file.
839 # Note that if you run doxygen from a directory containing a file called
840 # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE
843 LAYOUT_FILE = @DOXYGEN_DOCS_DIR@/DaliLayout.xml
845 # The CITE_BIB_FILES tag can be used to specify one or more bib files containing
846 # the reference definitions. This must be a list of .bib files. The .bib
847 # extension is automatically appended if omitted. This requires the bibtex tool
848 # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
849 # For LaTeX the style of the bibliography can be controlled using
850 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
851 # search path. Do not use file names with spaces, bibtex cannot handle them. See
852 # also \cite for info how to create references.
856 #---------------------------------------------------------------------------
857 # Configuration options related to warning and progress messages
858 #---------------------------------------------------------------------------
860 # The QUIET tag can be used to turn on/off the messages that are generated to
861 # standard output by doxygen. If QUIET is set to YES this implies that the
863 # The default value is: NO.
867 # The WARNINGS tag can be used to turn on/off the warning messages that are
868 # generated to standard error ( stderr) by doxygen. If WARNINGS is set to YES
869 # this implies that the warnings are on.
871 # Tip: Turn warnings on while writing the documentation.
872 # The default value is: YES.
876 # If the WARN_IF_UNDOCUMENTED tag is set to YES, then doxygen will generate
877 # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag
878 # will automatically be disabled.
879 # The default value is: YES.
881 WARN_IF_UNDOCUMENTED = YES
883 # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for
884 # potential errors in the documentation, such as not documenting some parameters
885 # in a documented function, or documenting parameters that don't exist or using
886 # markup commands wrongly.
887 # The default value is: YES.
889 WARN_IF_DOC_ERROR = YES
891 # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
892 # are documented, but have no documentation for their parameters or return
893 # value. If set to NO doxygen will only warn about wrong or incomplete parameter
894 # documentation, but not about the absence of documentation.
895 # The default value is: NO.
897 WARN_NO_PARAMDOC = YES
899 # The WARN_FORMAT tag determines the format of the warning messages that doxygen
900 # can produce. The string should contain the $file, $line, and $text tags, which
901 # will be replaced by the file and line number from which the warning originated
902 # and the warning text. Optionally the format may contain $version, which will
903 # be replaced by the version of the file (if it could be obtained via
904 # FILE_VERSION_FILTER)
905 # The default value is: $file:$line: $text.
907 WARN_FORMAT = "$file:$line: $text"
909 # The WARN_LOGFILE tag can be used to specify a file to which warning and error
910 # messages should be written. If left blank the output is written to standard
915 #---------------------------------------------------------------------------
916 # configuration options related to the input files
917 #---------------------------------------------------------------------------
919 # The INPUT tag is used to specify the files and/or directories that contain
920 # documented source files. You may enter file names like myfile.cpp or
921 # directories like /usr/src/myproject. Separate the files or directories with
923 # Note: If this tag is empty the current directory is searched.
925 INPUT = @DOXYGEN_DOCS_DIR@content \
926 ../../../../dali-core/dali \
927 ../../../../dali-adaptor/adaptors/public-api \
928 ../../../../dali-adaptor/adaptors/devel-api
929 ../../../../dali-adaptor/adaptors/base \
930 ../../../../dali-adaptor/adaptors/common \
931 ../../../../dali-adaptor/adaptors/ecore \
932 ../../../../dali-adaptor/adaptors/integration-api
933 ../../../../dali-adaptor/adaptors/mobile \
934 ../../../../dali-adaptor/adaptors/tizen
935 ../../../../dali-adaptor/adaptors/x11
936 ../../../../dali-adaptor/plugins \
937 ../../../../dali-adaptor/platform-abstractions/interfaces \
938 ../../../../dali-adaptor/platform-abstractions/portable \
939 ../../../../dali-adaptor/platform-abstractions/tizen \
940 ../../../dali-toolkit/devel-api \
941 ../../../dali-toolkit/internal \
942 ../../../dali-toolkit/public-api
944 # This tag can be used to specify the character encoding of the source files
945 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
946 # libiconv (or the iconv built into libc) for the transcoding. See the libiconv
947 # documentation (see: http://www.gnu.org/software/libiconv) for the list of
948 # possible encodings.
949 # The default value is: UTF-8.
951 INPUT_ENCODING = UTF-8
953 # If the value of the INPUT tag contains directories, you can use the
954 # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
955 # *.h) to filter out the source-files in the directories. If left blank the
956 # following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii,
957 # *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp,
958 # *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown,
959 # *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf,
960 # *.qsf, *.as and *.js.
962 FILE_PATTERNS = *.c \
995 # The RECURSIVE tag can be used to specify whether or not subdirectories should
996 # be searched for input files as well.
997 # The default value is: NO.
1001 # The EXCLUDE tag can be used to specify files and/or directories that should be
1002 # excluded from the INPUT source files. This way you can easily exclude a
1003 # subdirectory from a directory tree whose root is specified with the INPUT tag.
1005 # Note that relative paths are relative to the directory from which doxygen is
1010 # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
1011 # directories that are symbolic links (a Unix file system feature) are excluded
1013 # The default value is: NO.
1015 EXCLUDE_SYMLINKS = NO
1017 # If the value of the INPUT tag contains directories, you can use the
1018 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
1019 # certain files from those directories.
1021 # Note that the wildcards are matched against the file with absolute path, so to
1022 # exclude all test directories for example use the pattern */test/*
1026 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
1027 # (namespaces, classes, functions, etc.) that should be excluded from the
1028 # output. The symbol name can be a fully qualified name, a word, or if the
1029 # wildcard * is used, a substring. Examples: ANamespace, AClass,
1030 # AClass::ANamespace, ANamespace::*Test
1032 # Note that the wildcards are matched against the file with absolute path, so to
1033 # exclude all test directories use the pattern */test/*
1037 # The EXAMPLE_PATH tag can be used to specify one or more files or directories
1038 # that contain example code fragments that are included (see the \include
1041 EXAMPLE_PATH = ../../../docs/../
1043 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
1044 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and
1045 # *.h) to filter out the source-files in the directories. If left blank all
1046 # files are included.
1048 EXAMPLE_PATTERNS = *
1050 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
1051 # searched for input files to be used with the \include or \dontinclude commands
1052 # irrespective of the value of the RECURSIVE tag.
1053 # The default value is: NO.
1055 EXAMPLE_RECURSIVE = YES
1057 # The IMAGE_PATH tag can be used to specify one or more files or directories
1058 # that contain images that are to be included in the documentation (see the
1061 IMAGE_PATH = ../../../docs/content/images
1063 # The INPUT_FILTER tag can be used to specify a program that doxygen should
1064 # invoke to filter for each input file. Doxygen will invoke the filter program
1065 # by executing (via popen()) the command:
1067 # <filter> <input-file>
1069 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
1070 # name of an input file. Doxygen will then use the output that the filter
1071 # program writes to standard output. If FILTER_PATTERNS is specified, this tag
1074 # Note that the filter must not add or remove lines; it is applied before the
1075 # code is scanned, but not when the output code is generated. If lines are added
1076 # or removed, the anchors will not be placed correctly.
1080 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
1081 # basis. Doxygen will compare the file name with each pattern and apply the
1082 # filter if there is a match. The filters are a list of the form: pattern=filter
1083 # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
1084 # filters are used. If the FILTER_PATTERNS tag is empty or if none of the
1085 # patterns match the file name, INPUT_FILTER is applied.
1089 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
1090 # INPUT_FILTER ) will also be used to filter the input files that are used for
1091 # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
1092 # The default value is: NO.
1094 FILTER_SOURCE_FILES = NO
1096 # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
1097 # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and
1098 # it is also possible to disable source filtering for a specific pattern using
1099 # *.ext= (so without naming a filter).
1100 # This tag requires that the tag FILTER_SOURCE_FILES is set to YES.
1102 FILTER_SOURCE_PATTERNS =
1104 # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that
1105 # is part of the input, its contents will be placed on the main page
1106 # (index.html). This can be useful if you have a project on for instance GitHub
1107 # and want to reuse the introduction page also for the doxygen output.
1109 USE_MDFILE_AS_MAINPAGE = main.md
1111 #---------------------------------------------------------------------------
1112 # Configuration options related to source browsing
1113 #---------------------------------------------------------------------------
1115 # If the SOURCE_BROWSER tag is set to YES then a list of source files will be
1116 # generated. Documented entities will be cross-referenced with these sources.
1118 # Note: To get rid of all source code in the generated output, make sure that
1119 # also VERBATIM_HEADERS is set to NO.
1120 # The default value is: NO.
1122 SOURCE_BROWSER = YES
1124 # Setting the INLINE_SOURCES tag to YES will include the body of functions,
1125 # classes and enums directly into the documentation.
1126 # The default value is: NO.
1130 # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any
1131 # special comment blocks from generated source code fragments. Normal C, C++ and
1132 # Fortran comments will always remain visible.
1133 # The default value is: YES.
1135 STRIP_CODE_COMMENTS = YES
1137 # If the REFERENCED_BY_RELATION tag is set to YES then for each documented
1138 # function all documented functions referencing it will be listed.
1139 # The default value is: NO.
1141 REFERENCED_BY_RELATION = NO
1143 # If the REFERENCES_RELATION tag is set to YES then for each documented function
1144 # all documented entities called/used by that function will be listed.
1145 # The default value is: NO.
1147 REFERENCES_RELATION = NO
1149 # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set
1150 # to YES, then the hyperlinks from functions in REFERENCES_RELATION and
1151 # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will
1152 # link to the documentation.
1153 # The default value is: YES.
1155 REFERENCES_LINK_SOURCE = YES
1157 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1158 # source code will show a tooltip with additional information such as prototype,
1159 # brief description and links to the definition and documentation. Since this
1160 # will make the HTML file larger and loading of large files a bit slower, you
1161 # can opt to disable this feature.
1162 # The default value is: YES.
1163 # This tag requires that the tag SOURCE_BROWSER is set to YES.
1165 SOURCE_TOOLTIPS = NO
1167 # If the USE_HTAGS tag is set to YES then the references to source code will
1168 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1169 # source browser. The htags tool is part of GNU's global source tagging system
1170 # (see http://www.gnu.org/software/global/global.html). You will need version
1173 # To use it do the following:
1174 # - Install the latest version of global
1175 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
1176 # - Make sure the INPUT points to the root of the source tree
1177 # - Run doxygen as normal
1179 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
1180 # tools must be available from the command line (i.e. in the search path).
1182 # The result: instead of the source browser generated by doxygen, the links to
1183 # source code will now point to the output of htags.
1184 # The default value is: NO.
1185 # This tag requires that the tag SOURCE_BROWSER is set to YES.
1189 # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a
1190 # verbatim copy of the header file for each class for which an include is
1191 # specified. Set to NO to disable this.
1192 # See also: Section \class.
1193 # The default value is: YES.
1195 VERBATIM_HEADERS = YES
1197 #---------------------------------------------------------------------------
1198 # Configuration options related to the alphabetical class index
1199 #---------------------------------------------------------------------------
1201 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all
1202 # compounds will be generated. Enable this if the project contains a lot of
1203 # classes, structs, unions or interfaces.
1204 # The default value is: YES.
1206 ALPHABETICAL_INDEX = NO
1208 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
1209 # which the alphabetical index list will be split.
1210 # Minimum value: 1, maximum value: 20, default value: 5.
1211 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1213 COLS_IN_ALPHA_INDEX = 5
1215 # In case all classes in a project start with a common prefix, all classes will
1216 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1217 # can be used to specify a prefix (or a list of prefixes) that should be ignored
1218 # while generating the index headers.
1219 # This tag requires that the tag ALPHABETICAL_INDEX is set to YES.
1223 #---------------------------------------------------------------------------
1224 # Configuration options related to the HTML output
1225 #---------------------------------------------------------------------------
1227 # If the GENERATE_HTML tag is set to YES doxygen will generate HTML output
1228 # The default value is: YES.
1232 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a
1233 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1235 # The default directory is: html.
1236 # This tag requires that the tag GENERATE_HTML is set to YES.
1240 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each
1241 # generated HTML page (for example: .htm, .php, .asp).
1242 # The default value is: .html.
1243 # This tag requires that the tag GENERATE_HTML is set to YES.
1245 HTML_FILE_EXTENSION = .html
1247 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1248 # each generated HTML page. If the tag is left blank doxygen will generate a
1251 # To get valid HTML the header file that includes any scripts and style sheets
1252 # that doxygen needs, which is dependent on the configuration options used (e.g.
1253 # the setting GENERATE_TREEVIEW). It is highly recommended to start with a
1254 # default header using
1255 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1257 # and then modify the file new_header.html. See also section "Doxygen usage"
1258 # for information on how to generate the default header that doxygen normally
1260 # Note: The header is subject to change so you typically have to regenerate the
1261 # default header when upgrading to a newer version of doxygen. For a description
1262 # of the possible markers and block names see the documentation.
1263 # This tag requires that the tag GENERATE_HTML is set to YES.
1267 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1268 # generated HTML page. If the tag is left blank doxygen will generate a standard
1269 # footer. See HTML_HEADER for more information on how to generate a default
1270 # footer and what special commands can be used inside the footer. See also
1271 # section "Doxygen usage" for information on how to generate the default footer
1272 # that doxygen normally uses.
1273 # This tag requires that the tag GENERATE_HTML is set to YES.
1277 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1278 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1279 # the HTML output. If left blank doxygen will generate a default style sheet.
1280 # See also section "Doxygen usage" for information on how to generate the style
1281 # sheet that doxygen normally uses.
1282 # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as
1283 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1285 # This tag requires that the tag GENERATE_HTML is set to YES.
1289 # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
1290 # defined cascading style sheet that is included after the standard style sheets
1291 # created by doxygen. Using this option one can overrule certain style aspects.
1292 # This is preferred over using HTML_STYLESHEET since it does not replace the
1293 # standard style sheet and is therefor more robust against future updates.
1294 # Doxygen will copy the style sheet file to the output directory. For an example
1295 # see the documentation.
1296 # This tag requires that the tag GENERATE_HTML is set to YES.
1298 HTML_EXTRA_STYLESHEET = dali_doxygen.css
1300 # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
1301 # other source files which should be copied to the HTML output directory. Note
1302 # that these files will be copied to the base HTML output directory. Use the
1303 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1304 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1305 # files will be copied as-is; there are no commands or markers available.
1306 # This tag requires that the tag GENERATE_HTML is set to YES.
1310 # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1311 # will adjust the colors in the stylesheet and background images according to
1312 # this color. Hue is specified as an angle on a colorwheel, see
1313 # http://en.wikipedia.org/wiki/Hue for more information. For instance the value
1314 # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
1315 # purple, and 360 is red again.
1316 # Minimum value: 0, maximum value: 359, default value: 220.
1317 # This tag requires that the tag GENERATE_HTML is set to YES.
1319 HTML_COLORSTYLE_HUE = 220
1321 # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors
1322 # in the HTML output. For a value of 0 the output will use grayscales only. A
1323 # value of 255 will produce the most vivid colors.
1324 # Minimum value: 0, maximum value: 255, default value: 100.
1325 # This tag requires that the tag GENERATE_HTML is set to YES.
1327 HTML_COLORSTYLE_SAT = 100
1329 # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the
1330 # luminance component of the colors in the HTML output. Values below 100
1331 # gradually make the output lighter, whereas values above 100 make the output
1332 # darker. The value divided by 100 is the actual gamma applied, so 80 represents
1333 # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not
1335 # Minimum value: 40, maximum value: 240, default value: 80.
1336 # This tag requires that the tag GENERATE_HTML is set to YES.
1338 HTML_COLORSTYLE_GAMMA = 80
1340 # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
1341 # page will contain the date and time when the page was generated. Setting this
1342 # to NO can help when comparing the output of multiple runs.
1343 # The default value is: YES.
1344 # This tag requires that the tag GENERATE_HTML is set to YES.
1346 HTML_TIMESTAMP = YES
1348 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1349 # documentation will contain sections that can be hidden and shown after the
1351 # The default value is: NO.
1352 # This tag requires that the tag GENERATE_HTML is set to YES.
1354 HTML_DYNAMIC_SECTIONS = NO
1356 # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries
1357 # shown in the various tree structured indices initially; the user can expand
1358 # and collapse entries dynamically later on. Doxygen will expand the tree to
1359 # such a level that at most the specified number of entries are visible (unless
1360 # a fully collapsed tree already exceeds this amount). So setting the number of
1361 # entries 1 will produce a full collapsed tree by default. 0 is a special value
1362 # representing an infinite number of entries and will result in a full expanded
1364 # Minimum value: 0, maximum value: 9999, default value: 100.
1365 # This tag requires that the tag GENERATE_HTML is set to YES.
1367 HTML_INDEX_NUM_ENTRIES = 100
1369 # If the GENERATE_DOCSET tag is set to YES, additional index files will be
1370 # generated that can be used as input for Apple's Xcode 3 integrated development
1371 # environment (see: http://developer.apple.com/tools/xcode/), introduced with
1372 # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1373 # Makefile in the HTML output directory. Running make will produce the docset in
1374 # that directory and running make install will install the docset in
1375 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1376 # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
1377 # for more information.
1378 # The default value is: NO.
1379 # This tag requires that the tag GENERATE_HTML is set to YES.
1381 GENERATE_DOCSET = NO
1383 # This tag determines the name of the docset feed. A documentation feed provides
1384 # an umbrella under which multiple documentation sets from a single provider
1385 # (such as a company or product suite) can be grouped.
1386 # The default value is: Doxygen generated docs.
1387 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1389 DOCSET_FEEDNAME = "Doxygen generated docs"
1391 # This tag specifies a string that should uniquely identify the documentation
1392 # set bundle. This should be a reverse domain-name style string, e.g.
1393 # com.mycompany.MyDocSet. Doxygen will append .docset to the name.
1394 # The default value is: org.doxygen.Project.
1395 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1397 DOCSET_BUNDLE_ID = org.doxygen.Project
1399 # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify
1400 # the documentation publisher. This should be a reverse domain-name style
1401 # string, e.g. com.mycompany.MyDocSet.documentation.
1402 # The default value is: org.doxygen.Publisher.
1403 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1405 DOCSET_PUBLISHER_ID = org.doxygen.Publisher
1407 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1408 # The default value is: Publisher.
1409 # This tag requires that the tag GENERATE_DOCSET is set to YES.
1411 DOCSET_PUBLISHER_NAME = Publisher
1413 # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1414 # additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1415 # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1416 # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1419 # The HTML Help Workshop contains a compiler that can convert all HTML output
1420 # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML
1421 # files are now used as the Windows 98 help format, and will replace the old
1422 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1423 # HTML files also contain an index, a table of contents, and you can search for
1424 # words in the documentation. The HTML workshop also contains a viewer for
1425 # compressed HTML files.
1426 # The default value is: NO.
1427 # This tag requires that the tag GENERATE_HTML is set to YES.
1429 GENERATE_HTMLHELP = YES
1431 # The CHM_FILE tag can be used to specify the file name of the resulting .chm
1432 # file. You can add a path in front of the file if the result should not be
1433 # written to the html output directory.
1434 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1438 # The HHC_LOCATION tag can be used to specify the location (absolute path
1439 # including file name) of the HTML help compiler ( hhc.exe). If non-empty
1440 # doxygen will try to run the HTML help compiler on the generated index.hhp.
1441 # The file has to be specified with full path.
1442 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1446 # The GENERATE_CHI flag controls if a separate .chi index file is generated (
1447 # YES) or that it should be included in the master .chm file ( NO).
1448 # The default value is: NO.
1449 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1453 # The CHM_INDEX_ENCODING is used to encode HtmlHelp index ( hhk), content ( hhc)
1454 # and project file content.
1455 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1457 CHM_INDEX_ENCODING =
1459 # The BINARY_TOC flag controls whether a binary table of contents is generated (
1460 # YES) or a normal table of contents ( NO) in the .chm file.
1461 # The default value is: NO.
1462 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1466 # The TOC_EXPAND flag can be set to YES to add extra items for group members to
1467 # the table of contents of the HTML help documentation and to the tree view.
1468 # The default value is: NO.
1469 # This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1473 # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
1474 # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that
1475 # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help
1476 # (.qch) of the generated HTML documentation.
1477 # The default value is: NO.
1478 # This tag requires that the tag GENERATE_HTML is set to YES.
1482 # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify
1483 # the file name of the resulting .qch file. The path specified is relative to
1484 # the HTML output folder.
1485 # This tag requires that the tag GENERATE_QHP is set to YES.
1487 QCH_FILE = "Dali.qch"
1489 # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help
1490 # Project output. For more information please see Qt Help Project / Namespace
1491 # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1492 # The default value is: org.doxygen.Project.
1493 # This tag requires that the tag GENERATE_QHP is set to YES.
1495 QHP_NAMESPACE = "Dali"
1497 # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt
1498 # Help Project output. For more information please see Qt Help Project / Virtual
1499 # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1501 # The default value is: doc.
1502 # This tag requires that the tag GENERATE_QHP is set to YES.
1504 QHP_VIRTUAL_FOLDER = Dali
1506 # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom
1507 # filter to add. For more information please see Qt Help Project / Custom
1508 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1510 # This tag requires that the tag GENERATE_QHP is set to YES.
1512 QHP_CUST_FILTER_NAME =
1514 # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the
1515 # custom filter to add. For more information please see Qt Help Project / Custom
1516 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1518 # This tag requires that the tag GENERATE_QHP is set to YES.
1520 QHP_CUST_FILTER_ATTRS =
1522 # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
1523 # project's filter section matches. Qt Help Project / Filter Attributes (see:
1524 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1525 # This tag requires that the tag GENERATE_QHP is set to YES.
1527 QHP_SECT_FILTER_ATTRS =
1529 # The QHG_LOCATION tag can be used to specify the location of Qt's
1530 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1531 # generated .qhp file.
1532 # This tag requires that the tag GENERATE_QHP is set to YES.
1534 # Setting this works, but leaving empty to match public doxygen config.
1537 # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be
1538 # generated, together with the HTML files, they form an Eclipse help plugin. To
1539 # install this plugin and make it available under the help contents menu in
1540 # Eclipse, the contents of the directory containing the HTML and XML files needs
1541 # to be copied into the plugins directory of eclipse. The name of the directory
1542 # within the plugins directory should be the same as the ECLIPSE_DOC_ID value.
1543 # After copying Eclipse needs to be restarted before the help appears.
1544 # The default value is: NO.
1545 # This tag requires that the tag GENERATE_HTML is set to YES.
1547 GENERATE_ECLIPSEHELP = NO
1549 # A unique identifier for the Eclipse help plugin. When installing the plugin
1550 # the directory name containing the HTML and XML files should also have this
1551 # name. Each documentation set should have its own identifier.
1552 # The default value is: org.doxygen.Project.
1553 # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES.
1555 ECLIPSE_DOC_ID = org.doxygen.Project
1557 # If you want full control over the layout of the generated HTML pages it might
1558 # be necessary to disable the index and replace it with your own. The
1559 # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top
1560 # of each HTML page. A value of NO enables the index and the value YES disables
1561 # it. Since the tabs in the index contain the same information as the navigation
1562 # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES.
1563 # The default value is: NO.
1564 # This tag requires that the tag GENERATE_HTML is set to YES.
1568 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1569 # structure should be generated to display hierarchical information. If the tag
1570 # value is set to YES, a side panel will be generated containing a tree-like
1571 # index structure (just like the one that is generated for HTML Help). For this
1572 # to work a browser that supports JavaScript, DHTML, CSS and frames is required
1573 # (i.e. any modern browser). Windows users are probably better off using the
1574 # HTML help feature. Via custom stylesheets (see HTML_EXTRA_STYLESHEET) one can
1575 # further fine-tune the look of the index. As an example, the default style
1576 # sheet generated by doxygen has an example that shows how to put an image at
1577 # the root of the tree instead of the PROJECT_NAME. Since the tree basically has
1578 # the same information as the tab index, you could consider setting
1579 # DISABLE_INDEX to YES when enabling this option.
1580 # The default value is: NO.
1581 # This tag requires that the tag GENERATE_HTML is set to YES.
1583 GENERATE_TREEVIEW = NONE
1585 # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that
1586 # doxygen will group on one line in the generated HTML documentation.
1588 # Note that a value of 0 will completely suppress the enum values from appearing
1589 # in the overview section.
1590 # Minimum value: 0, maximum value: 20, default value: 4.
1591 # This tag requires that the tag GENERATE_HTML is set to YES.
1593 ENUM_VALUES_PER_LINE = 4
1595 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used
1596 # to set the initial width (in pixels) of the frame in which the tree is shown.
1597 # Minimum value: 0, maximum value: 1500, default value: 250.
1598 # This tag requires that the tag GENERATE_HTML is set to YES.
1600 TREEVIEW_WIDTH = 250
1602 # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open links to
1603 # external symbols imported via tag files in a separate window.
1604 # The default value is: NO.
1605 # This tag requires that the tag GENERATE_HTML is set to YES.
1607 EXT_LINKS_IN_WINDOW = NO
1609 # Use this tag to change the font size of LaTeX formulas included as images in
1610 # the HTML documentation. When you change the font size after a successful
1611 # doxygen run you need to manually remove any form_*.png images from the HTML
1612 # output directory to force them to be regenerated.
1613 # Minimum value: 8, maximum value: 50, default value: 10.
1614 # This tag requires that the tag GENERATE_HTML is set to YES.
1616 FORMULA_FONTSIZE = 10
1618 # Use the FORMULA_TRANPARENT tag to determine whether or not the images
1619 # generated for formulas are transparent PNGs. Transparent PNGs are not
1620 # supported properly for IE 6.0, but are supported on all modern browsers.
1622 # Note that when changing this option you need to delete any form_*.png files in
1623 # the HTML output directory before the changes have effect.
1624 # The default value is: YES.
1625 # This tag requires that the tag GENERATE_HTML is set to YES.
1627 FORMULA_TRANSPARENT = YES
1629 # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1630 # http://www.mathjax.org) which uses client side Javascript for the rendering
1631 # instead of using prerendered bitmaps. Use this if you do not have LaTeX
1632 # installed or if you want to formulas look prettier in the HTML output. When
1633 # enabled you may also need to install MathJax separately and configure the path
1634 # to it using the MATHJAX_RELPATH option.
1635 # The default value is: NO.
1636 # This tag requires that the tag GENERATE_HTML is set to YES.
1640 # When MathJax is enabled you can set the default output format to be used for
1641 # the MathJax output. See the MathJax site (see:
1642 # http://docs.mathjax.org/en/latest/output.html) for more details.
1643 # Possible values are: HTML-CSS (which is slower, but has the best
1644 # compatibility), NativeMML (i.e. MathML) and SVG.
1645 # The default value is: HTML-CSS.
1646 # This tag requires that the tag USE_MATHJAX is set to YES.
1648 MATHJAX_FORMAT = HTML-CSS
1650 # When MathJax is enabled you need to specify the location relative to the HTML
1651 # output directory using the MATHJAX_RELPATH option. The destination directory
1652 # should contain the MathJax.js script. For instance, if the mathjax directory
1653 # is located at the same level as the HTML output directory, then
1654 # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1655 # Content Delivery Network so you can quickly see the result without installing
1656 # MathJax. However, it is strongly recommended to install a local copy of
1657 # MathJax from http://www.mathjax.org before deployment.
1658 # The default value is: http://cdn.mathjax.org/mathjax/latest.
1659 # This tag requires that the tag USE_MATHJAX is set to YES.
1661 MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest
1663 # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax
1664 # extension names that should be enabled during MathJax rendering. For example
1665 # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols
1666 # This tag requires that the tag USE_MATHJAX is set to YES.
1668 MATHJAX_EXTENSIONS =
1670 # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces
1671 # of code that will be used on startup of the MathJax code. See the MathJax site
1672 # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an
1673 # example see the documentation.
1674 # This tag requires that the tag USE_MATHJAX is set to YES.
1678 # When the SEARCHENGINE tag is enabled doxygen will generate a search box for
1679 # the HTML output. The underlying search engine uses javascript and DHTML and
1680 # should work on any modern browser. Note that when using HTML help
1681 # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET)
1682 # there is already a search function so this one should typically be disabled.
1683 # For large projects the javascript based search engine can be slow, then
1684 # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to
1685 # search using the keyboard; to jump to the search box use <access key> + S
1686 # (what the <access key> is depends on the OS and browser, but it is typically
1687 # <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down
1688 # key> to jump into the search results window, the results can be navigated
1689 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1690 # the search. The filter options can be selected when the cursor is inside the
1691 # search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys>
1692 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1694 # The default value is: YES.
1695 # This tag requires that the tag GENERATE_HTML is set to YES.
1699 # When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1700 # implemented using a web server instead of a web client using Javascript. There
1701 # are two flavours of web server based searching depending on the
1702 # EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for
1703 # searching and an index file used by the script. When EXTERNAL_SEARCH is
1704 # enabled the indexing and searching needs to be provided by external tools. See
1705 # the section "External Indexing and Searching" for details.
1706 # The default value is: NO.
1707 # This tag requires that the tag SEARCHENGINE is set to YES.
1709 SERVER_BASED_SEARCH = NO
1711 # When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP
1712 # script for searching. Instead the search results are written to an XML file
1713 # which needs to be processed by an external indexer. Doxygen will invoke an
1714 # external search engine pointed to by the SEARCHENGINE_URL option to obtain the
1717 # Doxygen ships with an example indexer ( doxyindexer) and search engine
1718 # (doxysearch.cgi) which are based on the open source search engine library
1719 # Xapian (see: http://xapian.org/).
1721 # See the section "External Indexing and Searching" for details.
1722 # The default value is: NO.
1723 # This tag requires that the tag SEARCHENGINE is set to YES.
1725 EXTERNAL_SEARCH = NO
1727 # The SEARCHENGINE_URL should point to a search engine hosted by a web server
1728 # which will return the search results when EXTERNAL_SEARCH is enabled.
1730 # Doxygen ships with an example indexer ( doxyindexer) and search engine
1731 # (doxysearch.cgi) which are based on the open source search engine library
1732 # Xapian (see: http://xapian.org/). See the section "External Indexing and
1733 # Searching" for details.
1734 # This tag requires that the tag SEARCHENGINE is set to YES.
1738 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed
1739 # search data is written to a file for indexing by an external tool. With the
1740 # SEARCHDATA_FILE tag the name of this file can be specified.
1741 # The default file is: searchdata.xml.
1742 # This tag requires that the tag SEARCHENGINE is set to YES.
1744 SEARCHDATA_FILE = searchdata.xml
1746 # When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the
1747 # EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is
1748 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1749 # projects and redirect the results back to the right project.
1750 # This tag requires that the tag SEARCHENGINE is set to YES.
1752 EXTERNAL_SEARCH_ID =
1754 # The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen
1755 # projects other than the one defined by this configuration file, but that are
1756 # all added to the same external search index. Each project needs to have a
1757 # unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of
1758 # to a relative location where the documentation can be found. The format is:
1759 # EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ...
1760 # This tag requires that the tag SEARCHENGINE is set to YES.
1762 EXTRA_SEARCH_MAPPINGS =
1764 #---------------------------------------------------------------------------
1765 # Configuration options related to the LaTeX output
1766 #---------------------------------------------------------------------------
1768 # If the GENERATE_LATEX tag is set to YES doxygen will generate LaTeX output.
1769 # The default value is: YES.
1773 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a
1774 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1776 # The default directory is: latex.
1777 # This tag requires that the tag GENERATE_LATEX is set to YES.
1779 LATEX_OUTPUT = latex
1781 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1784 # Note that when enabling USE_PDFLATEX this option is only used for generating
1785 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1786 # written to the output directory.
1787 # The default file is: latex.
1788 # This tag requires that the tag GENERATE_LATEX is set to YES.
1790 LATEX_CMD_NAME = latex
1792 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
1794 # The default file is: makeindex.
1795 # This tag requires that the tag GENERATE_LATEX is set to YES.
1797 MAKEINDEX_CMD_NAME = makeindex
1799 # If the COMPACT_LATEX tag is set to YES doxygen generates more compact LaTeX
1800 # documents. This may be useful for small projects and may help to save some
1802 # The default value is: NO.
1803 # This tag requires that the tag GENERATE_LATEX is set to YES.
1807 # The PAPER_TYPE tag can be used to set the paper type that is used by the
1809 # Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x
1810 # 14 inches) and executive (7.25 x 10.5 inches).
1811 # The default value is: a4.
1812 # This tag requires that the tag GENERATE_LATEX is set to YES.
1816 # The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
1817 # that should be included in the LaTeX output. To get the times font for
1818 # instance you can specify
1819 # EXTRA_PACKAGES=times
1820 # If left blank no extra packages will be included.
1821 # This tag requires that the tag GENERATE_LATEX is set to YES.
1825 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for the
1826 # generated LaTeX document. The header should contain everything until the first
1827 # chapter. If it is left blank doxygen will generate a standard header. See
1828 # section "Doxygen usage" for information on how to let doxygen write the
1829 # default header to a separate file.
1831 # Note: Only use a user-defined header if you know what you are doing! The
1832 # following commands have a special meaning inside the header: $title,
1833 # $datetime, $date, $doxygenversion, $projectname, $projectnumber. Doxygen will
1834 # replace them by respectively the title of the page, the current date and time,
1835 # only the current date, the version number of doxygen, the project name (see
1836 # PROJECT_NAME), or the project number (see PROJECT_NUMBER).
1837 # This tag requires that the tag GENERATE_LATEX is set to YES.
1841 # The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1842 # generated LaTeX document. The footer should contain everything after the last
1843 # chapter. If it is left blank doxygen will generate a standard footer.
1845 # Note: Only use a user-defined footer if you know what you are doing!
1846 # This tag requires that the tag GENERATE_LATEX is set to YES.
1850 # The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1851 # other source files which should be copied to the LATEX_OUTPUT output
1852 # directory. Note that the files will be copied as-is; there are no commands or
1853 # markers available.
1854 # This tag requires that the tag GENERATE_LATEX is set to YES.
1858 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is
1859 # prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will
1860 # contain links (just like the HTML output) instead of page references. This
1861 # makes the output suitable for online browsing using a PDF viewer.
1862 # The default value is: YES.
1863 # This tag requires that the tag GENERATE_LATEX is set to YES.
1865 PDF_HYPERLINKS = YES
1867 # If the LATEX_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
1868 # the PDF file directly from the LaTeX files. Set this option to YES to get a
1869 # higher quality PDF documentation.
1870 # The default value is: YES.
1871 # This tag requires that the tag GENERATE_LATEX is set to YES.
1875 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode
1876 # command to the generated LaTeX files. This will instruct LaTeX to keep running
1877 # if errors occur, instead of asking the user for help. This option is also used
1878 # when generating formulas in HTML.
1879 # The default value is: NO.
1880 # This tag requires that the tag GENERATE_LATEX is set to YES.
1882 LATEX_BATCHMODE = NO
1884 # If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the
1885 # index chapters (such as File Index, Compound Index, etc.) in the output.
1886 # The default value is: NO.
1887 # This tag requires that the tag GENERATE_LATEX is set to YES.
1889 LATEX_HIDE_INDICES = NO
1891 # If the LATEX_SOURCE_CODE tag is set to YES then doxygen will include source
1892 # code with syntax highlighting in the LaTeX output.
1894 # Note that which sources are shown also depends on other settings such as
1896 # The default value is: NO.
1897 # This tag requires that the tag GENERATE_LATEX is set to YES.
1899 LATEX_SOURCE_CODE = NO
1901 # The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1902 # bibliography, e.g. plainnat, or ieeetr. See
1903 # http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
1904 # The default value is: plain.
1905 # This tag requires that the tag GENERATE_LATEX is set to YES.
1907 LATEX_BIB_STYLE = plain
1909 #---------------------------------------------------------------------------
1910 # Configuration options related to the RTF output
1911 #---------------------------------------------------------------------------
1913 # If the GENERATE_RTF tag is set to YES doxygen will generate RTF output. The
1914 # RTF output is optimized for Word 97 and may not look too pretty with other RTF
1916 # The default value is: NO.
1920 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a
1921 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1923 # The default directory is: rtf.
1924 # This tag requires that the tag GENERATE_RTF is set to YES.
1928 # If the COMPACT_RTF tag is set to YES doxygen generates more compact RTF
1929 # documents. This may be useful for small projects and may help to save some
1931 # The default value is: NO.
1932 # This tag requires that the tag GENERATE_RTF is set to YES.
1936 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will
1937 # contain hyperlink fields. The RTF file will contain links (just like the HTML
1938 # output) instead of page references. This makes the output suitable for online
1939 # browsing using Word or some other Word compatible readers that support those
1942 # Note: WordPad (write) and others do not support links.
1943 # The default value is: NO.
1944 # This tag requires that the tag GENERATE_RTF is set to YES.
1948 # Load stylesheet definitions from file. Syntax is similar to doxygen's config
1949 # file, i.e. a series of assignments. You only have to provide replacements,
1950 # missing definitions are set to their default value.
1952 # See also section "Doxygen usage" for information on how to generate the
1953 # default style sheet that doxygen normally uses.
1954 # This tag requires that the tag GENERATE_RTF is set to YES.
1956 RTF_STYLESHEET_FILE =
1958 # Set optional variables used in the generation of an RTF document. Syntax is
1959 # similar to doxygen's config file. A template extensions file can be generated
1960 # using doxygen -e rtf extensionFile.
1961 # This tag requires that the tag GENERATE_RTF is set to YES.
1963 RTF_EXTENSIONS_FILE =
1965 #---------------------------------------------------------------------------
1966 # Configuration options related to the man page output
1967 #---------------------------------------------------------------------------
1969 # If the GENERATE_MAN tag is set to YES doxygen will generate man pages for
1970 # classes and files.
1971 # The default value is: NO.
1975 # The MAN_OUTPUT tag is used to specify where the man pages will be put. If a
1976 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1977 # it. A directory man3 will be created inside the directory specified by
1979 # The default directory is: man.
1980 # This tag requires that the tag GENERATE_MAN is set to YES.
1984 # The MAN_EXTENSION tag determines the extension that is added to the generated
1985 # man pages. In case the manual section does not start with a number, the number
1986 # 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is
1988 # The default value is: .3.
1989 # This tag requires that the tag GENERATE_MAN is set to YES.
1993 # If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
1994 # will generate one additional man file for each entity documented in the real
1995 # man page(s). These additional files only source the real man page, but without
1996 # them the man command would be unable to find the correct page.
1997 # The default value is: NO.
1998 # This tag requires that the tag GENERATE_MAN is set to YES.
2002 #---------------------------------------------------------------------------
2003 # Configuration options related to the XML output
2004 #---------------------------------------------------------------------------
2006 # If the GENERATE_XML tag is set to YES doxygen will generate an XML file that
2007 # captures the structure of the code including all documentation.
2008 # The default value is: NO.
2012 # The XML_OUTPUT tag is used to specify where the XML pages will be put. If a
2013 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
2015 # The default directory is: xml.
2016 # This tag requires that the tag GENERATE_XML is set to YES.
2020 # The XML_SCHEMA tag can be used to specify a XML schema, which can be used by a
2021 # validating XML parser to check the syntax of the XML files.
2022 # This tag requires that the tag GENERATE_XML is set to YES.
2026 # The XML_DTD tag can be used to specify a XML DTD, which can be used by a
2027 # validating XML parser to check the syntax of the XML files.
2028 # This tag requires that the tag GENERATE_XML is set to YES.
2032 # If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program
2033 # listings (including syntax highlighting and cross-referencing information) to
2034 # the XML output. Note that enabling this will significantly increase the size
2035 # of the XML output.
2036 # The default value is: YES.
2037 # This tag requires that the tag GENERATE_XML is set to YES.
2039 XML_PROGRAMLISTING = YES
2041 #---------------------------------------------------------------------------
2042 # Configuration options related to the DOCBOOK output
2043 #---------------------------------------------------------------------------
2045 # If the GENERATE_DOCBOOK tag is set to YES doxygen will generate Docbook files
2046 # that can be used to generate PDF.
2047 # The default value is: NO.
2049 GENERATE_DOCBOOK = NO
2051 # The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put.
2052 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
2054 # The default directory is: docbook.
2055 # This tag requires that the tag GENERATE_DOCBOOK is set to YES.
2057 DOCBOOK_OUTPUT = docbook
2059 #---------------------------------------------------------------------------
2060 # Configuration options for the AutoGen Definitions output
2061 #---------------------------------------------------------------------------
2063 # If the GENERATE_AUTOGEN_DEF tag is set to YES doxygen will generate an AutoGen
2064 # Definitions (see http://autogen.sf.net) file that captures the structure of
2065 # the code including all documentation. Note that this feature is still
2066 # experimental and incomplete at the moment.
2067 # The default value is: NO.
2069 GENERATE_AUTOGEN_DEF = NO
2071 #---------------------------------------------------------------------------
2072 # Configuration options related to the Perl module output
2073 #---------------------------------------------------------------------------
2075 # If the GENERATE_PERLMOD tag is set to YES doxygen will generate a Perl module
2076 # file that captures the structure of the code including all documentation.
2078 # Note that this feature is still experimental and incomplete at the moment.
2079 # The default value is: NO.
2081 GENERATE_PERLMOD = NO
2083 # If the PERLMOD_LATEX tag is set to YES doxygen will generate the necessary
2084 # Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI
2085 # output from the Perl module output.
2086 # The default value is: NO.
2087 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2091 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be nicely
2092 # formatted so it can be parsed by a human reader. This is useful if you want to
2093 # understand what is going on. On the other hand, if this tag is set to NO the
2094 # size of the Perl module output will be much smaller and Perl will parse it
2096 # The default value is: YES.
2097 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2099 PERLMOD_PRETTY = YES
2101 # The names of the make variables in the generated doxyrules.make file are
2102 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
2103 # so different doxyrules.make files included by the same Makefile don't
2104 # overwrite each other's variables.
2105 # This tag requires that the tag GENERATE_PERLMOD is set to YES.
2107 PERLMOD_MAKEVAR_PREFIX =
2109 #---------------------------------------------------------------------------
2110 # Configuration options related to the preprocessor
2111 #---------------------------------------------------------------------------
2113 # If the ENABLE_PREPROCESSING tag is set to YES doxygen will evaluate all
2114 # C-preprocessor directives found in the sources and include files.
2115 # The default value is: YES.
2117 ENABLE_PREPROCESSING = YES
2119 # If the MACRO_EXPANSION tag is set to YES doxygen will expand all macro names
2120 # in the source code. If set to NO only conditional compilation will be
2121 # performed. Macro expansion can be done in a controlled way by setting
2122 # EXPAND_ONLY_PREDEF to YES.
2123 # The default value is: NO.
2124 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2126 MACRO_EXPANSION = YES
2128 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then
2129 # the macro expansion is limited to the macros specified with the PREDEFINED and
2130 # EXPAND_AS_DEFINED tags.
2131 # The default value is: NO.
2132 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2134 EXPAND_ONLY_PREDEF = YES
2136 # If the SEARCH_INCLUDES tag is set to YES the includes files in the
2137 # INCLUDE_PATH will be searched if a #include is found.
2138 # The default value is: YES.
2139 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2141 SEARCH_INCLUDES = YES
2143 # The INCLUDE_PATH tag can be used to specify one or more directories that
2144 # contain include files that are not input files but should be processed by the
2146 # This tag requires that the tag SEARCH_INCLUDES is set to YES.
2148 INCLUDE_PATH = ../../../../dali/dali \
2149 ../../../../dali-adaptor/adaptors \
2150 ../../../../dali-adaptor/plugins \
2151 ../../../../dali-adaptor/platform-abstractions \
2152 ../../../texture-atlas-exporter/dali-exporter \
2153 ../../../dali-toolkit
2155 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
2156 # patterns (like *.h and *.hpp) to filter out the header-files in the
2157 # directories. If left blank, the patterns specified with FILE_PATTERNS will be
2159 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2161 INCLUDE_FILE_PATTERNS =
2163 # The PREDEFINED tag can be used to specify one or more macro names that are
2164 # defined before the preprocessor is started (similar to the -D option of e.g.
2165 # gcc). The argument of the tag is a list of macros of the form: name or
2166 # name=definition (no spaces). If the definition and the "=" are omitted, "=1"
2167 # is assumed. To prevent a macro definition from being undefined via #undef or
2168 # recursively expanded use the := operator instead of the = operator.
2169 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2171 PREDEFINED = DALI_IMPORT_API \
2180 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this
2181 # tag can be used to specify a list of macro names that should be expanded. The
2182 # macro definition that is found in the sources will be used. Use the PREDEFINED
2183 # tag if you want to use a different macro definition that overrules the
2184 # definition found in the source code.
2185 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2189 # If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
2190 # remove all refrences to function-like macros that are alone on a line, have an
2191 # all uppercase name, and do not end with a semicolon. Such function macros are
2192 # typically used for boiler-plate code, and will confuse the parser if not
2194 # The default value is: YES.
2195 # This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
2197 SKIP_FUNCTION_MACROS = YES
2199 #---------------------------------------------------------------------------
2200 # Configuration options related to external references
2201 #---------------------------------------------------------------------------
2203 # The TAGFILES tag can be used to specify one or more tag files. For each tag
2204 # file the location of the external documentation should be added. The format of
2205 # a tag file without this location is as follows:
2206 # TAGFILES = file1 file2 ...
2207 # Adding location for the tag files is done as follows:
2208 # TAGFILES = file1=loc1 "file2 = loc2" ...
2209 # where loc1 and loc2 can be relative or absolute paths or URLs. See the
2210 # section "Linking to external documentation" for more information about the use
2212 # Note: Each tag file must have an unique name (where the name does NOT include
2213 # the path). If a tag file is not located in the directory in which doxygen is
2214 # run, you must also specify the path to the tagfile here.
2218 # When a file name is specified after GENERATE_TAGFILE, doxygen will create a
2219 # tag file that is based on the input files it reads. See section "Linking to
2220 # external documentation" for more information about the usage of tag files.
2224 # If the ALLEXTERNALS tag is set to YES all external class will be listed in the
2225 # class index. If set to NO only the inherited external classes will be listed.
2226 # The default value is: NO.
2230 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed in
2231 # the modules index. If set to NO, only the current project's groups will be
2233 # The default value is: YES.
2235 EXTERNAL_GROUPS = YES
2237 # If the EXTERNAL_PAGES tag is set to YES all external pages will be listed in
2238 # the related pages index. If set to NO, only the current project's pages will
2240 # The default value is: YES.
2242 EXTERNAL_PAGES = YES
2244 # The PERL_PATH should be the absolute path and name of the perl script
2245 # interpreter (i.e. the result of 'which perl').
2246 # The default file (with absolute path) is: /usr/bin/perl.
2248 PERL_PATH = /usr/bin/perl
2250 #---------------------------------------------------------------------------
2251 # Configuration options related to the dot tool
2252 #---------------------------------------------------------------------------
2254 # If the CLASS_DIAGRAMS tag is set to YES doxygen will generate a class diagram
2255 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2256 # NO turns the diagrams off. Note that this option also works with HAVE_DOT
2257 # disabled, but it is recommended to install and use dot, since it yields more
2259 # The default value is: YES.
2261 CLASS_DIAGRAMS = YES
2263 # You can define message sequence charts within doxygen comments using the \msc
2264 # command. Doxygen will then run the mscgen tool (see:
2265 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2266 # documentation. The MSCGEN_PATH tag allows you to specify the directory where
2267 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2268 # default search path.
2272 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2273 # then run dia to produce the diagram and insert it in the documentation. The
2274 # DIA_PATH tag allows you to specify the directory where the dia binary resides.
2275 # If left empty dia is assumed to be found in the default search path.
2279 # If set to YES, the inheritance and collaboration graphs will hide inheritance
2280 # and usage relations if the target is undocumented or is not a class.
2281 # The default value is: YES.
2283 HIDE_UNDOC_RELATIONS = YES
2285 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
2286 # available from the path. This tool is part of Graphviz (see:
2287 # http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent
2288 # Bell Labs. The other options in this section have no effect if this option is
2290 # The default value is: NO.
2294 # The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed
2295 # to run in parallel. When set to 0 doxygen will base this on the number of
2296 # processors available in the system. You can set it explicitly to a value
2297 # larger than 0 to get control over the balance between CPU load and processing
2299 # Minimum value: 0, maximum value: 32, default value: 0.
2300 # This tag requires that the tag HAVE_DOT is set to YES.
2304 # When you want a differently looking font n the dot files that doxygen
2305 # generates you can specify the font name using DOT_FONTNAME. You need to make
2306 # sure dot is able to find the font, which can be done by putting it in a
2307 # standard location or by setting the DOTFONTPATH environment variable or by
2308 # setting DOT_FONTPATH to the directory containing the font.
2309 # The default value is: Helvetica.
2310 # This tag requires that the tag HAVE_DOT is set to YES.
2314 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2316 # Minimum value: 4, maximum value: 24, default value: 10.
2317 # This tag requires that the tag HAVE_DOT is set to YES.
2321 # By default doxygen will tell dot to use the default font as specified with
2322 # DOT_FONTNAME. If you specify a different font using DOT_FONTNAME you can set
2323 # the path where dot can find it using this tag.
2324 # This tag requires that the tag HAVE_DOT is set to YES.
2328 # If the CLASS_GRAPH tag is set to YES then doxygen will generate a graph for
2329 # each documented class showing the direct and indirect inheritance relations.
2330 # Setting this tag to YES will force the CLASS_DIAGRAMS tag to NO.
2331 # The default value is: YES.
2332 # This tag requires that the tag HAVE_DOT is set to YES.
2336 # If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a
2337 # graph for each documented class showing the direct and indirect implementation
2338 # dependencies (inheritance, containment, and class references variables) of the
2339 # class with other documented classes.
2340 # The default value is: YES.
2341 # This tag requires that the tag HAVE_DOT is set to YES.
2343 COLLABORATION_GRAPH = YES
2345 # If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for
2346 # groups, showing the direct groups dependencies.
2347 # The default value is: YES.
2348 # This tag requires that the tag HAVE_DOT is set to YES.
2352 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
2353 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2355 # The default value is: NO.
2356 # This tag requires that the tag HAVE_DOT is set to YES.
2360 # If the UML_LOOK tag is enabled, the fields and methods are shown inside the
2361 # class node. If there are many fields or methods and many nodes the graph may
2362 # become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the
2363 # number of items for each type to make the size more manageable. Set this to 0
2364 # for no limit. Note that the threshold may be exceeded by 50% before the limit
2365 # is enforced. So when you set the threshold to 10, up to 15 fields may appear,
2366 # but if the number exceeds 15, the total amount of fields shown is limited to
2368 # Minimum value: 0, maximum value: 100, default value: 10.
2369 # This tag requires that the tag HAVE_DOT is set to YES.
2371 UML_LIMIT_NUM_FIELDS = 10
2373 # If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and
2374 # collaboration graphs will show the relations between templates and their
2376 # The default value is: NO.
2377 # This tag requires that the tag HAVE_DOT is set to YES.
2379 TEMPLATE_RELATIONS = NO
2381 # If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to
2382 # YES then doxygen will generate a graph for each documented file showing the
2383 # direct and indirect include dependencies of the file with other documented
2385 # The default value is: YES.
2386 # This tag requires that the tag HAVE_DOT is set to YES.
2390 # If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are
2391 # set to YES then doxygen will generate a graph for each documented file showing
2392 # the direct and indirect include dependencies of the file with other documented
2394 # The default value is: YES.
2395 # This tag requires that the tag HAVE_DOT is set to YES.
2397 INCLUDED_BY_GRAPH = YES
2399 # If the CALL_GRAPH tag is set to YES then doxygen will generate a call
2400 # dependency graph for every global function or class method.
2402 # Note that enabling this option will significantly increase the time of a run.
2403 # So in most cases it will be better to enable call graphs for selected
2404 # functions only using the \callgraph command.
2405 # The default value is: NO.
2406 # This tag requires that the tag HAVE_DOT is set to YES.
2410 # If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller
2411 # dependency graph for every global function or class method.
2413 # Note that enabling this option will significantly increase the time of a run.
2414 # So in most cases it will be better to enable caller graphs for selected
2415 # functions only using the \callergraph command.
2416 # The default value is: NO.
2417 # This tag requires that the tag HAVE_DOT is set to YES.
2421 # If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical
2422 # hierarchy of all classes instead of a textual one.
2423 # The default value is: YES.
2424 # This tag requires that the tag HAVE_DOT is set to YES.
2426 GRAPHICAL_HIERARCHY = YES
2428 # If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the
2429 # dependencies a directory has on other directories in a graphical way. The
2430 # dependency relations are determined by the #include relations between the
2431 # files in the directories.
2432 # The default value is: YES.
2433 # This tag requires that the tag HAVE_DOT is set to YES.
2435 DIRECTORY_GRAPH = YES
2437 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
2439 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2440 # to make the SVG files visible in IE 9+ (other browsers do not have this
2442 # Possible values are: png, jpg, gif and svg.
2443 # The default value is: png.
2444 # This tag requires that the tag HAVE_DOT is set to YES.
2446 DOT_IMAGE_FORMAT = png
2448 # If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to
2449 # enable generation of interactive SVG images that allow zooming and panning.
2451 # Note that this requires a modern browser other than Internet Explorer. Tested
2452 # and working are Firefox, Chrome, Safari, and Opera.
2453 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2454 # the SVG files visible. Older versions of IE do not have SVG support.
2455 # The default value is: NO.
2456 # This tag requires that the tag HAVE_DOT is set to YES.
2458 INTERACTIVE_SVG = NO
2460 # The DOT_PATH tag can be used to specify the path where the dot tool can be
2461 # found. If left blank, it is assumed the dot tool can be found in the path.
2462 # This tag requires that the tag HAVE_DOT is set to YES.
2466 # The DOTFILE_DIRS tag can be used to specify one or more directories that
2467 # contain dot files that are included in the documentation (see the \dotfile
2469 # This tag requires that the tag HAVE_DOT is set to YES.
2473 # The MSCFILE_DIRS tag can be used to specify one or more directories that
2474 # contain msc files that are included in the documentation (see the \mscfile
2479 # The DIAFILE_DIRS tag can be used to specify one or more directories that
2480 # contain dia files that are included in the documentation (see the \diafile
2485 # The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2486 # that will be shown in the graph. If the number of nodes in a graph becomes
2487 # larger than this value, doxygen will truncate the graph, which is visualized
2488 # by representing a node as a red box. Note that doxygen if the number of direct
2489 # children of the root node in a graph is already larger than
2490 # DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that
2491 # the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
2492 # Minimum value: 0, maximum value: 10000, default value: 50.
2493 # This tag requires that the tag HAVE_DOT is set to YES.
2495 DOT_GRAPH_MAX_NODES = 50
2497 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs
2498 # generated by dot. A depth value of 3 means that only nodes reachable from the
2499 # root by following a path via at most 3 edges will be shown. Nodes that lay
2500 # further from the root node will be omitted. Note that setting this option to 1
2501 # or 2 may greatly reduce the computation time needed for large code bases. Also
2502 # note that the size of a graph can be further restricted by
2503 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
2504 # Minimum value: 0, maximum value: 1000, default value: 0.
2505 # This tag requires that the tag HAVE_DOT is set to YES.
2507 MAX_DOT_GRAPH_DEPTH = 3
2509 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
2510 # background. This is disabled by default, because dot on Windows does not seem
2511 # to support this out of the box.
2513 # Warning: Depending on the platform used, enabling this option may lead to
2514 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2516 # The default value is: NO.
2517 # This tag requires that the tag HAVE_DOT is set to YES.
2519 DOT_TRANSPARENT = NO
2521 # Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
2522 # files in one run (i.e. multiple -o and -T options on the command line). This
2523 # makes dot run faster, but since only newer versions of dot (>1.8.10) support
2524 # this, this feature is disabled by default.
2525 # The default value is: NO.
2526 # This tag requires that the tag HAVE_DOT is set to YES.
2528 DOT_MULTI_TARGETS = YES
2530 # If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page
2531 # explaining the meaning of the various boxes and arrows in the dot generated
2533 # The default value is: YES.
2534 # This tag requires that the tag HAVE_DOT is set to YES.
2536 GENERATE_LEGEND = YES
2538 # If the DOT_CLEANUP tag is set to YES doxygen will remove the intermediate dot
2539 # files that are used to generate the various graphs.
2540 # The default value is: YES.
2541 # This tag requires that the tag HAVE_DOT is set to YES.
2545 #---------------------------------------------------------------------------
2546 # Configuration::additions related to the search engine
2547 #---------------------------------------------------------------------------
2549 # The SEARCHENGINE tag specifies whether or not a search engine should be
2550 # used. If set to NO the values of all tags below this one will be ignored.