COIN-OR::LEMON - Graph Library

source: lemon-0.x/src/work/Doxyfile @ 958:75f749682240

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