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