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
#---------------------------------------------------------------------------
16
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
17
# by quotes) that should identify the project.
18
PROJECT_NAME = foundation
20
# The PROJECT_NUMBER tag can be used to enter a project or revision number.
21
# This could be handy for archiving the generated documentation or
22
# if some version control system is used.
26
# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
27
# base path where the generated documentation will be put.
28
# If a relative path is entered, it will be relative to the location
29
# where doxygen was started. If left blank the current directory will be used.
33
# The OUTPUT_LANGUAGE tag is used to specify the language in which all
34
# documentation generated by doxygen is written. Doxygen will use this
35
# information to generate all constant output in the proper language.
36
# The default language is English, other supported languages are:
37
# Dutch, French, Italian, Czech, Swedish, German, Finnish, Japanese,
38
# Korean, Hungarian, Norwegian, Spanish, Romanian, Russian, Croatian,
39
# Polish, Portuguese and Slovene.
41
OUTPUT_LANGUAGE = English
43
# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
44
# documentation are documented, even if no documentation was available.
45
# Private class members and static file members will be hidden unless
46
# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
50
# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
51
# will be included in the documentation.
55
# If the EXTRACT_STATIC tag is set to YES all static members of a file
56
# will be included in the documentation.
60
# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
61
# undocumented members of documented classes, files or namespaces.
62
# If set to NO (the default) these members will be included in the
63
# various overviews, but no documentation section is generated.
64
# This option has no effect if EXTRACT_ALL is enabled.
66
HIDE_UNDOC_MEMBERS = NO
68
# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
69
# undocumented classes that are normally visible in the class hierarchy.
70
# If set to NO (the default) these class will be included in the various
71
# overviews. This option has no effect if EXTRACT_ALL is enabled.
73
HIDE_UNDOC_CLASSES = NO
75
# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
76
# include brief member descriptions after the members that are listed in
77
# the file and class documentation (similar to JavaDoc).
78
# Set to NO to disable this.
80
BRIEF_MEMBER_DESC = YES
82
# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
83
# the brief description of a member or function before the detailed description.
84
# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
85
# brief descriptions will be completely suppressed.
89
# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
90
# Doxygen will generate a detailed section even if there is only a brief
93
ALWAYS_DETAILED_SEC = NO
95
# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
96
# path before files name in the file list and in the header files. If set
97
# to NO the shortest path that makes the file name unique will be used.
101
# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
102
# can be used to strip a user defined part of the path. Stripping is
103
# only done if one of the specified strings matches the left-hand part of
104
# the path. It is allowed to use relative paths in the argument list.
108
# The INTERNAL_DOCS tag determines if documentation
109
# that is typed after a \internal command is included. If the tag is set
110
# to NO (the default) then the documentation will be excluded.
111
# Set it to YES to include the internal documentation.
115
# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
116
# generate a class diagram (in Html and LaTeX) for classes with base or
117
# super classes. Setting the tag to NO turns the diagrams off.
121
# If the SOURCE_BROWSER tag is set to YES then a list of source files will
122
# be generated. Documented entities will be cross-referenced with these sources.
126
# Setting the INLINE_SOURCES tag to YES will include the body
127
# of functions and classes directly in the documentation.
131
# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
132
# doxygen to hide any special comment blocks from generated source code
133
# fragments. Normal C and C++ comments will always remain visible.
135
STRIP_CODE_COMMENTS = YES
137
# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
138
# file names in lower case letters. If set to YES upper case letters are also
139
# allowed. This is useful if you have classes or files whose names only differ
140
# in case and if your file system supports case sensitive file names. Windows
141
# users are adviced to set this option to NO.
143
CASE_SENSE_NAMES = YES
145
# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
146
# will show members with their full class and namespace scopes in the
147
# documentation. If set to YES the scope will be hidden.
149
HIDE_SCOPE_NAMES = NO
151
# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
152
# will generate a verbatim copy of the header file for each class for
153
# which an include is specified. Set to NO to disable this.
155
VERBATIM_HEADERS = YES
157
# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
158
# will put list of the files that are included by a file in the documentation
161
SHOW_INCLUDE_FILES = YES
163
# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
164
# will interpret the first line (until the first dot) of a JavaDoc-style
165
# comment as the brief description. If set to NO, the JavaDoc
166
# comments will behave just like the Qt-style comments (thus requiring an
167
# explict @brief command for a brief description.
169
JAVADOC_AUTOBRIEF = YES
171
# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
172
# member inherits the documentation from any documented member that it
177
# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
178
# is inserted in the documentation for inline members.
182
# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
183
# will sort the (detailed) documentation of file and class members
184
# alphabetically by member name. If set to NO the members will appear in
187
SORT_MEMBER_DOCS = YES
189
# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
190
# tag is set to YES, then doxygen will reuse the documentation of the first
191
# member in the group (if any) for the other members of the group. By default
192
# all members of a group must be documented explicitly.
194
DISTRIBUTE_GROUP_DOC = NO
196
# The TAB_SIZE tag can be used to set the number of spaces in a tab.
197
# Doxygen uses this value to replace tabs by spaces in code fragments.
201
# The ENABLE_SECTIONS tag can be used to enable conditional
202
# documentation sections, marked by \if sectionname ... \endif.
206
# The GENERATE_TODOLIST tag can be used to enable (YES) or
207
# disable (NO) the todo list. This list is created by putting \todo
208
# commands in the documentation.
210
GENERATE_TODOLIST = YES
212
# The GENERATE_TESTLIST tag can be used to enable (YES) or
213
# disable (NO) the test list. This list is created by putting \test
214
# commands in the documentation.
216
GENERATE_TESTLIST = YES
218
# This tag can be used to specify a number of aliases that acts
219
# as commands in the documentation. An alias has the form "name=value".
220
# For example adding "sideeffect=\par Side Effects:\n" will allow you to
221
# put the command \sideeffect (or @sideeffect) in the documentation, which
222
# will result in a user defined paragraph with heading "Side Effects:".
223
# You can put \n's in the value part of an alias to insert newlines.
227
#---------------------------------------------------------------------------
228
# configuration options related to warning and progress messages
229
#---------------------------------------------------------------------------
231
# The QUIET tag can be used to turn on/off the messages that are generated
232
# by doxygen. Possible values are YES and NO. If left blank NO is used.
236
# The WARNINGS tag can be used to turn on/off the warning messages that are
237
# generated by doxygen. Possible values are YES and NO. If left blank
242
# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
243
# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
244
# automatically be disabled.
246
WARN_IF_UNDOCUMENTED = YES
248
# The WARN_FORMAT tag determines the format of the warning messages that
249
# doxygen can produce. The string should contain the $file, $line, and $text
250
# tags, which will be replaced by the file and line number from which the
251
# warning originated and the warning text.
253
WARN_FORMAT = "$file:$line: $text"
255
# The WARN_LOGFILE tag can be used to specify a file to which warning
256
# and error messages should be written. If left blank the output is written
261
#---------------------------------------------------------------------------
262
# configuration options related to the input files
263
#---------------------------------------------------------------------------
265
# The INPUT tag can be used to specify the files and/or directories that contain
266
# documented source files. You may enter file names like "myfile.cpp" or
267
# directories like "/usr/src/myproject". Separate the files or directories
270
INPUT = ../extern ../intern
273
# If the value of the INPUT tag contains directories, you can use the
274
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
275
# and *.h) to filter out the source-files in the directories. If left
276
# blank all files are included.
278
FILE_PATTERNS = *.h *.cpp *.c
280
# The RECURSIVE tag can be used to turn specify whether or not subdirectories
281
# should be searched for input files as well. Possible values are YES and NO.
282
# If left blank NO is used.
286
# The EXCLUDE tag can be used to specify files and/or directories that should
287
# excluded from the INPUT source files. This way you can easily exclude a
288
# subdirectory from a directory tree whose root is specified with the INPUT tag.
292
# If the value of the INPUT tag contains directories, you can use the
293
# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
294
# certain files from those directories.
298
# The EXAMPLE_PATH tag can be used to specify one or more files or
299
# directories that contain example code fragments that are included (see
300
# the \include command).
304
# If the value of the EXAMPLE_PATH tag contains directories, you can use the
305
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
306
# and *.h) to filter out the source-files in the directories. If left
307
# blank all files are included.
311
# The IMAGE_PATH tag can be used to specify one or more files or
312
# directories that contain image that are included in the documentation (see
313
# the \image command).
317
# The INPUT_FILTER tag can be used to specify a program that doxygen should
318
# invoke to filter for each input file. Doxygen will invoke the filter program
319
# by executing (via popen()) the command <filter> <input-file>, where <filter>
320
# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
321
# input file. Doxygen will then use the output that the filter program writes
322
# to standard output.
326
# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
327
# INPUT_FILTER) will be used to filter the input files when producing source
330
FILTER_SOURCE_FILES = NO
332
#---------------------------------------------------------------------------
333
# configuration options related to the alphabetical class index
334
#---------------------------------------------------------------------------
336
# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
337
# of all compounds will be generated. Enable this if the project
338
# contains a lot of classes, structs, unions or interfaces.
340
ALPHABETICAL_INDEX = NO
342
# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
343
# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
344
# in which this list will be split (can be a number in the range [1..20])
346
COLS_IN_ALPHA_INDEX = 5
348
# In case all classes in a project start with a common prefix, all
349
# classes will be put under the same header in the alphabetical index.
350
# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
351
# should be ignored while generating the index headers.
355
#---------------------------------------------------------------------------
356
# configuration options related to the HTML output
357
#---------------------------------------------------------------------------
359
# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
360
# generate HTML output.
364
# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
365
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
366
# put in front of it. If left blank `html' will be used as the default path.
370
# The HTML_HEADER tag can be used to specify a personal HTML header for
371
# each generated HTML page. If it is left blank doxygen will generate a
376
# The HTML_FOOTER tag can be used to specify a personal HTML footer for
377
# each generated HTML page. If it is left blank doxygen will generate a
382
# The HTML_STYLESHEET tag can be used to specify a user defined cascading
383
# style sheet that is used by each HTML page. It can be used to
384
# fine-tune the look of the HTML output. If the tag is left blank doxygen
385
# will generate a default style sheet
389
# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
390
# files or namespaces will be aligned in HTML using tables. If set to
391
# NO a bullet list will be used.
393
HTML_ALIGN_MEMBERS = YES
395
# If the GENERATE_HTMLHELP tag is set to YES, additional index files
396
# will be generated that can be used as input for tools like the
397
# Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
398
# of the generated HTML documentation.
400
GENERATE_HTMLHELP = NO
402
# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
403
# top of each HTML page. The value NO (the default) enables the index and
404
# the value YES disables it.
408
# This tag can be used to set the number of enum values (range [1..20])
409
# that doxygen will group on one line in the generated HTML documentation.
411
ENUM_VALUES_PER_LINE = 4
413
# If the GENERATE_TREEVIEW tag is set to YES, a side pannel will be
414
# generated containing a tree-like index structure (just like the one that
415
# is generated for HTML Help). For this to work a browser that supports
416
# JavaScript and frames is required (for instance Netscape 4.0+
417
# or Internet explorer 4.0+).
419
GENERATE_TREEVIEW = NO
421
# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
422
# used to set the initial width (in pixels) of the frame in which the tree
427
#---------------------------------------------------------------------------
428
# configuration options related to the LaTeX output
429
#---------------------------------------------------------------------------
431
# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
432
# generate Latex output.
436
# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
437
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
438
# put in front of it. If left blank `latex' will be used as the default path.
442
# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
443
# LaTeX documents. This may be useful for small projects and may help to
444
# save some trees in general.
448
# The PAPER_TYPE tag can be used to set the paper type that is used
449
# by the printer. Possible values are: a4, a4wide, letter, legal and
450
# executive. If left blank a4wide will be used.
454
# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
455
# packages that should be included in the LaTeX output.
459
# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
460
# the generated latex document. The header should contain everything until
461
# the first chapter. If it is left blank doxygen will generate a
462
# standard header. Notice: only use this tag if you know what you are doing!
466
# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
467
# is prepared for conversion to pdf (using ps2pdf). The pdf file will
468
# contain links (just like the HTML output) instead of page references
469
# This makes the output suitable for online browsing using a pdf viewer.
473
# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
474
# plain latex in the generated Makefile. Set this option to YES to get a
475
# higher quality PDF documentation.
479
# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
480
# command to the generated LaTeX files. This will instruct LaTeX to keep
481
# running if errors occur, instead of asking the user for help.
482
# This option is also used when generating formulas in HTML.
486
#---------------------------------------------------------------------------
487
# configuration options related to the RTF output
488
#---------------------------------------------------------------------------
490
# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
491
# The RTF output is optimised for Word 97 and may not look very pretty with
492
# other RTF readers or editors.
496
# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
497
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
498
# put in front of it. If left blank `rtf' will be used as the default path.
502
# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
503
# RTF documents. This may be useful for small projects and may help to
504
# save some trees in general.
508
# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
509
# will contain hyperlink fields. The RTF file will
510
# contain links (just like the HTML output) instead of page references.
511
# This makes the output suitable for online browsing using a WORD or other.
512
# programs which support those fields.
513
# Note: wordpad (write) and others do not support links.
517
# Load stylesheet definitions from file. Syntax is similar to doxygen's
518
# config file, i.e. a series of assigments. You only have to provide
519
# replacements, missing definitions are set to their default value.
521
RTF_STYLESHEET_FILE =
523
#---------------------------------------------------------------------------
524
# configuration options related to the man page output
525
#---------------------------------------------------------------------------
527
# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
532
# The MAN_OUTPUT tag is used to specify where the man pages will be put.
533
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
534
# put in front of it. If left blank `man' will be used as the default path.
538
# The MAN_EXTENSION tag determines the extension that is added to
539
# the generated man pages (default is the subroutine's section .3)
543
#---------------------------------------------------------------------------
544
# configuration options related to the XML output
545
#---------------------------------------------------------------------------
547
# If the GENERATE_XML tag is set to YES Doxygen will
548
# generate an XML file that captures the structure of
549
# the code including all documentation. Warning: This feature
550
# is still experimental and very incomplete.
554
#---------------------------------------------------------------------------
555
# Configuration options related to the preprocessor
556
#---------------------------------------------------------------------------
558
# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
559
# evaluate all C-preprocessor directives found in the sources and include
562
ENABLE_PREPROCESSING = YES
564
# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
565
# names in the source code. If set to NO (the default) only conditional
566
# compilation will be performed. Macro expansion can be done in a controlled
567
# way by setting EXPAND_ONLY_PREDEF to YES.
571
# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
572
# then the macro expansion is limited to the macros specified with the
573
# PREDEFINED and EXPAND_AS_PREDEFINED tags.
575
EXPAND_ONLY_PREDEF = NO
577
# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
578
# in the INCLUDE_PATH (see below) will be search if a #include is found.
580
SEARCH_INCLUDES = YES
582
# The INCLUDE_PATH tag can be used to specify one or more directories that
583
# contain include files that are not input files but should be processed by
586
INCLUDE_PATH = ../../generic/extern
588
# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
589
# patterns (like *.h and *.hpp) to filter out the header-files in the
590
# directories. If left blank, the patterns specified with FILE_PATTERNS will
593
INCLUDE_FILE_PATTERNS =
595
# The PREDEFINED tag can be used to specify one or more macro names that
596
# are defined before the preprocessor is started (similar to the -D option of
597
# gcc). The argument of the tag is a list of macros of the form: name
598
# or name=definition (no spaces). If the definition and the = are
599
# omitted =1 is assumed.
603
# If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then
604
# this tag can be used to specify a list of macro names that should be expanded.
605
# The macro definition that is found in the sources will be used.
606
# Use the PREDEFINED tag if you want to use a different macro definition.
610
#---------------------------------------------------------------------------
611
# Configuration::addtions related to external references
612
#---------------------------------------------------------------------------
614
# The TAGFILES tag can be used to specify one or more tagfiles.
618
# When a file name is specified after GENERATE_TAGFILE, doxygen will create
619
# a tag file that is based on the input files it reads.
623
# If the ALLEXTERNALS tag is set to YES all external classes will be listed
624
# in the class index. If set to NO only the inherited external classes
629
# The PERL_PATH should be the absolute path and name of the perl script
630
# interpreter (i.e. the result of `which perl').
632
PERL_PATH = /usr/bin/perl
634
#---------------------------------------------------------------------------
635
# Configuration options related to the dot tool
636
#---------------------------------------------------------------------------
638
# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
639
# available from the path. This tool is part of Graphviz, a graph visualization
640
# toolkit from AT&T and Lucent Bell Labs. The other options in this section
641
# have no effect if this option is set to NO (the default)
645
# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
646
# will generate a graph for each documented class showing the direct and
647
# indirect inheritance relations. Setting this tag to YES will force the
648
# the CLASS_DIAGRAMS tag to NO.
652
# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
653
# will generate a graph for each documented class showing the direct and
654
# indirect implementation dependencies (inheritance, containment, and
655
# class references variables) of the class with other documented classes.
657
COLLABORATION_GRAPH = YES
659
# If the ENABLE_PREPROCESSING, INCLUDE_GRAPH, and HAVE_DOT tags are set to
660
# YES then doxygen will generate a graph for each documented file showing
661
# the direct and indirect include dependencies of the file with other
666
# If the ENABLE_PREPROCESSING, INCLUDED_BY_GRAPH, and HAVE_DOT tags are set to
667
# YES then doxygen will generate a graph for each documented header file showing
668
# the documented files that directly or indirectly include this file
670
INCLUDED_BY_GRAPH = YES
672
# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
673
# will graphical hierarchy of all classes instead of a textual one.
675
GRAPHICAL_HIERARCHY = YES
677
# The tag DOT_PATH can be used to specify the path where the dot tool can be
678
# found. If left blank, it is assumed the dot tool can be found on the path.
682
# The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
683
# (in pixels) of the graphs generated by dot. If a graph becomes larger than
684
# this value, doxygen will try to truncate the graph, so that it fits within
685
# the specified constraint. Beware that most browsers cannot cope with very
688
MAX_DOT_GRAPH_WIDTH = 1024
690
# The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
691
# (in pixels) of the graphs generated by dot. If a graph becomes larger than
692
# this value, doxygen will try to truncate the graph, so that it fits within
693
# the specified constraint. Beware that most browsers cannot cope with very
696
MAX_DOT_GRAPH_HEIGHT = 1024
698
# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
699
# generate a legend page explaining the meaning of the various boxes and
700
# arrows in the dot generated graphs.
702
GENERATE_LEGEND = YES
704
#---------------------------------------------------------------------------
705
# Configuration::addtions related to the search engine
706
#---------------------------------------------------------------------------
708
# The SEARCHENGINE tag specifies whether or not a search engine should be
709
# used. If set to NO the values of all tags below this one will be ignored.
713
# The CGI_NAME tag should be the name of the CGI script that
714
# starts the search engine (doxysearch) with the correct parameters.
715
# A script with this name will be generated by doxygen.
717
CGI_NAME = search.cgi
719
# The CGI_URL tag should be the absolute URL to the directory where the
720
# cgi binaries are located. See the documentation of your http daemon for
725
# The DOC_URL tag should be the absolute URL to the directory where the
726
# documentation is located. If left blank the absolute path to the
727
# documentation, with file:// prepended to it, will be used.
731
# The DOC_ABSPATH tag should be the absolute path to the directory where the
732
# documentation is located. If left blank the directory on the local machine
737
# The BIN_ABSPATH tag must point to the directory where the doxysearch binary
740
BIN_ABSPATH = c:\program files\doxygen\bin
742
# The EXT_DOC_PATHS tag can be used to specify one or more paths to
743
# documentation generated for other projects. This allows doxysearch to search
744
# the documentation for these projects as well.
added
removed
intern/action/doc/Doxyfile
