COIN-OR::LEMON - Graph Library

source: lemon-0.x/doc/Doxyfile @ 253:f45703336699

Last change on this file since 253:f45703336699 was 253:f45703336699, checked in by Alpar Juttner, 16 years ago

Move invalid.h smart_graph.h maps.h emptygraph.h to include

File size: 45.0 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           = HugoLib
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.1
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         = NO
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  = YES
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        = NO
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           =
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                  = ../src/include/skeletons/graph.h \
395                         ../src/include/invalid.h \
396                         ../src/include/smart_graph.h \
397                         ../src/include/skeletons/maps.h \
398                         ../src/demo/alpar/dijkstra/dijkstra.h \
399                         ../src/demo/alpar/dijkstra/bin_heap.hh \
400                         ../src/demo/alpar/dijkstra/fib_heap.h \
401                         ../src/demo/athos/xy/xy.h \
402                         maps.dox
403
404# If the value of the INPUT tag contains directories, you can use the
405# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
406# and *.h) to filter out the source-files in the directories. If left
407# blank the following patterns are tested:
408# *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
409# *.h++ *.idl *.odl *.cs *.php *.php3 *.inc
410
411FILE_PATTERNS          =
412
413# The RECURSIVE tag can be used to turn specify whether or not subdirectories
414# should be searched for input files as well. Possible values are YES and NO.
415# If left blank NO is used.
416
417RECURSIVE              = NO
418
419# The EXCLUDE tag can be used to specify files and/or directories that should
420# excluded from the INPUT source files. This way you can easily exclude a
421# subdirectory from a directory tree whose root is specified with the INPUT tag.
422
423EXCLUDE                =
424
425# The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
426# that are symbolic links (a Unix filesystem feature) are excluded from the input.
427
428EXCLUDE_SYMLINKS       = NO
429
430# If the value of the INPUT tag contains directories, you can use the
431# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
432# certain files from those directories.
433
434EXCLUDE_PATTERNS       =
435
436# The EXAMPLE_PATH tag can be used to specify one or more files or
437# directories that contain example code fragments that are included (see
438# the \include command).
439
440EXAMPLE_PATH           = examples
441
442# If the value of the EXAMPLE_PATH tag contains directories, you can use the
443# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
444# and *.h) to filter out the source-files in the directories. If left
445# blank all files are included.
446
447EXAMPLE_PATTERNS       =
448
449# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
450# searched for input files to be used with the \include or \dontinclude
451# commands irrespective of the value of the RECURSIVE tag.
452# Possible values are YES and NO. If left blank NO is used.
453
454EXAMPLE_RECURSIVE      = NO
455
456# The IMAGE_PATH tag can be used to specify one or more files or
457# directories that contain image that are included in the documentation (see
458# the \image command).
459
460IMAGE_PATH             =
461
462# The INPUT_FILTER tag can be used to specify a program that doxygen should
463# invoke to filter for each input file. Doxygen will invoke the filter program
464# by executing (via popen()) the command <filter> <input-file>, where <filter>
465# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
466# input file. Doxygen will then use the output that the filter program writes
467# to standard output.
468
469INPUT_FILTER           =
470
471# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
472# INPUT_FILTER) will be used to filter the input files when producing source
473# files to browse (i.e. when SOURCE_BROWSER is set to YES).
474
475FILTER_SOURCE_FILES    = NO
476
477#---------------------------------------------------------------------------
478# configuration options related to source browsing
479#---------------------------------------------------------------------------
480
481# If the SOURCE_BROWSER tag is set to YES then a list of source files will
482# be generated. Documented entities will be cross-referenced with these sources.
483# Note: To get rid of all source code in the generated output, make sure also
484# VERBATIM_HEADERS is set to NO.
485
486SOURCE_BROWSER         = YES
487
488# Setting the INLINE_SOURCES tag to YES will include the body
489# of functions and classes directly in the documentation.
490
491INLINE_SOURCES         = NO
492
493# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
494# doxygen to hide any special comment blocks from generated source code
495# fragments. Normal C and C++ comments will always remain visible.
496
497STRIP_CODE_COMMENTS    = YES
498
499# If the REFERENCED_BY_RELATION tag is set to YES (the default)
500# then for each documented function all documented
501# functions referencing it will be listed.
502
503REFERENCED_BY_RELATION = YES
504
505# If the REFERENCES_RELATION tag is set to YES (the default)
506# then for each documented function all documented entities
507# called/used by that function will be listed.
508
509REFERENCES_RELATION    = YES
510
511# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
512# will generate a verbatim copy of the header file for each class for
513# which an include is specified. Set to NO to disable this.
514
515VERBATIM_HEADERS       = YES
516
517#---------------------------------------------------------------------------
518# configuration options related to the alphabetical class index
519#---------------------------------------------------------------------------
520
521# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
522# of all compounds will be generated. Enable this if the project
523# contains a lot of classes, structs, unions or interfaces.
524
525ALPHABETICAL_INDEX     = YES
526
527# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
528# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
529# in which this list will be split (can be a number in the range [1..20])
530
531COLS_IN_ALPHA_INDEX    = 2
532
533# In case all classes in a project start with a common prefix, all
534# classes will be put under the same header in the alphabetical index.
535# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
536# should be ignored while generating the index headers.
537
538IGNORE_PREFIX          =
539
540#---------------------------------------------------------------------------
541# configuration options related to the HTML output
542#---------------------------------------------------------------------------
543
544# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
545# generate HTML output.
546
547GENERATE_HTML          = YES
548
549# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
550# If a relative path is entered the value of OUTPUT_DIRECTORY will be
551# put in front of it. If left blank `html' will be used as the default path.
552
553HTML_OUTPUT            = html
554
555# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
556# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
557# doxygen will generate files with .html extension.
558
559HTML_FILE_EXTENSION    = .html
560
561# The HTML_HEADER tag can be used to specify a personal HTML header for
562# each generated HTML page. If it is left blank doxygen will generate a
563# standard header.
564
565HTML_HEADER            =
566
567# The HTML_FOOTER tag can be used to specify a personal HTML footer for
568# each generated HTML page. If it is left blank doxygen will generate a
569# standard footer.
570
571HTML_FOOTER            =
572
573# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
574# style sheet that is used by each HTML page. It can be used to
575# fine-tune the look of the HTML output. If the tag is left blank doxygen
576# will generate a default style sheet. Note that doxygen will try to copy
577# the style sheet file to the HTML output directory, so don't put your own
578# stylesheet in the HTML output directory as well, or it will be erased!
579
580HTML_STYLESHEET        =
581
582# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
583# files or namespaces will be aligned in HTML using tables. If set to
584# NO a bullet list will be used.
585
586HTML_ALIGN_MEMBERS     = YES
587
588# If the GENERATE_HTMLHELP tag is set to YES, additional index files
589# will be generated that can be used as input for tools like the
590# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
591# of the generated HTML documentation.
592
593GENERATE_HTMLHELP      = NO
594
595# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
596# be used to specify the file name of the resulting .chm file. You
597# can add a path in front of the file if the result should not be
598# written to the html output directory.
599
600CHM_FILE               =
601
602# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
603# be used to specify the location (absolute path including file name) of
604# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
605# the HTML help compiler on the generated index.hhp.
606
607HHC_LOCATION           =
608
609# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
610# controls if a separate .chi index file is generated (YES) or that
611# it should be included in the master .chm file (NO).
612
613GENERATE_CHI           = NO
614
615# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
616# controls whether a binary table of contents is generated (YES) or a
617# normal table of contents (NO) in the .chm file.
618
619BINARY_TOC             = NO
620
621# The TOC_EXPAND flag can be set to YES to add extra items for group members
622# to the contents of the HTML help documentation and to the tree view.
623
624TOC_EXPAND             = NO
625
626# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
627# top of each HTML page. The value NO (the default) enables the index and
628# the value YES disables it.
629
630DISABLE_INDEX          = NO
631
632# This tag can be used to set the number of enum values (range [1..20])
633# that doxygen will group on one line in the generated HTML documentation.
634
635ENUM_VALUES_PER_LINE   = 4
636
637# If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
638# generated containing a tree-like index structure (just like the one that
639# is generated for HTML Help). For this to work a browser that supports
640# JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
641# Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
642# probably better off using the HTML help feature.
643
644GENERATE_TREEVIEW      = YES
645
646# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
647# used to set the initial width (in pixels) of the frame in which the tree
648# is shown.
649
650TREEVIEW_WIDTH         = 250
651
652#---------------------------------------------------------------------------
653# configuration options related to the LaTeX output
654#---------------------------------------------------------------------------
655
656# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
657# generate Latex output.
658
659GENERATE_LATEX         = YES
660
661# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
662# If a relative path is entered the value of OUTPUT_DIRECTORY will be
663# put in front of it. If left blank `latex' will be used as the default path.
664
665LATEX_OUTPUT           = latex
666
667# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
668# invoked. If left blank `latex' will be used as the default command name.
669
670LATEX_CMD_NAME         = latex
671
672# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
673# generate index for LaTeX. If left blank `makeindex' will be used as the
674# default command name.
675
676MAKEINDEX_CMD_NAME     = makeindex
677
678# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
679# LaTeX documents. This may be useful for small projects and may help to
680# save some trees in general.
681
682COMPACT_LATEX          = YES
683
684# The PAPER_TYPE tag can be used to set the paper type that is used
685# by the printer. Possible values are: a4, a4wide, letter, legal and
686# executive. If left blank a4wide will be used.
687
688PAPER_TYPE             = a4wide
689
690# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
691# packages that should be included in the LaTeX output.
692
693EXTRA_PACKAGES         =
694
695# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
696# the generated latex document. The header should contain everything until
697# the first chapter. If it is left blank doxygen will generate a
698# standard header. Notice: only use this tag if you know what you are doing!
699
700LATEX_HEADER           =
701
702# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
703# is prepared for conversion to pdf (using ps2pdf). The pdf file will
704# contain links (just like the HTML output) instead of page references
705# This makes the output suitable for online browsing using a pdf viewer.
706
707PDF_HYPERLINKS         = YES
708
709# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
710# plain latex in the generated Makefile. Set this option to YES to get a
711# higher quality PDF documentation.
712
713USE_PDFLATEX           = YES
714
715# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
716# command to the generated LaTeX files. This will instruct LaTeX to keep
717# running if errors occur, instead of asking the user for help.
718# This option is also used when generating formulas in HTML.
719
720LATEX_BATCHMODE        = NO
721
722# If LATEX_HIDE_INDICES is set to YES then doxygen will not
723# include the index chapters (such as File Index, Compound Index, etc.)
724# in the output.
725
726LATEX_HIDE_INDICES     = NO
727
728#---------------------------------------------------------------------------
729# configuration options related to the RTF output
730#---------------------------------------------------------------------------
731
732# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
733# The RTF output is optimized for Word 97 and may not look very pretty with
734# other RTF readers or editors.
735
736GENERATE_RTF           = NO
737
738# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
739# If a relative path is entered the value of OUTPUT_DIRECTORY will be
740# put in front of it. If left blank `rtf' will be used as the default path.
741
742RTF_OUTPUT             = rtf
743
744# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
745# RTF documents. This may be useful for small projects and may help to
746# save some trees in general.
747
748COMPACT_RTF            = NO
749
750# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
751# will contain hyperlink fields. The RTF file will
752# contain links (just like the HTML output) instead of page references.
753# This makes the output suitable for online browsing using WORD or other
754# programs which support those fields.
755# Note: wordpad (write) and others do not support links.
756
757RTF_HYPERLINKS         = NO
758
759# Load stylesheet definitions from file. Syntax is similar to doxygen's
760# config file, i.e. a series of assignments. You only have to provide
761# replacements, missing definitions are set to their default value.
762
763RTF_STYLESHEET_FILE    =
764
765# Set optional variables used in the generation of an rtf document.
766# Syntax is similar to doxygen's config file.
767
768RTF_EXTENSIONS_FILE    =
769
770#---------------------------------------------------------------------------
771# configuration options related to the man page output
772#---------------------------------------------------------------------------
773
774# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
775# generate man pages
776
777GENERATE_MAN           = NO
778
779# The MAN_OUTPUT tag is used to specify where the man pages will be put.
780# If a relative path is entered the value of OUTPUT_DIRECTORY will be
781# put in front of it. If left blank `man' will be used as the default path.
782
783MAN_OUTPUT             = man
784
785# The MAN_EXTENSION tag determines the extension that is added to
786# the generated man pages (default is the subroutine's section .3)
787
788MAN_EXTENSION          = .3
789
790# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
791# then it will generate one additional man file for each entity
792# documented in the real man page(s). These additional files
793# only source the real man page, but without them the man command
794# would be unable to find the correct page. The default is NO.
795
796MAN_LINKS              = NO
797
798#---------------------------------------------------------------------------
799# configuration options related to the XML output
800#---------------------------------------------------------------------------
801
802# If the GENERATE_XML tag is set to YES Doxygen will
803# generate an XML file that captures the structure of
804# the code including all documentation.
805
806GENERATE_XML           = NO
807
808# The XML_OUTPUT tag is used to specify where the XML pages will be put.
809# If a relative path is entered the value of OUTPUT_DIRECTORY will be
810# put in front of it. If left blank `xml' will be used as the default path.
811
812XML_OUTPUT             = xml
813
814# The XML_SCHEMA tag can be used to specify an XML schema,
815# which can be used by a validating XML parser to check the
816# syntax of the XML files.
817
818XML_SCHEMA             =
819
820# The XML_DTD tag can be used to specify an XML DTD,
821# which can be used by a validating XML parser to check the
822# syntax of the XML files.
823
824XML_DTD                =
825
826# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
827# dump the program listings (including syntax highlighting
828# and cross-referencing information) to the XML output. Note that
829# enabling this will significantly increase the size of the XML output.
830
831XML_PROGRAMLISTING     = YES
832
833#---------------------------------------------------------------------------
834# configuration options for the AutoGen Definitions output
835#---------------------------------------------------------------------------
836
837# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
838# generate an AutoGen Definitions (see autogen.sf.net) file
839# that captures the structure of the code including all
840# documentation. Note that this feature is still experimental
841# and incomplete at the moment.
842
843GENERATE_AUTOGEN_DEF   = NO
844
845#---------------------------------------------------------------------------
846# configuration options related to the Perl module output
847#---------------------------------------------------------------------------
848
849# If the GENERATE_PERLMOD tag is set to YES Doxygen will
850# generate a Perl module file that captures the structure of
851# the code including all documentation. Note that this
852# feature is still experimental and incomplete at the
853# moment.
854
855GENERATE_PERLMOD       = NO
856
857# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
858# the necessary Makefile rules, Perl scripts and LaTeX code to be able
859# to generate PDF and DVI output from the Perl module output.
860
861PERLMOD_LATEX          = NO
862
863# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
864# nicely formatted so it can be parsed by a human reader.  This is useful
865# if you want to understand what is going on.  On the other hand, if this
866# tag is set to NO the size of the Perl module output will be much smaller
867# and Perl will parse it just the same.
868
869PERLMOD_PRETTY         = YES
870
871# The names of the make variables in the generated doxyrules.make file
872# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
873# This is useful so different doxyrules.make files included by the same
874# Makefile don't overwrite each other's variables.
875
876PERLMOD_MAKEVAR_PREFIX =
877
878#---------------------------------------------------------------------------
879# Configuration options related to the preprocessor   
880#---------------------------------------------------------------------------
881
882# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
883# evaluate all C-preprocessor directives found in the sources and include
884# files.
885
886ENABLE_PREPROCESSING   = YES
887
888# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
889# names in the source code. If set to NO (the default) only conditional
890# compilation will be performed. Macro expansion can be done in a controlled
891# way by setting EXPAND_ONLY_PREDEF to YES.
892
893MACRO_EXPANSION        = NO
894
895# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
896# then the macro expansion is limited to the macros specified with the
897# PREDEFINED and EXPAND_AS_PREDEFINED tags.
898
899EXPAND_ONLY_PREDEF     = NO
900
901# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
902# in the INCLUDE_PATH (see below) will be search if a #include is found.
903
904SEARCH_INCLUDES        = YES
905
906# The INCLUDE_PATH tag can be used to specify one or more directories that
907# contain include files that are not input files but should be processed by
908# the preprocessor.
909
910INCLUDE_PATH           =
911
912# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
913# patterns (like *.h and *.hpp) to filter out the header-files in the
914# directories. If left blank, the patterns specified with FILE_PATTERNS will
915# be used.
916
917INCLUDE_FILE_PATTERNS  =
918
919# The PREDEFINED tag can be used to specify one or more macro names that
920# are defined before the preprocessor is started (similar to the -D option of
921# gcc). The argument of the tag is a list of macros of the form: name
922# or name=definition (no spaces). If the definition and the = are
923# omitted =1 is assumed.
924
925PREDEFINED             = DOXYGEN
926
927# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
928# this tag can be used to specify a list of macro names that should be expanded.
929# The macro definition that is found in the sources will be used.
930# Use the PREDEFINED tag if you want to use a different macro definition.
931
932EXPAND_AS_DEFINED      =
933
934# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
935# doxygen's preprocessor will remove all function-like macros that are alone
936# on a line, have an all uppercase name, and do not end with a semicolon. Such
937# function macros are typically used for boiler-plate code, and will confuse the
938# parser if not removed.
939
940SKIP_FUNCTION_MACROS   = YES
941
942#---------------------------------------------------------------------------
943# Configuration::additions related to external references   
944#---------------------------------------------------------------------------
945
946# The TAGFILES option can be used to specify one or more tagfiles.
947# Optionally an initial location of the external documentation
948# can be added for each tagfile. The format of a tag file without
949# this location is as follows:
950#   TAGFILES = file1 file2 ...
951# Adding location for the tag files is done as follows:
952#   TAGFILES = file1=loc1 "file2 = loc2" ...
953# where "loc1" and "loc2" can be relative or absolute paths or
954# URLs. If a location is present for each tag, the installdox tool
955# does not have to be run to correct the links.
956# Note that each tag file must have a unique name
957# (where the name does NOT include the path)
958# If a tag file is not located in the directory in which doxygen
959# is run, you must also specify the path to the tagfile here.
960
961TAGFILES               =
962
963# When a file name is specified after GENERATE_TAGFILE, doxygen will create
964# a tag file that is based on the input files it reads.
965
966GENERATE_TAGFILE       =
967
968# If the ALLEXTERNALS tag is set to YES all external classes will be listed
969# in the class index. If set to NO only the inherited external classes
970# will be listed.
971
972ALLEXTERNALS           = NO
973
974# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
975# in the modules index. If set to NO, only the current project's groups will
976# be listed.
977
978EXTERNAL_GROUPS        = YES
979
980# The PERL_PATH should be the absolute path and name of the perl script
981# interpreter (i.e. the result of `which perl').
982
983PERL_PATH              = /usr/bin/perl
984
985#---------------------------------------------------------------------------
986# Configuration options related to the dot tool   
987#---------------------------------------------------------------------------
988
989# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
990# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or
991# super classes. Setting the tag to NO turns the diagrams off. Note that this
992# option is superseded by the HAVE_DOT option below. This is only a fallback. It is
993# recommended to install and use dot, since it yields more powerful graphs.
994
995CLASS_DIAGRAMS         = YES
996
997# If set to YES, the inheritance and collaboration graphs will hide
998# inheritance and usage relations if the target is undocumented
999# or is not a class.
1000
1001HIDE_UNDOC_RELATIONS   = NO
1002
1003# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1004# available from the path. This tool is part of Graphviz, a graph visualization
1005# toolkit from AT&T and Lucent Bell Labs. The other options in this section
1006# have no effect if this option is set to NO (the default)
1007
1008HAVE_DOT               = YES
1009
1010# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1011# will generate a graph for each documented class showing the direct and
1012# indirect inheritance relations. Setting this tag to YES will force the
1013# the CLASS_DIAGRAMS tag to NO.
1014
1015CLASS_GRAPH            = YES
1016
1017# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1018# will generate a graph for each documented class showing the direct and
1019# indirect implementation dependencies (inheritance, containment, and
1020# class references variables) of the class with other documented classes.
1021
1022COLLABORATION_GRAPH    = YES
1023
1024# If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1025# collaboration diagrams in a style similar to the OMG's Unified Modeling
1026# Language.
1027
1028UML_LOOK               = NO
1029
1030# If set to YES, the inheritance and collaboration graphs will show the
1031# relations between templates and their instances.
1032
1033TEMPLATE_RELATIONS     = YES
1034
1035# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1036# tags are set to YES then doxygen will generate a graph for each documented
1037# file showing the direct and indirect include dependencies of the file with
1038# other documented files.
1039
1040INCLUDE_GRAPH          = YES
1041
1042# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1043# HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1044# documented header file showing the documented files that directly or
1045# indirectly include this file.
1046
1047INCLUDED_BY_GRAPH      = YES
1048
1049# If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1050# generate a call dependency graph for every global function or class method.
1051# Note that enabling this option will significantly increase the time of a run.
1052# So in most cases it will be better to enable call graphs for selected
1053# functions only using the \callgraph command.
1054
1055CALL_GRAPH             = YES
1056
1057# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1058# will graphical hierarchy of all classes instead of a textual one.
1059
1060GRAPHICAL_HIERARCHY    = YES
1061
1062# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1063# generated by dot. Possible values are png, jpg, or gif
1064# If left blank png will be used.
1065
1066DOT_IMAGE_FORMAT       = png
1067
1068# The tag DOT_PATH can be used to specify the path where the dot tool can be
1069# found. If left blank, it is assumed the dot tool can be found on the path.
1070
1071DOT_PATH               =
1072
1073# The DOTFILE_DIRS tag can be used to specify one or more directories that
1074# contain dot files that are included in the documentation (see the
1075# \dotfile command).
1076
1077DOTFILE_DIRS           =
1078
1079# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1080# (in pixels) of the graphs generated by dot. If a graph becomes larger than
1081# this value, doxygen will try to truncate the graph, so that it fits within
1082# the specified constraint. Beware that most browsers cannot cope with very
1083# large images.
1084
1085MAX_DOT_GRAPH_WIDTH    = 1024
1086
1087# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1088# (in pixels) of the graphs generated by dot. If a graph becomes larger than
1089# this value, doxygen will try to truncate the graph, so that it fits within
1090# the specified constraint. Beware that most browsers cannot cope with very
1091# large images.
1092
1093MAX_DOT_GRAPH_HEIGHT   = 1024
1094
1095# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1096# graphs generated by dot. A depth value of 3 means that only nodes reachable
1097# from the root by following a path via at most 3 edges will be shown. Nodes that
1098# lay further from the root node will be omitted. Note that setting this option to
1099# 1 or 2 may greatly reduce the computation time needed for large code bases. Also
1100# note that a graph may be further truncated if the graph's image dimensions are
1101# not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT).
1102# If 0 is used for the depth value (the default), the graph is not depth-constrained.
1103
1104MAX_DOT_GRAPH_DEPTH    = 0
1105
1106# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1107# generate a legend page explaining the meaning of the various boxes and
1108# arrows in the dot generated graphs.
1109
1110GENERATE_LEGEND        = YES
1111
1112# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1113# remove the intermediate dot files that are used to generate
1114# the various graphs.
1115
1116DOT_CLEANUP            = YES
1117
1118#---------------------------------------------------------------------------
1119# Configuration::additions related to the search engine   
1120#---------------------------------------------------------------------------
1121
1122# The SEARCHENGINE tag specifies whether or not a search engine should be
1123# used. If set to NO the values of all tags below this one will be ignored.
1124
1125SEARCHENGINE           = YES
Note: See TracBrowser for help on using the repository browser.