source: doxygen.conf

Last change on this file was 334402c, checked in by Pawel Foremski <pjf@…>, 11 years ago

Initial commit

  • Property mode set to 100644
File size: 50.6 KB
Line 
1# Doxyfile 1.5.2
2
3# This file describes the settings to be used by the documentation system
4# doxygen (www.doxygen.org) for a project
5#
6# All text after a hash (#) is considered a comment and will be ignored
7# The format is:
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 (" ")
12
13#---------------------------------------------------------------------------
14# Project related configuration options
15#---------------------------------------------------------------------------
16
17# This tag specifies the encoding used for all characters in the config file that
18# follow. The default is UTF-8 which is also the encoding used for all text before
19# the first occurrence of this tag. Doxygen uses libiconv (or the iconv built into
20# libc) for the transcoding. See http://www.gnu.org/software/libiconv for the list of
21# possible encodings.
22
23DOXYFILE_ENCODING      = UTF-8
24
25# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
26# by quotes) that should identify the project.
27
28PROJECT_NAME           = ef
29
30# The PROJECT_NUMBER tag can be used to enter a project or revision number.
31# This could be handy for archiving the generated documentation or
32# if some version control system is used.
33
34PROJECT_NUMBER         =
35
36# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
37# base path where the generated documentation will be put.
38# If a relative path is entered, it will be relative to the location
39# where doxygen was started. If left blank the current directory will be used.
40
41OUTPUT_DIRECTORY       = doc
42
43# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
44# 4096 sub-directories (in 2 levels) under the output directory of each output
45# format and will distribute the generated files over these directories.
46# Enabling this option can be useful when feeding doxygen a huge amount of
47# source files, where putting all generated files in the same directory would
48# otherwise cause performance problems for the file system.
49
50CREATE_SUBDIRS         = NO
51
52# The OUTPUT_LANGUAGE tag is used to specify the language in which all
53# documentation generated by doxygen is written. Doxygen will use this
54# information to generate all constant output in the proper language.
55# The default language is English, other supported languages are:
56# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
57# Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian,
58# Italian, Japanese, Japanese-en (Japanese with English messages), Korean,
59# Korean-en, Lithuanian, Norwegian, Polish, Portuguese, Romanian, Russian,
60# Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
61
62OUTPUT_LANGUAGE        = English
63
64# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
65# include brief member descriptions after the members that are listed in
66# the file and class documentation (similar to JavaDoc).
67# Set to NO to disable this.
68
69BRIEF_MEMBER_DESC      = YES
70
71# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
72# the brief description of a member or function before the detailed description.
73# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
74# brief descriptions will be completely suppressed.
75
76REPEAT_BRIEF           = YES
77
78# This tag implements a quasi-intelligent brief description abbreviator
79# that is used to form the text in various listings. Each string
80# in this list, if found as the leading text of the brief description, will be
81# stripped from the text and the result after processing the whole list, is
82# used as the annotated text. Otherwise, the brief description is used as-is.
83# If left blank, the following values are used ("$name" is automatically
84# replaced with the name of the entity): "The $name class" "The $name widget"
85# "The $name file" "is" "provides" "specifies" "contains"
86# "represents" "a" "an" "the"
87
88ABBREVIATE_BRIEF       =
89
90# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
91# Doxygen will generate a detailed section even if there is only a brief
92# description.
93
94ALWAYS_DETAILED_SEC    = NO
95
96# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
97# inherited members of a class in the documentation of that class as if those
98# members were ordinary class members. Constructors, destructors and assignment
99# operators of the base classes will not be shown.
100
101INLINE_INHERITED_MEMB  = NO
102
103# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
104# path before files name in the file list and in the header files. If set
105# to NO the shortest path that makes the file name unique will be used.
106
107FULL_PATH_NAMES        = YES
108
109# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
110# can be used to strip a user-defined part of the path. Stripping is
111# only done if one of the specified strings matches the left-hand part of
112# the path. The tag can be used to show relative paths in the file list.
113# If left blank the directory from which doxygen is run is used as the
114# path to strip.
115
116STRIP_FROM_PATH        =
117
118# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
119# the path mentioned in the documentation of a class, which tells
120# the reader which header file to include in order to use a class.
121# If left blank only the name of the header file containing the class
122# definition is used. Otherwise one should specify the include paths that
123# are normally passed to the compiler using the -I flag.
124
125STRIP_FROM_INC_PATH    =
126
127# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
128# (but less readable) file names. This can be useful is your file systems
129# doesn't support long names like on DOS, Mac, or CD-ROM.
130
131SHORT_NAMES            = NO
132
133# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
134# will interpret the first line (until the first dot) of a JavaDoc-style
135# comment as the brief description. If set to NO, the JavaDoc
136# comments will behave just like the Qt-style comments (thus requiring an
137# explicit @brief command for a brief description.
138
139JAVADOC_AUTOBRIEF      = YES
140
141# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
142# treat a multi-line C++ special comment block (i.e. a block of //! or ///
143# comments) as a brief description. This used to be the default behaviour.
144# The new default is to treat a multi-line C++ comment block as a detailed
145# description. Set this tag to YES if you prefer the old behaviour instead.
146
147MULTILINE_CPP_IS_BRIEF = YES
148
149# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
150# member inherits the documentation from any documented member that it
151# re-implements.
152
153INHERIT_DOCS           = YES
154
155# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
156# a new page for each member. If set to NO, the documentation of a member will
157# be part of the file/class/namespace that contains it.
158
159SEPARATE_MEMBER_PAGES  = NO
160
161# The TAB_SIZE tag can be used to set the number of spaces in a tab.
162# Doxygen uses this value to replace tabs by spaces in code fragments.
163
164TAB_SIZE               = 8
165
166# This tag can be used to specify a number of aliases that acts
167# as commands in the documentation. An alias has the form "name=value".
168# For example adding "sideeffect=\par Side Effects:\n" will allow you to
169# put the command \sideeffect (or @sideeffect) in the documentation, which
170# will result in a user-defined paragraph with heading "Side Effects:".
171# You can put \n's in the value part of an alias to insert newlines.
172
173ALIASES                =
174
175# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
176# sources only. Doxygen will then generate output that is more tailored for C.
177# For instance, some of the names that are used will be different. The list
178# of all members will be omitted, etc.
179
180OPTIMIZE_OUTPUT_FOR_C  = NO
181
182# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
183# sources only. Doxygen will then generate output that is more tailored for Java.
184# For instance, namespaces will be presented as packages, qualified scopes
185# will look different, etc.
186
187OPTIMIZE_OUTPUT_JAVA   = NO
188
189# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want to
190# include (a tag file for) the STL sources as input, then you should
191# set this tag to YES in order to let doxygen match functions declarations and
192# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
193# func(std::string) {}). This also make the inheritance and collaboration
194# diagrams that involve STL classes more complete and accurate.
195
196BUILTIN_STL_SUPPORT    = NO
197
198# If you use Microsoft's C++/CLI language, you should set this option to YES to
199# enable parsing support.
200
201CPP_CLI_SUPPORT        = NO
202
203# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
204# tag is set to YES, then doxygen will reuse the documentation of the first
205# member in the group (if any) for the other members of the group. By default
206# all members of a group must be documented explicitly.
207
208DISTRIBUTE_GROUP_DOC   = NO
209
210# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
211# the same type (for instance a group of public functions) to be put as a
212# subgroup of that type (e.g. under the Public Functions section). Set it to
213# NO to prevent subgrouping. Alternatively, this can be done per class using
214# the \nosubgrouping command.
215
216SUBGROUPING            = YES
217
218#---------------------------------------------------------------------------
219# Build related configuration options
220#---------------------------------------------------------------------------
221
222# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
223# documentation are documented, even if no documentation was available.
224# Private class members and static file members will be hidden unless
225# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
226
227EXTRACT_ALL            = YES
228
229# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
230# will be included in the documentation.
231
232EXTRACT_PRIVATE        = YES
233
234# If the EXTRACT_STATIC tag is set to YES all static members of a file
235# will be included in the documentation.
236
237EXTRACT_STATIC         = YES
238
239# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
240# defined locally in source files will be included in the documentation.
241# If set to NO only classes defined in header files are included.
242
243EXTRACT_LOCAL_CLASSES  = YES
244
245# This flag is only useful for Objective-C code. When set to YES local
246# methods, which are defined in the implementation section but not in
247# the interface are included in the documentation.
248# If set to NO (the default) only methods in the interface are included.
249
250EXTRACT_LOCAL_METHODS  = NO
251
252# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
253# undocumented members of documented classes, files or namespaces.
254# If set to NO (the default) these members will be included in the
255# various overviews, but no documentation section is generated.
256# This option has no effect if EXTRACT_ALL is enabled.
257
258HIDE_UNDOC_MEMBERS     = NO
259
260# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
261# undocumented classes that are normally visible in the class hierarchy.
262# If set to NO (the default) these classes will be included in the various
263# overviews. This option has no effect if EXTRACT_ALL is enabled.
264
265HIDE_UNDOC_CLASSES     = NO
266
267# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
268# friend (class|struct|union) declarations.
269# If set to NO (the default) these declarations will be included in the
270# documentation.
271
272HIDE_FRIEND_COMPOUNDS  = NO
273
274# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
275# documentation blocks found inside the body of a function.
276# If set to NO (the default) these blocks will be appended to the
277# function's detailed documentation block.
278
279HIDE_IN_BODY_DOCS      = NO
280
281# The INTERNAL_DOCS tag determines if documentation
282# that is typed after a \internal command is included. If the tag is set
283# to NO (the default) then the documentation will be excluded.
284# Set it to YES to include the internal documentation.
285
286INTERNAL_DOCS          = YES
287
288# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
289# file names in lower-case letters. If set to YES upper-case letters are also
290# allowed. This is useful if you have classes or files whose names only differ
291# in case and if your file system supports case sensitive file names. Windows
292# and Mac users are advised to set this option to NO.
293
294CASE_SENSE_NAMES       = YES
295
296# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
297# will show members with their full class and namespace scopes in the
298# documentation. If set to YES the scope will be hidden.
299
300HIDE_SCOPE_NAMES       = NO
301
302# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
303# will put a list of the files that are included by a file in the documentation
304# of that file.
305
306SHOW_INCLUDE_FILES     = YES
307
308# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
309# is inserted in the documentation for inline members.
310
311INLINE_INFO            = YES
312
313# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
314# will sort the (detailed) documentation of file and class members
315# alphabetically by member name. If set to NO the members will appear in
316# declaration order.
317
318SORT_MEMBER_DOCS       = YES
319
320# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
321# brief documentation of file, namespace and class members alphabetically
322# by member name. If set to NO (the default) the members will appear in
323# declaration order.
324
325SORT_BRIEF_DOCS        = NO
326
327# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
328# sorted by fully-qualified names, including namespaces. If set to
329# NO (the default), the class list will be sorted only by class name,
330# not including the namespace part.
331# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
332# Note: This option applies only to the class list, not to the
333# alphabetical list.
334
335SORT_BY_SCOPE_NAME     = NO
336
337# The GENERATE_TODOLIST tag can be used to enable (YES) or
338# disable (NO) the todo list. This list is created by putting \todo
339# commands in the documentation.
340
341GENERATE_TODOLIST      = YES
342
343# The GENERATE_TESTLIST tag can be used to enable (YES) or
344# disable (NO) the test list. This list is created by putting \test
345# commands in the documentation.
346
347GENERATE_TESTLIST      = YES
348
349# The GENERATE_BUGLIST tag can be used to enable (YES) or
350# disable (NO) the bug list. This list is created by putting \bug
351# commands in the documentation.
352
353GENERATE_BUGLIST       = YES
354
355# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
356# disable (NO) the deprecated list. This list is created by putting
357# \deprecated commands in the documentation.
358
359GENERATE_DEPRECATEDLIST= YES
360
361# The ENABLED_SECTIONS tag can be used to enable conditional
362# documentation sections, marked by \if sectionname ... \endif.
363
364ENABLED_SECTIONS       =
365
366# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
367# the initial value of a variable or define consists of for it to appear in
368# the documentation. If the initializer consists of more lines than specified
369# here it will be hidden. Use a value of 0 to hide initializers completely.
370# The appearance of the initializer of individual variables and defines in the
371# documentation can be controlled using \showinitializer or \hideinitializer
372# command in the documentation regardless of this setting.
373
374MAX_INITIALIZER_LINES  = 30
375
376# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
377# at the bottom of the documentation of classes and structs. If set to YES the
378# list will mention the files that were used to generate the documentation.
379
380SHOW_USED_FILES        = YES
381
382# If the sources in your project are distributed over multiple directories
383# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
384# in the documentation. The default is NO.
385
386SHOW_DIRECTORIES       = NO
387
388# The FILE_VERSION_FILTER tag can be used to specify a program or script that
389# doxygen should invoke to get the current version for each file (typically from the
390# version control system). Doxygen will invoke the program by executing (via
391# popen()) the command <command> <input-file>, where <command> is the value of
392# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
393# provided by doxygen. Whatever the program writes to standard output
394# is used as the file version. See the manual for examples.
395
396FILE_VERSION_FILTER    =
397
398#---------------------------------------------------------------------------
399# configuration options related to warning and progress messages
400#---------------------------------------------------------------------------
401
402# The QUIET tag can be used to turn on/off the messages that are generated
403# by doxygen. Possible values are YES and NO. If left blank NO is used.
404
405QUIET                  = YES
406
407# The WARNINGS tag can be used to turn on/off the warning messages that are
408# generated by doxygen. Possible values are YES and NO. If left blank
409# NO is used.
410
411WARNINGS               = YES
412
413# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
414# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
415# automatically be disabled.
416
417WARN_IF_UNDOCUMENTED   = YES
418
419# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
420# potential errors in the documentation, such as not documenting some
421# parameters in a documented function, or documenting parameters that
422# don't exist or using markup commands wrongly.
423
424WARN_IF_DOC_ERROR      = YES
425
426# This WARN_NO_PARAMDOC option can be abled to get warnings for
427# functions that are documented, but have no documentation for their parameters
428# or return value. If set to NO (the default) doxygen will only warn about
429# wrong or incomplete parameter documentation, but not about the absence of
430# documentation.
431
432WARN_NO_PARAMDOC       = NO
433
434# The WARN_FORMAT tag determines the format of the warning messages that
435# doxygen can produce. The string should contain the $file, $line, and $text
436# tags, which will be replaced by the file and line number from which the
437# warning originated and the warning text. Optionally the format may contain
438# $version, which will be replaced by the version of the file (if it could
439# be obtained via FILE_VERSION_FILTER)
440
441WARN_FORMAT            = "$file:$line: $text"
442
443# The WARN_LOGFILE tag can be used to specify a file to which warning
444# and error messages should be written. If left blank the output is written
445# to stderr.
446
447WARN_LOGFILE           =
448
449#---------------------------------------------------------------------------
450# configuration options related to the input files
451#---------------------------------------------------------------------------
452
453# The INPUT tag can be used to specify the files and/or directories that contain
454# documented source files. You may enter file names like "myfile.cpp" or
455# directories like "/usr/src/myproject". Separate the files or directories
456# with spaces.
457
458INPUT                  =
459
460# This tag can be used to specify the character encoding of the source files that
461# doxygen parses. Internally doxygen uses the UTF-8 encoding, which is also the default
462# input encoding. Doxygen uses libiconv (or the iconv built into libc) for the transcoding.
463# See http://www.gnu.org/software/libiconv for the list of possible encodings.
464
465INPUT_ENCODING         = UTF-8
466
467# If the value of the INPUT tag contains directories, you can use the
468# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
469# and *.h) to filter out the source-files in the directories. If left
470# blank the following patterns are tested:
471# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx
472# *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.py
473
474FILE_PATTERNS          =
475
476# The RECURSIVE tag can be used to turn specify whether or not subdirectories
477# should be searched for input files as well. Possible values are YES and NO.
478# If left blank NO is used.
479
480RECURSIVE              = NO
481
482# The EXCLUDE tag can be used to specify files and/or directories that should
483# excluded from the INPUT source files. This way you can easily exclude a
484# subdirectory from a directory tree whose root is specified with the INPUT tag.
485
486EXCLUDE                =
487
488# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
489# directories that are symbolic links (a Unix filesystem feature) are excluded
490# from the input.
491
492EXCLUDE_SYMLINKS       = YES
493
494# If the value of the INPUT tag contains directories, you can use the
495# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
496# certain files from those directories. Note that the wildcards are matched
497# against the file with absolute path, so to exclude all test directories
498# for example use the pattern */test/*
499
500EXCLUDE_PATTERNS       =
501
502# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
503# (namespaces, classes, functions, etc.) that should be excluded from the output.
504# The symbol name can be a fully qualified name, a word, or if the wildcard * is used,
505# a substring. Examples: ANamespace, AClass, AClass::ANamespace, ANamespace::*Test
506
507EXCLUDE_SYMBOLS        =
508
509# The EXAMPLE_PATH tag can be used to specify one or more files or
510# directories that contain example code fragments that are included (see
511# the \include command).
512
513EXAMPLE_PATH           =
514
515# If the value of the EXAMPLE_PATH tag contains directories, you can use the
516# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
517# and *.h) to filter out the source-files in the directories. If left
518# blank all files are included.
519
520EXAMPLE_PATTERNS       =
521
522# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
523# searched for input files to be used with the \include or \dontinclude
524# commands irrespective of the value of the RECURSIVE tag.
525# Possible values are YES and NO. If left blank NO is used.
526
527EXAMPLE_RECURSIVE      = NO
528
529# The IMAGE_PATH tag can be used to specify one or more files or
530# directories that contain image that are included in the documentation (see
531# the \image command).
532
533IMAGE_PATH             =
534
535# The INPUT_FILTER tag can be used to specify a program that doxygen should
536# invoke to filter for each input file. Doxygen will invoke the filter program
537# by executing (via popen()) the command <filter> <input-file>, where <filter>
538# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
539# input file. Doxygen will then use the output that the filter program writes
540# to standard output.  If FILTER_PATTERNS is specified, this tag will be
541# ignored.
542
543INPUT_FILTER           =
544
545# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
546# basis.  Doxygen will compare the file name with each pattern and apply the
547# filter if there is a match.  The filters are a list of the form:
548# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
549# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
550# is applied to all files.
551
552FILTER_PATTERNS        =
553
554# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
555# INPUT_FILTER) will be used to filter the input files when producing source
556# files to browse (i.e. when SOURCE_BROWSER is set to YES).
557
558FILTER_SOURCE_FILES    = NO
559
560#---------------------------------------------------------------------------
561# configuration options related to source browsing
562#---------------------------------------------------------------------------
563
564# If the SOURCE_BROWSER tag is set to YES then a list of source files will
565# be generated. Documented entities will be cross-referenced with these sources.
566# Note: To get rid of all source code in the generated output, make sure also
567# VERBATIM_HEADERS is set to NO.
568
569SOURCE_BROWSER         = YES
570
571# Setting the INLINE_SOURCES tag to YES will include the body
572# of functions and classes directly in the documentation.
573
574INLINE_SOURCES         = NO
575
576# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
577# doxygen to hide any special comment blocks from generated source code
578# fragments. Normal C and C++ comments will always remain visible.
579
580STRIP_CODE_COMMENTS    = YES
581
582# If the REFERENCED_BY_RELATION tag is set to YES (the default)
583# then for each documented function all documented
584# functions referencing it will be listed.
585
586REFERENCED_BY_RELATION = YES
587
588# If the REFERENCES_RELATION tag is set to YES (the default)
589# then for each documented function all documented entities
590# called/used by that function will be listed.
591
592REFERENCES_RELATION    = YES
593
594# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
595# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
596# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
597# link to the source code.  Otherwise they will link to the documentstion.
598
599REFERENCES_LINK_SOURCE = YES
600
601# If the USE_HTAGS tag is set to YES then the references to source code
602# will point to the HTML generated by the htags(1) tool instead of doxygen
603# built-in source browser. The htags tool is part of GNU's global source
604# tagging system (see http://www.gnu.org/software/global/global.html). You
605# will need version 4.8.6 or higher.
606
607USE_HTAGS              = NO
608
609# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
610# will generate a verbatim copy of the header file for each class for
611# which an include is specified. Set to NO to disable this.
612
613VERBATIM_HEADERS       = YES
614
615#---------------------------------------------------------------------------
616# configuration options related to the alphabetical class index
617#---------------------------------------------------------------------------
618
619# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
620# of all compounds will be generated. Enable this if the project
621# contains a lot of classes, structs, unions or interfaces.
622
623ALPHABETICAL_INDEX     = NO
624
625# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
626# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
627# in which this list will be split (can be a number in the range [1..20])
628
629COLS_IN_ALPHA_INDEX    = 5
630
631# In case all classes in a project start with a common prefix, all
632# classes will be put under the same header in the alphabetical index.
633# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
634# should be ignored while generating the index headers.
635
636IGNORE_PREFIX          =
637
638#---------------------------------------------------------------------------
639# configuration options related to the HTML output
640#---------------------------------------------------------------------------
641
642# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
643# generate HTML output.
644
645GENERATE_HTML          = YES
646
647# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
648# If a relative path is entered the value of OUTPUT_DIRECTORY will be
649# put in front of it. If left blank `html' will be used as the default path.
650
651HTML_OUTPUT            = html
652
653# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
654# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
655# doxygen will generate files with .html extension.
656
657HTML_FILE_EXTENSION    = .html
658
659# The HTML_HEADER tag can be used to specify a personal HTML header for
660# each generated HTML page. If it is left blank doxygen will generate a
661# standard header.
662
663HTML_HEADER            =
664
665# The HTML_FOOTER tag can be used to specify a personal HTML footer for
666# each generated HTML page. If it is left blank doxygen will generate a
667# standard footer.
668
669HTML_FOOTER            =
670
671# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
672# style sheet that is used by each HTML page. It can be used to
673# fine-tune the look of the HTML output. If the tag is left blank doxygen
674# will generate a default style sheet. Note that doxygen will try to copy
675# the style sheet file to the HTML output directory, so don't put your own
676# stylesheet in the HTML output directory as well, or it will be erased!
677
678HTML_STYLESHEET        =
679
680# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
681# files or namespaces will be aligned in HTML using tables. If set to
682# NO a bullet list will be used.
683
684HTML_ALIGN_MEMBERS     = YES
685
686# If the GENERATE_HTMLHELP tag is set to YES, additional index files
687# will be generated that can be used as input for tools like the
688# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
689# of the generated HTML documentation.
690
691GENERATE_HTMLHELP      = NO
692
693# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
694# be used to specify the file name of the resulting .chm file. You
695# can add a path in front of the file if the result should not be
696# written to the html output directory.
697
698CHM_FILE               =
699
700# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
701# be used to specify the location (absolute path including file name) of
702# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
703# the HTML help compiler on the generated index.hhp.
704
705HHC_LOCATION           =
706
707# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
708# controls if a separate .chi index file is generated (YES) or that
709# it should be included in the master .chm file (NO).
710
711GENERATE_CHI           = NO
712
713# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
714# controls whether a binary table of contents is generated (YES) or a
715# normal table of contents (NO) in the .chm file.
716
717BINARY_TOC             = NO
718
719# The TOC_EXPAND flag can be set to YES to add extra items for group members
720# to the contents of the HTML help documentation and to the tree view.
721
722TOC_EXPAND             = NO
723
724# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
725# top of each HTML page. The value NO (the default) enables the index and
726# the value YES disables it.
727
728DISABLE_INDEX          = NO
729
730# This tag can be used to set the number of enum values (range [1..20])
731# that doxygen will group on one line in the generated HTML documentation.
732
733ENUM_VALUES_PER_LINE   = 4
734
735# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
736# generated containing a tree-like index structure (just like the one that
737# is generated for HTML Help). For this to work a browser that supports
738# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
739# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
740# probably better off using the HTML help feature.
741
742GENERATE_TREEVIEW      = NO
743
744# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
745# used to set the initial width (in pixels) of the frame in which the tree
746# is shown.
747
748TREEVIEW_WIDTH         = 250
749
750#---------------------------------------------------------------------------
751# configuration options related to the LaTeX output
752#---------------------------------------------------------------------------
753
754# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
755# generate Latex output.
756
757GENERATE_LATEX         = YES
758
759# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
760# If a relative path is entered the value of OUTPUT_DIRECTORY will be
761# put in front of it. If left blank `latex' will be used as the default path.
762
763LATEX_OUTPUT           = latex
764
765# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
766# invoked. If left blank `latex' will be used as the default command name.
767
768LATEX_CMD_NAME         = latex
769
770# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
771# generate index for LaTeX. If left blank `makeindex' will be used as the
772# default command name.
773
774MAKEINDEX_CMD_NAME     = makeindex
775
776# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
777# LaTeX documents. This may be useful for small projects and may help to
778# save some trees in general.
779
780COMPACT_LATEX          = NO
781
782# The PAPER_TYPE tag can be used to set the paper type that is used
783# by the printer. Possible values are: a4, a4wide, letter, legal and
784# executive. If left blank a4wide will be used.
785
786PAPER_TYPE             = a4wide
787
788# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
789# packages that should be included in the LaTeX output.
790
791EXTRA_PACKAGES         =
792
793# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
794# the generated latex document. The header should contain everything until
795# the first chapter. If it is left blank doxygen will generate a
796# standard header. Notice: only use this tag if you know what you are doing!
797
798LATEX_HEADER           =
799
800# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
801# is prepared for conversion to pdf (using ps2pdf). The pdf file will
802# contain links (just like the HTML output) instead of page references
803# This makes the output suitable for online browsing using a pdf viewer.
804
805PDF_HYPERLINKS         = NO
806
807# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
808# plain latex in the generated Makefile. Set this option to YES to get a
809# higher quality PDF documentation.
810
811USE_PDFLATEX           = NO
812
813# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
814# command to the generated LaTeX files. This will instruct LaTeX to keep
815# running if errors occur, instead of asking the user for help.
816# This option is also used when generating formulas in HTML.
817
818LATEX_BATCHMODE        = NO
819
820# If LATEX_HIDE_INDICES is set to YES then doxygen will not
821# include the index chapters (such as File Index, Compound Index, etc.)
822# in the output.
823
824LATEX_HIDE_INDICES     = NO
825
826#---------------------------------------------------------------------------
827# configuration options related to the RTF output
828#---------------------------------------------------------------------------
829
830# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
831# The RTF output is optimized for Word 97 and may not look very pretty with
832# other RTF readers or editors.
833
834GENERATE_RTF           = NO
835
836# The RTF_OUTPUT tag is used to specify where the RTF docs 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 `rtf' will be used as the default path.
839
840RTF_OUTPUT             = rtf
841
842# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
843# RTF documents. This may be useful for small projects and may help to
844# save some trees in general.
845
846COMPACT_RTF            = NO
847
848# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
849# will contain hyperlink fields. The RTF file will
850# contain links (just like the HTML output) instead of page references.
851# This makes the output suitable for online browsing using WORD or other
852# programs which support those fields.
853# Note: wordpad (write) and others do not support links.
854
855RTF_HYPERLINKS         = NO
856
857# Load stylesheet definitions from file. Syntax is similar to doxygen's
858# config file, i.e. a series of assignments. You only have to provide
859# replacements, missing definitions are set to their default value.
860
861RTF_STYLESHEET_FILE    =
862
863# Set optional variables used in the generation of an rtf document.
864# Syntax is similar to doxygen's config file.
865
866RTF_EXTENSIONS_FILE    =
867
868#---------------------------------------------------------------------------
869# configuration options related to the man page output
870#---------------------------------------------------------------------------
871
872# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
873# generate man pages
874
875GENERATE_MAN           = NO
876
877# The MAN_OUTPUT tag is used to specify where the man pages will be put.
878# If a relative path is entered the value of OUTPUT_DIRECTORY will be
879# put in front of it. If left blank `man' will be used as the default path.
880
881MAN_OUTPUT             = man
882
883# The MAN_EXTENSION tag determines the extension that is added to
884# the generated man pages (default is the subroutine's section .3)
885
886MAN_EXTENSION          = .3
887
888# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
889# then it will generate one additional man file for each entity
890# documented in the real man page(s). These additional files
891# only source the real man page, but without them the man command
892# would be unable to find the correct page. The default is NO.
893
894MAN_LINKS              = NO
895
896#---------------------------------------------------------------------------
897# configuration options related to the XML output
898#---------------------------------------------------------------------------
899
900# If the GENERATE_XML tag is set to YES Doxygen will
901# generate an XML file that captures the structure of
902# the code including all documentation.
903
904GENERATE_XML           = NO
905
906# The XML_OUTPUT tag is used to specify where the XML pages will be put.
907# If a relative path is entered the value of OUTPUT_DIRECTORY will be
908# put in front of it. If left blank `xml' will be used as the default path.
909
910XML_OUTPUT             = xml
911
912# The XML_SCHEMA tag can be used to specify an XML schema,
913# which can be used by a validating XML parser to check the
914# syntax of the XML files.
915
916XML_SCHEMA             =
917
918# The XML_DTD tag can be used to specify an XML DTD,
919# which can be used by a validating XML parser to check the
920# syntax of the XML files.
921
922XML_DTD                =
923
924# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
925# dump the program listings (including syntax highlighting
926# and cross-referencing information) to the XML output. Note that
927# enabling this will significantly increase the size of the XML output.
928
929XML_PROGRAMLISTING     = YES
930
931#---------------------------------------------------------------------------
932# configuration options for the AutoGen Definitions output
933#---------------------------------------------------------------------------
934
935# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
936# generate an AutoGen Definitions (see autogen.sf.net) file
937# that captures the structure of the code including all
938# documentation. Note that this feature is still experimental
939# and incomplete at the moment.
940
941GENERATE_AUTOGEN_DEF   = NO
942
943#---------------------------------------------------------------------------
944# configuration options related to the Perl module output
945#---------------------------------------------------------------------------
946
947# If the GENERATE_PERLMOD tag is set to YES Doxygen will
948# generate a Perl module file that captures the structure of
949# the code including all documentation. Note that this
950# feature is still experimental and incomplete at the
951# moment.
952
953GENERATE_PERLMOD       = NO
954
955# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
956# the necessary Makefile rules, Perl scripts and LaTeX code to be able
957# to generate PDF and DVI output from the Perl module output.
958
959PERLMOD_LATEX          = NO
960
961# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
962# nicely formatted so it can be parsed by a human reader.  This is useful
963# if you want to understand what is going on.  On the other hand, if this
964# tag is set to NO the size of the Perl module output will be much smaller
965# and Perl will parse it just the same.
966
967PERLMOD_PRETTY         = YES
968
969# The names of the make variables in the generated doxyrules.make file
970# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
971# This is useful so different doxyrules.make files included by the same
972# Makefile don't overwrite each other's variables.
973
974PERLMOD_MAKEVAR_PREFIX =
975
976#---------------------------------------------------------------------------
977# Configuration options related to the preprocessor   
978#---------------------------------------------------------------------------
979
980# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
981# evaluate all C-preprocessor directives found in the sources and include
982# files.
983
984ENABLE_PREPROCESSING   = YES
985
986# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
987# names in the source code. If set to NO (the default) only conditional
988# compilation will be performed. Macro expansion can be done in a controlled
989# way by setting EXPAND_ONLY_PREDEF to YES.
990
991MACRO_EXPANSION        = NO
992
993# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
994# then the macro expansion is limited to the macros specified with the
995# PREDEFINED and EXPAND_AS_DEFINED tags.
996
997EXPAND_ONLY_PREDEF     = NO
998
999# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1000# in the INCLUDE_PATH (see below) will be search if a #include is found.
1001
1002SEARCH_INCLUDES        = YES
1003
1004# The INCLUDE_PATH tag can be used to specify one or more directories that
1005# contain include files that are not input files but should be processed by
1006# the preprocessor.
1007
1008INCLUDE_PATH           =
1009
1010# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1011# patterns (like *.h and *.hpp) to filter out the header-files in the
1012# directories. If left blank, the patterns specified with FILE_PATTERNS will
1013# be used.
1014
1015INCLUDE_FILE_PATTERNS  =
1016
1017# The PREDEFINED tag can be used to specify one or more macro names that
1018# are defined before the preprocessor is started (similar to the -D option of
1019# gcc). The argument of the tag is a list of macros of the form: name
1020# or name=definition (no spaces). If the definition and the = are
1021# omitted =1 is assumed. To prevent a macro definition from being
1022# undefined via #undef or recursively expanded use the := operator
1023# instead of the = operator.
1024
1025PREDEFINED             =
1026
1027# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1028# this tag can be used to specify a list of macro names that should be expanded.
1029# The macro definition that is found in the sources will be used.
1030# Use the PREDEFINED tag if you want to use a different macro definition.
1031
1032EXPAND_AS_DEFINED      =
1033
1034# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1035# doxygen's preprocessor will remove all function-like macros that are alone
1036# on a line, have an all uppercase name, and do not end with a semicolon. Such
1037# function macros are typically used for boiler-plate code, and will confuse
1038# the parser if not removed.
1039
1040SKIP_FUNCTION_MACROS   = YES
1041
1042#---------------------------------------------------------------------------
1043# Configuration::additions related to external references   
1044#---------------------------------------------------------------------------
1045
1046# The TAGFILES option can be used to specify one or more tagfiles.
1047# Optionally an initial location of the external documentation
1048# can be added for each tagfile. The format of a tag file without
1049# this location is as follows:
1050#   TAGFILES = file1 file2 ...
1051# Adding location for the tag files is done as follows:
1052#   TAGFILES = file1=loc1 "file2 = loc2" ...
1053# where "loc1" and "loc2" can be relative or absolute paths or
1054# URLs. If a location is present for each tag, the installdox tool
1055# does not have to be run to correct the links.
1056# Note that each tag file must have a unique name
1057# (where the name does NOT include the path)
1058# If a tag file is not located in the directory in which doxygen
1059# is run, you must also specify the path to the tagfile here.
1060
1061TAGFILES               =
1062
1063# When a file name is specified after GENERATE_TAGFILE, doxygen will create
1064# a tag file that is based on the input files it reads.
1065
1066GENERATE_TAGFILE       =
1067
1068# If the ALLEXTERNALS tag is set to YES all external classes will be listed
1069# in the class index. If set to NO only the inherited external classes
1070# will be listed.
1071
1072ALLEXTERNALS           = NO
1073
1074# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1075# in the modules index. If set to NO, only the current project's groups will
1076# be listed.
1077
1078EXTERNAL_GROUPS        = YES
1079
1080# The PERL_PATH should be the absolute path and name of the perl script
1081# interpreter (i.e. the result of `which perl').
1082
1083PERL_PATH              = /usr/bin/perl
1084
1085#---------------------------------------------------------------------------
1086# Configuration options related to the dot tool   
1087#---------------------------------------------------------------------------
1088
1089# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1090# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1091# or super classes. Setting the tag to NO turns the diagrams off. Note that
1092# this option is superseded by the HAVE_DOT option below. This is only a
1093# fallback. It is recommended to install and use dot, since it yields more
1094# powerful graphs.
1095
1096CLASS_DIAGRAMS         = YES
1097
1098# You can define message sequence charts within doxygen comments using the \msc
1099# command. Doxygen will then run the mscgen tool (see http://www.mcternan.me.uk/mscgen/) to
1100# produce the chart and insert it in the documentation. The MSCGEN_PATH tag allows you to
1101# specify the directory where the mscgen tool resides. If left empty the tool is assumed to
1102# be found in the default search path.
1103
1104MSCGEN_PATH            =
1105
1106# If set to YES, the inheritance and collaboration graphs will hide
1107# inheritance and usage relations if the target is undocumented
1108# or is not a class.
1109
1110HIDE_UNDOC_RELATIONS   = YES
1111
1112# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1113# available from the path. This tool is part of Graphviz, a graph visualization
1114# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1115# have no effect if this option is set to NO (the default)
1116
1117HAVE_DOT               = YES
1118
1119# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1120# will generate a graph for each documented class showing the direct and
1121# indirect inheritance relations. Setting this tag to YES will force the
1122# the CLASS_DIAGRAMS tag to NO.
1123
1124CLASS_GRAPH            = YES
1125
1126# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1127# will generate a graph for each documented class showing the direct and
1128# indirect implementation dependencies (inheritance, containment, and
1129# class references variables) of the class with other documented classes.
1130
1131COLLABORATION_GRAPH    = YES
1132
1133# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen
1134# will generate a graph for groups, showing the direct groups dependencies
1135
1136GROUP_GRAPHS           = YES
1137
1138# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1139# collaboration diagrams in a style similar to the OMG's Unified Modeling
1140# Language.
1141
1142UML_LOOK               = NO
1143
1144# If set to YES, the inheritance and collaboration graphs will show the
1145# relations between templates and their instances.
1146
1147TEMPLATE_RELATIONS     = NO
1148
1149# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1150# tags are set to YES then doxygen will generate a graph for each documented
1151# file showing the direct and indirect include dependencies of the file with
1152# other documented files.
1153
1154INCLUDE_GRAPH          = YES
1155
1156# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1157# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1158# documented header file showing the documented files that directly or
1159# indirectly include this file.
1160
1161INCLUDED_BY_GRAPH      = YES
1162
1163# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1164# generate a call dependency graph for every global function or class method.
1165# Note that enabling this option will significantly increase the time of a run.
1166# So in most cases it will be better to enable call graphs for selected
1167# functions only using the \callgraph command.
1168
1169CALL_GRAPH             = NO
1170
1171# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1172# generate a caller dependency graph for every global function or class method.
1173# Note that enabling this option will significantly increase the time of a run.
1174# So in most cases it will be better to enable caller graphs for selected
1175# functions only using the \callergraph command.
1176
1177CALLER_GRAPH           = NO
1178
1179# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1180# will graphical hierarchy of all classes instead of a textual one.
1181
1182GRAPHICAL_HIERARCHY    = YES
1183
1184# If the DIRECTORY_GRAPH, SHOW_DIRECTORIES and HAVE_DOT tags are set to YES
1185# then doxygen will show the dependencies a directory has on other directories
1186# in a graphical way. The dependency relations are determined by the #include
1187# relations between the files in the directories.
1188
1189DIRECTORY_GRAPH        = YES
1190
1191# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1192# generated by dot. Possible values are png, jpg, or gif
1193# If left blank png will be used.
1194
1195DOT_IMAGE_FORMAT       = png
1196
1197# The tag DOT_PATH can be used to specify the path where the dot tool can be
1198# found. If left blank, it is assumed the dot tool can be found in the path.
1199
1200DOT_PATH               =
1201
1202# The DOTFILE_DIRS tag can be used to specify one or more directories that
1203# contain dot files that are included in the documentation (see the
1204# \dotfile command).
1205
1206DOTFILE_DIRS           =
1207
1208# The MAX_DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of
1209# nodes that will be shown in the graph. If the number of nodes in a graph
1210# becomes larger than this value, doxygen will truncate the graph, which is
1211# visualized by representing a node as a red box. Note that doxygen will always
1212# show the root nodes and its direct children regardless of this setting.
1213
1214DOT_GRAPH_MAX_NODES    = 50
1215
1216# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1217# background. This is disabled by default, which results in a white background.
1218# Warning: Depending on the platform used, enabling this option may lead to
1219# badly anti-aliased labels on the edges of a graph (i.e. they become hard to
1220# read).
1221
1222DOT_TRANSPARENT        = NO
1223
1224# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output
1225# files in one run (i.e. multiple -o and -T options on the command line). This
1226# makes dot run faster, but since only newer versions of dot (>1.8.10)
1227# support this, this feature is disabled by default.
1228
1229DOT_MULTI_TARGETS      = NO
1230
1231# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1232# generate a legend page explaining the meaning of the various boxes and
1233# arrows in the dot generated graphs.
1234
1235GENERATE_LEGEND        = YES
1236
1237# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1238# remove the intermediate dot files that are used to generate
1239# the various graphs.
1240
1241DOT_CLEANUP            = YES
1242
1243#---------------------------------------------------------------------------
1244# Configuration::additions related to the search engine   
1245#---------------------------------------------------------------------------
1246
1247# The SEARCHENGINE tag specifies whether or not a search engine should be
1248# used. If set to NO the values of all tags below this one will be ignored.
1249
1250SEARCHENGINE           = NO
Note: See TracBrowser for help on using the repository browser.