1# Doxyfile 1.9.6 2 3# This file describes the settings to be used by the documentation system 4# doxygen (www.doxygen.org) for a project. 5# 6# All text after a double hash (##) is considered a comment and is placed in 7# front of the TAG it is preceding. 8# 9# All text after a single hash (#) is considered a comment and will be ignored. 10# The format is: 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 (\" \"). 15# 16# Note: 17# 18# Use doxygen to compare the used configuration file with the template 19# configuration file: 20# doxygen -x [configFile] 21# Use doxygen to compare the used configuration file with the template 22# configuration file without replacing the environment variables or CMake type 23# replacement variables: 24# doxygen -x_noenv [configFile] 25 26#--------------------------------------------------------------------------- 27# Project related configuration options 28#--------------------------------------------------------------------------- 29 30# This tag specifies the encoding used for all characters in the configuration 31# file that follow. The default is UTF-8 which is also the encoding used for all 32# text before the first occurrence of this tag. Doxygen uses libiconv (or the 33# iconv built into libc) for the transcoding. See 34# https://www.gnu.org/software/libiconv/ for the list of possible encodings. 35# The default value is: UTF-8. 36 37DOXYFILE_ENCODING = UTF-8 38 39# The PROJECT_NAME tag is a single word (or a sequence of words surrounded by 40# double-quotes, unless you are using Doxywizard) that should identify the 41# project for which the documentation is generated. This name is used in the 42# title of most generated pages and in a few other places. 43# The default value is: My Project. 44 45PROJECT_NAME = "Zephyr API Documentation" 46 47# The PROJECT_NUMBER tag can be used to enter a project or revision number. This 48# could be handy for archiving the generated documentation or if some version 49# control system is used. 50 51PROJECT_NUMBER = @ZEPHYR_VERSION@ 52 53# Using the PROJECT_BRIEF tag one can provide an optional one line description 54# for a project that appears at the top of each page and should give viewer a 55# quick idea about the purpose of the project. Keep the description short. 56 57PROJECT_BRIEF = "A Scalable Open Source RTOS" 58 59# With the PROJECT_LOGO tag one can specify a logo or an icon that is included 60# in the documentation. The maximum height of the logo should not exceed 55 61# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy 62# the logo to the output directory. 63 64PROJECT_LOGO = @ZEPHYR_BASE@/doc/_doxygen/logo.svg 65 66# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 67# into which the generated documentation will be written. If a relative path is 68# entered, it will be relative to the location where doxygen was started. If 69# left blank the current directory will be used. 70 71OUTPUT_DIRECTORY = @DOXY_OUT@ 72 73# If the CREATE_SUBDIRS tag is set to YES then doxygen will create up to 4096 74# sub-directories (in 2 levels) under the output directory of each output format 75# and will distribute the generated files over these directories. Enabling this 76# option can be useful when feeding doxygen a huge amount of source files, where 77# putting all generated files in the same directory would otherwise causes 78# performance problems for the file system. Adapt CREATE_SUBDIRS_LEVEL to 79# control the number of sub-directories. 80# The default value is: NO. 81 82CREATE_SUBDIRS = NO 83 84# Controls the number of sub-directories that will be created when 85# CREATE_SUBDIRS tag is set to YES. Level 0 represents 16 directories, and every 86# level increment doubles the number of directories, resulting in 4096 87# directories at level 8 which is the default and also the maximum value. The 88# sub-directories are organized in 2 levels, the first level always has a fixed 89# number of 16 directories. 90# Minimum value: 0, maximum value: 8, default value: 8. 91# This tag requires that the tag CREATE_SUBDIRS is set to YES. 92 93CREATE_SUBDIRS_LEVEL = 8 94 95# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII 96# characters to appear in the names of generated files. If set to NO, non-ASCII 97# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode 98# U+3044. 99# The default value is: NO. 100 101ALLOW_UNICODE_NAMES = NO 102 103# The OUTPUT_LANGUAGE tag is used to specify the language in which all 104# documentation generated by doxygen is written. Doxygen will use this 105# information to generate all constant output in the proper language. 106# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Bulgarian, 107# Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, English 108# (United States), Esperanto, Farsi (Persian), Finnish, French, German, Greek, 109# Hindi, Hungarian, Indonesian, Italian, Japanese, Japanese-en (Japanese with 110# English messages), Korean, Korean-en (Korean with English messages), Latvian, 111# Lithuanian, Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, 112# Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, 113# Swedish, Turkish, Ukrainian and Vietnamese. 114# The default value is: English. 115 116OUTPUT_LANGUAGE = English 117 118# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member 119# descriptions after the members that are listed in the file and class 120# documentation (similar to Javadoc). Set to NO to disable this. 121# The default value is: YES. 122 123BRIEF_MEMBER_DESC = YES 124 125# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief 126# description of a member or function before the detailed description 127# 128# Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 129# brief descriptions will be completely suppressed. 130# The default value is: YES. 131 132REPEAT_BRIEF = YES 133 134# This tag implements a quasi-intelligent brief description abbreviator that is 135# used to form the text in various listings. Each string in this list, if found 136# as the leading text of the brief description, will be stripped from the text 137# and the result, after processing the whole list, is used as the annotated 138# text. Otherwise, the brief description is used as-is. If left blank, the 139# following values are used ($name is automatically replaced with the name of 140# the entity):The $name class, The $name widget, The $name file, is, provides, 141# specifies, contains, represents, a, an and the. 142 143ABBREVIATE_BRIEF = YES 144 145# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 146# doxygen will generate a detailed section even if there is only a brief 147# description. 148# The default value is: NO. 149 150ALWAYS_DETAILED_SEC = YES 151 152# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 153# inherited members of a class in the documentation of that class as if those 154# members were ordinary class members. Constructors, destructors and assignment 155# operators of the base classes will not be shown. 156# The default value is: NO. 157 158INLINE_INHERITED_MEMB = YES 159 160# If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path 161# before files name in the file list and in the header files. If set to NO the 162# shortest path that makes the file name unique will be used 163# The default value is: YES. 164 165FULL_PATH_NAMES = YES 166 167# The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path. 168# Stripping is only done if one of the specified strings matches the left-hand 169# part of the path. The tag can be used to show relative paths in the file list. 170# If left blank the directory from which doxygen is run is used as the path to 171# strip. 172# 173# Note that you can specify absolute paths here, but also relative paths, which 174# will be relative from the directory where doxygen is started. 175# This tag requires that the tag FULL_PATH_NAMES is set to YES. 176 177STRIP_FROM_PATH = @ZEPHYR_BASE@/include 178 179# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the 180# path mentioned in the documentation of a class, which tells the reader which 181# header file to include in order to use a class. If left blank only the name of 182# the header file containing the class definition is used. Otherwise one should 183# specify the list of include paths that are normally passed to the compiler 184# using the -I flag. 185 186STRIP_FROM_INC_PATH = 187 188# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but 189# less readable) file names. This can be useful is your file systems doesn't 190# support long names like on DOS, Mac, or CD-ROM. 191# The default value is: NO. 192 193SHORT_NAMES = NO 194 195# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the 196# first line (until the first dot) of a Javadoc-style comment as the brief 197# description. If set to NO, the Javadoc-style will behave just like regular Qt- 198# style comments (thus requiring an explicit @brief command for a brief 199# description.) 200# The default value is: NO. 201 202JAVADOC_AUTOBRIEF = YES 203 204# If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line 205# such as 206# /*************** 207# as being the beginning of a Javadoc-style comment "banner". If set to NO, the 208# Javadoc-style will behave just like regular comments and it will not be 209# interpreted by doxygen. 210# The default value is: NO. 211 212JAVADOC_BANNER = NO 213 214# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first 215# line (until the first dot) of a Qt-style comment as the brief description. If 216# set to NO, the Qt-style will behave just like regular Qt-style comments (thus 217# requiring an explicit \brief command for a brief description.) 218# The default value is: NO. 219 220QT_AUTOBRIEF = YES 221 222# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a 223# multi-line C++ special comment block (i.e. a block of //! or /// comments) as 224# a brief description. This used to be the default behavior. The new default is 225# to treat a multi-line C++ comment block as a detailed description. Set this 226# tag to YES if you prefer the old behavior instead. 227# 228# Note that setting this tag to YES also means that rational rose comments are 229# not recognized any more. 230# The default value is: NO. 231 232MULTILINE_CPP_IS_BRIEF = NO 233 234# By default Python docstrings are displayed as preformatted text and doxygen's 235# special commands cannot be used. By setting PYTHON_DOCSTRING to NO the 236# doxygen's special commands can be used and the contents of the docstring 237# documentation blocks is shown as doxygen documentation. 238# The default value is: YES. 239 240PYTHON_DOCSTRING = YES 241 242# If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the 243# documentation from any documented member that it re-implements. 244# The default value is: YES. 245 246INHERIT_DOCS = YES 247 248# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new 249# page for each member. If set to NO, the documentation of a member will be part 250# of the file/class/namespace that contains it. 251# The default value is: NO. 252 253SEPARATE_MEMBER_PAGES = NO 254 255# The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen 256# uses this value to replace tabs by spaces in code fragments. 257# Minimum value: 1, maximum value: 16, default value: 4. 258 259TAB_SIZE = 8 260 261# This tag can be used to specify a number of aliases that act as commands in 262# the documentation. An alias has the form: 263# name=value 264# For example adding 265# "sideeffect=@par Side Effects:^^" 266# will allow you to put the command \sideeffect (or @sideeffect) in the 267# documentation, which will result in a user-defined paragraph with heading 268# "Side Effects:". Note that you cannot put \n's in the value part of an alias 269# to insert newlines (in the resulting output). You can put ^^ in the value part 270# of an alias to insert a newline as if a physical newline was in the original 271# file. When you need a literal { or } or , in the value part of an alias you 272# have to escape them by means of a backslash (\), this can lead to conflicts 273# with the commands \{ and \} for these it is advised to use the version @{ and 274# @} or use a double escape (\\{ and \\}) 275 276ALIASES = "rst=\verbatim embed:rst:leading-asterisk" \ 277 endrst=\endverbatim \ 278 "kconfig{1}=\htmlonly <code>\1</code> \endhtmlonly \xmlonly <verbatim>embed:rst:inline :kconfig:option:`\1`</verbatim> \endxmlonly" \ 279 "req{1}=\ref ZEPH_\1 \"ZEPH-\1\"" \ 280 "satisfy{1}=\xrefitem satisfy \"Satisfies requirement\" \"Requirement Implementation\" \1" \ 281 "verify{1}=\xrefitem verify \"Verifies requirement\" \"Requirement Verification\" \1" \ 282 "funcprops=\par \"Function properties (list may not be complete)\"" \ 283 "reschedule=\htmlonly reschedule \endhtmlonly \xmlonly <verbatim>embed:rst:inline :ref:`api_term_reschedule`</verbatim> \endxmlonly" \ 284 "sleep=\htmlonly sleep \endhtmlonly \xmlonly <verbatim>embed:rst:inline :ref:`api_term_sleep`</verbatim> \endxmlonly" \ 285 "no_wait=\htmlonly no-wait \endhtmlonly \xmlonly <verbatim>embed:rst:inline :ref:`api_term_no-wait`</verbatim> \endxmlonly" \ 286 "isr_ok=\htmlonly isr-ok \endhtmlonly \xmlonly <verbatim>embed:rst:inline :ref:`api_term_isr-ok`</verbatim> \endxmlonly" \ 287 "pre_kernel_ok=\htmlonly pre-kernel-ok \endhtmlonly \xmlonly <verbatim>embed:rst:inline :ref:`api_term_pre-kernel-ok`</verbatim> \endxmlonly" \ 288 "async=\htmlonly async \endhtmlonly \xmlonly <verbatim>embed:rst:inline :ref:`api_term_async`</verbatim> \endxmlonly" \ 289 "atomic_api=As for all atomic APIs, includes a full/sequentially-consistent memory barrier (where applicable)." \ 290 "supervisor=\htmlonly supervisor \endhtmlonly \xmlonly <verbatim>embed:rst:inline :ref:`api_term_supervisor`</verbatim> \endxmlonly" 291 292# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources 293# only. Doxygen will then generate output that is more tailored for C. For 294# instance, some of the names that are used will be different. The list of all 295# members will be omitted, etc. 296# The default value is: NO. 297 298OPTIMIZE_OUTPUT_FOR_C = YES 299 300# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or 301# Python sources only. Doxygen will then generate output that is more tailored 302# for that language. For instance, namespaces will be presented as packages, 303# qualified scopes will look different, etc. 304# The default value is: NO. 305 306OPTIMIZE_OUTPUT_JAVA = NO 307 308# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 309# sources. Doxygen will then generate output that is tailored for Fortran. 310# The default value is: NO. 311 312OPTIMIZE_FOR_FORTRAN = NO 313 314# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 315# sources. Doxygen will then generate output that is tailored for VHDL. 316# The default value is: NO. 317 318OPTIMIZE_OUTPUT_VHDL = NO 319 320# Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice 321# sources only. Doxygen will then generate output that is more tailored for that 322# language. For instance, namespaces will be presented as modules, types will be 323# separated into more groups, etc. 324# The default value is: NO. 325 326OPTIMIZE_OUTPUT_SLICE = NO 327 328# Doxygen selects the parser to use depending on the extension of the files it 329# parses. With this tag you can assign which parser to use for a given 330# extension. Doxygen has a built-in mapping, but you can override or extend it 331# using this tag. The format is ext=language, where ext is a file extension, and 332# language is one of the parsers supported by doxygen: IDL, Java, JavaScript, 333# Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice, 334# VHDL, Fortran (fixed format Fortran: FortranFixed, free formatted Fortran: 335# FortranFree, unknown formatted Fortran: Fortran. In the later case the parser 336# tries to guess whether the code is fixed or free formatted code, this is the 337# default for Fortran type files). For instance to make doxygen treat .inc files 338# as Fortran files (default is PHP), and .f files as C (default is Fortran), 339# use: inc=Fortran f=C. 340# 341# Note: For files without extension you can use no_extension as a placeholder. 342# 343# Note that for custom extensions you also need to set FILE_PATTERNS otherwise 344# the files are not read by doxygen. When specifying no_extension you should add 345# * to the FILE_PATTERNS. 346# 347# Note see also the list of default file extension mappings. 348 349EXTENSION_MAPPING = 350 351# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments 352# according to the Markdown format, which allows for more readable 353# documentation. See https://daringfireball.net/projects/markdown/ for details. 354# The output of markdown processing is further processed by doxygen, so you can 355# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in 356# case of backward compatibilities issues. 357# The default value is: YES. 358 359MARKDOWN_SUPPORT = YES 360 361# When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up 362# to that level are automatically included in the table of contents, even if 363# they do not have an id attribute. 364# Note: This feature currently applies only to Markdown headings. 365# Minimum value: 0, maximum value: 99, default value: 5. 366# This tag requires that the tag MARKDOWN_SUPPORT is set to YES. 367 368TOC_INCLUDE_HEADINGS = 5 369 370# When enabled doxygen tries to link words that correspond to documented 371# classes, or namespaces to their corresponding documentation. Such a link can 372# be prevented in individual cases by putting a % sign in front of the word or 373# globally by setting AUTOLINK_SUPPORT to NO. 374# The default value is: YES. 375 376AUTOLINK_SUPPORT = YES 377 378# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 379# to include (a tag file for) the STL sources as input, then you should set this 380# tag to YES in order to let doxygen match functions declarations and 381# definitions whose arguments contain STL classes (e.g. func(std::string); 382# versus func(std::string) {}). This also make the inheritance and collaboration 383# diagrams that involve STL classes more complete and accurate. 384# The default value is: NO. 385 386BUILTIN_STL_SUPPORT = NO 387 388# If you use Microsoft's C++/CLI language, you should set this option to YES to 389# enable parsing support. 390# The default value is: NO. 391 392CPP_CLI_SUPPORT = YES 393 394# Set the SIP_SUPPORT tag to YES if your project consists of sip (see: 395# https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen 396# will parse them like normal C++ but will assume all classes use public instead 397# of private inheritance when no explicit protection keyword is present. 398# The default value is: NO. 399 400SIP_SUPPORT = NO 401 402# For Microsoft's IDL there are propget and propput attributes to indicate 403# getter and setter methods for a property. Setting this option to YES will make 404# doxygen to replace the get and set methods by a property in the documentation. 405# This will only work if the methods are indeed getting or setting a simple 406# type. If this is not the case, or you want to show the methods anyway, you 407# should set this option to NO. 408# The default value is: YES. 409 410IDL_PROPERTY_SUPPORT = YES 411 412# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 413# tag is set to YES then doxygen will reuse the documentation of the first 414# member in the group (if any) for the other members of the group. By default 415# all members of a group must be documented explicitly. 416# The default value is: NO. 417 418DISTRIBUTE_GROUP_DOC = NO 419 420# If one adds a struct or class to a group and this option is enabled, then also 421# any nested class or struct is added to the same group. By default this option 422# is disabled and one has to add nested compounds explicitly via \ingroup. 423# The default value is: NO. 424 425GROUP_NESTED_COMPOUNDS = NO 426 427# Set the SUBGROUPING tag to YES to allow class member groups of the same type 428# (for instance a group of public functions) to be put as a subgroup of that 429# type (e.g. under the Public Functions section). Set it to NO to prevent 430# subgrouping. Alternatively, this can be done per class using the 431# \nosubgrouping command. 432# The default value is: YES. 433 434SUBGROUPING = YES 435 436# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions 437# are shown inside the group in which they are included (e.g. using \ingroup) 438# instead of on a separate page (for HTML and Man pages) or section (for LaTeX 439# and RTF). 440# 441# Note that this feature does not work in combination with 442# SEPARATE_MEMBER_PAGES. 443# The default value is: NO. 444 445INLINE_GROUPED_CLASSES = NO 446 447# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions 448# with only public data fields or simple typedef fields will be shown inline in 449# the documentation of the scope in which they are defined (i.e. file, 450# namespace, or group documentation), provided this scope is documented. If set 451# to NO, structs, classes, and unions are shown on a separate page (for HTML and 452# Man pages) or section (for LaTeX and RTF). 453# The default value is: NO. 454 455INLINE_SIMPLE_STRUCTS = NO 456 457# When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or 458# enum is documented as struct, union, or enum with the name of the typedef. So 459# typedef struct TypeS {} TypeT, will appear in the documentation as a struct 460# with name TypeT. When disabled the typedef will appear as a member of a file, 461# namespace, or class. And the struct will be named TypeS. This can typically be 462# useful for C code in case the coding convention dictates that all compound 463# types are typedef'ed and only the typedef is referenced, never the tag name. 464# The default value is: NO. 465 466TYPEDEF_HIDES_STRUCT = NO 467 468# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This 469# cache is used to resolve symbols given their name and scope. Since this can be 470# an expensive process and often the same symbol appears multiple times in the 471# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small 472# doxygen will become slower. If the cache is too large, memory is wasted. The 473# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range 474# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536 475# symbols. At the end of a run doxygen will report the cache usage and suggest 476# the optimal cache size from a speed point of view. 477# Minimum value: 0, maximum value: 9, default value: 0. 478 479LOOKUP_CACHE_SIZE = 9 480 481# The NUM_PROC_THREADS specifies the number of threads doxygen is allowed to use 482# during processing. When set to 0 doxygen will based this on the number of 483# cores available in the system. You can set it explicitly to a value larger 484# than 0 to get more control over the balance between CPU load and processing 485# speed. At this moment only the input processing can be done using multiple 486# threads. Since this is still an experimental feature the default is set to 1, 487# which effectively disables parallel processing. Please report any issues you 488# encounter. Generating dot graphs in parallel is controlled by the 489# DOT_NUM_THREADS setting. 490# Minimum value: 0, maximum value: 32, default value: 1. 491 492NUM_PROC_THREADS = 1 493 494#--------------------------------------------------------------------------- 495# Build related configuration options 496#--------------------------------------------------------------------------- 497 498# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in 499# documentation are documented, even if no documentation was available. Private 500# class members and static file members will be hidden unless the 501# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES. 502# Note: This will also disable the warnings about undocumented members that are 503# normally produced when WARNINGS is set to YES. 504# The default value is: NO. 505 506EXTRACT_ALL = YES 507 508# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will 509# be included in the documentation. 510# The default value is: NO. 511 512EXTRACT_PRIVATE = NO 513 514# If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual 515# methods of a class will be included in the documentation. 516# The default value is: NO. 517 518EXTRACT_PRIV_VIRTUAL = NO 519 520# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal 521# scope will be included in the documentation. 522# The default value is: NO. 523 524EXTRACT_PACKAGE = YES 525 526# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be 527# included in the documentation. 528# The default value is: NO. 529 530EXTRACT_STATIC = YES 531 532# If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined 533# locally in source files will be included in the documentation. If set to NO, 534# only classes defined in header files are included. Does not have any effect 535# for Java sources. 536# The default value is: YES. 537 538EXTRACT_LOCAL_CLASSES = YES 539 540# This flag is only useful for Objective-C code. If set to YES, local methods, 541# which are defined in the implementation section but not in the interface are 542# included in the documentation. If set to NO, only methods in the interface are 543# included. 544# The default value is: NO. 545 546EXTRACT_LOCAL_METHODS = YES 547 548# If this flag is set to YES, the members of anonymous namespaces will be 549# extracted and appear in the documentation as a namespace called 550# 'anonymous_namespace{file}', where file will be replaced with the base name of 551# the file that contains the anonymous namespace. By default anonymous namespace 552# are hidden. 553# The default value is: NO. 554 555EXTRACT_ANON_NSPACES = NO 556 557# If this flag is set to YES, the name of an unnamed parameter in a declaration 558# will be determined by the corresponding definition. By default unnamed 559# parameters remain unnamed in the output. 560# The default value is: YES. 561 562RESOLVE_UNNAMED_PARAMS = YES 563 564# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all 565# undocumented members inside documented classes or files. If set to NO these 566# members will be included in the various overviews, but no documentation 567# section is generated. This option has no effect if EXTRACT_ALL is enabled. 568# The default value is: NO. 569 570HIDE_UNDOC_MEMBERS = NO 571 572# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all 573# undocumented classes that are normally visible in the class hierarchy. If set 574# to NO, these classes will be included in the various overviews. This option 575# will also hide undocumented C++ concepts if enabled. This option has no effect 576# if EXTRACT_ALL is enabled. 577# The default value is: NO. 578 579HIDE_UNDOC_CLASSES = NO 580 581# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend 582# declarations. If set to NO, these declarations will be included in the 583# documentation. 584# The default value is: NO. 585 586HIDE_FRIEND_COMPOUNDS = NO 587 588# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any 589# documentation blocks found inside the body of a function. If set to NO, these 590# blocks will be appended to the function's detailed documentation block. 591# The default value is: NO. 592 593HIDE_IN_BODY_DOCS = NO 594 595# The INTERNAL_DOCS tag determines if documentation that is typed after a 596# \internal command is included. If the tag is set to NO then the documentation 597# will be excluded. Set it to YES to include the internal documentation. 598# The default value is: NO. 599 600INTERNAL_DOCS = NO 601 602# With the correct setting of option CASE_SENSE_NAMES doxygen will better be 603# able to match the capabilities of the underlying filesystem. In case the 604# filesystem is case sensitive (i.e. it supports files in the same directory 605# whose names only differ in casing), the option must be set to YES to properly 606# deal with such files in case they appear in the input. For filesystems that 607# are not case sensitive the option should be set to NO to properly deal with 608# output files written for symbols that only differ in casing, such as for two 609# classes, one named CLASS and the other named Class, and to also support 610# references to files without having to specify the exact matching casing. On 611# Windows (including Cygwin) and MacOS, users should typically set this option 612# to NO, whereas on Linux or other Unix flavors it should typically be set to 613# YES. 614# Possible values are: SYSTEM, NO and YES. 615# The default value is: SYSTEM. 616 617CASE_SENSE_NAMES = YES 618 619# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with 620# their full class and namespace scopes in the documentation. If set to YES, the 621# scope will be hidden. 622# The default value is: NO. 623 624HIDE_SCOPE_NAMES = NO 625 626# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will 627# append additional text to a page's title, such as Class Reference. If set to 628# YES the compound reference will be hidden. 629# The default value is: NO. 630 631HIDE_COMPOUND_REFERENCE= NO 632 633# If the SHOW_HEADERFILE tag is set to YES then the documentation for a class 634# will show which file needs to be included to use the class. 635# The default value is: YES. 636 637SHOW_HEADERFILE = YES 638 639# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of 640# the files that are included by a file in the documentation of that file. 641# The default value is: YES. 642 643SHOW_INCLUDE_FILES = YES 644 645# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each 646# grouped member an include statement to the documentation, telling the reader 647# which file to include in order to use the member. 648# The default value is: NO. 649 650SHOW_GROUPED_MEMB_INC = YES 651 652# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include 653# files with double quotes in the documentation rather than with sharp brackets. 654# The default value is: NO. 655 656FORCE_LOCAL_INCLUDES = NO 657 658# If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the 659# documentation for inline members. 660# The default value is: YES. 661 662INLINE_INFO = YES 663 664# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the 665# (detailed) documentation of file and class members alphabetically by member 666# name. If set to NO, the members will appear in declaration order. 667# The default value is: YES. 668 669SORT_MEMBER_DOCS = YES 670 671# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief 672# descriptions of file, namespace and class members alphabetically by member 673# name. If set to NO, the members will appear in declaration order. Note that 674# this will also influence the order of the classes in the class list. 675# The default value is: NO. 676 677SORT_BRIEF_DOCS = NO 678 679# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the 680# (brief and detailed) documentation of class members so that constructors and 681# destructors are listed first. If set to NO the constructors will appear in the 682# respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS. 683# Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief 684# member documentation. 685# Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting 686# detailed member documentation. 687# The default value is: NO. 688 689SORT_MEMBERS_CTORS_1ST = NO 690 691# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy 692# of group names into alphabetical order. If set to NO the group names will 693# appear in their defined order. 694# The default value is: NO. 695 696SORT_GROUP_NAMES = YES 697 698# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by 699# fully-qualified names, including namespaces. If set to NO, the class list will 700# be sorted only by class name, not including the namespace part. 701# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 702# Note: This option applies only to the class list, not to the alphabetical 703# list. 704# The default value is: NO. 705 706SORT_BY_SCOPE_NAME = YES 707 708# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper 709# type resolution of all parameters of a function it will reject a match between 710# the prototype and the implementation of a member function even if there is 711# only one candidate or it is obvious which candidate to choose by doing a 712# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still 713# accept a match between prototype and implementation in such cases. 714# The default value is: NO. 715 716STRICT_PROTO_MATCHING = YES 717 718# The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo 719# list. This list is created by putting \todo commands in the documentation. 720# The default value is: YES. 721 722GENERATE_TODOLIST = NO 723 724# The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test 725# list. This list is created by putting \test commands in the documentation. 726# The default value is: YES. 727 728GENERATE_TESTLIST = NO 729 730# The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug 731# list. This list is created by putting \bug commands in the documentation. 732# The default value is: YES. 733 734GENERATE_BUGLIST = NO 735 736# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO) 737# the deprecated list. This list is created by putting \deprecated commands in 738# the documentation. 739# The default value is: YES. 740 741GENERATE_DEPRECATEDLIST= YES 742 743# The ENABLED_SECTIONS tag can be used to enable conditional documentation 744# sections, marked by \if <section_label> ... \endif and \cond <section_label> 745# ... \endcond blocks. 746 747ENABLED_SECTIONS = YES 748 749# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the 750# initial value of a variable or macro / define can have for it to appear in the 751# documentation. If the initializer consists of more lines than specified here 752# it will be hidden. Use a value of 0 to hide initializers completely. The 753# appearance of the value of individual variables and macros / defines can be 754# controlled using \showinitializer or \hideinitializer command in the 755# documentation regardless of this setting. 756# Minimum value: 0, maximum value: 10000, default value: 30. 757 758MAX_INITIALIZER_LINES = 300 759 760# Set the SHOW_USED_FILES tag to NO to disable the list of files generated at 761# the bottom of the documentation of classes and structs. If set to YES, the 762# list will mention the files that were used to generate the documentation. 763# The default value is: YES. 764 765SHOW_USED_FILES = YES 766 767# Set the SHOW_FILES tag to NO to disable the generation of the Files page. This 768# will remove the Files entry from the Quick Index and from the Folder Tree View 769# (if specified). 770# The default value is: YES. 771 772SHOW_FILES = YES 773 774# Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces 775# page. This will remove the Namespaces entry from the Quick Index and from the 776# Folder Tree View (if specified). 777# The default value is: YES. 778 779SHOW_NAMESPACES = YES 780 781# The FILE_VERSION_FILTER tag can be used to specify a program or script that 782# doxygen should invoke to get the current version for each file (typically from 783# the version control system). Doxygen will invoke the program by executing (via 784# popen()) the command command input-file, where command is the value of the 785# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided 786# by doxygen. Whatever the program writes to standard output is used as the file 787# version. For an example see the documentation. 788 789FILE_VERSION_FILTER = 790 791# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed 792# by doxygen. The layout file controls the global structure of the generated 793# output files in an output format independent way. To create the layout file 794# that represents doxygen's defaults, run doxygen with the -l option. You can 795# optionally specify a file name after the option, if omitted DoxygenLayout.xml 796# will be used as the name of the layout file. See also section "Changing the 797# layout of pages" for information. 798# 799# Note that if you run doxygen from a directory containing a file called 800# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE 801# tag is left empty. 802 803LAYOUT_FILE = 804 805# The CITE_BIB_FILES tag can be used to specify one or more bib files containing 806# the reference definitions. This must be a list of .bib files. The .bib 807# extension is automatically appended if omitted. This requires the bibtex tool 808# to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info. 809# For LaTeX the style of the bibliography can be controlled using 810# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the 811# search path. See also \cite for info how to create references. 812 813CITE_BIB_FILES = 814 815#--------------------------------------------------------------------------- 816# Configuration options related to warning and progress messages 817#--------------------------------------------------------------------------- 818 819# The QUIET tag can be used to turn on/off the messages that are generated to 820# standard output by doxygen. If QUIET is set to YES this implies that the 821# messages are off. 822# The default value is: NO. 823 824QUIET = YES 825 826# The WARNINGS tag can be used to turn on/off the warning messages that are 827# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES 828# this implies that the warnings are on. 829# 830# Tip: Turn warnings on while writing the documentation. 831# The default value is: YES. 832 833WARNINGS = YES 834 835# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate 836# warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag 837# will automatically be disabled. 838# The default value is: YES. 839 840WARN_IF_UNDOCUMENTED = YES 841 842# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for 843# potential errors in the documentation, such as documenting some parameters in 844# a documented function twice, or documenting parameters that don't exist or 845# using markup commands wrongly. 846# The default value is: YES. 847 848WARN_IF_DOC_ERROR = YES 849 850# If WARN_IF_INCOMPLETE_DOC is set to YES, doxygen will warn about incomplete 851# function parameter documentation. If set to NO, doxygen will accept that some 852# parameters have no documentation without warning. 853# The default value is: YES. 854 855WARN_IF_INCOMPLETE_DOC = YES 856 857# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that 858# are documented, but have no documentation for their parameters or return 859# value. If set to NO, doxygen will only warn about wrong parameter 860# documentation, but not about the absence of documentation. If EXTRACT_ALL is 861# set to YES then this flag will automatically be disabled. See also 862# WARN_IF_INCOMPLETE_DOC 863# The default value is: NO. 864 865WARN_NO_PARAMDOC = NO 866 867# If WARN_IF_UNDOC_ENUM_VAL option is set to YES, doxygen will warn about 868# undocumented enumeration values. If set to NO, doxygen will accept 869# undocumented enumeration values. If EXTRACT_ALL is set to YES then this flag 870# will automatically be disabled. 871# The default value is: NO. 872 873WARN_IF_UNDOC_ENUM_VAL = NO 874 875# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when 876# a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS 877# then doxygen will continue running as if WARN_AS_ERROR tag is set to NO, but 878# at the end of the doxygen process doxygen will return with a non-zero status. 879# Possible values are: NO, YES and FAIL_ON_WARNINGS. 880# The default value is: NO. 881 882WARN_AS_ERROR = NO 883 884# The WARN_FORMAT tag determines the format of the warning messages that doxygen 885# can produce. The string should contain the $file, $line, and $text tags, which 886# will be replaced by the file and line number from which the warning originated 887# and the warning text. Optionally the format may contain $version, which will 888# be replaced by the version of the file (if it could be obtained via 889# FILE_VERSION_FILTER) 890# See also: WARN_LINE_FORMAT 891# The default value is: $file:$line: $text. 892 893WARN_FORMAT = "$file:$line: $text" 894 895# In the $text part of the WARN_FORMAT command it is possible that a reference 896# to a more specific place is given. To make it easier to jump to this place 897# (outside of doxygen) the user can define a custom "cut" / "paste" string. 898# Example: 899# WARN_LINE_FORMAT = "'vi $file +$line'" 900# See also: WARN_FORMAT 901# The default value is: at line $line of file $file. 902 903WARN_LINE_FORMAT = "at line $line of file $file" 904 905# The WARN_LOGFILE tag can be used to specify a file to which warning and error 906# messages should be written. If left blank the output is written to standard 907# error (stderr). In case the file specified cannot be opened for writing the 908# warning and error messages are written to standard error. When as file - is 909# specified the warning and error messages are written to standard output 910# (stdout). 911 912WARN_LOGFILE = 913 914#--------------------------------------------------------------------------- 915# Configuration options related to the input files 916#--------------------------------------------------------------------------- 917 918# The INPUT tag is used to specify the files and/or directories that contain 919# documented source files. You may enter file names like myfile.cpp or 920# directories like /usr/src/myproject. Separate the files or directories with 921# spaces. See also FILE_PATTERNS and EXTENSION_MAPPING 922# Note: If this tag is empty the current directory is searched. 923 924INPUT = @ZEPHYR_BASE@/doc/_doxygen/mainpage.md \ 925 @ZEPHYR_BASE@/doc/_doxygen/groups.dox \ 926 @ZEPHYR_BASE@/kernel/include/kernel_arch_interface.h \ 927 @ZEPHYR_BASE@/include/zephyr/arch/cache.h \ 928 @ZEPHYR_BASE@/include/zephyr/sys/atomic.h \ 929 @ZEPHYR_BASE@/include/ \ 930 @ZEPHYR_BASE@/lib/libc/minimal/include/ \ 931 @ZEPHYR_BASE@/subsys/testsuite/include/ \ 932 @ZEPHYR_BASE@/subsys/testsuite/ztest/include/ 933 934# This tag can be used to specify the character encoding of the source files 935# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses 936# libiconv (or the iconv built into libc) for the transcoding. See the libiconv 937# documentation (see: 938# https://www.gnu.org/software/libiconv/) for the list of possible encodings. 939# See also: INPUT_FILE_ENCODING 940# The default value is: UTF-8. 941 942INPUT_ENCODING = UTF-8 943 944# This tag can be used to specify the character encoding of the source files 945# that doxygen parses The INPUT_FILE_ENCODING tag can be used to specify 946# character encoding on a per file pattern basis. Doxygen will compare the file 947# name with each pattern and apply the encoding instead of the default 948# INPUT_ENCODING) if there is a match. The character encodings are a list of the 949# form: pattern=encoding (like *.php=ISO-8859-1). See cfg_input_encoding 950# "INPUT_ENCODING" for further information on supported encodings. 951 952INPUT_FILE_ENCODING = 953 954# If the value of the INPUT tag contains directories, you can use the 955# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and 956# *.h) to filter out the source-files in the directories. 957# 958# Note that for custom extensions or not directly supported extensions you also 959# need to set EXTENSION_MAPPING for the extension otherwise the files are not 960# read by doxygen. 961# 962# Note the list of default checked file patterns might differ from the list of 963# default file extension mappings. 964# 965# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp, 966# *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, 967# *.hh, *.hxx, *.hpp, *.h++, *.l, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, 968# *.inc, *.m, *.markdown, *.md, *.mm, *.dox (to be provided as doxygen C 969# comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, *.f18, *.f, *.for, *.vhd, 970# *.vhdl, *.ucf, *.qsf and *.ice. 971 972FILE_PATTERNS = *.c \ 973 *.h \ 974 *.S \ 975 *.md 976 977# The RECURSIVE tag can be used to specify whether or not subdirectories should 978# be searched for input files as well. 979# The default value is: NO. 980 981RECURSIVE = YES 982 983# The EXCLUDE tag can be used to specify files and/or directories that should be 984# excluded from the INPUT source files. This way you can easily exclude a 985# subdirectory from a directory tree whose root is specified with the INPUT tag. 986# 987# Note that relative paths are relative to the directory from which doxygen is 988# run. 989 990EXCLUDE = @ZEPHYR_BASE@/include/zephyr/portability/cmsis_os.h \ 991 @ZEPHYR_BASE@/include/zephyr/portability/cmsis_os2.h 992 993# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or 994# directories that are symbolic links (a Unix file system feature) are excluded 995# from the input. 996# The default value is: NO. 997 998EXCLUDE_SYMLINKS = NO 999 1000# If the value of the INPUT tag contains directories, you can use the 1001# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 1002# certain files from those directories. 1003# 1004# Note that the wildcards are matched against the file with absolute path, so to 1005# exclude all test directories for example use the pattern */test/* 1006 1007EXCLUDE_PATTERNS = 1008 1009# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 1010# (namespaces, classes, functions, etc.) that should be excluded from the 1011# output. The symbol name can be a fully qualified name, a word, or if the 1012# wildcard * is used, a substring. Examples: ANamespace, AClass, 1013# ANamespace::AClass, ANamespace::*Test 1014# 1015# Note that the wildcards are matched against the file with absolute path, so to 1016# exclude all test directories use the pattern */test/* 1017 1018EXCLUDE_SYMBOLS = _* \ 1019 *.__unnamed__ \ 1020 z_* \ 1021 Z_* 1022 1023# The EXAMPLE_PATH tag can be used to specify one or more files or directories 1024# that contain example code fragments that are included (see the \include 1025# command). 1026 1027EXAMPLE_PATH = 1028 1029# If the value of the EXAMPLE_PATH tag contains directories, you can use the 1030# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and 1031# *.h) to filter out the source-files in the directories. If left blank all 1032# files are included. 1033 1034EXAMPLE_PATTERNS = 1035 1036# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 1037# searched for input files to be used with the \include or \dontinclude commands 1038# irrespective of the value of the RECURSIVE tag. 1039# The default value is: NO. 1040 1041EXAMPLE_RECURSIVE = YES 1042 1043# The IMAGE_PATH tag can be used to specify one or more files or directories 1044# that contain images that are to be included in the documentation (see the 1045# \image command). 1046 1047IMAGE_PATH = 1048 1049# The INPUT_FILTER tag can be used to specify a program that doxygen should 1050# invoke to filter for each input file. Doxygen will invoke the filter program 1051# by executing (via popen()) the command: 1052# 1053# <filter> <input-file> 1054# 1055# where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the 1056# name of an input file. Doxygen will then use the output that the filter 1057# program writes to standard output. If FILTER_PATTERNS is specified, this tag 1058# will be ignored. 1059# 1060# Note that the filter must not add or remove lines; it is applied before the 1061# code is scanned, but not when the output code is generated. If lines are added 1062# or removed, the anchors will not be placed correctly. 1063# 1064# Note that doxygen will use the data processed and written to standard output 1065# for further processing, therefore nothing else, like debug statements or used 1066# commands (so in case of a Windows batch file always use @echo OFF), should be 1067# written to standard output. 1068# 1069# Note that for custom extensions or not directly supported extensions you also 1070# need to set EXTENSION_MAPPING for the extension otherwise the files are not 1071# properly processed by doxygen. 1072 1073INPUT_FILTER = 1074 1075# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 1076# basis. Doxygen will compare the file name with each pattern and apply the 1077# filter if there is a match. The filters are a list of the form: pattern=filter 1078# (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how 1079# filters are used. If the FILTER_PATTERNS tag is empty or if none of the 1080# patterns match the file name, INPUT_FILTER is applied. 1081# 1082# Note that for custom extensions or not directly supported extensions you also 1083# need to set EXTENSION_MAPPING for the extension otherwise the files are not 1084# properly processed by doxygen. 1085 1086FILTER_PATTERNS = 1087 1088# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 1089# INPUT_FILTER) will also be used to filter the input files that are used for 1090# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES). 1091# The default value is: NO. 1092 1093FILTER_SOURCE_FILES = NO 1094 1095# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file 1096# pattern. A pattern will override the setting for FILTER_PATTERN (if any) and 1097# it is also possible to disable source filtering for a specific pattern using 1098# *.ext= (so without naming a filter). 1099# This tag requires that the tag FILTER_SOURCE_FILES is set to YES. 1100 1101FILTER_SOURCE_PATTERNS = 1102 1103# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that 1104# is part of the input, its contents will be placed on the main page 1105# (index.html). This can be useful if you have a project on for instance GitHub 1106# and want to reuse the introduction page also for the doxygen output. 1107 1108USE_MDFILE_AS_MAINPAGE = @ZEPHYR_BASE@/doc/_doxygen/mainpage.md 1109 1110# The Fortran standard specifies that for fixed formatted Fortran code all 1111# characters from position 72 are to be considered as comment. A common 1112# extension is to allow longer lines before the automatic comment starts. The 1113# setting FORTRAN_COMMENT_AFTER will also make it possible that longer lines can 1114# be processed before the automatic comment starts. 1115# Minimum value: 7, maximum value: 10000, default value: 72. 1116 1117FORTRAN_COMMENT_AFTER = 72 1118 1119#--------------------------------------------------------------------------- 1120# Configuration options related to source browsing 1121#--------------------------------------------------------------------------- 1122 1123# If the SOURCE_BROWSER tag is set to YES then a list of source files will be 1124# generated. Documented entities will be cross-referenced with these sources. 1125# 1126# Note: To get rid of all source code in the generated output, make sure that 1127# also VERBATIM_HEADERS is set to NO. 1128# The default value is: NO. 1129 1130SOURCE_BROWSER = NO 1131 1132# Setting the INLINE_SOURCES tag to YES will include the body of functions, 1133# classes and enums directly into the documentation. 1134# The default value is: NO. 1135 1136INLINE_SOURCES = NO 1137 1138# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any 1139# special comment blocks from generated source code fragments. Normal C, C++ and 1140# Fortran comments will always remain visible. 1141# The default value is: YES. 1142 1143STRIP_CODE_COMMENTS = YES 1144 1145# If the REFERENCED_BY_RELATION tag is set to YES then for each documented 1146# entity all documented functions referencing it will be listed. 1147# The default value is: NO. 1148 1149REFERENCED_BY_RELATION = NO 1150 1151# If the REFERENCES_RELATION tag is set to YES then for each documented function 1152# all documented entities called/used by that function will be listed. 1153# The default value is: NO. 1154 1155REFERENCES_RELATION = NO 1156 1157# If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set 1158# to YES then the hyperlinks from functions in REFERENCES_RELATION and 1159# REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will 1160# link to the documentation. 1161# The default value is: YES. 1162 1163REFERENCES_LINK_SOURCE = YES 1164 1165# If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the 1166# source code will show a tooltip with additional information such as prototype, 1167# brief description and links to the definition and documentation. Since this 1168# will make the HTML file larger and loading of large files a bit slower, you 1169# can opt to disable this feature. 1170# The default value is: YES. 1171# This tag requires that the tag SOURCE_BROWSER is set to YES. 1172 1173SOURCE_TOOLTIPS = YES 1174 1175# If the USE_HTAGS tag is set to YES then the references to source code will 1176# point to the HTML generated by the htags(1) tool instead of doxygen built-in 1177# source browser. The htags tool is part of GNU's global source tagging system 1178# (see https://www.gnu.org/software/global/global.html). You will need version 1179# 4.8.6 or higher. 1180# 1181# To use it do the following: 1182# - Install the latest version of global 1183# - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file 1184# - Make sure the INPUT points to the root of the source tree 1185# - Run doxygen as normal 1186# 1187# Doxygen will invoke htags (and that will in turn invoke gtags), so these 1188# tools must be available from the command line (i.e. in the search path). 1189# 1190# The result: instead of the source browser generated by doxygen, the links to 1191# source code will now point to the output of htags. 1192# The default value is: NO. 1193# This tag requires that the tag SOURCE_BROWSER is set to YES. 1194 1195USE_HTAGS = NO 1196 1197# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a 1198# verbatim copy of the header file for each class for which an include is 1199# specified. Set to NO to disable this. 1200# See also: Section \class. 1201# The default value is: YES. 1202 1203VERBATIM_HEADERS = YES 1204 1205# If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the 1206# clang parser (see: 1207# http://clang.llvm.org/) for more accurate parsing at the cost of reduced 1208# performance. This can be particularly helpful with template rich C++ code for 1209# which doxygen's built-in parser lacks the necessary type information. 1210# Note: The availability of this option depends on whether or not doxygen was 1211# generated with the -Duse_libclang=ON option for CMake. 1212# The default value is: NO. 1213 1214CLANG_ASSISTED_PARSING = NO 1215 1216# If the CLANG_ASSISTED_PARSING tag is set to YES and the CLANG_ADD_INC_PATHS 1217# tag is set to YES then doxygen will add the directory of each input to the 1218# include path. 1219# The default value is: YES. 1220# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES. 1221 1222CLANG_ADD_INC_PATHS = YES 1223 1224# If clang assisted parsing is enabled you can provide the compiler with command 1225# line options that you would normally use when invoking the compiler. Note that 1226# the include paths will already be set by doxygen for the files and directories 1227# specified with INPUT and INCLUDE_PATH. 1228# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES. 1229 1230CLANG_OPTIONS = 1231 1232# If clang assisted parsing is enabled you can provide the clang parser with the 1233# path to the directory containing a file called compile_commands.json. This 1234# file is the compilation database (see: 1235# http://clang.llvm.org/docs/HowToSetupToolingForLLVM.html) containing the 1236# options used when the source files were built. This is equivalent to 1237# specifying the -p option to a clang tool, such as clang-check. These options 1238# will then be passed to the parser. Any options specified with CLANG_OPTIONS 1239# will be added as well. 1240# Note: The availability of this option depends on whether or not doxygen was 1241# generated with the -Duse_libclang=ON option for CMake. 1242 1243CLANG_DATABASE_PATH = 1244 1245#--------------------------------------------------------------------------- 1246# Configuration options related to the alphabetical class index 1247#--------------------------------------------------------------------------- 1248 1249# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all 1250# compounds will be generated. Enable this if the project contains a lot of 1251# classes, structs, unions or interfaces. 1252# The default value is: YES. 1253 1254ALPHABETICAL_INDEX = YES 1255 1256# The IGNORE_PREFIX tag can be used to specify a prefix (or a list of prefixes) 1257# that should be ignored while generating the index headers. The IGNORE_PREFIX 1258# tag works for classes, function and member names. The entity will be placed in 1259# the alphabetical list under the first letter of the entity name that remains 1260# after removing the prefix. 1261# This tag requires that the tag ALPHABETICAL_INDEX is set to YES. 1262 1263IGNORE_PREFIX = 1264 1265#--------------------------------------------------------------------------- 1266# Configuration options related to the HTML output 1267#--------------------------------------------------------------------------- 1268 1269# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output 1270# The default value is: YES. 1271 1272GENERATE_HTML = YES 1273 1274# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a 1275# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of 1276# it. 1277# The default directory is: html. 1278# This tag requires that the tag GENERATE_HTML is set to YES. 1279 1280HTML_OUTPUT = html 1281 1282# The HTML_FILE_EXTENSION tag can be used to specify the file extension for each 1283# generated HTML page (for example: .htm, .php, .asp). 1284# The default value is: .html. 1285# This tag requires that the tag GENERATE_HTML is set to YES. 1286 1287HTML_FILE_EXTENSION = .html 1288 1289# The HTML_HEADER tag can be used to specify a user-defined HTML header file for 1290# each generated HTML page. If the tag is left blank doxygen will generate a 1291# standard header. 1292# 1293# To get valid HTML the header file that includes any scripts and style sheets 1294# that doxygen needs, which is dependent on the configuration options used (e.g. 1295# the setting GENERATE_TREEVIEW). It is highly recommended to start with a 1296# default header using 1297# doxygen -w html new_header.html new_footer.html new_stylesheet.css 1298# YourConfigFile 1299# and then modify the file new_header.html. See also section "Doxygen usage" 1300# for information on how to generate the default header that doxygen normally 1301# uses. 1302# Note: The header is subject to change so you typically have to regenerate the 1303# default header when upgrading to a newer version of doxygen. For a description 1304# of the possible markers and block names see the documentation. 1305# This tag requires that the tag GENERATE_HTML is set to YES. 1306 1307HTML_HEADER = @ZEPHYR_BASE@/doc/_doxygen/header.html 1308 1309# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each 1310# generated HTML page. If the tag is left blank doxygen will generate a standard 1311# footer. See HTML_HEADER for more information on how to generate a default 1312# footer and what special commands can be used inside the footer. See also 1313# section "Doxygen usage" for information on how to generate the default footer 1314# that doxygen normally uses. 1315# This tag requires that the tag GENERATE_HTML is set to YES. 1316 1317HTML_FOOTER = @ZEPHYR_BASE@/doc/_doxygen/footer.html 1318 1319# The HTML_STYLESHEET tag can be used to specify a user-defined cascading style 1320# sheet that is used by each HTML page. It can be used to fine-tune the look of 1321# the HTML output. If left blank doxygen will generate a default style sheet. 1322# See also section "Doxygen usage" for information on how to generate the style 1323# sheet that doxygen normally uses. 1324# Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as 1325# it is more robust and this tag (HTML_STYLESHEET) will in the future become 1326# obsolete. 1327# This tag requires that the tag GENERATE_HTML is set to YES. 1328 1329HTML_STYLESHEET = 1330 1331# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined 1332# cascading style sheets that are included after the standard style sheets 1333# created by doxygen. Using this option one can overrule certain style aspects. 1334# This is preferred over using HTML_STYLESHEET since it does not replace the 1335# standard style sheet and is therefore more robust against future updates. 1336# Doxygen will copy the style sheet files to the output directory. 1337# Note: The order of the extra style sheet files is of importance (e.g. the last 1338# style sheet in the list overrules the setting of the previous ones in the 1339# list). 1340# Note: Since the styling of scrollbars can currently not be overruled in 1341# Webkit/Chromium, the styling will be left out of the default doxygen.css if 1342# one or more extra stylesheets have been specified. So if scrollbar 1343# customization is desired it has to be added explicitly. For an example see the 1344# documentation. 1345# This tag requires that the tag GENERATE_HTML is set to YES. 1346 1347HTML_EXTRA_STYLESHEET = @ZEPHYR_BASE@/doc/_doxygen/doxygen-awesome.css \ 1348 @ZEPHYR_BASE@/doc/_doxygen/doxygen-awesome-sidebar-only.css \ 1349 @ZEPHYR_BASE@/doc/_doxygen/doxygen-awesome-sidebar-only-darkmode-toggle.css \ 1350 @ZEPHYR_BASE@/doc/_doxygen/doxygen-awesome-zephyr.css 1351 1352# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or 1353# other source files which should be copied to the HTML output directory. Note 1354# that these files will be copied to the base HTML output directory. Use the 1355# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these 1356# files. In the HTML_STYLESHEET file, use the file name only. Also note that the 1357# files will be copied as-is; there are no commands or markers available. 1358# This tag requires that the tag GENERATE_HTML is set to YES. 1359 1360HTML_EXTRA_FILES = @ZEPHYR_BASE@/doc/_doxygen/doxygen-awesome-darkmode-toggle.js \ 1361 @ZEPHYR_BASE@/doc/_doxygen/doxygen-awesome-zephyr.js 1362 1363# The HTML_COLORSTYLE tag can be used to specify if the generated HTML output 1364# should be rendered with a dark or light theme. 1365# Possible values are: LIGHT always generate light mode output, DARK always 1366# generate dark mode output, AUTO_LIGHT automatically set the mode according to 1367# the user preference, use light mode if no preference is set (the default), 1368# AUTO_DARK automatically set the mode according to the user preference, use 1369# dark mode if no preference is set and TOGGLE allow to user to switch between 1370# light and dark mode via a button. 1371# The default value is: AUTO_LIGHT. 1372# This tag requires that the tag GENERATE_HTML is set to YES. 1373 1374HTML_COLORSTYLE = LIGHT 1375 1376# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen 1377# will adjust the colors in the style sheet and background images according to 1378# this color. Hue is specified as an angle on a color-wheel, see 1379# https://en.wikipedia.org/wiki/Hue for more information. For instance the value 1380# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 1381# purple, and 360 is red again. 1382# Minimum value: 0, maximum value: 359, default value: 220. 1383# This tag requires that the tag GENERATE_HTML is set to YES. 1384 1385HTML_COLORSTYLE_HUE = 220 1386 1387# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors 1388# in the HTML output. For a value of 0 the output will use gray-scales only. A 1389# value of 255 will produce the most vivid colors. 1390# Minimum value: 0, maximum value: 255, default value: 100. 1391# This tag requires that the tag GENERATE_HTML is set to YES. 1392 1393HTML_COLORSTYLE_SAT = 100 1394 1395# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the 1396# luminance component of the colors in the HTML output. Values below 100 1397# gradually make the output lighter, whereas values above 100 make the output 1398# darker. The value divided by 100 is the actual gamma applied, so 80 represents 1399# a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not 1400# change the gamma. 1401# Minimum value: 40, maximum value: 240, default value: 80. 1402# This tag requires that the tag GENERATE_HTML is set to YES. 1403 1404HTML_COLORSTYLE_GAMMA = 80 1405 1406# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML 1407# page will contain the date and time when the page was generated. Setting this 1408# to YES can help to show when doxygen was last run and thus if the 1409# documentation is up to date. 1410# The default value is: NO. 1411# This tag requires that the tag GENERATE_HTML is set to YES. 1412 1413HTML_TIMESTAMP = YES 1414 1415# If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML 1416# documentation will contain a main index with vertical navigation menus that 1417# are dynamically created via JavaScript. If disabled, the navigation index will 1418# consists of multiple levels of tabs that are statically embedded in every HTML 1419# page. Disable this option to support browsers that do not have JavaScript, 1420# like the Qt help browser. 1421# The default value is: YES. 1422# This tag requires that the tag GENERATE_HTML is set to YES. 1423 1424HTML_DYNAMIC_MENUS = YES 1425 1426# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 1427# documentation will contain sections that can be hidden and shown after the 1428# page has loaded. 1429# The default value is: NO. 1430# This tag requires that the tag GENERATE_HTML is set to YES. 1431 1432HTML_DYNAMIC_SECTIONS = YES 1433 1434# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries 1435# shown in the various tree structured indices initially; the user can expand 1436# and collapse entries dynamically later on. Doxygen will expand the tree to 1437# such a level that at most the specified number of entries are visible (unless 1438# a fully collapsed tree already exceeds this amount). So setting the number of 1439# entries 1 will produce a full collapsed tree by default. 0 is a special value 1440# representing an infinite number of entries and will result in a full expanded 1441# tree by default. 1442# Minimum value: 0, maximum value: 9999, default value: 100. 1443# This tag requires that the tag GENERATE_HTML is set to YES. 1444 1445HTML_INDEX_NUM_ENTRIES = 100 1446 1447# If the GENERATE_DOCSET tag is set to YES, additional index files will be 1448# generated that can be used as input for Apple's Xcode 3 integrated development 1449# environment (see: 1450# https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard). To 1451# create a documentation set, doxygen will generate a Makefile in the HTML 1452# output directory. Running make will produce the docset in that directory and 1453# running make install will install the docset in 1454# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at 1455# startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy 1456# genXcode/_index.html for more information. 1457# The default value is: NO. 1458# This tag requires that the tag GENERATE_HTML is set to YES. 1459 1460GENERATE_DOCSET = YES 1461 1462# This tag determines the name of the docset feed. A documentation feed provides 1463# an umbrella under which multiple documentation sets from a single provider 1464# (such as a company or product suite) can be grouped. 1465# The default value is: Doxygen generated docs. 1466# This tag requires that the tag GENERATE_DOCSET is set to YES. 1467 1468DOCSET_FEEDNAME = "Doxygen generated docs" 1469 1470# This tag determines the URL of the docset feed. A documentation feed provides 1471# an umbrella under which multiple documentation sets from a single provider 1472# (such as a company or product suite) can be grouped. 1473# This tag requires that the tag GENERATE_DOCSET is set to YES. 1474 1475DOCSET_FEEDURL = 1476 1477# This tag specifies a string that should uniquely identify the documentation 1478# set bundle. This should be a reverse domain-name style string, e.g. 1479# com.mycompany.MyDocSet. Doxygen will append .docset to the name. 1480# The default value is: org.doxygen.Project. 1481# This tag requires that the tag GENERATE_DOCSET is set to YES. 1482 1483DOCSET_BUNDLE_ID = org.doxygen.Project 1484 1485# The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify 1486# the documentation publisher. This should be a reverse domain-name style 1487# string, e.g. com.mycompany.MyDocSet.documentation. 1488# The default value is: org.doxygen.Publisher. 1489# This tag requires that the tag GENERATE_DOCSET is set to YES. 1490 1491DOCSET_PUBLISHER_ID = org.doxygen.Publisher 1492 1493# The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher. 1494# The default value is: Publisher. 1495# This tag requires that the tag GENERATE_DOCSET is set to YES. 1496 1497DOCSET_PUBLISHER_NAME = Publisher 1498 1499# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three 1500# additional HTML index files: index.hhp, index.hhc, and index.hhk. The 1501# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop 1502# on Windows. In the beginning of 2021 Microsoft took the original page, with 1503# a.o. the download links, offline the HTML help workshop was already many years 1504# in maintenance mode). You can download the HTML help workshop from the web 1505# archives at Installation executable (see: 1506# http://web.archive.org/web/20160201063255/http://download.microsoft.com/downlo 1507# ad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe). 1508# 1509# The HTML Help Workshop contains a compiler that can convert all HTML output 1510# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML 1511# files are now used as the Windows 98 help format, and will replace the old 1512# Windows help format (.hlp) on all Windows platforms in the future. Compressed 1513# HTML files also contain an index, a table of contents, and you can search for 1514# words in the documentation. The HTML workshop also contains a viewer for 1515# compressed HTML files. 1516# The default value is: NO. 1517# This tag requires that the tag GENERATE_HTML is set to YES. 1518 1519GENERATE_HTMLHELP = NO 1520 1521# The CHM_FILE tag can be used to specify the file name of the resulting .chm 1522# file. You can add a path in front of the file if the result should not be 1523# written to the html output directory. 1524# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1525 1526CHM_FILE = NO 1527 1528# The HHC_LOCATION tag can be used to specify the location (absolute path 1529# including file name) of the HTML help compiler (hhc.exe). If non-empty, 1530# doxygen will try to run the HTML help compiler on the generated index.hhp. 1531# The file has to be specified with full path. 1532# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1533 1534HHC_LOCATION = 1535 1536# The GENERATE_CHI flag controls if a separate .chi index file is generated 1537# (YES) or that it should be included in the main .chm file (NO). 1538# The default value is: NO. 1539# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1540 1541GENERATE_CHI = NO 1542 1543# The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc) 1544# and project file content. 1545# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1546 1547CHM_INDEX_ENCODING = 1548 1549# The BINARY_TOC flag controls whether a binary table of contents is generated 1550# (YES) or a normal table of contents (NO) in the .chm file. Furthermore it 1551# enables the Previous and Next buttons. 1552# The default value is: NO. 1553# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1554 1555BINARY_TOC = YES 1556 1557# The TOC_EXPAND flag can be set to YES to add extra items for group members to 1558# the table of contents of the HTML help documentation and to the tree view. 1559# The default value is: NO. 1560# This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1561 1562TOC_EXPAND = NO 1563 1564# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and 1565# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that 1566# can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help 1567# (.qch) of the generated HTML documentation. 1568# The default value is: NO. 1569# This tag requires that the tag GENERATE_HTML is set to YES. 1570 1571GENERATE_QHP = NO 1572 1573# If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify 1574# the file name of the resulting .qch file. The path specified is relative to 1575# the HTML output folder. 1576# This tag requires that the tag GENERATE_QHP is set to YES. 1577 1578QCH_FILE = 1579 1580# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help 1581# Project output. For more information please see Qt Help Project / Namespace 1582# (see: 1583# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace). 1584# The default value is: org.doxygen.Project. 1585# This tag requires that the tag GENERATE_QHP is set to YES. 1586 1587QHP_NAMESPACE = org.doxygen.Project 1588 1589# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt 1590# Help Project output. For more information please see Qt Help Project / Virtual 1591# Folders (see: 1592# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders). 1593# The default value is: doc. 1594# This tag requires that the tag GENERATE_QHP is set to YES. 1595 1596QHP_VIRTUAL_FOLDER = doc 1597 1598# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom 1599# filter to add. For more information please see Qt Help Project / Custom 1600# Filters (see: 1601# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters). 1602# This tag requires that the tag GENERATE_QHP is set to YES. 1603 1604QHP_CUST_FILTER_NAME = 1605 1606# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the 1607# custom filter to add. For more information please see Qt Help Project / Custom 1608# Filters (see: 1609# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters). 1610# This tag requires that the tag GENERATE_QHP is set to YES. 1611 1612QHP_CUST_FILTER_ATTRS = 1613 1614# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this 1615# project's filter section matches. Qt Help Project / Filter Attributes (see: 1616# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes). 1617# This tag requires that the tag GENERATE_QHP is set to YES. 1618 1619QHP_SECT_FILTER_ATTRS = 1620 1621# The QHG_LOCATION tag can be used to specify the location (absolute path 1622# including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to 1623# run qhelpgenerator on the generated .qhp file. 1624# This tag requires that the tag GENERATE_QHP is set to YES. 1625 1626QHG_LOCATION = 1627 1628# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be 1629# generated, together with the HTML files, they form an Eclipse help plugin. To 1630# install this plugin and make it available under the help contents menu in 1631# Eclipse, the contents of the directory containing the HTML and XML files needs 1632# to be copied into the plugins directory of eclipse. The name of the directory 1633# within the plugins directory should be the same as the ECLIPSE_DOC_ID value. 1634# After copying Eclipse needs to be restarted before the help appears. 1635# The default value is: NO. 1636# This tag requires that the tag GENERATE_HTML is set to YES. 1637 1638GENERATE_ECLIPSEHELP = NO 1639 1640# A unique identifier for the Eclipse help plugin. When installing the plugin 1641# the directory name containing the HTML and XML files should also have this 1642# name. Each documentation set should have its own identifier. 1643# The default value is: org.doxygen.Project. 1644# This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES. 1645 1646ECLIPSE_DOC_ID = org.doxygen.Project 1647 1648# If you want full control over the layout of the generated HTML pages it might 1649# be necessary to disable the index and replace it with your own. The 1650# DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top 1651# of each HTML page. A value of NO enables the index and the value YES disables 1652# it. Since the tabs in the index contain the same information as the navigation 1653# tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES. 1654# The default value is: NO. 1655# This tag requires that the tag GENERATE_HTML is set to YES. 1656 1657DISABLE_INDEX = NO 1658 1659# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 1660# structure should be generated to display hierarchical information. If the tag 1661# value is set to YES, a side panel will be generated containing a tree-like 1662# index structure (just like the one that is generated for HTML Help). For this 1663# to work a browser that supports JavaScript, DHTML, CSS and frames is required 1664# (i.e. any modern browser). Windows users are probably better off using the 1665# HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can 1666# further fine tune the look of the index (see "Fine-tuning the output"). As an 1667# example, the default style sheet generated by doxygen has an example that 1668# shows how to put an image at the root of the tree instead of the PROJECT_NAME. 1669# Since the tree basically has the same information as the tab index, you could 1670# consider setting DISABLE_INDEX to YES when enabling this option. 1671# The default value is: NO. 1672# This tag requires that the tag GENERATE_HTML is set to YES. 1673 1674GENERATE_TREEVIEW = YES 1675 1676# When both GENERATE_TREEVIEW and DISABLE_INDEX are set to YES, then the 1677# FULL_SIDEBAR option determines if the side bar is limited to only the treeview 1678# area (value NO) or if it should extend to the full height of the window (value 1679# YES). Setting this to YES gives a layout similar to 1680# https://docs.readthedocs.io with more room for contents, but less room for the 1681# project logo, title, and description. If either GENERATE_TREEVIEW or 1682# DISABLE_INDEX is set to NO, this option has no effect. 1683# The default value is: NO. 1684# This tag requires that the tag GENERATE_HTML is set to YES. 1685 1686FULL_SIDEBAR = NO 1687 1688# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that 1689# doxygen will group on one line in the generated HTML documentation. 1690# 1691# Note that a value of 0 will completely suppress the enum values from appearing 1692# in the overview section. 1693# Minimum value: 0, maximum value: 20, default value: 4. 1694# This tag requires that the tag GENERATE_HTML is set to YES. 1695 1696ENUM_VALUES_PER_LINE = 4 1697 1698# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used 1699# to set the initial width (in pixels) of the frame in which the tree is shown. 1700# Minimum value: 0, maximum value: 1500, default value: 250. 1701# This tag requires that the tag GENERATE_HTML is set to YES. 1702 1703TREEVIEW_WIDTH = 300 1704 1705# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to 1706# external symbols imported via tag files in a separate window. 1707# The default value is: NO. 1708# This tag requires that the tag GENERATE_HTML is set to YES. 1709 1710EXT_LINKS_IN_WINDOW = NO 1711 1712# If the OBFUSCATE_EMAILS tag is set to YES, doxygen will obfuscate email 1713# addresses. 1714# The default value is: YES. 1715# This tag requires that the tag GENERATE_HTML is set to YES. 1716 1717OBFUSCATE_EMAILS = YES 1718 1719# If the HTML_FORMULA_FORMAT option is set to svg, doxygen will use the pdf2svg 1720# tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see 1721# https://inkscape.org) to generate formulas as SVG images instead of PNGs for 1722# the HTML output. These images will generally look nicer at scaled resolutions. 1723# Possible values are: png (the default) and svg (looks nicer but requires the 1724# pdf2svg or inkscape tool). 1725# The default value is: png. 1726# This tag requires that the tag GENERATE_HTML is set to YES. 1727 1728HTML_FORMULA_FORMAT = png 1729 1730# Use this tag to change the font size of LaTeX formulas included as images in 1731# the HTML documentation. When you change the font size after a successful 1732# doxygen run you need to manually remove any form_*.png images from the HTML 1733# output directory to force them to be regenerated. 1734# Minimum value: 8, maximum value: 50, default value: 10. 1735# This tag requires that the tag GENERATE_HTML is set to YES. 1736 1737FORMULA_FONTSIZE = 10 1738 1739# The FORMULA_MACROFILE can contain LaTeX \newcommand and \renewcommand commands 1740# to create new LaTeX commands to be used in formulas as building blocks. See 1741# the section "Including formulas" for details. 1742 1743FORMULA_MACROFILE = 1744 1745# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see 1746# https://www.mathjax.org) which uses client side JavaScript for the rendering 1747# instead of using pre-rendered bitmaps. Use this if you do not have LaTeX 1748# installed or if you want to formulas look prettier in the HTML output. When 1749# enabled you may also need to install MathJax separately and configure the path 1750# to it using the MATHJAX_RELPATH option. 1751# The default value is: NO. 1752# This tag requires that the tag GENERATE_HTML is set to YES. 1753 1754USE_MATHJAX = NO 1755 1756# With MATHJAX_VERSION it is possible to specify the MathJax version to be used. 1757# Note that the different versions of MathJax have different requirements with 1758# regards to the different settings, so it is possible that also other MathJax 1759# settings have to be changed when switching between the different MathJax 1760# versions. 1761# Possible values are: MathJax_2 and MathJax_3. 1762# The default value is: MathJax_2. 1763# This tag requires that the tag USE_MATHJAX is set to YES. 1764 1765MATHJAX_VERSION = MathJax_2 1766 1767# When MathJax is enabled you can set the default output format to be used for 1768# the MathJax output. For more details about the output format see MathJax 1769# version 2 (see: 1770# http://docs.mathjax.org/en/v2.7-latest/output.html) and MathJax version 3 1771# (see: 1772# http://docs.mathjax.org/en/latest/web/components/output.html). 1773# Possible values are: HTML-CSS (which is slower, but has the best 1774# compatibility. This is the name for Mathjax version 2, for MathJax version 3 1775# this will be translated into chtml), NativeMML (i.e. MathML. Only supported 1776# for NathJax 2. For MathJax version 3 chtml will be used instead.), chtml (This 1777# is the name for Mathjax version 3, for MathJax version 2 this will be 1778# translated into HTML-CSS) and SVG. 1779# The default value is: HTML-CSS. 1780# This tag requires that the tag USE_MATHJAX is set to YES. 1781 1782MATHJAX_FORMAT = HTML-CSS 1783 1784# When MathJax is enabled you need to specify the location relative to the HTML 1785# output directory using the MATHJAX_RELPATH option. The destination directory 1786# should contain the MathJax.js script. For instance, if the mathjax directory 1787# is located at the same level as the HTML output directory, then 1788# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax 1789# Content Delivery Network so you can quickly see the result without installing 1790# MathJax. However, it is strongly recommended to install a local copy of 1791# MathJax from https://www.mathjax.org before deployment. The default value is: 1792# - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2 1793# - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3 1794# This tag requires that the tag USE_MATHJAX is set to YES. 1795 1796MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest 1797 1798# The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax 1799# extension names that should be enabled during MathJax rendering. For example 1800# for MathJax version 2 (see https://docs.mathjax.org/en/v2.7-latest/tex.html 1801# #tex-and-latex-extensions): 1802# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols 1803# For example for MathJax version 3 (see 1804# http://docs.mathjax.org/en/latest/input/tex/extensions/index.html): 1805# MATHJAX_EXTENSIONS = ams 1806# This tag requires that the tag USE_MATHJAX is set to YES. 1807 1808MATHJAX_EXTENSIONS = 1809 1810# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces 1811# of code that will be used on startup of the MathJax code. See the MathJax site 1812# (see: 1813# http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an 1814# example see the documentation. 1815# This tag requires that the tag USE_MATHJAX is set to YES. 1816 1817MATHJAX_CODEFILE = 1818 1819# When the SEARCHENGINE tag is enabled doxygen will generate a search box for 1820# the HTML output. The underlying search engine uses javascript and DHTML and 1821# should work on any modern browser. Note that when using HTML help 1822# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) 1823# there is already a search function so this one should typically be disabled. 1824# For large projects the javascript based search engine can be slow, then 1825# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to 1826# search using the keyboard; to jump to the search box use <access key> + S 1827# (what the <access key> is depends on the OS and browser, but it is typically 1828# <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down 1829# key> to jump into the search results window, the results can be navigated 1830# using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel 1831# the search. The filter options can be selected when the cursor is inside the 1832# search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys> 1833# to select a filter and <Enter> or <escape> to activate or cancel the filter 1834# option. 1835# The default value is: YES. 1836# This tag requires that the tag GENERATE_HTML is set to YES. 1837 1838SEARCHENGINE = YES 1839 1840# When the SERVER_BASED_SEARCH tag is enabled the search engine will be 1841# implemented using a web server instead of a web client using JavaScript. There 1842# are two flavors of web server based searching depending on the EXTERNAL_SEARCH 1843# setting. When disabled, doxygen will generate a PHP script for searching and 1844# an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing 1845# and searching needs to be provided by external tools. See the section 1846# "External Indexing and Searching" for details. 1847# The default value is: NO. 1848# This tag requires that the tag SEARCHENGINE is set to YES. 1849 1850SERVER_BASED_SEARCH = NO 1851 1852# When EXTERNAL_SEARCH tag is enabled doxygen will no longer generate the PHP 1853# script for searching. Instead the search results are written to an XML file 1854# which needs to be processed by an external indexer. Doxygen will invoke an 1855# external search engine pointed to by the SEARCHENGINE_URL option to obtain the 1856# search results. 1857# 1858# Doxygen ships with an example indexer (doxyindexer) and search engine 1859# (doxysearch.cgi) which are based on the open source search engine library 1860# Xapian (see: 1861# https://xapian.org/). 1862# 1863# See the section "External Indexing and Searching" for details. 1864# The default value is: NO. 1865# This tag requires that the tag SEARCHENGINE is set to YES. 1866 1867EXTERNAL_SEARCH = NO 1868 1869# The SEARCHENGINE_URL should point to a search engine hosted by a web server 1870# which will return the search results when EXTERNAL_SEARCH is enabled. 1871# 1872# Doxygen ships with an example indexer (doxyindexer) and search engine 1873# (doxysearch.cgi) which are based on the open source search engine library 1874# Xapian (see: 1875# https://xapian.org/). See the section "External Indexing and Searching" for 1876# details. 1877# This tag requires that the tag SEARCHENGINE is set to YES. 1878 1879SEARCHENGINE_URL = 1880 1881# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed 1882# search data is written to a file for indexing by an external tool. With the 1883# SEARCHDATA_FILE tag the name of this file can be specified. 1884# The default file is: searchdata.xml. 1885# This tag requires that the tag SEARCHENGINE is set to YES. 1886 1887SEARCHDATA_FILE = searchdata.xml 1888 1889# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the 1890# EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is 1891# useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple 1892# projects and redirect the results back to the right project. 1893# This tag requires that the tag SEARCHENGINE is set to YES. 1894 1895EXTERNAL_SEARCH_ID = 1896 1897# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen 1898# projects other than the one defined by this configuration file, but that are 1899# all added to the same external search index. Each project needs to have a 1900# unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id of 1901# to a relative location where the documentation can be found. The format is: 1902# EXTRA_SEARCH_MAPPINGS = tagname1=loc1 tagname2=loc2 ... 1903# This tag requires that the tag SEARCHENGINE is set to YES. 1904 1905EXTRA_SEARCH_MAPPINGS = 1906 1907#--------------------------------------------------------------------------- 1908# Configuration options related to the LaTeX output 1909#--------------------------------------------------------------------------- 1910 1911# If the GENERATE_LATEX tag is set to YES, doxygen will generate LaTeX output. 1912# The default value is: YES. 1913 1914GENERATE_LATEX = NO 1915 1916# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. If a 1917# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of 1918# it. 1919# The default directory is: latex. 1920# This tag requires that the tag GENERATE_LATEX is set to YES. 1921 1922LATEX_OUTPUT = latex 1923 1924# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 1925# invoked. 1926# 1927# Note that when not enabling USE_PDFLATEX the default is latex when enabling 1928# USE_PDFLATEX the default is pdflatex and when in the later case latex is 1929# chosen this is overwritten by pdflatex. For specific output languages the 1930# default can have been set differently, this depends on the implementation of 1931# the output language. 1932# This tag requires that the tag GENERATE_LATEX is set to YES. 1933 1934LATEX_CMD_NAME = latex 1935 1936# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate 1937# index for LaTeX. 1938# Note: This tag is used in the Makefile / make.bat. 1939# See also: LATEX_MAKEINDEX_CMD for the part in the generated output file 1940# (.tex). 1941# The default file is: makeindex. 1942# This tag requires that the tag GENERATE_LATEX is set to YES. 1943 1944MAKEINDEX_CMD_NAME = makeindex 1945 1946# The LATEX_MAKEINDEX_CMD tag can be used to specify the command name to 1947# generate index for LaTeX. In case there is no backslash (\) as first character 1948# it will be automatically added in the LaTeX code. 1949# Note: This tag is used in the generated output file (.tex). 1950# See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat. 1951# The default value is: makeindex. 1952# This tag requires that the tag GENERATE_LATEX is set to YES. 1953 1954LATEX_MAKEINDEX_CMD = makeindex 1955 1956# If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX 1957# documents. This may be useful for small projects and may help to save some 1958# trees in general. 1959# The default value is: NO. 1960# This tag requires that the tag GENERATE_LATEX is set to YES. 1961 1962COMPACT_LATEX = NO 1963 1964# The PAPER_TYPE tag can be used to set the paper type that is used by the 1965# printer. 1966# Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x 1967# 14 inches) and executive (7.25 x 10.5 inches). 1968# The default value is: a4. 1969# This tag requires that the tag GENERATE_LATEX is set to YES. 1970 1971PAPER_TYPE = a4 1972 1973# The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names 1974# that should be included in the LaTeX output. The package can be specified just 1975# by its name or with the correct syntax as to be used with the LaTeX 1976# \usepackage command. To get the times font for instance you can specify : 1977# EXTRA_PACKAGES=times or EXTRA_PACKAGES={times} 1978# To use the option intlimits with the amsmath package you can specify: 1979# EXTRA_PACKAGES=[intlimits]{amsmath} 1980# If left blank no extra packages will be included. 1981# This tag requires that the tag GENERATE_LATEX is set to YES. 1982 1983EXTRA_PACKAGES = 1984 1985# The LATEX_HEADER tag can be used to specify a user-defined LaTeX header for 1986# the generated LaTeX document. The header should contain everything until the 1987# first chapter. If it is left blank doxygen will generate a standard header. It 1988# is highly recommended to start with a default header using 1989# doxygen -w latex new_header.tex new_footer.tex new_stylesheet.sty 1990# and then modify the file new_header.tex. See also section "Doxygen usage" for 1991# information on how to generate the default header that doxygen normally uses. 1992# 1993# Note: Only use a user-defined header if you know what you are doing! 1994# Note: The header is subject to change so you typically have to regenerate the 1995# default header when upgrading to a newer version of doxygen. The following 1996# commands have a special meaning inside the header (and footer): For a 1997# description of the possible markers and block names see the documentation. 1998# This tag requires that the tag GENERATE_LATEX is set to YES. 1999 2000LATEX_HEADER = 2001 2002# The LATEX_FOOTER tag can be used to specify a user-defined LaTeX footer for 2003# the generated LaTeX document. The footer should contain everything after the 2004# last chapter. If it is left blank doxygen will generate a standard footer. See 2005# LATEX_HEADER for more information on how to generate a default footer and what 2006# special commands can be used inside the footer. See also section "Doxygen 2007# usage" for information on how to generate the default footer that doxygen 2008# normally uses. Note: Only use a user-defined footer if you know what you are 2009# doing! 2010# This tag requires that the tag GENERATE_LATEX is set to YES. 2011 2012LATEX_FOOTER = 2013 2014# The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined 2015# LaTeX style sheets that are included after the standard style sheets created 2016# by doxygen. Using this option one can overrule certain style aspects. Doxygen 2017# will copy the style sheet files to the output directory. 2018# Note: The order of the extra style sheet files is of importance (e.g. the last 2019# style sheet in the list overrules the setting of the previous ones in the 2020# list). 2021# This tag requires that the tag GENERATE_LATEX is set to YES. 2022 2023LATEX_EXTRA_STYLESHEET = 2024 2025# The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or 2026# other source files which should be copied to the LATEX_OUTPUT output 2027# directory. Note that the files will be copied as-is; there are no commands or 2028# markers available. 2029# This tag requires that the tag GENERATE_LATEX is set to YES. 2030 2031LATEX_EXTRA_FILES = 2032 2033# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated is 2034# prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will 2035# contain links (just like the HTML output) instead of page references. This 2036# makes the output suitable for online browsing using a PDF viewer. 2037# The default value is: YES. 2038# This tag requires that the tag GENERATE_LATEX is set to YES. 2039 2040PDF_HYPERLINKS = YES 2041 2042# If the USE_PDFLATEX tag is set to YES, doxygen will use the engine as 2043# specified with LATEX_CMD_NAME to generate the PDF file directly from the LaTeX 2044# files. Set this option to YES, to get a higher quality PDF documentation. 2045# 2046# See also section LATEX_CMD_NAME for selecting the engine. 2047# The default value is: YES. 2048# This tag requires that the tag GENERATE_LATEX is set to YES. 2049 2050USE_PDFLATEX = YES 2051 2052# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \batchmode 2053# command to the generated LaTeX files. This will instruct LaTeX to keep running 2054# if errors occur, instead of asking the user for help. 2055# The default value is: NO. 2056# This tag requires that the tag GENERATE_LATEX is set to YES. 2057 2058LATEX_BATCHMODE = NO 2059 2060# If the LATEX_HIDE_INDICES tag is set to YES then doxygen will not include the 2061# index chapters (such as File Index, Compound Index, etc.) in the output. 2062# The default value is: NO. 2063# This tag requires that the tag GENERATE_LATEX is set to YES. 2064 2065LATEX_HIDE_INDICES = NO 2066 2067# The LATEX_BIB_STYLE tag can be used to specify the style to use for the 2068# bibliography, e.g. plainnat, or ieeetr. See 2069# https://en.wikipedia.org/wiki/BibTeX and \cite for more info. 2070# The default value is: plain. 2071# This tag requires that the tag GENERATE_LATEX is set to YES. 2072 2073LATEX_BIB_STYLE = plain 2074 2075# If the LATEX_TIMESTAMP tag is set to YES then the footer of each generated 2076# page will contain the date and time when the page was generated. Setting this 2077# to NO can help when comparing the output of multiple runs. 2078# The default value is: NO. 2079# This tag requires that the tag GENERATE_LATEX is set to YES. 2080 2081LATEX_TIMESTAMP = NO 2082 2083# The LATEX_EMOJI_DIRECTORY tag is used to specify the (relative or absolute) 2084# path from which the emoji images will be read. If a relative path is entered, 2085# it will be relative to the LATEX_OUTPUT directory. If left blank the 2086# LATEX_OUTPUT directory will be used. 2087# This tag requires that the tag GENERATE_LATEX is set to YES. 2088 2089LATEX_EMOJI_DIRECTORY = 2090 2091#--------------------------------------------------------------------------- 2092# Configuration options related to the RTF output 2093#--------------------------------------------------------------------------- 2094 2095# If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The 2096# RTF output is optimized for Word 97 and may not look too pretty with other RTF 2097# readers/editors. 2098# The default value is: NO. 2099 2100GENERATE_RTF = NO 2101 2102# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. If a 2103# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of 2104# it. 2105# The default directory is: rtf. 2106# This tag requires that the tag GENERATE_RTF is set to YES. 2107 2108RTF_OUTPUT = rtf 2109 2110# If the COMPACT_RTF tag is set to YES, doxygen generates more compact RTF 2111# documents. This may be useful for small projects and may help to save some 2112# trees in general. 2113# The default value is: NO. 2114# This tag requires that the tag GENERATE_RTF is set to YES. 2115 2116COMPACT_RTF = NO 2117 2118# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated will 2119# contain hyperlink fields. The RTF file will contain links (just like the HTML 2120# output) instead of page references. This makes the output suitable for online 2121# browsing using Word or some other Word compatible readers that support those 2122# fields. 2123# 2124# Note: WordPad (write) and others do not support links. 2125# The default value is: NO. 2126# This tag requires that the tag GENERATE_RTF is set to YES. 2127 2128RTF_HYPERLINKS = YES 2129 2130# Load stylesheet definitions from file. Syntax is similar to doxygen's 2131# configuration file, i.e. a series of assignments. You only have to provide 2132# replacements, missing definitions are set to their default value. 2133# 2134# See also section "Doxygen usage" for information on how to generate the 2135# default style sheet that doxygen normally uses. 2136# This tag requires that the tag GENERATE_RTF is set to YES. 2137 2138RTF_STYLESHEET_FILE = 2139 2140# Set optional variables used in the generation of an RTF document. Syntax is 2141# similar to doxygen's configuration file. A template extensions file can be 2142# generated using doxygen -e rtf extensionFile. 2143# This tag requires that the tag GENERATE_RTF is set to YES. 2144 2145RTF_EXTENSIONS_FILE = 2146 2147#--------------------------------------------------------------------------- 2148# Configuration options related to the man page output 2149#--------------------------------------------------------------------------- 2150 2151# If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for 2152# classes and files. 2153# The default value is: NO. 2154 2155GENERATE_MAN = NO 2156 2157# The MAN_OUTPUT tag is used to specify where the man pages will be put. If a 2158# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of 2159# it. A directory man3 will be created inside the directory specified by 2160# MAN_OUTPUT. 2161# The default directory is: man. 2162# This tag requires that the tag GENERATE_MAN is set to YES. 2163 2164MAN_OUTPUT = man 2165 2166# The MAN_EXTENSION tag determines the extension that is added to the generated 2167# man pages. In case the manual section does not start with a number, the number 2168# 3 is prepended. The dot (.) at the beginning of the MAN_EXTENSION tag is 2169# optional. 2170# The default value is: .3. 2171# This tag requires that the tag GENERATE_MAN is set to YES. 2172 2173MAN_EXTENSION = .3 2174 2175# The MAN_SUBDIR tag determines the name of the directory created within 2176# MAN_OUTPUT in which the man pages are placed. If defaults to man followed by 2177# MAN_EXTENSION with the initial . removed. 2178# This tag requires that the tag GENERATE_MAN is set to YES. 2179 2180MAN_SUBDIR = 2181 2182# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it 2183# will generate one additional man file for each entity documented in the real 2184# man page(s). These additional files only source the real man page, but without 2185# them the man command would be unable to find the correct page. 2186# The default value is: NO. 2187# This tag requires that the tag GENERATE_MAN is set to YES. 2188 2189MAN_LINKS = NO 2190 2191#--------------------------------------------------------------------------- 2192# Configuration options related to the XML output 2193#--------------------------------------------------------------------------- 2194 2195# If the GENERATE_XML tag is set to YES, doxygen will generate an XML file that 2196# captures the structure of the code including all documentation. 2197# The default value is: NO. 2198 2199GENERATE_XML = YES 2200 2201# The XML_OUTPUT tag is used to specify where the XML pages will be put. If a 2202# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of 2203# it. 2204# The default directory is: xml. 2205# This tag requires that the tag GENERATE_XML is set to YES. 2206 2207XML_OUTPUT = xml 2208 2209# If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program 2210# listings (including syntax highlighting and cross-referencing information) to 2211# the XML output. Note that enabling this will significantly increase the size 2212# of the XML output. 2213# The default value is: YES. 2214# This tag requires that the tag GENERATE_XML is set to YES. 2215 2216XML_PROGRAMLISTING = YES 2217 2218# If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, doxygen will include 2219# namespace members in file scope as well, matching the HTML output. 2220# The default value is: NO. 2221# This tag requires that the tag GENERATE_XML is set to YES. 2222 2223XML_NS_MEMB_FILE_SCOPE = NO 2224 2225#--------------------------------------------------------------------------- 2226# Configuration options related to the DOCBOOK output 2227#--------------------------------------------------------------------------- 2228 2229# If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files 2230# that can be used to generate PDF. 2231# The default value is: NO. 2232 2233GENERATE_DOCBOOK = NO 2234 2235# The DOCBOOK_OUTPUT tag is used to specify where the Docbook pages will be put. 2236# If a relative path is entered the value of OUTPUT_DIRECTORY will be put in 2237# front of it. 2238# The default directory is: docbook. 2239# This tag requires that the tag GENERATE_DOCBOOK is set to YES. 2240 2241DOCBOOK_OUTPUT = docbook 2242 2243#--------------------------------------------------------------------------- 2244# Configuration options for the AutoGen Definitions output 2245#--------------------------------------------------------------------------- 2246 2247# If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an 2248# AutoGen Definitions (see http://autogen.sourceforge.net/) file that captures 2249# the structure of the code including all documentation. Note that this feature 2250# is still experimental and incomplete at the moment. 2251# The default value is: NO. 2252 2253GENERATE_AUTOGEN_DEF = NO 2254 2255#--------------------------------------------------------------------------- 2256# Configuration options related to the Perl module output 2257#--------------------------------------------------------------------------- 2258 2259# If the GENERATE_PERLMOD tag is set to YES, doxygen will generate a Perl module 2260# file that captures the structure of the code including all documentation. 2261# 2262# Note that this feature is still experimental and incomplete at the moment. 2263# The default value is: NO. 2264 2265GENERATE_PERLMOD = NO 2266 2267# If the PERLMOD_LATEX tag is set to YES, doxygen will generate the necessary 2268# Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI 2269# output from the Perl module output. 2270# The default value is: NO. 2271# This tag requires that the tag GENERATE_PERLMOD is set to YES. 2272 2273PERLMOD_LATEX = NO 2274 2275# If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely 2276# formatted so it can be parsed by a human reader. This is useful if you want to 2277# understand what is going on. On the other hand, if this tag is set to NO, the 2278# size of the Perl module output will be much smaller and Perl will parse it 2279# just the same. 2280# The default value is: YES. 2281# This tag requires that the tag GENERATE_PERLMOD is set to YES. 2282 2283PERLMOD_PRETTY = YES 2284 2285# The names of the make variables in the generated doxyrules.make file are 2286# prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful 2287# so different doxyrules.make files included by the same Makefile don't 2288# overwrite each other's variables. 2289# This tag requires that the tag GENERATE_PERLMOD is set to YES. 2290 2291PERLMOD_MAKEVAR_PREFIX = 2292 2293#--------------------------------------------------------------------------- 2294# Configuration options related to the preprocessor 2295#--------------------------------------------------------------------------- 2296 2297# If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all 2298# C-preprocessor directives found in the sources and include files. 2299# The default value is: YES. 2300 2301ENABLE_PREPROCESSING = YES 2302 2303# If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names 2304# in the source code. If set to NO, only conditional compilation will be 2305# performed. Macro expansion can be done in a controlled way by setting 2306# EXPAND_ONLY_PREDEF to YES. 2307# The default value is: NO. 2308# This tag requires that the tag ENABLE_PREPROCESSING is set to YES. 2309 2310MACRO_EXPANSION = YES 2311 2312# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES then 2313# the macro expansion is limited to the macros specified with the PREDEFINED and 2314# EXPAND_AS_DEFINED tags. 2315# The default value is: NO. 2316# This tag requires that the tag ENABLE_PREPROCESSING is set to YES. 2317 2318EXPAND_ONLY_PREDEF = NO 2319 2320# If the SEARCH_INCLUDES tag is set to YES, the include files in the 2321# INCLUDE_PATH will be searched if a #include is found. 2322# The default value is: YES. 2323# This tag requires that the tag ENABLE_PREPROCESSING is set to YES. 2324 2325SEARCH_INCLUDES = YES 2326 2327# The INCLUDE_PATH tag can be used to specify one or more directories that 2328# contain include files that are not input files but should be processed by the 2329# preprocessor. Note that the INCLUDE_PATH is not recursive, so the setting of 2330# RECURSIVE has no effect here. 2331# This tag requires that the tag SEARCH_INCLUDES is set to YES. 2332 2333INCLUDE_PATH = 2334 2335# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 2336# patterns (like *.h and *.hpp) to filter out the header-files in the 2337# directories. If left blank, the patterns specified with FILE_PATTERNS will be 2338# used. 2339# This tag requires that the tag ENABLE_PREPROCESSING is set to YES. 2340 2341INCLUDE_FILE_PATTERNS = 2342 2343# The PREDEFINED tag can be used to specify one or more macro names that are 2344# defined before the preprocessor is started (similar to the -D option of e.g. 2345# gcc). The argument of the tag is a list of macros of the form: name or 2346# name=definition (no spaces). If the definition and the "=" are omitted, "=1" 2347# is assumed. To prevent a macro definition from being undefined via #undef or 2348# recursively expanded use the := operator instead of the = operator. 2349# This tag requires that the tag ENABLE_PREPROCESSING is set to YES. 2350 2351PREDEFINED = __DOXYGEN__ \ 2352 CONFIG_ARCH_HAS_CUSTOM_BUSY_WAIT \ 2353 CONFIG_ARCH_HAS_CUSTOM_SWAP_TO_MAIN \ 2354 CONFIG_BT_CLASSIC \ 2355 CONFIG_BT_EATT \ 2356 CONFIG_BT_L2CAP_SEG_RECV \ 2357 CONFIG_BT_MESH_MODEL_EXTENSIONS \ 2358 CONFIG_BT_REMOTE_INFO \ 2359 CONFIG_BT_USER_DATA_LEN_UPDATE \ 2360 CONFIG_BT_USER_PHY_UPDATE \ 2361 CONFIG_BT_SMP \ 2362 CONFIG_BT_SMP_APP_PAIRING_ACCEPT \ 2363 CONFIG_CBPRINTF_LIBC_SUBSTS \ 2364 CONFIG_ERRNO \ 2365 CONFIG_FLASH_JESD216_API \ 2366 CONFIG_FLASH_PAGE_LAYOUT \ 2367 CONFIG_FP16 \ 2368 CONFIG_FPU \ 2369 CONFIG_FPU_SHARING \ 2370 CONFIG_GDBSTUB \ 2371 CONFIG_HEAP_MEM_POOL_SIZE \ 2372 CONFIG_MMU \ 2373 CONFIG_NET_L2_ETHERNET_MGMT \ 2374 CONFIG_NET_L2_IEEE802154_MGMT \ 2375 CONFIG_NET_L2_IEEE802154_SECURITY \ 2376 CONFIG_NET_MGMT_EVENT \ 2377 CONFIG_NET_SOCKETS_POSIX_NAMES \ 2378 CONFIG_NET_TCP \ 2379 CONFIG_NET_UDP \ 2380 CONFIG_SCHED_CPU_MASK \ 2381 CONFIG_SCHED_DEADLINE \ 2382 CONFIG_SCHED_DEADLINE \ 2383 CONFIG_SETTINGS_RUNTIME \ 2384 CONFIG_SMP \ 2385 CONFIG_SYS_CLOCK_EXISTS \ 2386 CONFIG_THREAD_CUSTOM_DATA \ 2387 CONFIG_THREAD_MONITOR \ 2388 CONFIG_THREAD_STACK_INFO \ 2389 CONFIG_TIMING_FUNCTIONS \ 2390 CONFIG_UART_DRV_CMD \ 2391 CONFIG_UART_INTERRUPT_DRIVEN \ 2392 CONFIG_UART_ASYNC_API \ 2393 CONFIG_USERSPACE \ 2394 CONFIG_USE_SWITCH \ 2395 NET_MGMT_DEFINE_REQUEST_HANDLER(x)= \ 2396 DEVICE_DEFINE()= \ 2397 BUILD_ASSERT()= \ 2398 XEN_GUEST_HANDLE_64(x)= \ 2399 _LINKER \ 2400 __deprecated= \ 2401 __sparse_cache= \ 2402 __packed= \ 2403 __aligned(x)= \ 2404 __attribute_nonnull(...)= \ 2405 "__printf_like(x, y)=" \ 2406 __attribute__(x)= \ 2407 __syscall= \ 2408 __syscall_always_inline= \ 2409 __must_check= \ 2410 "ATOMIC_DEFINE(x, y)=atomic_t x[ATOMIC_BITMAP_SIZE(y)]" \ 2411 "ZTEST(suite, fn)=void fn(void)" \ 2412 "ZTEST_USER(suite, fn)=void fn(void)" \ 2413 "ZTEST_USER_F(suite, fn)=void fn(void)" \ 2414 "ZTEST_F(suite, fn)=void fn(void)" 2415 2416# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then this 2417# tag can be used to specify a list of macro names that should be expanded. The 2418# macro definition that is found in the sources will be used. Use the PREDEFINED 2419# tag if you want to use a different macro definition that overrules the 2420# definition found in the source code. 2421# This tag requires that the tag ENABLE_PREPROCESSING is set to YES. 2422 2423EXPAND_AS_DEFINED = 2424 2425# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will 2426# remove all references to function-like macros that are alone on a line, have 2427# an all uppercase name, and do not end with a semicolon. Such function macros 2428# are typically used for boiler-plate code, and will confuse the parser if not 2429# removed. 2430# The default value is: YES. 2431# This tag requires that the tag ENABLE_PREPROCESSING is set to YES. 2432 2433SKIP_FUNCTION_MACROS = NO 2434 2435#--------------------------------------------------------------------------- 2436# Configuration options related to external references 2437#--------------------------------------------------------------------------- 2438 2439# The TAGFILES tag can be used to specify one or more tag files. For each tag 2440# file the location of the external documentation should be added. The format of 2441# a tag file without this location is as follows: 2442# TAGFILES = file1 file2 ... 2443# Adding location for the tag files is done as follows: 2444# TAGFILES = file1=loc1 "file2 = loc2" ... 2445# where loc1 and loc2 can be relative or absolute paths or URLs. See the 2446# section "Linking to external documentation" for more information about the use 2447# of tag files. 2448# Note: Each tag file must have a unique name (where the name does NOT include 2449# the path). If a tag file is not located in the directory in which doxygen is 2450# run, you must also specify the path to the tagfile here. 2451 2452TAGFILES = 2453 2454# When a file name is specified after GENERATE_TAGFILE, doxygen will create a 2455# tag file that is based on the input files it reads. See section "Linking to 2456# external documentation" for more information about the usage of tag files. 2457 2458GENERATE_TAGFILE = @DOXY_OUT@/html/zephyr.tag 2459 2460# If the ALLEXTERNALS tag is set to YES, all external class will be listed in 2461# the class index. If set to NO, only the inherited external classes will be 2462# listed. 2463# The default value is: NO. 2464 2465ALLEXTERNALS = NO 2466 2467# If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed 2468# in the modules index. If set to NO, only the current project's groups will be 2469# listed. 2470# The default value is: YES. 2471 2472EXTERNAL_GROUPS = YES 2473 2474# If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in 2475# the related pages index. If set to NO, only the current project's pages will 2476# be listed. 2477# The default value is: YES. 2478 2479EXTERNAL_PAGES = YES 2480 2481#--------------------------------------------------------------------------- 2482# Configuration options related to the dot tool 2483#--------------------------------------------------------------------------- 2484 2485# You can include diagrams made with dia in doxygen documentation. Doxygen will 2486# then run dia to produce the diagram and insert it in the documentation. The 2487# DIA_PATH tag allows you to specify the directory where the dia binary resides. 2488# If left empty dia is assumed to be found in the default search path. 2489 2490DIA_PATH = 2491 2492# If set to YES the inheritance and collaboration graphs will hide inheritance 2493# and usage relations if the target is undocumented or is not a class. 2494# The default value is: YES. 2495 2496HIDE_UNDOC_RELATIONS = YES 2497 2498# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 2499# available from the path. This tool is part of Graphviz (see: 2500# http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent 2501# Bell Labs. The other options in this section have no effect if this option is 2502# set to NO 2503# The default value is: NO. 2504 2505HAVE_DOT = NO 2506 2507# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is allowed 2508# to run in parallel. When set to 0 doxygen will base this on the number of 2509# processors available in the system. You can set it explicitly to a value 2510# larger than 0 to get control over the balance between CPU load and processing 2511# speed. 2512# Minimum value: 0, maximum value: 32, default value: 0. 2513# This tag requires that the tag HAVE_DOT is set to YES. 2514 2515DOT_NUM_THREADS = 0 2516 2517# DOT_COMMON_ATTR is common attributes for nodes, edges and labels of 2518# subgraphs. When you want a differently looking font in the dot files that 2519# doxygen generates you can specify fontname, fontcolor and fontsize attributes. 2520# For details please see <a href=https://graphviz.org/doc/info/attrs.html>Node, 2521# Edge and Graph Attributes specification</a> You need to make sure dot is able 2522# to find the font, which can be done by putting it in a standard location or by 2523# setting the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the 2524# directory containing the font. Default graphviz fontsize is 14. 2525# The default value is: fontname=Helvetica,fontsize=10. 2526# This tag requires that the tag HAVE_DOT is set to YES. 2527 2528DOT_COMMON_ATTR = "fontname=Helvetica,fontsize=10" 2529 2530# DOT_EDGE_ATTR is concatenated with DOT_COMMON_ATTR. For elegant style you can 2531# add 'arrowhead=open, arrowtail=open, arrowsize=0.5'. <a 2532# href=https://graphviz.org/doc/info/arrows.html>Complete documentation about 2533# arrows shapes.</a> 2534# The default value is: labelfontname=Helvetica,labelfontsize=10. 2535# This tag requires that the tag HAVE_DOT is set to YES. 2536 2537DOT_EDGE_ATTR = "labelfontname=Helvetica,labelfontsize=10" 2538 2539# DOT_NODE_ATTR is concatenated with DOT_COMMON_ATTR. For view without boxes 2540# around nodes set 'shape=plain' or 'shape=plaintext' <a 2541# href=https://www.graphviz.org/doc/info/shapes.html>Shapes specification</a> 2542# The default value is: shape=box,height=0.2,width=0.4. 2543# This tag requires that the tag HAVE_DOT is set to YES. 2544 2545DOT_NODE_ATTR = "shape=box,height=0.2,width=0.4" 2546 2547# You can set the path where dot can find font specified with fontname in 2548# DOT_COMMON_ATTR and others dot attributes. 2549# This tag requires that the tag HAVE_DOT is set to YES. 2550 2551DOT_FONTPATH = 2552 2553# If the CLASS_GRAPH tag is set to YES (or GRAPH) then doxygen will generate a 2554# graph for each documented class showing the direct and indirect inheritance 2555# relations. In case HAVE_DOT is set as well dot will be used to draw the graph, 2556# otherwise the built-in generator will be used. If the CLASS_GRAPH tag is set 2557# to TEXT the direct and indirect inheritance relations will be shown as texts / 2558# links. 2559# Possible values are: NO, YES, TEXT and GRAPH. 2560# The default value is: YES. 2561 2562CLASS_GRAPH = TEXT 2563 2564# If the COLLABORATION_GRAPH tag is set to YES then doxygen will generate a 2565# graph for each documented class showing the direct and indirect implementation 2566# dependencies (inheritance, containment, and class references variables) of the 2567# class with other documented classes. 2568# The default value is: YES. 2569# This tag requires that the tag HAVE_DOT is set to YES. 2570 2571COLLABORATION_GRAPH = YES 2572 2573# If the GROUP_GRAPHS tag is set to YES then doxygen will generate a graph for 2574# groups, showing the direct groups dependencies. See also the chapter Grouping 2575# in the manual. 2576# The default value is: YES. 2577# This tag requires that the tag HAVE_DOT is set to YES. 2578 2579GROUP_GRAPHS = YES 2580 2581# If the UML_LOOK tag is set to YES, doxygen will generate inheritance and 2582# collaboration diagrams in a style similar to the OMG's Unified Modeling 2583# Language. 2584# The default value is: NO. 2585# This tag requires that the tag HAVE_DOT is set to YES. 2586 2587UML_LOOK = NO 2588 2589# If the UML_LOOK tag is enabled, the fields and methods are shown inside the 2590# class node. If there are many fields or methods and many nodes the graph may 2591# become too big to be useful. The UML_LIMIT_NUM_FIELDS threshold limits the 2592# number of items for each type to make the size more manageable. Set this to 0 2593# for no limit. Note that the threshold may be exceeded by 50% before the limit 2594# is enforced. So when you set the threshold to 10, up to 15 fields may appear, 2595# but if the number exceeds 15, the total amount of fields shown is limited to 2596# 10. 2597# Minimum value: 0, maximum value: 100, default value: 10. 2598# This tag requires that the tag UML_LOOK is set to YES. 2599 2600UML_LIMIT_NUM_FIELDS = 10 2601 2602# If the DOT_UML_DETAILS tag is set to NO, doxygen will show attributes and 2603# methods without types and arguments in the UML graphs. If the DOT_UML_DETAILS 2604# tag is set to YES, doxygen will add type and arguments for attributes and 2605# methods in the UML graphs. If the DOT_UML_DETAILS tag is set to NONE, doxygen 2606# will not generate fields with class member information in the UML graphs. The 2607# class diagrams will look similar to the default class diagrams but using UML 2608# notation for the relationships. 2609# Possible values are: NO, YES and NONE. 2610# The default value is: NO. 2611# This tag requires that the tag UML_LOOK is set to YES. 2612 2613DOT_UML_DETAILS = NO 2614 2615# The DOT_WRAP_THRESHOLD tag can be used to set the maximum number of characters 2616# to display on a single line. If the actual line length exceeds this threshold 2617# significantly it will wrapped across multiple lines. Some heuristics are apply 2618# to avoid ugly line breaks. 2619# Minimum value: 0, maximum value: 1000, default value: 17. 2620# This tag requires that the tag HAVE_DOT is set to YES. 2621 2622DOT_WRAP_THRESHOLD = 17 2623 2624# If the TEMPLATE_RELATIONS tag is set to YES then the inheritance and 2625# collaboration graphs will show the relations between templates and their 2626# instances. 2627# The default value is: NO. 2628# This tag requires that the tag HAVE_DOT is set to YES. 2629 2630TEMPLATE_RELATIONS = NO 2631 2632# If the INCLUDE_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are set to 2633# YES then doxygen will generate a graph for each documented file showing the 2634# direct and indirect include dependencies of the file with other documented 2635# files. 2636# The default value is: YES. 2637# This tag requires that the tag HAVE_DOT is set to YES. 2638 2639INCLUDE_GRAPH = YES 2640 2641# If the INCLUDED_BY_GRAPH, ENABLE_PREPROCESSING and SEARCH_INCLUDES tags are 2642# set to YES then doxygen will generate a graph for each documented file showing 2643# the direct and indirect include dependencies of the file with other documented 2644# files. 2645# The default value is: YES. 2646# This tag requires that the tag HAVE_DOT is set to YES. 2647 2648INCLUDED_BY_GRAPH = YES 2649 2650# If the CALL_GRAPH tag is set to YES then doxygen will generate a call 2651# dependency graph for every global function or class method. 2652# 2653# Note that enabling this option will significantly increase the time of a run. 2654# So in most cases it will be better to enable call graphs for selected 2655# functions only using the \callgraph command. Disabling a call graph can be 2656# accomplished by means of the command \hidecallgraph. 2657# The default value is: NO. 2658# This tag requires that the tag HAVE_DOT is set to YES. 2659 2660CALL_GRAPH = NO 2661 2662# If the CALLER_GRAPH tag is set to YES then doxygen will generate a caller 2663# dependency graph for every global function or class method. 2664# 2665# Note that enabling this option will significantly increase the time of a run. 2666# So in most cases it will be better to enable caller graphs for selected 2667# functions only using the \callergraph command. Disabling a caller graph can be 2668# accomplished by means of the command \hidecallergraph. 2669# The default value is: NO. 2670# This tag requires that the tag HAVE_DOT is set to YES. 2671 2672CALLER_GRAPH = NO 2673 2674# If the GRAPHICAL_HIERARCHY tag is set to YES then doxygen will graphical 2675# hierarchy of all classes instead of a textual one. 2676# The default value is: YES. 2677# This tag requires that the tag HAVE_DOT is set to YES. 2678 2679GRAPHICAL_HIERARCHY = YES 2680 2681# If the DIRECTORY_GRAPH tag is set to YES then doxygen will show the 2682# dependencies a directory has on other directories in a graphical way. The 2683# dependency relations are determined by the #include relations between the 2684# files in the directories. 2685# The default value is: YES. 2686# This tag requires that the tag HAVE_DOT is set to YES. 2687 2688DIRECTORY_GRAPH = YES 2689 2690# The DIR_GRAPH_MAX_DEPTH tag can be used to limit the maximum number of levels 2691# of child directories generated in directory dependency graphs by dot. 2692# Minimum value: 1, maximum value: 25, default value: 1. 2693# This tag requires that the tag DIRECTORY_GRAPH is set to YES. 2694 2695DIR_GRAPH_MAX_DEPTH = 1 2696 2697# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 2698# generated by dot. For an explanation of the image formats see the section 2699# output formats in the documentation of the dot tool (Graphviz (see: 2700# http://www.graphviz.org/)). 2701# Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order 2702# to make the SVG files visible in IE 9+ (other browsers do not have this 2703# requirement). 2704# Possible values are: png, jpg, gif, svg, png:gd, png:gd:gd, png:cairo, 2705# png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and 2706# png:gdiplus:gdiplus. 2707# The default value is: png. 2708# This tag requires that the tag HAVE_DOT is set to YES. 2709 2710DOT_IMAGE_FORMAT = png 2711 2712# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to 2713# enable generation of interactive SVG images that allow zooming and panning. 2714# 2715# Note that this requires a modern browser other than Internet Explorer. Tested 2716# and working are Firefox, Chrome, Safari, and Opera. 2717# Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make 2718# the SVG files visible. Older versions of IE do not have SVG support. 2719# The default value is: NO. 2720# This tag requires that the tag HAVE_DOT is set to YES. 2721 2722INTERACTIVE_SVG = NO 2723 2724# The DOT_PATH tag can be used to specify the path where the dot tool can be 2725# found. If left blank, it is assumed the dot tool can be found in the path. 2726# This tag requires that the tag HAVE_DOT is set to YES. 2727 2728DOT_PATH = 2729 2730# The DOTFILE_DIRS tag can be used to specify one or more directories that 2731# contain dot files that are included in the documentation (see the \dotfile 2732# command). 2733# This tag requires that the tag HAVE_DOT is set to YES. 2734 2735DOTFILE_DIRS = 2736 2737# The MSCFILE_DIRS tag can be used to specify one or more directories that 2738# contain msc files that are included in the documentation (see the \mscfile 2739# command). 2740 2741MSCFILE_DIRS = 2742 2743# The DIAFILE_DIRS tag can be used to specify one or more directories that 2744# contain dia files that are included in the documentation (see the \diafile 2745# command). 2746 2747DIAFILE_DIRS = 2748 2749# When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the 2750# path where java can find the plantuml.jar file or to the filename of jar file 2751# to be used. If left blank, it is assumed PlantUML is not used or called during 2752# a preprocessing step. Doxygen will generate a warning when it encounters a 2753# \startuml command in this case and will not generate output for the diagram. 2754 2755PLANTUML_JAR_PATH = 2756 2757# When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a 2758# configuration file for plantuml. 2759 2760PLANTUML_CFG_FILE = 2761 2762# When using plantuml, the specified paths are searched for files specified by 2763# the !include statement in a plantuml block. 2764 2765PLANTUML_INCLUDE_PATH = 2766 2767# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes 2768# that will be shown in the graph. If the number of nodes in a graph becomes 2769# larger than this value, doxygen will truncate the graph, which is visualized 2770# by representing a node as a red box. Note that doxygen if the number of direct 2771# children of the root node in a graph is already larger than 2772# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note that 2773# the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. 2774# Minimum value: 0, maximum value: 10000, default value: 50. 2775# This tag requires that the tag HAVE_DOT is set to YES. 2776 2777DOT_GRAPH_MAX_NODES = 50 2778 2779# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the graphs 2780# generated by dot. A depth value of 3 means that only nodes reachable from the 2781# root by following a path via at most 3 edges will be shown. Nodes that lay 2782# further from the root node will be omitted. Note that setting this option to 1 2783# or 2 may greatly reduce the computation time needed for large code bases. Also 2784# note that the size of a graph can be further restricted by 2785# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. 2786# Minimum value: 0, maximum value: 1000, default value: 0. 2787# This tag requires that the tag HAVE_DOT is set to YES. 2788 2789MAX_DOT_GRAPH_DEPTH = 0 2790 2791# Set the DOT_MULTI_TARGETS tag to YES to allow dot to generate multiple output 2792# files in one run (i.e. multiple -o and -T options on the command line). This 2793# makes dot run faster, but since only newer versions of dot (>1.8.10) support 2794# this, this feature is disabled by default. 2795# The default value is: NO. 2796# This tag requires that the tag HAVE_DOT is set to YES. 2797 2798DOT_MULTI_TARGETS = NO 2799 2800# If the GENERATE_LEGEND tag is set to YES doxygen will generate a legend page 2801# explaining the meaning of the various boxes and arrows in the dot generated 2802# graphs. 2803# Note: This tag requires that UML_LOOK isn't set, i.e. the doxygen internal 2804# graphical representation for inheritance and collaboration diagrams is used. 2805# The default value is: YES. 2806# This tag requires that the tag HAVE_DOT is set to YES. 2807 2808GENERATE_LEGEND = YES 2809 2810# If the DOT_CLEANUP tag is set to YES, doxygen will remove the intermediate 2811# files that are used to generate the various graphs. 2812# 2813# Note: This setting is not only used for dot files but also for msc temporary 2814# files. 2815# The default value is: YES. 2816 2817DOT_CLEANUP = YES 2818 2819@INCLUDE_CUSTOM_FILE@ 2820
