3
# This file describes the settings to be used by the documentation system
4
# doxygen (www.doxygen.org) for a project
6
# All text after a hash (#) is considered a comment and will be ignored
8
# TAG = value [value, ...]
9
# For lists items can also be appended using:
10
# TAG += value [value, ...]
11
# Values that contain spaces should be placed between quotes (" ")
13
#---------------------------------------------------------------------------
14
# Project related configuration options
15
#---------------------------------------------------------------------------
17
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
18
# by quotes) that should identify the project.
20
PROJECT_NAME = IrisNet
22
# The PROJECT_NUMBER tag can be used to enter a project or revision number.
23
# This could be handy for archiving the generated documentation or
24
# if some version control system is used.
28
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
29
# base path where the generated documentation will be put.
30
# If a relative path is entered, it will be relative to the location
31
# where doxygen was started. If left blank the current directory will be used.
33
OUTPUT_DIRECTORY = docs
35
# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
36
# 4096 sub-directories (in 2 levels) under the output directory of each output
37
# format and will distribute the generated files over these directories.
38
# Enabling this option can be useful when feeding doxygen a huge amount of
39
# source files, where putting all generated files in the same directory would
40
# otherwise cause performance problems for the file system.
44
# The OUTPUT_LANGUAGE tag is used to specify the language in which all
45
# documentation generated by doxygen is written. Doxygen will use this
46
# information to generate all constant output in the proper language.
47
# The default language is English, other supported languages are:
48
# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,
49
# Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,
50
# Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,
51
# Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,
52
# Swedish, and Ukrainian.
54
OUTPUT_LANGUAGE = English
56
# This tag can be used to specify the encoding used in the generated output.
57
# The encoding is not always determined by the language that is chosen,
58
# but also whether or not the output is meant for Windows or non-Windows users.
59
# In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
60
# forces the Windows encoding (this is the default for the Windows binary),
61
# whereas setting the tag to NO uses a Unix-style encoding (the default for
62
# all platforms other than Windows).
64
USE_WINDOWS_ENCODING = NO
66
# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
67
# include brief member descriptions after the members that are listed in
68
# the file and class documentation (similar to JavaDoc).
69
# Set to NO to disable this.
71
BRIEF_MEMBER_DESC = NO
73
# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
74
# the brief description of a member or function before the detailed description.
75
# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
76
# brief descriptions will be completely suppressed.
80
# This tag implements a quasi-intelligent brief description abbreviator
81
# that is used to form the text in various listings. Each string
82
# in this list, if found as the leading text of the brief description, will be
83
# stripped from the text and the result after processing the whole list, is
84
# used as the annotated text. Otherwise, the brief description is used as-is.
85
# If left blank, the following values are used ("$name" is automatically
86
# replaced with the name of the entity): "The $name class" "The $name widget"
87
# "The $name file" "is" "provides" "specifies" "contains"
88
# "represents" "a" "an" "the"
92
# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
93
# Doxygen will generate a detailed section even if there is only a brief
96
ALWAYS_DETAILED_SEC = NO
98
# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
99
# inherited members of a class in the documentation of that class as if those
100
# members were ordinary class members. Constructors, destructors and assignment
101
# operators of the base classes will not be shown.
103
INLINE_INHERITED_MEMB = NO
105
# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
106
# path before files name in the file list and in the header files. If set
107
# to NO the shortest path that makes the file name unique will be used.
109
FULL_PATH_NAMES = YES
111
# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
112
# can be used to strip a user-defined part of the path. Stripping is
113
# only done if one of the specified strings matches the left-hand part of
114
# the path. The tag can be used to show relative paths in the file list.
115
# If left blank the directory from which doxygen is run is used as the
120
# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
121
# the path mentioned in the documentation of a class, which tells
122
# the reader which header file to include in order to use a class.
123
# If left blank only the name of the header file containing the class
124
# definition is used. Otherwise one should specify the include paths that
125
# are normally passed to the compiler using the -I flag.
127
STRIP_FROM_INC_PATH =
129
# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
130
# (but less readable) file names. This can be useful is your file systems
131
# doesn't support long names like on DOS, Mac, or CD-ROM.
135
# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
136
# will interpret the first line (until the first dot) of a JavaDoc-style
137
# comment as the brief description. If set to NO, the JavaDoc
138
# comments will behave just like the Qt-style comments (thus requiring an
139
# explicit @brief command for a brief description.
141
JAVADOC_AUTOBRIEF = NO
143
# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
144
# treat a multi-line C++ special comment block (i.e. a block of //! or ///
145
# comments) as a brief description. This used to be the default behaviour.
146
# The new default is to treat a multi-line C++ comment block as a detailed
147
# description. Set this tag to YES if you prefer the old behaviour instead.
149
MULTILINE_CPP_IS_BRIEF = NO
151
# If the DETAILS_AT_TOP tag is set to YES then Doxygen
152
# will output the detailed description near the top, like JavaDoc.
153
# If set to NO, the detailed description appears after the member
158
# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
159
# member inherits the documentation from any documented member that it
164
# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
165
# tag is set to YES, then doxygen will reuse the documentation of the first
166
# member in the group (if any) for the other members of the group. By default
167
# all members of a group must be documented explicitly.
169
DISTRIBUTE_GROUP_DOC = NO
171
# The TAB_SIZE tag can be used to set the number of spaces in a tab.
172
# Doxygen uses this value to replace tabs by spaces in code fragments.
176
# This tag can be used to specify a number of aliases that acts
177
# as commands in the documentation. An alias has the form "name=value".
178
# For example adding "sideeffect=\par Side Effects:\n" will allow you to
179
# put the command \sideeffect (or @sideeffect) in the documentation, which
180
# will result in a user-defined paragraph with heading "Side Effects:".
181
# You can put \n's in the value part of an alias to insert newlines.
185
# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
186
# sources only. Doxygen will then generate output that is more tailored for C.
187
# For instance, some of the names that are used will be different. The list
188
# of all members will be omitted, etc.
190
OPTIMIZE_OUTPUT_FOR_C = NO
192
# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
193
# only. Doxygen will then generate output that is more tailored for Java.
194
# For instance, namespaces will be presented as packages, qualified scopes
195
# will look different, etc.
197
OPTIMIZE_OUTPUT_JAVA = NO
199
# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
200
# the same type (for instance a group of public functions) to be put as a
201
# subgroup of that type (e.g. under the Public Functions section). Set it to
202
# NO to prevent subgrouping. Alternatively, this can be done per class using
203
# the \nosubgrouping command.
207
#---------------------------------------------------------------------------
208
# Build related configuration options
209
#---------------------------------------------------------------------------
211
# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
212
# documentation are documented, even if no documentation was available.
213
# Private class members and static file members will be hidden unless
214
# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
218
# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
219
# will be included in the documentation.
223
# If the EXTRACT_STATIC tag is set to YES all static members of a file
224
# will be included in the documentation.
228
# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
229
# defined locally in source files will be included in the documentation.
230
# If set to NO only classes defined in header files are included.
232
EXTRACT_LOCAL_CLASSES = YES
234
# This flag is only useful for Objective-C code. When set to YES local
235
# methods, which are defined in the implementation section but not in
236
# the interface are included in the documentation.
237
# If set to NO (the default) only methods in the interface are included.
239
EXTRACT_LOCAL_METHODS = NO
241
# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
242
# undocumented members of documented classes, files or namespaces.
243
# If set to NO (the default) these members will be included in the
244
# various overviews, but no documentation section is generated.
245
# This option has no effect if EXTRACT_ALL is enabled.
247
HIDE_UNDOC_MEMBERS = YES
249
# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
250
# undocumented classes that are normally visible in the class hierarchy.
251
# If set to NO (the default) these classes will be included in the various
252
# overviews. This option has no effect if EXTRACT_ALL is enabled.
254
HIDE_UNDOC_CLASSES = YES
256
# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
257
# friend (class|struct|union) declarations.
258
# If set to NO (the default) these declarations will be included in the
261
HIDE_FRIEND_COMPOUNDS = NO
263
# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
264
# documentation blocks found inside the body of a function.
265
# If set to NO (the default) these blocks will be appended to the
266
# function's detailed documentation block.
268
HIDE_IN_BODY_DOCS = NO
270
# The INTERNAL_DOCS tag determines if documentation
271
# that is typed after a \internal command is included. If the tag is set
272
# to NO (the default) then the documentation will be excluded.
273
# Set it to YES to include the internal documentation.
277
# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
278
# file names in lower-case letters. If set to YES upper-case letters are also
279
# allowed. This is useful if you have classes or files whose names only differ
280
# in case and if your file system supports case sensitive file names. Windows
281
# and Mac users are advised to set this option to NO.
283
CASE_SENSE_NAMES = YES
285
# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
286
# will show members with their full class and namespace scopes in the
287
# documentation. If set to YES the scope will be hidden.
289
HIDE_SCOPE_NAMES = NO
291
# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
292
# will put a list of the files that are included by a file in the documentation
295
SHOW_INCLUDE_FILES = YES
297
# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
298
# is inserted in the documentation for inline members.
302
# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
303
# will sort the (detailed) documentation of file and class members
304
# alphabetically by member name. If set to NO the members will appear in
307
SORT_MEMBER_DOCS = YES
309
# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
310
# brief documentation of file, namespace and class members alphabetically
311
# by member name. If set to NO (the default) the members will appear in
316
# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
317
# sorted by fully-qualified names, including namespaces. If set to
318
# NO (the default), the class list will be sorted only by class name,
319
# not including the namespace part.
320
# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
321
# Note: This option applies only to the class list, not to the
324
SORT_BY_SCOPE_NAME = NO
326
# The GENERATE_TODOLIST tag can be used to enable (YES) or
327
# disable (NO) the todo list. This list is created by putting \todo
328
# commands in the documentation.
330
GENERATE_TODOLIST = YES
332
# The GENERATE_TESTLIST tag can be used to enable (YES) or
333
# disable (NO) the test list. This list is created by putting \test
334
# commands in the documentation.
336
GENERATE_TESTLIST = YES
338
# The GENERATE_BUGLIST tag can be used to enable (YES) or
339
# disable (NO) the bug list. This list is created by putting \bug
340
# commands in the documentation.
342
GENERATE_BUGLIST = YES
344
# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
345
# disable (NO) the deprecated list. This list is created by putting
346
# \deprecated commands in the documentation.
348
GENERATE_DEPRECATEDLIST= YES
350
# The ENABLED_SECTIONS tag can be used to enable conditional
351
# documentation sections, marked by \if sectionname ... \endif.
355
# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
356
# the initial value of a variable or define consists of for it to appear in
357
# the documentation. If the initializer consists of more lines than specified
358
# here it will be hidden. Use a value of 0 to hide initializers completely.
359
# The appearance of the initializer of individual variables and defines in the
360
# documentation can be controlled using \showinitializer or \hideinitializer
361
# command in the documentation regardless of this setting.
363
MAX_INITIALIZER_LINES = 30
365
# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
366
# at the bottom of the documentation of classes and structs. If set to YES the
367
# list will mention the files that were used to generate the documentation.
369
SHOW_USED_FILES = YES
371
# If the sources in your project are distributed over multiple directories
372
# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
373
# in the documentation.
375
SHOW_DIRECTORIES = YES
377
# The FILE_VERSION_FILTER tag can be used to specify a program or script that
378
# doxygen should invoke to get the current version for each file (typically from the
379
# version control system). Doxygen will invoke the program by executing (via
380
# popen()) the command <command> <input-file>, where <command> is the value of
381
# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
382
# provided by doxygen. Whatever the progam writes to standard output
383
# is used as the file version. See the manual for examples.
385
FILE_VERSION_FILTER =
387
#---------------------------------------------------------------------------
388
# configuration options related to warning and progress messages
389
#---------------------------------------------------------------------------
391
# The QUIET tag can be used to turn on/off the messages that are generated
392
# by doxygen. Possible values are YES and NO. If left blank NO is used.
396
# The WARNINGS tag can be used to turn on/off the warning messages that are
397
# generated by doxygen. Possible values are YES and NO. If left blank
402
# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
403
# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
404
# automatically be disabled.
406
WARN_IF_UNDOCUMENTED = YES
408
# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
409
# potential errors in the documentation, such as not documenting some
410
# parameters in a documented function, or documenting parameters that
411
# don't exist or using markup commands wrongly.
413
WARN_IF_DOC_ERROR = YES
415
# This WARN_NO_PARAMDOC option can be abled to get warnings for
416
# functions that are documented, but have no documentation for their parameters
417
# or return value. If set to NO (the default) doxygen will only warn about
418
# wrong or incomplete parameter documentation, but not about the absence of
421
WARN_NO_PARAMDOC = NO
423
# The WARN_FORMAT tag determines the format of the warning messages that
424
# doxygen can produce. The string should contain the $file, $line, and $text
425
# tags, which will be replaced by the file and line number from which the
426
# warning originated and the warning text. Optionally the format may contain
427
# $version, which will be replaced by the version of the file (if it could
428
# be obtained via FILE_VERSION_FILTER)
430
WARN_FORMAT = "$file:$line: $text"
432
# The WARN_LOGFILE tag can be used to specify a file to which warning
433
# and error messages should be written. If left blank the output is written
438
#---------------------------------------------------------------------------
439
# configuration options related to the input files
440
#---------------------------------------------------------------------------
442
# The INPUT tag can be used to specify the files and/or directories that contain
443
# documented source files. You may enter file names like "myfile.cpp" or
444
# directories like "/usr/src/myproject". Separate the files or directories
449
# If the value of the INPUT tag contains directories, you can use the
450
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
451
# and *.h) to filter out the source-files in the directories. If left
452
# blank the following patterns are tested:
453
# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
454
# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
458
# The RECURSIVE tag can be used to turn specify whether or not subdirectories
459
# should be searched for input files as well. Possible values are YES and NO.
460
# If left blank NO is used.
464
# The EXCLUDE tag can be used to specify files and/or directories that should
465
# excluded from the INPUT source files. This way you can easily exclude a
466
# subdirectory from a directory tree whose root is specified with the INPUT tag.
470
# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
471
# directories that are symbolic links (a Unix filesystem feature) are excluded
474
EXCLUDE_SYMLINKS = NO
476
# If the value of the INPUT tag contains directories, you can use the
477
# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
478
# certain files from those directories.
480
EXCLUDE_PATTERNS = *.moc.* \
483
# The EXAMPLE_PATH tag can be used to specify one or more files or
484
# directories that contain example code fragments that are included (see
485
# the \include command).
489
# If the value of the EXAMPLE_PATH tag contains directories, you can use the
490
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
491
# and *.h) to filter out the source-files in the directories. If left
492
# blank all files are included.
496
# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
497
# searched for input files to be used with the \include or \dontinclude
498
# commands irrespective of the value of the RECURSIVE tag.
499
# Possible values are YES and NO. If left blank NO is used.
501
EXAMPLE_RECURSIVE = NO
503
# The IMAGE_PATH tag can be used to specify one or more files or
504
# directories that contain image that are included in the documentation (see
505
# the \image command).
509
# The INPUT_FILTER tag can be used to specify a program that doxygen should
510
# invoke to filter for each input file. Doxygen will invoke the filter program
511
# by executing (via popen()) the command <filter> <input-file>, where <filter>
512
# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
513
# input file. Doxygen will then use the output that the filter program writes
514
# to standard output. If FILTER_PATTERNS is specified, this tag will be
519
# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
520
# basis. Doxygen will compare the file name with each pattern and apply the
521
# filter if there is a match. The filters are a list of the form:
522
# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
523
# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
524
# is applied to all files.
528
# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
529
# INPUT_FILTER) will be used to filter the input files when producing source
530
# files to browse (i.e. when SOURCE_BROWSER is set to YES).
532
FILTER_SOURCE_FILES = NO
534
#---------------------------------------------------------------------------
535
# configuration options related to source browsing
536
#---------------------------------------------------------------------------
538
# If the SOURCE_BROWSER tag is set to YES then a list of source files will
539
# be generated. Documented entities will be cross-referenced with these sources.
540
# Note: To get rid of all source code in the generated output, make sure also
541
# VERBATIM_HEADERS is set to NO.
545
# Setting the INLINE_SOURCES tag to YES will include the body
546
# of functions and classes directly in the documentation.
550
# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
551
# doxygen to hide any special comment blocks from generated source code
552
# fragments. Normal C and C++ comments will always remain visible.
554
STRIP_CODE_COMMENTS = YES
556
# If the REFERENCED_BY_RELATION tag is set to YES (the default)
557
# then for each documented function all documented
558
# functions referencing it will be listed.
560
REFERENCED_BY_RELATION = YES
562
# If the REFERENCES_RELATION tag is set to YES (the default)
563
# then for each documented function all documented entities
564
# called/used by that function will be listed.
566
REFERENCES_RELATION = YES
568
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
569
# will generate a verbatim copy of the header file for each class for
570
# which an include is specified. Set to NO to disable this.
572
VERBATIM_HEADERS = YES
574
#---------------------------------------------------------------------------
575
# configuration options related to the alphabetical class index
576
#---------------------------------------------------------------------------
578
# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
579
# of all compounds will be generated. Enable this if the project
580
# contains a lot of classes, structs, unions or interfaces.
582
ALPHABETICAL_INDEX = NO
584
# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
585
# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
586
# in which this list will be split (can be a number in the range [1..20])
588
COLS_IN_ALPHA_INDEX = 5
590
# In case all classes in a project start with a common prefix, all
591
# classes will be put under the same header in the alphabetical index.
592
# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
593
# should be ignored while generating the index headers.
597
#---------------------------------------------------------------------------
598
# configuration options related to the HTML output
599
#---------------------------------------------------------------------------
601
# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
602
# generate HTML output.
606
# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
607
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
608
# put in front of it. If left blank `html' will be used as the default path.
612
# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
613
# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
614
# doxygen will generate files with .html extension.
616
HTML_FILE_EXTENSION = .html
618
# The HTML_HEADER tag can be used to specify a personal HTML header for
619
# each generated HTML page. If it is left blank doxygen will generate a
624
# The HTML_FOOTER tag can be used to specify a personal HTML footer for
625
# each generated HTML page. If it is left blank doxygen will generate a
630
# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
631
# style sheet that is used by each HTML page. It can be used to
632
# fine-tune the look of the HTML output. If the tag is left blank doxygen
633
# will generate a default style sheet. Note that doxygen will try to copy
634
# the style sheet file to the HTML output directory, so don't put your own
635
# stylesheet in the HTML output directory as well, or it will be erased!
639
# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
640
# files or namespaces will be aligned in HTML using tables. If set to
641
# NO a bullet list will be used.
643
HTML_ALIGN_MEMBERS = YES
645
# If the GENERATE_HTMLHELP tag is set to YES, additional index files
646
# will be generated that can be used as input for tools like the
647
# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
648
# of the generated HTML documentation.
650
GENERATE_HTMLHELP = NO
652
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
653
# be used to specify the file name of the resulting .chm file. You
654
# can add a path in front of the file if the result should not be
655
# written to the html output directory.
659
# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
660
# be used to specify the location (absolute path including file name) of
661
# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
662
# the HTML help compiler on the generated index.hhp.
666
# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
667
# controls if a separate .chi index file is generated (YES) or that
668
# it should be included in the master .chm file (NO).
672
# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
673
# controls whether a binary table of contents is generated (YES) or a
674
# normal table of contents (NO) in the .chm file.
678
# The TOC_EXPAND flag can be set to YES to add extra items for group members
679
# to the contents of the HTML help documentation and to the tree view.
683
# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
684
# top of each HTML page. The value NO (the default) enables the index and
685
# the value YES disables it.
689
# This tag can be used to set the number of enum values (range [1..20])
690
# that doxygen will group on one line in the generated HTML documentation.
692
ENUM_VALUES_PER_LINE = 4
694
# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
695
# generated containing a tree-like index structure (just like the one that
696
# is generated for HTML Help). For this to work a browser that supports
697
# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
698
# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
699
# probably better off using the HTML help feature.
701
GENERATE_TREEVIEW = NO
703
# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
704
# used to set the initial width (in pixels) of the frame in which the tree
709
#---------------------------------------------------------------------------
710
# configuration options related to the LaTeX output
711
#---------------------------------------------------------------------------
713
# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
714
# generate Latex output.
718
# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
719
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
720
# put in front of it. If left blank `latex' will be used as the default path.
724
# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
725
# invoked. If left blank `latex' will be used as the default command name.
727
LATEX_CMD_NAME = latex
729
# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
730
# generate index for LaTeX. If left blank `makeindex' will be used as the
731
# default command name.
733
MAKEINDEX_CMD_NAME = makeindex
735
# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
736
# LaTeX documents. This may be useful for small projects and may help to
737
# save some trees in general.
741
# The PAPER_TYPE tag can be used to set the paper type that is used
742
# by the printer. Possible values are: a4, a4wide, letter, legal and
743
# executive. If left blank a4wide will be used.
747
# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
748
# packages that should be included in the LaTeX output.
752
# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
753
# the generated latex document. The header should contain everything until
754
# the first chapter. If it is left blank doxygen will generate a
755
# standard header. Notice: only use this tag if you know what you are doing!
759
# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
760
# is prepared for conversion to pdf (using ps2pdf). The pdf file will
761
# contain links (just like the HTML output) instead of page references
762
# This makes the output suitable for online browsing using a pdf viewer.
766
# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
767
# plain latex in the generated Makefile. Set this option to YES to get a
768
# higher quality PDF documentation.
772
# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
773
# command to the generated LaTeX files. This will instruct LaTeX to keep
774
# running if errors occur, instead of asking the user for help.
775
# This option is also used when generating formulas in HTML.
779
# If LATEX_HIDE_INDICES is set to YES then doxygen will not
780
# include the index chapters (such as File Index, Compound Index, etc.)
783
LATEX_HIDE_INDICES = NO
785
#---------------------------------------------------------------------------
786
# configuration options related to the RTF output
787
#---------------------------------------------------------------------------
789
# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
790
# The RTF output is optimized for Word 97 and may not look very pretty with
791
# other RTF readers or editors.
795
# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
796
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
797
# put in front of it. If left blank `rtf' will be used as the default path.
801
# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
802
# RTF documents. This may be useful for small projects and may help to
803
# save some trees in general.
807
# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
808
# will contain hyperlink fields. The RTF file will
809
# contain links (just like the HTML output) instead of page references.
810
# This makes the output suitable for online browsing using WORD or other
811
# programs which support those fields.
812
# Note: wordpad (write) and others do not support links.
816
# Load stylesheet definitions from file. Syntax is similar to doxygen's
817
# config file, i.e. a series of assignments. You only have to provide
818
# replacements, missing definitions are set to their default value.
820
RTF_STYLESHEET_FILE =
822
# Set optional variables used in the generation of an rtf document.
823
# Syntax is similar to doxygen's config file.
825
RTF_EXTENSIONS_FILE =
827
#---------------------------------------------------------------------------
828
# configuration options related to the man page output
829
#---------------------------------------------------------------------------
831
# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
836
# The MAN_OUTPUT tag is used to specify where the man pages will be put.
837
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
838
# put in front of it. If left blank `man' will be used as the default path.
842
# The MAN_EXTENSION tag determines the extension that is added to
843
# the generated man pages (default is the subroutine's section .3)
847
# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
848
# then it will generate one additional man file for each entity
849
# documented in the real man page(s). These additional files
850
# only source the real man page, but without them the man command
851
# would be unable to find the correct page. The default is NO.
855
#---------------------------------------------------------------------------
856
# configuration options related to the XML output
857
#---------------------------------------------------------------------------
859
# If the GENERATE_XML tag is set to YES Doxygen will
860
# generate an XML file that captures the structure of
861
# the code including all documentation.
865
# The XML_OUTPUT tag is used to specify where the XML pages will be put.
866
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
867
# put in front of it. If left blank `xml' will be used as the default path.
871
# The XML_SCHEMA tag can be used to specify an XML schema,
872
# which can be used by a validating XML parser to check the
873
# syntax of the XML files.
877
# The XML_DTD tag can be used to specify an XML DTD,
878
# which can be used by a validating XML parser to check the
879
# syntax of the XML files.
883
# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
884
# dump the program listings (including syntax highlighting
885
# and cross-referencing information) to the XML output. Note that
886
# enabling this will significantly increase the size of the XML output.
888
XML_PROGRAMLISTING = YES
890
#---------------------------------------------------------------------------
891
# configuration options for the AutoGen Definitions output
892
#---------------------------------------------------------------------------
894
# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
895
# generate an AutoGen Definitions (see autogen.sf.net) file
896
# that captures the structure of the code including all
897
# documentation. Note that this feature is still experimental
898
# and incomplete at the moment.
900
GENERATE_AUTOGEN_DEF = NO
902
#---------------------------------------------------------------------------
903
# configuration options related to the Perl module output
904
#---------------------------------------------------------------------------
906
# If the GENERATE_PERLMOD tag is set to YES Doxygen will
907
# generate a Perl module file that captures the structure of
908
# the code including all documentation. Note that this
909
# feature is still experimental and incomplete at the
912
GENERATE_PERLMOD = NO
914
# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
915
# the necessary Makefile rules, Perl scripts and LaTeX code to be able
916
# to generate PDF and DVI output from the Perl module output.
920
# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
921
# nicely formatted so it can be parsed by a human reader. This is useful
922
# if you want to understand what is going on. On the other hand, if this
923
# tag is set to NO the size of the Perl module output will be much smaller
924
# and Perl will parse it just the same.
928
# The names of the make variables in the generated doxyrules.make file
929
# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
930
# This is useful so different doxyrules.make files included by the same
931
# Makefile don't overwrite each other's variables.
933
PERLMOD_MAKEVAR_PREFIX =
935
#---------------------------------------------------------------------------
936
# Configuration options related to the preprocessor
937
#---------------------------------------------------------------------------
939
# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
940
# evaluate all C-preprocessor directives found in the sources and include
943
ENABLE_PREPROCESSING = YES
945
# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
946
# names in the source code. If set to NO (the default) only conditional
947
# compilation will be performed. Macro expansion can be done in a controlled
948
# way by setting EXPAND_ONLY_PREDEF to YES.
952
# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
953
# then the macro expansion is limited to the macros specified with the
954
# PREDEFINED and EXPAND_AS_PREDEFINED tags.
956
EXPAND_ONLY_PREDEF = NO
958
# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
959
# in the INCLUDE_PATH (see below) will be search if a #include is found.
961
SEARCH_INCLUDES = YES
963
# The INCLUDE_PATH tag can be used to specify one or more directories that
964
# contain include files that are not input files but should be processed by
969
# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
970
# patterns (like *.h and *.hpp) to filter out the header-files in the
971
# directories. If left blank, the patterns specified with FILE_PATTERNS will
974
INCLUDE_FILE_PATTERNS =
976
# The PREDEFINED tag can be used to specify one or more macro names that
977
# are defined before the preprocessor is started (similar to the -D option of
978
# gcc). The argument of the tag is a list of macros of the form: name
979
# or name=definition (no spaces). If the definition and the = are
980
# omitted =1 is assumed. To prevent a macro definition from being
981
# undefined via #undef or recursively expanded use the := operator
982
# instead of the = operator.
986
# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
987
# this tag can be used to specify a list of macro names that should be expanded.
988
# The macro definition that is found in the sources will be used.
989
# Use the PREDEFINED tag if you want to use a different macro definition.
993
# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
994
# doxygen's preprocessor will remove all function-like macros that are alone
995
# on a line, have an all uppercase name, and do not end with a semicolon. Such
996
# function macros are typically used for boiler-plate code, and will confuse
997
# the parser if not removed.
999
SKIP_FUNCTION_MACROS = YES
1001
#---------------------------------------------------------------------------
1002
# Configuration::additions related to external references
1003
#---------------------------------------------------------------------------
1005
# The TAGFILES option can be used to specify one or more tagfiles.
1006
# Optionally an initial location of the external documentation
1007
# can be added for each tagfile. The format of a tag file without
1008
# this location is as follows:
1009
# TAGFILES = file1 file2 ...
1010
# Adding location for the tag files is done as follows:
1011
# TAGFILES = file1=loc1 "file2 = loc2" ...
1012
# where "loc1" and "loc2" can be relative or absolute paths or
1013
# URLs. If a location is present for each tag, the installdox tool
1014
# does not have to be run to correct the links.
1015
# Note that each tag file must have a unique name
1016
# (where the name does NOT include the path)
1017
# If a tag file is not located in the directory in which doxygen
1018
# is run, you must also specify the path to the tagfile here.
1022
# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1023
# a tag file that is based on the input files it reads.
1027
# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1028
# in the class index. If set to NO only the inherited external classes
1033
# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1034
# in the modules index. If set to NO, only the current project's groups will
1037
EXTERNAL_GROUPS = YES
1039
# The PERL_PATH should be the absolute path and name of the perl script
1040
# interpreter (i.e. the result of `which perl').
1042
PERL_PATH = /usr/bin/perl
1044
#---------------------------------------------------------------------------
1045
# Configuration options related to the dot tool
1046
#---------------------------------------------------------------------------
1048
# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1049
# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1050
# or super classes. Setting the tag to NO turns the diagrams off. Note that
1051
# this option is superseded by the HAVE_DOT option below. This is only a
1052
# fallback. It is recommended to install and use dot, since it yields more
1055
CLASS_DIAGRAMS = YES
1057
# If set to YES, the inheritance and collaboration graphs will hide
1058
# inheritance and usage relations if the target is undocumented
1059
# or is not a class.
1061
HIDE_UNDOC_RELATIONS = YES
1063
# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1064
# available from the path. This tool is part of Graphviz, a graph visualization
1065
# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1066
# have no effect if this option is set to NO (the default)
1070
# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1071
# will generate a graph for each documented class showing the direct and
1072
# indirect inheritance relations. Setting this tag to YES will force the
1073
# the CLASS_DIAGRAMS tag to NO.
1077
# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1078
# will generate a graph for each documented class showing the direct and
1079
# indirect implementation dependencies (inheritance, containment, and
1080
# class references variables) of the class with other documented classes.
1082
COLLABORATION_GRAPH = YES
1084
# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1085
# will generate a graph for groups, showing the direct groups dependencies
1089
# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1090
# collaboration diagrams in a style similar to the OMG's Unified Modeling
1095
# If set to YES, the inheritance and collaboration graphs will show the
1096
# relations between templates and their instances.
1098
TEMPLATE_RELATIONS = NO
1100
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1101
# tags are set to YES then doxygen will generate a graph for each documented
1102
# file showing the direct and indirect include dependencies of the file with
1103
# other documented files.
1107
# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1108
# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1109
# documented header file showing the documented files that directly or
1110
# indirectly include this file.
1112
INCLUDED_BY_GRAPH = YES
1114
# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1115
# generate a call dependency graph for every global function or class method.
1116
# Note that enabling this option will significantly increase the time of a run.
1117
# So in most cases it will be better to enable call graphs for selected
1118
# functions only using the \callgraph command.
1122
# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1123
# will graphical hierarchy of all classes instead of a textual one.
1125
GRAPHICAL_HIERARCHY = YES
1127
# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1128
# then doxygen will show the dependencies a directory has on other directories
1129
# in a graphical way. The dependency relations are determined by the #include
1130
# relations between the files in the directories.
1132
DIRECTORY_GRAPH = YES
1134
# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1135
# generated by dot. Possible values are png, jpg, or gif
1136
# If left blank png will be used.
1138
DOT_IMAGE_FORMAT = png
1140
# The tag DOT_PATH can be used to specify the path where the dot tool can be
1141
# found. If left blank, it is assumed the dot tool can be found on the path.
1145
# The DOTFILE_DIRS tag can be used to specify one or more directories that
1146
# contain dot files that are included in the documentation (see the
1147
# \dotfile command).
1151
# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1152
# (in pixels) of the graphs generated by dot. If a graph becomes larger than
1153
# this value, doxygen will try to truncate the graph, so that it fits within
1154
# the specified constraint. Beware that most browsers cannot cope with very
1157
MAX_DOT_GRAPH_WIDTH = 1024
1159
# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1160
# (in pixels) of the graphs generated by dot. If a graph becomes larger than
1161
# this value, doxygen will try to truncate the graph, so that it fits within
1162
# the specified constraint. Beware that most browsers cannot cope with very
1165
MAX_DOT_GRAPH_HEIGHT = 1024
1167
# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1168
# graphs generated by dot. A depth value of 3 means that only nodes reachable
1169
# from the root by following a path via at most 3 edges will be shown. Nodes
1170
# that lay further from the root node will be omitted. Note that setting this
1171
# option to 1 or 2 may greatly reduce the computation time needed for large
1172
# code bases. Also note that a graph may be further truncated if the graph's
1173
# image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH
1174
# and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default),
1175
# the graph is not depth-constrained.
1177
MAX_DOT_GRAPH_DEPTH = 0
1179
# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1180
# background. This is disabled by default, which results in a white background.
1181
# Warning: Depending on the platform used, enabling this option may lead to
1182
# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
1185
DOT_TRANSPARENT = NO
1187
# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1188
# files in one run (i.e. multiple -o and -T options on the command line). This
1189
# makes dot run faster, but since only newer versions of dot (>1.8.10)
1190
# support this, this feature is disabled by default.
1192
DOT_MULTI_TARGETS = NO
1194
# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1195
# generate a legend page explaining the meaning of the various boxes and
1196
# arrows in the dot generated graphs.
1198
GENERATE_LEGEND = YES
1200
# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1201
# remove the intermediate dot files that are used to generate
1202
# the various graphs.
1206
#---------------------------------------------------------------------------
1207
# Configuration::additions related to the search engine
1208
#---------------------------------------------------------------------------
1210
# The SEARCHENGINE tag specifies whether or not a search engine should be
1211
# used. If set to NO the values of all tags below this one will be ignored.
added
removed
iris/irisnet/Doxyfile
