3 # This file describes the settings to be used by doxygen for a project
5 # All text after a hash (#) is considered a comment and will be ignored
7 # TAG = value [value, ...]
8 # For lists items can also be appended using:
9 # TAG += value [value, ...]
10 # Values that contain spaces should be placed between quotes (" ")
12 #---------------------------------------------------------------------------
13 # General configuration options
14 #---------------------------------------------------------------------------
19 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
20 # by quotes) that should identify the project.
21 PROJECT_NAME = "Bullet Collision Detection & Physics Library"
23 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
24 # This could be handy for archiving the generated documentation or
25 # if some version control system is used.
29 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
30 # base path where the generated documentation will be put.
31 # If a relative path is entered, it will be relative to the location
32 # where doxygen was started. If left blank the current directory will be used.
36 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
37 # documentation generated by doxygen is written. Doxygen will use this
38 # information to generate all constant output in the proper language.
39 # The default language is English, other supported languages are:
40 # Dutch, French, Italian, Czech, Swedish, German, Finnish, Japanese,
41 # Korean, Hungarian, Norwegian, Spanish, Romanian, Russian, Croatian,
42 # Polish, Portuguese and Slovene.
44 OUTPUT_LANGUAGE = English
46 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
47 # documentation are documented, even if no documentation was available.
48 # Private class members and static file members will be hidden unless
49 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
53 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
54 # will be included in the documentation.
58 # If the EXTRACT_STATIC tag is set to YES all static members of a file
59 # will be included in the documentation.
63 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
64 # undocumented members of documented classes, files or namespaces.
65 # If set to NO (the default) these members will be included in the
66 # various overviews, but no documentation section is generated.
67 # This option has no effect if EXTRACT_ALL is enabled.
69 HIDE_UNDOC_MEMBERS = NO
71 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
72 # undocumented classes that are normally visible in the class hierarchy.
73 # If set to NO (the default) these class will be included in the various
74 # overviews. This option has no effect if EXTRACT_ALL is enabled.
76 HIDE_UNDOC_CLASSES = NO
78 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
79 # include brief member descriptions after the members that are listed in
80 # the file and class documentation (similar to JavaDoc).
81 # Set to NO to disable this.
83 BRIEF_MEMBER_DESC = YES
85 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
86 # the brief description of a member or function before the detailed description.
87 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
88 # brief descriptions will be completely suppressed.
92 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
93 # Doxygen will generate a detailed section even if there is only a brief
96 ALWAYS_DETAILED_SEC = NO
98 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
99 # path before files name in the file list and in the header files. If set
100 # to NO the shortest path that makes the file name unique will be used.
104 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
105 # can be used to strip a user defined part of the path. Stripping is
106 # only done if one of the specified strings matches the left-hand part of
107 # the path. It is allowed to use relative paths in the argument list.
111 # The INTERNAL_DOCS tag determines if documentation
112 # that is typed after a \internal command is included. If the tag is set
113 # to NO (the default) then the documentation will be excluded.
114 # Set it to YES to include the internal documentation.
118 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
119 # generate a class diagram (in Html and LaTeX) for classes with base or
120 # super classes. Setting the tag to NO turns the diagrams off.
124 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
125 # be generated. Documented entities will be cross-referenced with these sources.
129 # Setting the INLINE_SOURCES tag to YES will include the body
130 # of functions and classes directly in the documentation.
134 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
135 # doxygen to hide any special comment blocks from generated source code
136 # fragments. Normal C and C++ comments will always remain visible.
138 STRIP_CODE_COMMENTS = YES
140 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
141 # file names in lower case letters. If set to YES upper case letters are also
142 # allowed. This is useful if you have classes or files whose names only differ
143 # in case and if your file system supports case sensitive file names. Windows
144 # users are adviced to set this option to NO.
146 CASE_SENSE_NAMES = YES
148 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
149 # will show members with their full class and namespace scopes in the
150 # documentation. If set to YES the scope will be hidden.
152 HIDE_SCOPE_NAMES = NO
154 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
155 # will generate a verbatim copy of the header file for each class for
156 # which an include is specified. Set to NO to disable this.
158 VERBATIM_HEADERS = YES
160 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
161 # will put list of the files that are included by a file in the documentation
164 SHOW_INCLUDE_FILES = YES
166 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
167 # will interpret the first line (until the first dot) of a JavaDoc-style
168 # comment as the brief description. If set to NO, the JavaDoc
169 # comments will behave just like the Qt-style comments (thus requiring an
170 # explict @brief command for a brief description.
172 JAVADOC_AUTOBRIEF = YES
174 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
175 # member inherits the documentation from any documented member that it
180 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
181 # is inserted in the documentation for inline members.
185 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
186 # will sort the (detailed) documentation of file and class members
187 # alphabetically by member name. If set to NO the members will appear in
190 SORT_MEMBER_DOCS = YES
192 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
193 # tag is set to YES, then doxygen will reuse the documentation of the first
194 # member in the group (if any) for the other members of the group. By default
195 # all members of a group must be documented explicitly.
197 DISTRIBUTE_GROUP_DOC = NO
199 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
200 # Doxygen uses this value to replace tabs by spaces in code fragments.
204 # The ENABLE_SECTIONS tag can be used to enable conditional
205 # documentation sections, marked by \if sectionname ... \endif.
209 # The GENERATE_TODOLIST tag can be used to enable (YES) or
210 # disable (NO) the todo list. This list is created by putting \todo
211 # commands in the documentation.
213 GENERATE_TODOLIST = NO
215 # The GENERATE_TESTLIST tag can be used to enable (YES) or
216 # disable (NO) the test list. This list is created by putting \test
217 # commands in the documentation.
219 GENERATE_TESTLIST = YES
221 # This tag can be used to specify a number of aliases that acts
222 # as commands in the documentation. An alias has the form "name=value".
223 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
224 # put the command \sideeffect (or @sideeffect) in the documentation, which
225 # will result in a user defined paragraph with heading "Side Effects:".
226 # You can put \n's in the value part of an alias to insert newlines.
230 #---------------------------------------------------------------------------
231 # configuration options related to warning and progress messages
232 #---------------------------------------------------------------------------
234 # The QUIET tag can be used to turn on/off the messages that are generated
235 # by doxygen. Possible values are YES and NO. If left blank NO is used.
239 # The WARNINGS tag can be used to turn on/off the warning messages that are
240 # generated by doxygen. Possible values are YES and NO. If left blank
245 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
246 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
247 # automatically be disabled.
249 WARN_IF_UNDOCUMENTED = YES
251 # The WARN_FORMAT tag determines the format of the warning messages that
252 # doxygen can produce. The string should contain the $file, $line, and $text
253 # tags, which will be replaced by the file and line number from which the
254 # warning originated and the warning text.
256 WARN_FORMAT = "$file:$line: $text"
258 # The WARN_LOGFILE tag can be used to specify a file to which warning
259 # and error messages should be written. If left blank the output is written
264 #---------------------------------------------------------------------------
265 # configuration options related to the input files
266 #---------------------------------------------------------------------------
268 # The INPUT tag can be used to specify the files and/or directories that contain
269 # documented source files. You may enter file names like "myfile.cpp" or
270 # directories like "/usr/src/myproject". Separate the files or directories
276 # If the value of the INPUT tag contains directories, you can use the
277 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
278 # and *.h) to filter out the source-files in the directories. If left
279 # blank all files are included.
281 FILE_PATTERNS = *.h *.cpp *.c
283 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
284 # should be searched for input files as well. Possible values are YES and NO.
285 # If left blank NO is used.
289 # The EXCLUDE tag can be used to specify files and/or directories that should
290 # excluded from the INPUT source files. This way you can easily exclude a
291 # subdirectory from a directory tree whose root is specified with the INPUT tag.
295 # If the value of the INPUT tag contains directories, you can use the
296 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
297 # certain files from those directories.
301 # The EXAMPLE_PATH tag can be used to specify one or more files or
302 # directories that contain example code fragments that are included (see
303 # the \include command).
307 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
308 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
309 # and *.h) to filter out the source-files in the directories. If left
310 # blank all files are included.
314 # The IMAGE_PATH tag can be used to specify one or more files or
315 # directories that contain image that are included in the documentation (see
316 # the \image command).
320 # The INPUT_FILTER tag can be used to specify a program that doxygen should
321 # invoke to filter for each input file. Doxygen will invoke the filter program
322 # by executing (via popen()) the command <filter> <input-file>, where <filter>
323 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
324 # input file. Doxygen will then use the output that the filter program writes
325 # to standard output.
329 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
330 # INPUT_FILTER) will be used to filter the input files when producing source
333 FILTER_SOURCE_FILES = NO
335 #---------------------------------------------------------------------------
336 # configuration options related to the alphabetical class index
337 #---------------------------------------------------------------------------
339 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
340 # of all compounds will be generated. Enable this if the project
341 # contains a lot of classes, structs, unions or interfaces.
343 ALPHABETICAL_INDEX = NO
345 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
346 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
347 # in which this list will be split (can be a number in the range [1..20])
349 COLS_IN_ALPHA_INDEX = 5
351 # In case all classes in a project start with a common prefix, all
352 # classes will be put under the same header in the alphabetical index.
353 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
354 # should be ignored while generating the index headers.
358 #---------------------------------------------------------------------------
359 # configuration options related to the HTML output
360 #---------------------------------------------------------------------------
362 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
363 # generate HTML output.
367 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
368 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
369 # put in front of it. If left blank `html' will be used as the default path.
373 # The HTML_HEADER tag can be used to specify a personal HTML header for
374 # each generated HTML page. If it is left blank doxygen will generate a
379 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
380 # each generated HTML page. If it is left blank doxygen will generate a
385 # The HTML_STYLESHEET tag can be used to specify a user defined cascading
386 # style sheet that is used by each HTML page. It can be used to
387 # fine-tune the look of the HTML output. If the tag is left blank doxygen
388 # will generate a default style sheet
392 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
393 # files or namespaces will be aligned in HTML using tables. If set to
394 # NO a bullet list will be used.
396 HTML_ALIGN_MEMBERS = YES
398 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
399 # will be generated that can be used as input for tools like the
400 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
401 # of the generated HTML documentation.
403 GENERATE_HTMLHELP = YES
405 # HHC_LOCATION = "C:\Program Files\HTML Help Workshop\hhc.exe"
406 HHC_LOCATION = "C:\Program Files (x86)\HTML Help Workshop\hhc.exe"
409 HTML_FILE_EXTENSION = .html
412 #HTML_STYLESHEET = "\\server\exchange\Software Development\Documentation\DoxyGen\doxygen.css"
414 CHM_FILE = BulletDocs.chm
415 HHC_LOCATION = "c:\program files\HTML Help Workshop\hhc.exe"
421 SHOW_DIRECTORIES = YES
424 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
425 # top of each HTML page. The value NO (the default) enables the index and
426 # the value YES disables it.
430 # This tag can be used to set the number of enum values (range [1..20])
431 # that doxygen will group on one line in the generated HTML documentation.
433 ENUM_VALUES_PER_LINE = 1
435 # If the GENERATE_TREEVIEW tag is set to YES, a side pannel will be
436 # generated containing a tree-like index structure (just like the one that
437 # is generated for HTML Help). For this to work a browser that supports
438 # JavaScript and frames is required (for instance Netscape 4.0+
439 # or Internet explorer 4.0+).
441 GENERATE_TREEVIEW = YES
443 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
444 # used to set the initial width (in pixels) of the frame in which the tree
449 #---------------------------------------------------------------------------
450 # configuration options related to the LaTeX output
451 #---------------------------------------------------------------------------
453 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
454 # generate Latex output.
458 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
459 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
460 # put in front of it. If left blank `latex' will be used as the default path.
464 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
465 # LaTeX documents. This may be useful for small projects and may help to
466 # save some trees in general.
470 # The PAPER_TYPE tag can be used to set the paper type that is used
471 # by the printer. Possible values are: a4, a4wide, letter, legal and
472 # executive. If left blank a4wide will be used.
476 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
477 # packages that should be included in the LaTeX output.
481 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
482 # the generated latex document. The header should contain everything until
483 # the first chapter. If it is left blank doxygen will generate a
484 # standard header. Notice: only use this tag if you know what you are doing!
488 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
489 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
490 # contain links (just like the HTML output) instead of page references
491 # This makes the output suitable for online browsing using a pdf viewer.
495 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
496 # plain latex in the generated Makefile. Set this option to YES to get a
497 # higher quality PDF documentation.
501 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
502 # command to the generated LaTeX files. This will instruct LaTeX to keep
503 # running if errors occur, instead of asking the user for help.
504 # This option is also used when generating formulas in HTML.
508 #---------------------------------------------------------------------------
509 # configuration options related to the RTF output
510 #---------------------------------------------------------------------------
512 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
513 # The RTF output is optimised for Word 97 and may not look very pretty with
514 # other RTF readers or editors.
518 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
519 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
520 # put in front of it. If left blank `rtf' will be used as the default path.
524 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
525 # RTF documents. This may be useful for small projects and may help to
526 # save some trees in general.
530 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
531 # will contain hyperlink fields. The RTF file will
532 # contain links (just like the HTML output) instead of page references.
533 # This makes the output suitable for online browsing using a WORD or other.
534 # programs which support those fields.
535 # Note: wordpad (write) and others do not support links.
539 # Load stylesheet definitions from file. Syntax is similar to doxygen's
540 # config file, i.e. a series of assigments. You only have to provide
541 # replacements, missing definitions are set to their default value.
543 RTF_STYLESHEET_FILE =
545 #---------------------------------------------------------------------------
546 # configuration options related to the man page output
547 #---------------------------------------------------------------------------
549 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
554 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
555 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
556 # put in front of it. If left blank `man' will be used as the default path.
560 # The MAN_EXTENSION tag determines the extension that is added to
561 # the generated man pages (default is the subroutine's section .3)
565 #---------------------------------------------------------------------------
566 # configuration options related to the XML output
567 #---------------------------------------------------------------------------
569 # If the GENERATE_XML tag is set to YES Doxygen will
570 # generate an XML file that captures the structure of
571 # the code including all documentation. Warning: This feature
572 # is still experimental and very incomplete.
576 #---------------------------------------------------------------------------
577 # Configuration options related to the preprocessor
578 #---------------------------------------------------------------------------
580 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
581 # evaluate all C-preprocessor directives found in the sources and include
584 ENABLE_PREPROCESSING = YES
586 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
587 # names in the source code. If set to NO (the default) only conditional
588 # compilation will be performed. Macro expansion can be done in a controlled
589 # way by setting EXPAND_ONLY_PREDEF to YES.
591 MACRO_EXPANSION = YES
593 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
594 # then the macro expansion is limited to the macros specified with the
595 # PREDEFINED and EXPAND_AS_PREDEFINED tags.
597 EXPAND_ONLY_PREDEF = YES
599 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
600 # in the INCLUDE_PATH (see below) will be search if a #include is found.
602 SEARCH_INCLUDES = YES
604 # The INCLUDE_PATH tag can be used to specify one or more directories that
605 # contain include files that are not input files but should be processed by
610 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
611 # patterns (like *.h and *.hpp) to filter out the header-files in the
612 # directories. If left blank, the patterns specified with FILE_PATTERNS will
615 INCLUDE_FILE_PATTERNS =
617 # The PREDEFINED tag can be used to specify one or more macro names that
618 # are defined before the preprocessor is started (similar to the -D option of
619 # gcc). The argument of the tag is a list of macros of the form: name
620 # or name=definition (no spaces). If the definition and the = are
621 # omitted =1 is assumed.
623 PREDEFINED = "ATTRIBUTE_ALIGNED128(x)=x" \
624 "ATTRIBUTE_ALIGNED16(x)=x" \
625 "SIMD_FORCE_INLINE=inline" \
626 "VECTORMATH_FORCE_INLINE=inline" \
627 "USE_WIN32_THREADING=1"\
632 # If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then
633 # this tag can be used to specify a list of macro names that should be expanded.
634 # The macro definition that is found in the sources will be used.
635 # Use the PREDEFINED tag if you want to use a different macro definition.
639 #---------------------------------------------------------------------------
640 # Configuration::addtions related to external references
641 #---------------------------------------------------------------------------
643 # The TAGFILES tag can be used to specify one or more tagfiles.
647 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
648 # a tag file that is based on the input files it reads.
652 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
653 # in the class index. If set to NO only the inherited external classes
658 # The PERL_PATH should be the absolute path and name of the perl script
659 # interpreter (i.e. the result of `which perl').
661 PERL_PATH = /usr/bin/perl
663 #---------------------------------------------------------------------------
664 # Configuration options related to the dot tool
665 #---------------------------------------------------------------------------
667 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
668 # available from the path. This tool is part of Graphviz, a graph visualization
669 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
670 # have no effect if this option is set to NO (the default)
674 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
675 # will generate a graph for each documented class showing the direct and
676 # indirect inheritance relations. Setting this tag to YES will force the
677 # the CLASS_DIAGRAMS tag to NO.
681 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
682 # will generate a graph for each documented class showing the direct and
683 # indirect implementation dependencies (inheritance, containment, and
684 # class references variables) of the class with other documented classes.
686 COLLABORATION_GRAPH = YES
688 # If the ENABLE_PREPROCESSING, INCLUDE_GRAPH, and HAVE_DOT tags are set to
689 # YES then doxygen will generate a graph for each documented file showing
690 # the direct and indirect include dependencies of the file with other
695 # If the ENABLE_PREPROCESSING, INCLUDED_BY_GRAPH, and HAVE_DOT tags are set to
696 # YES then doxygen will generate a graph for each documented header file showing
697 # the documented files that directly or indirectly include this file
699 INCLUDED_BY_GRAPH = YES
701 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
702 # will graphical hierarchy of all classes instead of a textual one.
704 GRAPHICAL_HIERARCHY = YES
706 # The tag DOT_PATH can be used to specify the path where the dot tool can be
707 # found. If left blank, it is assumed the dot tool can be found on the path.
711 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
712 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
713 # this value, doxygen will try to truncate the graph, so that it fits within
714 # the specified constraint. Beware that most browsers cannot cope with very
717 MAX_DOT_GRAPH_WIDTH = 1024
719 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
720 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
721 # this value, doxygen will try to truncate the graph, so that it fits within
722 # the specified constraint. Beware that most browsers cannot cope with very
725 MAX_DOT_GRAPH_HEIGHT = 1024
727 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
728 # generate a legend page explaining the meaning of the various boxes and
729 # arrows in the dot generated graphs.
731 GENERATE_LEGEND = YES
734 # delete intermediate dot files?
738 #---------------------------------------------------------------------------
739 # Configuration::addtions related to the search engine
740 #---------------------------------------------------------------------------
742 # The SEARCHENGINE tag specifies whether or not a search engine should be
743 # used. If set to NO the values of all tags below this one will be ignored.
747 # The CGI_NAME tag should be the name of the CGI script that
748 # starts the search engine (doxysearch) with the correct parameters.
749 # A script with this name will be generated by doxygen.
751 CGI_NAME = search.cgi
753 # The CGI_URL tag should be the absolute URL to the directory where the
754 # cgi binaries are located. See the documentation of your http daemon for
759 # The DOC_URL tag should be the absolute URL to the directory where the
760 # documentation is located. If left blank the absolute path to the
761 # documentation, with file:// prepended to it, will be used.
765 # The DOC_ABSPATH tag should be the absolute path to the directory where the
766 # documentation is located. If left blank the directory on the local machine
771 # The BIN_ABSPATH tag must point to the directory where the doxysearch binary
774 BIN_ABSPATH = c:\program files\doxygen\bin
776 # The EXT_DOC_PATHS tag can be used to specify one or more paths to
777 # documentation generated for other projects. This allows doxysearch to search
778 # the documentation for these projects as well.