17
17
# Project related configuration options
18
18
#---------------------------------------------------------------------------
20
# This tag specifies the encoding used for all characters in the config file
21
# that follow. The default is UTF-8 which is also the encoding used for all text
22
# before the first occurrence of this tag. Doxygen uses libiconv (or the iconv
23
# built into libc) for the transcoding. See http://www.gnu.org/software/libiconv
24
# for the list of possible encodings.
20
# This tag specifies the encoding used for all characters in the configuration
21
# file that follow. The default is UTF-8 which is also the encoding used for all
22
# text before the first occurrence of this tag. Doxygen uses libiconv (or the
23
# iconv built into libc) for the transcoding. See
24
# https://www.gnu.org/software/libiconv/ for the list of possible encodings.
25
25
# The default value is: UTF-8.
27
27
DOXYFILE_ENCODING = UTF-8
47
47
PROJECT_BRIEF = "Research Assistant: source code documentation"
49
# With the PROJECT_LOGO tag one can specify an logo or icon that is included in
50
# the documentation. The maximum height of the logo should not exceed 55 pixels
51
# and the maximum width should not exceed 200 pixels. Doxygen will copy the logo
52
# to the output directory.
49
# With the PROJECT_LOGO tag one can specify a logo or an icon that is included
50
# in the documentation. The maximum height of the logo should not exceed 55
51
# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy
52
# the logo to the output directory.
54
54
PROJECT_LOGO = RaEye_71x43.png
71
71
CREATE_SUBDIRS = NO
73
# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII
74
# characters to appear in the names of generated files. If set to NO, non-ASCII
75
# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode
77
# The default value is: NO.
79
ALLOW_UNICODE_NAMES = NO
73
81
# The OUTPUT_LANGUAGE tag is used to specify the language in which all
74
82
# documentation generated by doxygen is written. Doxygen will use this
75
83
# information to generate all constant output in the proper language.
86
94
OUTPUT_LANGUAGE = English
88
# If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member
96
# The OUTPUT_TEXT_DIRECTION tag is used to specify the direction in which all
97
# documentation generated by doxygen is written. Doxygen will use this
98
# information to generate all generated output in the proper direction.
99
# Possible values are: None, LTR, RTL and Context.
100
# The default value is: None.
102
OUTPUT_TEXT_DIRECTION = None
104
# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member
89
105
# descriptions after the members that are listed in the file and class
90
106
# documentation (similar to Javadoc). Set to NO to disable this.
91
107
# The default value is: YES.
93
109
BRIEF_MEMBER_DESC = YES
95
# If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief
111
# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief
96
112
# description of a member or function before the detailed description
98
114
# Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
172
188
JAVADOC_AUTOBRIEF = NO
190
# If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line
193
# as being the beginning of a Javadoc-style comment "banner". If set to NO, the
194
# Javadoc-style will behave just like regular comments and it will not be
195
# interpreted by doxygen.
196
# The default value is: NO.
174
200
# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first
175
201
# line (until the first dot) of a Qt-style comment as the brief description. If
176
202
# set to NO, the Qt-style will behave just like regular Qt-style comments (thus
198
224
INHERIT_DOCS = YES
200
# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce a
201
# new page for each member. If set to NO, the documentation of a member will be
202
# part of the file/class/namespace that contains it.
226
# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new
227
# page for each member. If set to NO, the documentation of a member will be part
228
# of the file/class/namespace that contains it.
203
229
# The default value is: NO.
205
231
SEPARATE_MEMBER_PAGES = NO
218
244
# will allow you to put the command \sideeffect (or @sideeffect) in the
219
245
# documentation, which will result in a user-defined paragraph with heading
220
246
# "Side Effects:". You can put \n's in the value part of an alias to insert
247
# newlines (in the resulting output). You can put ^^ in the value part of an
248
# alias to insert a newline as if a physical newline was in the original file.
249
# When you need a literal { or } or , in the value part of an alias you have to
250
# escape them by means of a backslash (\), this can lead to conflicts with the
251
# commands \{ and \} for these it is advised to use the version @{ and @} or use
252
# a double escape (\\{ and \\})
223
254
ALIASES = "sotovarischam=@xrefitem sotovarischamkey \"Коментарий для со-разработчика\" \"Коментарии для сотоварищей по разработке\"" \
224
255
"macro=@xrefitem macrodefs \"Macro\" \"Macro list\"" \
261
292
OPTIMIZE_OUTPUT_VHDL = NO
294
# Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice
295
# sources only. Doxygen will then generate output that is more tailored for that
296
# language. For instance, namespaces will be presented as modules, types will be
297
# separated into more groups, etc.
298
# The default value is: NO.
300
OPTIMIZE_OUTPUT_SLICE = NO
263
302
# Doxygen selects the parser to use depending on the extension of the files it
264
303
# parses. With this tag you can assign which parser to use for a given
265
304
# extension. Doxygen has a built-in mapping, but you can override or extend it
266
305
# using this tag. The format is ext=language, where ext is a file extension, and
267
# language is one of the parsers supported by doxygen: IDL, Java, Javascript,
268
# C#, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL. For instance to make
269
# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
270
# (default is Fortran), use: inc=Fortran f=C.
306
# language is one of the parsers supported by doxygen: IDL, Java, JavaScript,
307
# Csharp (C#), C, C++, D, PHP, md (Markdown), Objective-C, Python, Slice,
308
# Fortran (fixed format Fortran: FortranFixed, free formatted Fortran:
309
# FortranFree, unknown formatted Fortran: Fortran. In the later case the parser
310
# tries to guess whether the code is fixed or free formatted code, this is the
311
# default for Fortran type files), VHDL, tcl. For instance to make doxygen treat
312
# .inc files as Fortran files (default is PHP), and .f files as C (default is
313
# Fortran), use: inc=Fortran f=C.
272
# Note For files without extension you can use no_extension as a placeholder.
315
# Note: For files without extension you can use no_extension as a placeholder.
274
317
# Note that for custom extensions you also need to set FILE_PATTERNS otherwise
275
318
# the files are not read by doxygen.
279
322
# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
280
323
# according to the Markdown format, which allows for more readable
281
# documentation. See http://daringfireball.net/projects/markdown/ for details.
324
# documentation. See https://daringfireball.net/projects/markdown/ for details.
282
325
# The output of markdown processing is further processed by doxygen, so you can
283
326
# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
284
327
# case of backward compatibilities issues.
287
330
MARKDOWN_SUPPORT = YES
332
# When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
333
# to that level are automatically included in the table of contents, even if
334
# they do not have an id attribute.
335
# Note: This feature currently applies only to Markdown headings.
336
# Minimum value: 0, maximum value: 99, default value: 5.
337
# This tag requires that the tag MARKDOWN_SUPPORT is set to YES.
339
TOC_INCLUDE_HEADINGS = 5
289
341
# When enabled doxygen tries to link words that correspond to documented
290
342
# classes, or namespaces to their corresponding documentation. Such a link can
291
# be prevented in individual cases by by putting a % sign in front of the word
292
# or globally by setting AUTOLINK_SUPPORT to NO.
343
# be prevented in individual cases by putting a % sign in front of the word or
344
# globally by setting AUTOLINK_SUPPORT to NO.
293
345
# The default value is: YES.
295
347
AUTOLINK_SUPPORT = YES
329
381
IDL_PROPERTY_SUPPORT = YES
331
383
# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
332
# tag is set to YES, then doxygen will reuse the documentation of the first
384
# tag is set to YES then doxygen will reuse the documentation of the first
333
385
# member in the group (if any) for the other members of the group. By default
334
386
# all members of a group must be documented explicitly.
335
387
# The default value is: NO.
337
389
DISTRIBUTE_GROUP_DOC = NO
391
# If one adds a struct or class to a group and this option is enabled, then also
392
# any nested class or struct is added to the same group. By default this option
393
# is disabled and one has to add nested compounds explicitly via \ingroup.
394
# The default value is: NO.
396
GROUP_NESTED_COMPOUNDS = NO
339
398
# Set the SUBGROUPING tag to YES to allow class member groups of the same type
340
399
# (for instance a group of public functions) to be put as a subgroup of that
341
400
# type (e.g. under the Public Functions section). Set it to NO to prevent
394
453
# Build related configuration options
395
454
#---------------------------------------------------------------------------
397
# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
456
# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
398
457
# documentation are documented, even if no documentation was available. Private
399
458
# class members and static file members will be hidden unless the
400
459
# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES.
405
464
EXTRACT_ALL = YES
407
# If the EXTRACT_PRIVATE tag is set to YES all private members of a class will
466
# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will
408
467
# be included in the documentation.
409
468
# The default value is: NO.
411
470
EXTRACT_PRIVATE = YES
413
# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
472
# If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual
473
# methods of a class will be included in the documentation.
474
# The default value is: NO.
476
EXTRACT_PRIV_VIRTUAL = NO
478
# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal
414
479
# scope will be included in the documentation.
415
480
# The default value is: NO.
417
482
EXTRACT_PACKAGE = NO
419
# If the EXTRACT_STATIC tag is set to YES all static members of a file will be
484
# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be
420
485
# included in the documentation.
421
486
# The default value is: NO.
423
488
EXTRACT_STATIC = YES
425
# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) defined
426
# locally in source files will be included in the documentation. If set to NO
490
# If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined
491
# locally in source files will be included in the documentation. If set to NO,
427
492
# only classes defined in header files are included. Does not have any effect
428
493
# for Java sources.
429
494
# The default value is: YES.
431
496
EXTRACT_LOCAL_CLASSES = YES
433
# This flag is only useful for Objective-C code. When set to YES local methods,
498
# This flag is only useful for Objective-C code. If set to YES, local methods,
434
499
# which are defined in the implementation section but not in the interface are
435
# included in the documentation. If set to NO only methods in the interface are
500
# included in the documentation. If set to NO, only methods in the interface are
437
502
# The default value is: NO.
458
523
# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all
459
524
# undocumented classes that are normally visible in the class hierarchy. If set
460
# to NO these classes will be included in the various overviews. This option has
461
# no effect if EXTRACT_ALL is enabled.
525
# to NO, these classes will be included in the various overviews. This option
526
# has no effect if EXTRACT_ALL is enabled.
462
527
# The default value is: NO.
464
529
HIDE_UNDOC_CLASSES = NO
466
531
# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend
467
# (class|struct|union) declarations. If set to NO these declarations will be
468
# included in the documentation.
532
# declarations. If set to NO, these declarations will be included in the
469
534
# The default value is: NO.
471
536
HIDE_FRIEND_COMPOUNDS = NO
473
538
# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any
474
# documentation blocks found inside the body of a function. If set to NO these
539
# documentation blocks found inside the body of a function. If set to NO, these
475
540
# blocks will be appended to the function's detailed documentation block.
476
541
# The default value is: NO.
485
550
INTERNAL_DOCS = NO
487
552
# If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file
488
# names in lower-case letters. If set to YES upper-case letters are also
553
# names in lower-case letters. If set to YES, upper-case letters are also
489
554
# allowed. This is useful if you have classes or files whose names only differ
490
555
# in case and if your file system supports case sensitive file names. Windows
491
# and Mac users are advised to set this option to NO.
556
# (including Cygwin) ands Mac users are advised to set this option to NO.
492
557
# The default value is: system dependent.
494
559
CASE_SENSE_NAMES = YES
496
561
# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with
497
# their full class and namespace scopes in the documentation. If set to YES the
562
# their full class and namespace scopes in the documentation. If set to YES, the
498
563
# scope will be hidden.
499
564
# The default value is: NO.
501
566
HIDE_SCOPE_NAMES = NO
568
# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will
569
# append additional text to a page's title, such as Class Reference. If set to
570
# YES the compound reference will be hidden.
571
# The default value is: NO.
573
HIDE_COMPOUND_REFERENCE= NO
503
575
# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of
504
576
# the files that are included by a file in the documentation of that file.
505
577
# The default value is: YES.
528
600
# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the
529
601
# (detailed) documentation of file and class members alphabetically by member
530
# name. If set to NO the members will appear in declaration order.
602
# name. If set to NO, the members will appear in declaration order.
531
603
# The default value is: YES.
533
605
SORT_MEMBER_DOCS = YES
535
607
# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief
536
608
# descriptions of file, namespace and class members alphabetically by member
537
# name. If set to NO the members will appear in declaration order. Note that
609
# name. If set to NO, the members will appear in declaration order. Note that
538
610
# this will also influence the order of the classes in the class list.
539
611
# The default value is: NO.
580
652
STRICT_PROTO_MATCHING = NO
582
# The GENERATE_TODOLIST tag can be used to enable ( YES) or disable ( NO) the
583
# todo list. This list is created by putting \todo commands in the
654
# The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo
655
# list. This list is created by putting \todo commands in the documentation.
585
656
# The default value is: YES.
587
658
GENERATE_TODOLIST = YES
589
# The GENERATE_TESTLIST tag can be used to enable ( YES) or disable ( NO) the
590
# test list. This list is created by putting \test commands in the
660
# The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test
661
# list. This list is created by putting \test commands in the documentation.
592
662
# The default value is: YES.
594
664
GENERATE_TESTLIST = YES
596
# The GENERATE_BUGLIST tag can be used to enable ( YES) or disable ( NO) the bug
666
# The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug
597
667
# list. This list is created by putting \bug commands in the documentation.
598
668
# The default value is: YES.
600
670
GENERATE_BUGLIST = YES
602
# The GENERATE_DEPRECATEDLIST tag can be used to enable ( YES) or disable ( NO)
672
# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO)
603
673
# the deprecated list. This list is created by putting \deprecated commands in
604
674
# the documentation.
605
675
# The default value is: YES.
624
694
MAX_INITIALIZER_LINES = 30
626
696
# Set the SHOW_USED_FILES tag to NO to disable the list of files generated at
627
# the bottom of the documentation of classes and structs. If set to YES the list
628
# will mention the files that were used to generate the documentation.
697
# the bottom of the documentation of classes and structs. If set to YES, the
698
# list will mention the files that were used to generate the documentation.
629
699
# The default value is: YES.
631
701
SHOW_USED_FILES = YES
670
740
# The CITE_BIB_FILES tag can be used to specify one or more bib files containing
671
741
# the reference definitions. This must be a list of .bib files. The .bib
672
742
# extension is automatically appended if omitted. This requires the bibtex tool
673
# to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.
743
# to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info.
674
744
# For LaTeX the style of the bibliography can be controlled using
675
745
# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
676
# search path. Do not use file names with spaces, bibtex cannot handle them. See
677
# also \cite for info how to create references.
746
# search path. See also \cite for info how to create references.
716
785
# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that
717
786
# are documented, but have no documentation for their parameters or return
718
# value. If set to NO doxygen will only warn about wrong or incomplete parameter
719
# documentation, but not about the absence of documentation.
787
# value. If set to NO, doxygen will only warn about wrong or incomplete
788
# parameter documentation, but not about the absence of documentation. If
789
# EXTRACT_ALL is set to YES then this flag will automatically be disabled.
720
790
# The default value is: NO.
722
792
WARN_NO_PARAMDOC = NO
794
# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when
795
# a warning is encountered.
796
# The default value is: NO.
724
800
# The WARN_FORMAT tag determines the format of the warning messages that doxygen
725
801
# can produce. The string should contain the $file, $line, and $text tags, which
726
802
# will be replaced by the file and line number from which the warning originated
761
837
# If the value of the INPUT tag contains directories, you can use the
762
838
# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and
763
# *.h) to filter out the source-files in the directories. If left blank the
764
# following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii,
765
# *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp,
766
# *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown,
767
# *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf,
768
# *.qsf, *.as and *.js.
839
# *.h) to filter out the source-files in the directories.
841
# Note that for custom extensions or not directly supported extensions you also
842
# need to set EXTENSION_MAPPING for the extension otherwise the files are not
845
# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp,
846
# *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h,
847
# *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc,
848
# *.m, *.markdown, *.md, *.mm, *.dox (to be provided as doxygen C comment),
849
# *.doc (to be provided as doxygen C comment), *.txt (to be provided as doxygen
850
# C comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, *.f, *.for, *.tcl, *.vhd,
851
# *.vhdl, *.ucf, *.qsf and *.ice.
770
853
FILE_PATTERNS = *.h \
865
954
# (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how
866
955
# filters are used. If the FILTER_PATTERNS tag is empty or if none of the
867
956
# patterns match the file name, INPUT_FILTER is applied.
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
# properly processed by doxygen.
869
962
FILTER_PATTERNS =
871
964
# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
872
# INPUT_FILTER ) will also be used to filter the input files that are used for
965
# INPUT_FILTER) will also be used to filter the input files that are used for
873
966
# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES).
874
967
# The default value is: NO.
949
1042
# If the USE_HTAGS tag is set to YES then the references to source code will
950
1043
# point to the HTML generated by the htags(1) tool instead of doxygen built-in
951
1044
# source browser. The htags tool is part of GNU's global source tagging system
952
# (see http://www.gnu.org/software/global/global.html). You will need version
1045
# (see https://www.gnu.org/software/global/global.html). You will need version
953
1046
# 4.8.6 or higher.
955
1048
# To use it do the following:
956
1049
# - Install the latest version of global
957
# - Enable SOURCE_BROWSER and USE_HTAGS in the config file
1050
# - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file
958
1051
# - Make sure the INPUT points to the root of the source tree
959
1052
# - Run doxygen as normal
977
1070
VERBATIM_HEADERS = NO
1072
# If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the
1073
# clang parser (see: http://clang.llvm.org/) for more accurate parsing at the
1074
# cost of reduced performance. This can be particularly helpful with template
1075
# rich C++ code for which doxygen's built-in parser lacks the necessary type
1077
# Note: The availability of this option depends on whether or not doxygen was
1078
# generated with the -Duse_libclang=ON option for CMake.
1079
# The default value is: NO.
1081
CLANG_ASSISTED_PARSING = NO
1083
# If clang assisted parsing is enabled you can provide the compiler with command
1084
# line options that you would normally use when invoking the compiler. Note that
1085
# the include paths will already be set by doxygen for the files and directories
1086
# specified with INPUT and INCLUDE_PATH.
1087
# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES.
1091
# If clang assisted parsing is enabled you can provide the clang parser with the
1092
# path to the compilation database (see:
1093
# http://clang.llvm.org/docs/HowToSetupToolingForLLVM.html) used when the files
1094
# were built. This is equivalent to specifying the "-p" option to a clang tool,
1095
# such as clang-check. These options will then be passed to the parser.
1096
# Note: The availability of this option depends on whether or not doxygen was
1097
# generated with the -Duse_libclang=ON option for CMake.
1099
CLANG_DATABASE_PATH =
979
1101
#---------------------------------------------------------------------------
980
1102
# Configuration options related to the alphabetical class index
981
1103
#---------------------------------------------------------------------------
1069
1191
HTML_STYLESHEET =
1071
# The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
1072
# defined cascading style sheet that is included after the standard style sheets
1193
# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1194
# cascading style sheets that are included after the standard style sheets
1073
1195
# created by doxygen. Using this option one can overrule certain style aspects.
1074
1196
# This is preferred over using HTML_STYLESHEET since it does not replace the
1075
# standard style sheet and is therefor more robust against future updates.
1076
# Doxygen will copy the style sheet file to the output directory. For an example
1077
# see the documentation.
1197
# standard style sheet and is therefore more robust against future updates.
1198
# Doxygen will copy the style sheet files to the output directory.
1199
# Note: The order of the extra style sheet files is of importance (e.g. the last
1200
# style sheet in the list overrules the setting of the previous ones in the
1201
# list). For an example see the documentation.
1078
1202
# This tag requires that the tag GENERATE_HTML is set to YES.
1080
1204
HTML_EXTRA_STYLESHEET =
1090
1214
HTML_EXTRA_FILES =
1092
1216
# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen
1093
# will adjust the colors in the stylesheet and background images according to
1217
# will adjust the colors in the style sheet and background images according to
1094
1218
# this color. Hue is specified as an angle on a colorwheel, see
1095
# http://en.wikipedia.org/wiki/Hue for more information. For instance the value
1219
# https://en.wikipedia.org/wiki/Hue for more information. For instance the value
1096
1220
# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300
1097
1221
# purple, and 360 is red again.
1098
1222
# Minimum value: 0, maximum value: 359, default value: 220.
1122
1246
# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
1123
1247
# page will contain the date and time when the page was generated. Setting this
1124
# to NO can help when comparing the output of multiple runs.
1125
# The default value is: YES.
1248
# to YES can help to show when doxygen was last run and thus if the
1249
# documentation is up to date.
1250
# The default value is: NO.
1126
1251
# This tag requires that the tag GENERATE_HTML is set to YES.
1128
1253
HTML_TIMESTAMP = YES
1255
# If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML
1256
# documentation will contain a main index with vertical navigation menus that
1257
# are dynamically created via JavaScript. If disabled, the navigation index will
1258
# consists of multiple levels of tabs that are statically embedded in every HTML
1259
# page. Disable this option to support browsers that do not have JavaScript,
1260
# like the Qt help browser.
1261
# The default value is: YES.
1262
# This tag requires that the tag GENERATE_HTML is set to YES.
1264
HTML_DYNAMIC_MENUS = YES
1130
1266
# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
1131
1267
# documentation will contain sections that can be hidden and shown after the
1132
1268
# page has loaded.
1151
1287
# If the GENERATE_DOCSET tag is set to YES, additional index files will be
1152
1288
# generated that can be used as input for Apple's Xcode 3 integrated development
1153
# environment (see: http://developer.apple.com/tools/xcode/), introduced with
1154
# OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a
1289
# environment (see: https://developer.apple.com/xcode/), introduced with OSX
1290
# 10.5 (Leopard). To create a documentation set, doxygen will generate a
1155
1291
# Makefile in the HTML output directory. Running make will produce the docset in
1156
1292
# that directory and running make install will install the docset in
1157
1293
# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1158
# startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
1159
# for more information.
1294
# startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy
1295
# genXcode/_index.html for more information.
1160
1296
# The default value is: NO.
1161
1297
# This tag requires that the tag GENERATE_HTML is set to YES.
1195
1331
# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three
1196
1332
# additional HTML index files: index.hhp, index.hhc, and index.hhk. The
1197
1333
# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop
1198
# (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1334
# (see: https://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1201
1337
# The HTML Help Workshop contains a compiler that can convert all HTML output
1220
1356
# The HHC_LOCATION tag can be used to specify the location (absolute path
1221
# including file name) of the HTML help compiler ( hhc.exe). If non-empty
1357
# including file name) of the HTML help compiler (hhc.exe). If non-empty,
1222
1358
# doxygen will try to run the HTML help compiler on the generated index.hhp.
1223
1359
# The file has to be specified with full path.
1224
1360
# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1228
# The GENERATE_CHI flag controls if a separate .chi index file is generated (
1229
# YES) or that it should be included in the master .chm file ( NO).
1364
# The GENERATE_CHI flag controls if a separate .chi index file is generated
1365
# (YES) or that it should be included in the master .chm file (NO).
1230
1366
# The default value is: NO.
1231
1367
# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1233
1369
GENERATE_CHI = NO
1235
# The CHM_INDEX_ENCODING is used to encode HtmlHelp index ( hhk), content ( hhc)
1371
# The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc)
1236
1372
# and project file content.
1237
1373
# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1239
1375
CHM_INDEX_ENCODING =
1241
# The BINARY_TOC flag controls whether a binary table of contents is generated (
1242
# YES) or a normal table of contents ( NO) in the .chm file.
1377
# The BINARY_TOC flag controls whether a binary table of contents is generated
1378
# (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1379
# enables the Previous and Next buttons.
1243
1380
# The default value is: NO.
1244
1381
# This tag requires that the tag GENERATE_HTMLHELP is set to YES.
1352
1489
# index structure (just like the one that is generated for HTML Help). For this
1353
1490
# to work a browser that supports JavaScript, DHTML, CSS and frames is required
1354
1491
# (i.e. any modern browser). Windows users are probably better off using the
1355
# HTML help feature. Via custom stylesheets (see HTML_EXTRA_STYLESHEET) one can
1492
# HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can
1356
1493
# further fine-tune the look of the index. As an example, the default style
1357
1494
# sheet generated by doxygen has an example that shows how to put an image at
1358
1495
# the root of the tree instead of the PROJECT_NAME. Since the tree basically has
1408
1545
FORMULA_TRANSPARENT = YES
1547
# The FORMULA_MACROFILE can contain LaTeX \newcommand and \renewcommand commands
1548
# to create new LaTeX commands to be used in formulas as building blocks. See
1549
# the section "Including formulas" for details.
1410
1553
# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see
1411
# http://www.mathjax.org) which uses client side Javascript for the rendering
1412
# instead of using prerendered bitmaps. Use this if you do not have LaTeX
1554
# https://www.mathjax.org) which uses client side JavaScript for the rendering
1555
# instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
1413
1556
# installed or if you want to formulas look prettier in the HTML output. When
1414
1557
# enabled you may also need to install MathJax separately and configure the path
1415
1558
# to it using the MATHJAX_RELPATH option.
1435
1578
# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax
1436
1579
# Content Delivery Network so you can quickly see the result without installing
1437
1580
# MathJax. However, it is strongly recommended to install a local copy of
1438
# MathJax from http://www.mathjax.org before deployment.
1439
# The default value is: http://cdn.mathjax.org/mathjax/latest.
1581
# MathJax from https://www.mathjax.org before deployment.
1582
# The default value is: https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/.
1440
1583
# This tag requires that the tag USE_MATHJAX is set to YES.
1442
1585
MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest
1478
1621
SEARCHENGINE = NO
1480
1623
# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
1481
# implemented using a web server instead of a web client using Javascript. There
1482
# are two flavours of web server based searching depending on the
1483
# EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for
1484
# searching and an index file used by the script. When EXTERNAL_SEARCH is
1485
# enabled the indexing and searching needs to be provided by external tools. See
1486
# the section "External Indexing and Searching" for details.
1624
# implemented using a web server instead of a web client using JavaScript. There
1625
# are two flavors of web server based searching depending on the EXTERNAL_SEARCH
1626
# setting. When disabled, doxygen will generate a PHP script for searching and
1627
# an index file used by the script. When EXTERNAL_SEARCH is enabled the indexing
1628
# and searching needs to be provided by external tools. See the section
1629
# "External Indexing and Searching" for details.
1487
1630
# The default value is: NO.
1488
1631
# This tag requires that the tag SEARCHENGINE is set to YES.
1495
1638
# external search engine pointed to by the SEARCHENGINE_URL option to obtain the
1496
1639
# search results.
1498
# Doxygen ships with an example indexer ( doxyindexer) and search engine
1641
# Doxygen ships with an example indexer (doxyindexer) and search engine
1499
1642
# (doxysearch.cgi) which are based on the open source search engine library
1500
# Xapian (see: http://xapian.org/).
1643
# Xapian (see: https://xapian.org/).
1502
1645
# See the section "External Indexing and Searching" for details.
1503
1646
# The default value is: NO.
1508
1651
# The SEARCHENGINE_URL should point to a search engine hosted by a web server
1509
1652
# which will return the search results when EXTERNAL_SEARCH is enabled.
1511
# Doxygen ships with an example indexer ( doxyindexer) and search engine
1654
# Doxygen ships with an example indexer (doxyindexer) and search engine
1512
1655
# (doxysearch.cgi) which are based on the open source search engine library
1513
# Xapian (see: http://xapian.org/). See the section "External Indexing and
1656
# Xapian (see: https://xapian.org/). See the section "External Indexing and
1514
1657
# Searching" for details.
1515
1658
# This tag requires that the tag SEARCHENGINE is set to YES.
1562
1705
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1565
# Note that when enabling USE_PDFLATEX this option is only used for generating
1566
# bitmaps for formulas in the HTML output, but not in the Makefile that is
1567
# written to the output directory.
1568
# The default file is: latex.
1708
# Note that when not enabling USE_PDFLATEX the default is latex when enabling
1709
# USE_PDFLATEX the default is pdflatex and when in the later case latex is
1710
# chosen this is overwritten by pdflatex. For specific output languages the
1711
# default can have been set differently, this depends on the implementation of
1712
# the output language.
1569
1713
# This tag requires that the tag GENERATE_LATEX is set to YES.
1571
1715
LATEX_CMD_NAME = latex
1573
1717
# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to generate
1574
1718
# index for LaTeX.
1719
# Note: This tag is used in the Makefile / make.bat.
1720
# See also: LATEX_MAKEINDEX_CMD for the part in the generated output file
1575
1722
# The default file is: makeindex.
1576
1723
# This tag requires that the tag GENERATE_LATEX is set to YES.
1578
1725
MAKEINDEX_CMD_NAME = makeindex
1580
# If the COMPACT_LATEX tag is set to YES doxygen generates more compact LaTeX
1727
# The LATEX_MAKEINDEX_CMD tag can be used to specify the command name to
1728
# generate index for LaTeX. In case there is no backslash (\) as first character
1729
# it will be automatically added in the LaTeX code.
1730
# Note: This tag is used in the generated output file (.tex).
1731
# See also: MAKEINDEX_CMD_NAME for the part in the Makefile / make.bat.
1732
# The default value is: makeindex.
1733
# This tag requires that the tag GENERATE_LATEX is set to YES.
1735
LATEX_MAKEINDEX_CMD = makeindex
1737
# If the COMPACT_LATEX tag is set to YES, doxygen generates more compact LaTeX
1581
1738
# documents. This may be useful for small projects and may help to save some
1582
1739
# trees in general.
1583
1740
# The default value is: NO.
1595
1752
PAPER_TYPE = a4wide
1597
1754
# The EXTRA_PACKAGES tag can be used to specify one or more LaTeX package names
1598
# that should be included in the LaTeX output. To get the times font for
1599
# instance you can specify
1600
# EXTRA_PACKAGES=times
1755
# that should be included in the LaTeX output. The package can be specified just
1756
# by its name or with the correct syntax as to be used with the LaTeX
1757
# \usepackage command. To get the times font for instance you can specify :
1758
# EXTRA_PACKAGES=times or EXTRA_PACKAGES={times}
1759
# To use the option intlimits with the amsmath package you can specify:
1760
# EXTRA_PACKAGES=[intlimits]{amsmath}
1601
1761
# If left blank no extra packages will be included.
1602
1762
# This tag requires that the tag GENERATE_LATEX is set to YES.
1612
1772
# Note: Only use a user-defined header if you know what you are doing! The
1613
1773
# following commands have a special meaning inside the header: $title,
1614
# $datetime, $date, $doxygenversion, $projectname, $projectnumber. Doxygen will
1615
# replace them by respectively the title of the page, the current date and time,
1616
# only the current date, the version number of doxygen, the project name (see
1617
# PROJECT_NAME), or the project number (see PROJECT_NUMBER).
1774
# $datetime, $date, $doxygenversion, $projectname, $projectnumber,
1775
# $projectbrief, $projectlogo. Doxygen will replace $title with the empty
1776
# string, for the replacement values of the other commands the user is referred
1618
1778
# This tag requires that the tag GENERATE_LATEX is set to YES.
1622
1782
# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for the
1623
1783
# generated LaTeX document. The footer should contain everything after the last
1624
# chapter. If it is left blank doxygen will generate a standard footer.
1784
# chapter. If it is left blank doxygen will generate a standard footer. See
1785
# LATEX_HEADER for more information on how to generate a default footer and what
1786
# special commands can be used inside the footer.
1626
1788
# Note: Only use a user-defined footer if you know what you are doing!
1627
1789
# This tag requires that the tag GENERATE_LATEX is set to YES.
1793
# The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1794
# LaTeX style sheets that are included after the standard style sheets created
1795
# by doxygen. Using this option one can overrule certain style aspects. Doxygen
1796
# will copy the style sheet files to the output directory.
1797
# Note: The order of the extra style sheet files is of importance (e.g. the last
1798
# style sheet in the list overrules the setting of the previous ones in the
1800
# This tag requires that the tag GENERATE_LATEX is set to YES.
1802
LATEX_EXTRA_STYLESHEET =
1631
1804
# The LATEX_EXTRA_FILES tag can be used to specify one or more extra images or
1632
1805
# other source files which should be copied to the LATEX_OUTPUT output
1633
1806
# directory. Note that the files will be copied as-is; there are no commands or
1646
1819
PDF_HYPERLINKS = YES
1648
# If the LATEX_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
1649
# the PDF file directly from the LaTeX files. Set this option to YES to get a
1821
# If the USE_PDFLATEX tag is set to YES, doxygen will use pdflatex to generate
1822
# the PDF file directly from the LaTeX files. Set this option to YES, to get a
1650
1823
# higher quality PDF documentation.
1651
1824
# The default value is: YES.
1652
1825
# This tag requires that the tag GENERATE_LATEX is set to YES.
1682
1855
# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
1683
1856
# bibliography, e.g. plainnat, or ieeetr. See
1684
# http://en.wikipedia.org/wiki/BibTeX and \cite for more info.
1857
# https://en.wikipedia.org/wiki/BibTeX and \cite for more info.
1685
1858
# The default value is: plain.
1686
1859
# This tag requires that the tag GENERATE_LATEX is set to YES.
1688
1861
LATEX_BIB_STYLE = plain
1863
# If the LATEX_TIMESTAMP tag is set to YES then the footer of each generated
1864
# page will contain the date and time when the page was generated. Setting this
1865
# to NO can help when comparing the output of multiple runs.
1866
# The default value is: NO.
1867
# This tag requires that the tag GENERATE_LATEX is set to YES.
1869
LATEX_TIMESTAMP = NO
1871
# The LATEX_EMOJI_DIRECTORY tag is used to specify the (relative or absolute)
1872
# path from which the emoji images will be read. If a relative path is entered,
1873
# it will be relative to the LATEX_OUTPUT directory. If left blank the
1874
# LATEX_OUTPUT directory will be used.
1875
# This tag requires that the tag GENERATE_LATEX is set to YES.
1877
LATEX_EMOJI_DIRECTORY =
1690
1879
#---------------------------------------------------------------------------
1691
1880
# Configuration options related to the RTF output
1692
1881
#---------------------------------------------------------------------------
1694
# If the GENERATE_RTF tag is set to YES doxygen will generate RTF output. The
1883
# If the GENERATE_RTF tag is set to YES, doxygen will generate RTF output. The
1695
1884
# RTF output is optimized for Word 97 and may not look too pretty with other RTF
1696
1885
# readers/editors.
1697
1886
# The default value is: NO.
1727
1916
RTF_HYPERLINKS = NO
1729
# Load stylesheet definitions from file. Syntax is similar to doxygen's config
1730
# file, i.e. a series of assignments. You only have to provide replacements,
1731
# missing definitions are set to their default value.
1918
# Load stylesheet definitions from file. Syntax is similar to doxygen's
1919
# configuration file, i.e. a series of assignments. You only have to provide
1920
# replacements, missing definitions are set to their default value.
1733
1922
# See also section "Doxygen usage" for information on how to generate the
1734
1923
# default style sheet that doxygen normally uses.
1737
1926
RTF_STYLESHEET_FILE =
1739
1928
# Set optional variables used in the generation of an RTF document. Syntax is
1740
# similar to doxygen's config file. A template extensions file can be generated
1741
# using doxygen -e rtf extensionFile.
1929
# similar to doxygen's configuration file. A template extensions file can be
1930
# generated using doxygen -e rtf extensionFile.
1742
1931
# This tag requires that the tag GENERATE_RTF is set to YES.
1744
1933
RTF_EXTENSIONS_FILE =
1935
# If the RTF_SOURCE_CODE tag is set to YES then doxygen will include source code
1936
# with syntax highlighting in the RTF output.
1938
# Note that which sources are shown also depends on other settings such as
1940
# The default value is: NO.
1941
# This tag requires that the tag GENERATE_RTF is set to YES.
1943
RTF_SOURCE_CODE = NO
1746
1945
#---------------------------------------------------------------------------
1747
1946
# Configuration options related to the man page output
1748
1947
#---------------------------------------------------------------------------
1750
# If the GENERATE_MAN tag is set to YES doxygen will generate man pages for
1949
# If the GENERATE_MAN tag is set to YES, doxygen will generate man pages for
1751
1950
# classes and files.
1752
1951
# The default value is: NO.
1772
1971
MAN_EXTENSION = .3
1973
# The MAN_SUBDIR tag determines the name of the directory created within
1974
# MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
1975
# MAN_EXTENSION with the initial . removed.
1976
# This tag requires that the tag GENERATE_MAN is set to YES.
1774
1980
# If the MAN_LINKS tag is set to YES and doxygen generates man output, then it
1775
1981
# will generate one additional man file for each entity documented in the real
1776
1982
# man page(s). These additional files only source the real man page, but without
1799
2005
XML_OUTPUT = xml
1801
# The XML_SCHEMA tag can be used to specify a XML schema, which can be used by a
1802
# validating XML parser to check the syntax of the XML files.
1803
# This tag requires that the tag GENERATE_XML is set to YES.
1807
# The XML_DTD tag can be used to specify a XML DTD, which can be used by a
1808
# validating XML parser to check the syntax of the XML files.
1809
# This tag requires that the tag GENERATE_XML is set to YES.
1813
# If the XML_PROGRAMLISTING tag is set to YES doxygen will dump the program
2007
# If the XML_PROGRAMLISTING tag is set to YES, doxygen will dump the program
1814
2008
# listings (including syntax highlighting and cross-referencing information) to
1815
2009
# the XML output. Note that enabling this will significantly increase the size
1816
2010
# of the XML output.
1820
2014
XML_PROGRAMLISTING = YES
2016
# If the XML_NS_MEMB_FILE_SCOPE tag is set to YES, doxygen will include
2017
# namespace members in file scope as well, matching the HTML output.
2018
# The default value is: NO.
2019
# This tag requires that the tag GENERATE_XML is set to YES.
2021
XML_NS_MEMB_FILE_SCOPE = NO
1822
2023
#---------------------------------------------------------------------------
1823
2024
# Configuration options related to the DOCBOOK output
1824
2025
#---------------------------------------------------------------------------
1826
# If the GENERATE_DOCBOOK tag is set to YES doxygen will generate Docbook files
2027
# If the GENERATE_DOCBOOK tag is set to YES, doxygen will generate Docbook files
1827
2028
# that can be used to generate PDF.
1828
2029
# The default value is: NO.
1838
2039
DOCBOOK_OUTPUT = docbook
2041
# If the DOCBOOK_PROGRAMLISTING tag is set to YES, doxygen will include the
2042
# program listings (including syntax highlighting and cross-referencing
2043
# information) to the DOCBOOK output. Note that enabling this will significantly
2044
# increase the size of the DOCBOOK output.
2045
# The default value is: NO.
2046
# This tag requires that the tag GENERATE_DOCBOOK is set to YES.
2048
DOCBOOK_PROGRAMLISTING = NO
1840
2050
#---------------------------------------------------------------------------
1841
2051
# Configuration options for the AutoGen Definitions output
1842
2052
#---------------------------------------------------------------------------
1844
# If the GENERATE_AUTOGEN_DEF tag is set to YES doxygen will generate an AutoGen
1845
# Definitions (see http://autogen.sf.net) file that captures the structure of
1846
# the code including all documentation. Note that this feature is still
1847
# experimental and incomplete at the moment.
2054
# If the GENERATE_AUTOGEN_DEF tag is set to YES, doxygen will generate an
2055
# AutoGen Definitions (see http://autogen.sourceforge.net/) file that captures
2056
# the structure of the code including all documentation. Note that this feature
2057
# is still experimental and incomplete at the moment.
1848
2058
# The default value is: NO.
1850
2060
GENERATE_AUTOGEN_DEF = NO
1870
2080
PERLMOD_LATEX = NO
1872
# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be nicely
2082
# If the PERLMOD_PRETTY tag is set to YES, the Perl module output will be nicely
1873
2083
# formatted so it can be parsed by a human reader. This is useful if you want to
1874
# understand what is going on. On the other hand, if this tag is set to NO the
2084
# understand what is going on. On the other hand, if this tag is set to NO, the
1875
2085
# size of the Perl module output will be much smaller and Perl will parse it
1876
2086
# just the same.
1877
2087
# The default value is: YES.
1891
2101
# Configuration options related to the preprocessor
1892
2102
#---------------------------------------------------------------------------
1894
# If the ENABLE_PREPROCESSING tag is set to YES doxygen will evaluate all
2104
# If the ENABLE_PREPROCESSING tag is set to YES, doxygen will evaluate all
1895
2105
# C-preprocessor directives found in the sources and include files.
1896
2106
# The default value is: YES.
1898
2108
ENABLE_PREPROCESSING = YES
1900
# If the MACRO_EXPANSION tag is set to YES doxygen will expand all macro names
1901
# in the source code. If set to NO only conditional compilation will be
2110
# If the MACRO_EXPANSION tag is set to YES, doxygen will expand all macro names
2111
# in the source code. If set to NO, only conditional compilation will be
1902
2112
# performed. Macro expansion can be done in a controlled way by setting
1903
2113
# EXPAND_ONLY_PREDEF to YES.
1904
2114
# The default value is: NO.
1956
2166
EXPAND_AS_DEFINED =
1958
2168
# If the SKIP_FUNCTION_MACROS tag is set to YES then doxygen's preprocessor will
1959
# remove all refrences to function-like macros that are alone on a line, have an
1960
# all uppercase name, and do not end with a semicolon. Such function macros are
1961
# typically used for boiler-plate code, and will confuse the parser if not
2169
# remove all references to function-like macros that are alone on a line, have
2170
# an all uppercase name, and do not end with a semicolon. Such function macros
2171
# are typically used for boiler-plate code, and will confuse the parser if not
1963
2173
# The default value is: YES.
1964
2174
# This tag requires that the tag ENABLE_PREPROCESSING is set to YES.
1991
2201
GENERATE_TAGFILE =
1993
# If the ALLEXTERNALS tag is set to YES all external class will be listed in the
1994
# class index. If set to NO only the inherited external classes will be listed.
2203
# If the ALLEXTERNALS tag is set to YES, all external class will be listed in
2204
# the class index. If set to NO, only the inherited external classes will be
1995
2206
# The default value is: NO.
1997
2208
ALLEXTERNALS = NO
1999
# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed in
2000
# the modules index. If set to NO, only the current project's groups will be
2210
# If the EXTERNAL_GROUPS tag is set to YES, all external groups will be listed
2211
# in the modules index. If set to NO, only the current project's groups will be
2002
2213
# The default value is: YES.
2004
2215
EXTERNAL_GROUPS = YES
2006
# If the EXTERNAL_PAGES tag is set to YES all external pages will be listed in
2217
# If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
2007
2218
# the related pages index. If set to NO, only the current project's pages will
2009
2220
# The default value is: YES.
2011
2222
EXTERNAL_PAGES = YES
2013
# The PERL_PATH should be the absolute path and name of the perl script
2014
# interpreter (i.e. the result of 'which perl').
2015
# The default file (with absolute path) is: /usr/bin/perl.
2017
PERL_PATH = /usr/bin/perl
2019
2224
#---------------------------------------------------------------------------
2020
2225
# Configuration options related to the dot tool
2021
2226
#---------------------------------------------------------------------------
2023
# If the CLASS_DIAGRAMS tag is set to YES doxygen will generate a class diagram
2228
# If the CLASS_DIAGRAMS tag is set to YES, doxygen will generate a class diagram
2024
2229
# (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2025
2230
# NO turns the diagrams off. Note that this option also works with HAVE_DOT
2026
2231
# disabled, but it is recommended to install and use dot, since it yields more
2030
2235
CLASS_DIAGRAMS = NO
2032
# You can define message sequence charts within doxygen comments using the \msc
2033
# command. Doxygen will then run the mscgen tool (see:
2034
# http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2035
# documentation. The MSCGEN_PATH tag allows you to specify the directory where
2036
# the mscgen tool resides. If left empty the tool is assumed to be found in the
2037
# default search path.
2041
2237
# You can include diagrams made with dia in doxygen documentation. Doxygen will
2042
2238
# then run dia to produce the diagram and insert it in the documentation. The
2043
2239
# DIA_PATH tag allows you to specify the directory where the dia binary resides.
2204
2402
DIRECTORY_GRAPH = YES
2206
2404
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
2405
# generated by dot. For an explanation of the image formats see the section
2406
# output formats in the documentation of the dot tool (Graphviz (see:
2407
# http://www.graphviz.org/)).
2208
2408
# Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2209
2409
# to make the SVG files visible in IE 9+ (other browsers do not have this
2210
2410
# requirement).
2211
# Possible values are: png, jpg, gif and svg.
2411
# Possible values are: png, png:cairo, png:cairo:cairo, png:cairo:gd, png:gd,
2412
# png:gd:gd, jpg, jpg:cairo, jpg:cairo:gd, jpg:gd, jpg:gd:gd, gif, gif:cairo,
2413
# gif:cairo:gd, gif:gd, gif:gd:gd, svg, png:gd, png:gd:gd, png:cairo,
2414
# png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and
2415
# png:gdiplus:gdiplus.
2212
2416
# The default value is: png.
2213
2417
# This tag requires that the tag HAVE_DOT is set to YES.
2458
# When using plantuml, the PLANTUML_JAR_PATH tag should be used to specify the
2459
# path where java can find the plantuml.jar file. If left blank, it is assumed
2460
# PlantUML is not used or called during a preprocessing step. Doxygen will
2461
# generate a warning when it encounters a \startuml command in this case and
2462
# will not generate output for the diagram.
2466
# When using plantuml, the PLANTUML_CFG_FILE tag can be used to specify a
2467
# configuration file for plantuml.
2471
# When using plantuml, the specified paths are searched for files specified by
2472
# the !include statement in a plantuml block.
2474
PLANTUML_INCLUDE_PATH =
2254
2476
# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of nodes
2255
2477
# that will be shown in the graph. If the number of nodes in a graph becomes
2256
2478
# larger than this value, doxygen will truncate the graph, which is visualized