]>
Commit | Line | Data |
---|---|---|
ffe94f83 | 1 | # Doxyfile 1.2.12 |
e03f70b3 | 2 | |
ffe94f83 PE |
3 | # This file describes the settings to be used by the documentation system |
4 | # doxygen (www.doxygen.org) for a project | |
e03f70b3 PE |
5 | # |
6 | # All text after a hash (#) is considered a comment and will be ignored | |
7 | # The format is: | |
8 | # TAG = value [value, ...] | |
9 | # For lists items can also be appended using: | |
10 | # TAG += value [value, ...] | |
11 | # Values that contain spaces should be placed between quotes (" ") | |
12 | ||
ffe94f83 PE |
13 | ### When doxygen is run, the current directory is the top of the |
14 | ### libstdc++-v3 build directory. Keep this in mind while writing | |
15 | ### relative-path directories. | |
16 | ### | |
17 | ### Currently this is not really run through autoconf; it just looks that way. | |
18 | ||
fb75f5eb | 19 | |
e03f70b3 PE |
20 | #--------------------------------------------------------------------------- |
21 | # General configuration options | |
22 | #--------------------------------------------------------------------------- | |
23 | ||
24 | # The PROJECT_NAME tag is a single word (or a sequence of words surrounded | |
ffe94f83 | 25 | # by quotes) that should identify the project. |
e03f70b3 | 26 | |
462b7396 | 27 | PROJECT_NAME = "libstdc++-v3 Source" |
e03f70b3 PE |
28 | |
29 | # The PROJECT_NUMBER tag can be used to enter a project or revision number. | |
30 | # This could be handy for archiving the generated documentation or | |
31 | # if some version control system is used. | |
32 | ||
3f3942e8 | 33 | PROJECT_NUMBER = |
e03f70b3 PE |
34 | |
35 | # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) | |
36 | # base path where the generated documentation will be put. | |
37 | # If a relative path is entered, it will be relative to the location | |
38 | # where doxygen was started. If left blank the current directory will be used. | |
ffe94f83 | 39 | |
e03f70b3 PE |
40 | OUTPUT_DIRECTORY = @outdir@ |
41 | ||
42 | # The OUTPUT_LANGUAGE tag is used to specify the language in which all | |
43 | # documentation generated by doxygen is written. Doxygen will use this | |
44 | # information to generate all constant output in the proper language. | |
45 | # The default language is English, other supported languages are: | |
ffe94f83 PE |
46 | # Brazilian, Chinese, Croatian, Czech, Danish, Dutch, Finnish, French, |
47 | # German, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, | |
48 | # Portuguese, Romanian, Russian, Slovak, Slovene, Spanish and Swedish. | |
e03f70b3 PE |
49 | |
50 | OUTPUT_LANGUAGE = English | |
51 | ||
52 | # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in | |
53 | # documentation are documented, even if no documentation was available. | |
54 | # Private class members and static file members will be hidden unless | |
ffe94f83 | 55 | # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES |
e03f70b3 | 56 | |
b0037845 | 57 | EXTRACT_ALL = NO |
e03f70b3 PE |
58 | |
59 | # If the EXTRACT_PRIVATE tag is set to YES all private members of a class | |
ffe94f83 | 60 | # will be included in the documentation. |
e03f70b3 | 61 | |
3f3942e8 | 62 | EXTRACT_PRIVATE = YES |
e03f70b3 PE |
63 | |
64 | # If the EXTRACT_STATIC tag is set to YES all static members of a file | |
ffe94f83 | 65 | # will be included in the documentation. |
e03f70b3 PE |
66 | |
67 | EXTRACT_STATIC = YES | |
68 | ||
69 | # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all | |
70 | # undocumented members of documented classes, files or namespaces. | |
71 | # If set to NO (the default) these members will be included in the | |
72 | # various overviews, but no documentation section is generated. | |
ffe94f83 | 73 | # This option has no effect if EXTRACT_ALL is enabled. |
e03f70b3 PE |
74 | |
75 | HIDE_UNDOC_MEMBERS = YES | |
76 | ||
77 | # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all | |
78 | # undocumented classes that are normally visible in the class hierarchy. | |
79 | # If set to NO (the default) these class will be included in the various | |
ffe94f83 | 80 | # overviews. This option has no effect if EXTRACT_ALL is enabled. |
e03f70b3 PE |
81 | |
82 | HIDE_UNDOC_CLASSES = YES | |
83 | ||
84 | # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will | |
85 | # include brief member descriptions after the members that are listed in | |
86 | # the file and class documentation (similar to JavaDoc). | |
ffe94f83 | 87 | # Set to NO to disable this. |
e03f70b3 | 88 | |
fb75f5eb | 89 | BRIEF_MEMBER_DESC = YES |
e03f70b3 PE |
90 | |
91 | # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend | |
92 | # the brief description of a member or function before the detailed description. | |
93 | # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the | |
ffe94f83 | 94 | # brief descriptions will be completely suppressed. |
e03f70b3 | 95 | |
fb75f5eb | 96 | REPEAT_BRIEF = YES |
e03f70b3 PE |
97 | |
98 | # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then | |
99 | # Doxygen will generate a detailed section even if there is only a brief | |
ffe94f83 | 100 | # description. |
e03f70b3 | 101 | |
ffe94f83 | 102 | ALWAYS_DETAILED_SEC = YES |
e03f70b3 PE |
103 | |
104 | # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full | |
105 | # path before files name in the file list and in the header files. If set | |
ffe94f83 | 106 | # to NO the shortest path that makes the file name unique will be used. |
e03f70b3 PE |
107 | |
108 | FULL_PATH_NAMES = NO | |
109 | ||
110 | # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag | |
111 | # can be used to strip a user defined part of the path. Stripping is | |
112 | # only done if one of the specified strings matches the left-hand part of | |
113 | # the path. It is allowed to use relative paths in the argument list. | |
114 | ||
115 | STRIP_FROM_PATH = | |
116 | ||
117 | # The INTERNAL_DOCS tag determines if documentation | |
118 | # that is typed after a \internal command is included. If the tag is set | |
119 | # to NO (the default) then the documentation will be excluded. | |
ffe94f83 | 120 | # Set it to YES to include the internal documentation. |
e03f70b3 PE |
121 | |
122 | INTERNAL_DOCS = NO | |
123 | ||
e03f70b3 PE |
124 | # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct |
125 | # doxygen to hide any special comment blocks from generated source code | |
ffe94f83 | 126 | # fragments. Normal C and C++ comments will always remain visible. |
e03f70b3 PE |
127 | |
128 | STRIP_CODE_COMMENTS = YES | |
129 | ||
130 | # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate | |
131 | # file names in lower case letters. If set to YES upper case letters are also | |
132 | # allowed. This is useful if you have classes or files whose names only differ | |
133 | # in case and if your file system supports case sensitive file names. Windows | |
763b9879 | 134 | # users are adviced to set this option to NO. |
e03f70b3 | 135 | |
3f3942e8 | 136 | CASE_SENSE_NAMES = NO |
e03f70b3 | 137 | |
ffe94f83 PE |
138 | # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter |
139 | # (but less readable) file names. This can be useful is your file systems | |
140 | # doesn't support long names like on DOS, Mac, or CD-ROM. | |
141 | ||
142 | SHORT_NAMES = NO | |
143 | ||
e03f70b3 PE |
144 | # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen |
145 | # will show members with their full class and namespace scopes in the | |
ffe94f83 | 146 | # documentation. If set to YES the scope will be hidden. |
e03f70b3 | 147 | |
3f3942e8 | 148 | HIDE_SCOPE_NAMES = NO |
e03f70b3 PE |
149 | |
150 | # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen | |
151 | # will generate a verbatim copy of the header file for each class for | |
ffe94f83 | 152 | # which an include is specified. Set to NO to disable this. |
e03f70b3 PE |
153 | |
154 | VERBATIM_HEADERS = NO | |
155 | ||
156 | # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen | |
157 | # will put list of the files that are included by a file in the documentation | |
ffe94f83 | 158 | # of that file. |
e03f70b3 | 159 | |
3f3942e8 | 160 | SHOW_INCLUDE_FILES = YES |
e03f70b3 PE |
161 | |
162 | # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen | |
163 | # will interpret the first line (until the first dot) of a JavaDoc-style | |
164 | # comment as the brief description. If set to NO, the JavaDoc | |
165 | # comments will behave just like the Qt-style comments (thus requiring an | |
ffe94f83 | 166 | # explict @brief command for a brief description. |
e03f70b3 PE |
167 | |
168 | JAVADOC_AUTOBRIEF = NO | |
169 | ||
170 | # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented | |
171 | # member inherits the documentation from any documented member that it | |
ffe94f83 | 172 | # reimplements. |
e03f70b3 PE |
173 | |
174 | INHERIT_DOCS = YES | |
175 | ||
176 | # If the INLINE_INFO tag is set to YES (the default) then a tag [inline] | |
ffe94f83 | 177 | # is inserted in the documentation for inline members. |
e03f70b3 PE |
178 | |
179 | INLINE_INFO = YES | |
180 | ||
181 | # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen | |
182 | # will sort the (detailed) documentation of file and class members | |
183 | # alphabetically by member name. If set to NO the members will appear in | |
ffe94f83 | 184 | # declaration order. |
e03f70b3 | 185 | |
7f2e0dff | 186 | SORT_MEMBER_DOCS = NO |
e03f70b3 PE |
187 | |
188 | # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC | |
189 | # tag is set to YES, then doxygen will reuse the documentation of the first | |
190 | # member in the group (if any) for the other members of the group. By default | |
191 | # all members of a group must be documented explicitly. | |
192 | ||
669f7a03 | 193 | DISTRIBUTE_GROUP_DOC = YES |
e03f70b3 PE |
194 | |
195 | # The TAB_SIZE tag can be used to set the number of spaces in a tab. | |
ffe94f83 | 196 | # Doxygen uses this value to replace tabs by spaces in code fragments. |
e03f70b3 PE |
197 | |
198 | TAB_SIZE = 4 | |
199 | ||
e03f70b3 PE |
200 | # The GENERATE_TODOLIST tag can be used to enable (YES) or |
201 | # disable (NO) the todo list. This list is created by putting \todo | |
202 | # commands in the documentation. | |
203 | ||
8f94053d | 204 | GENERATE_TODOLIST = YES |
e03f70b3 PE |
205 | |
206 | # The GENERATE_TESTLIST tag can be used to enable (YES) or | |
207 | # disable (NO) the test list. This list is created by putting \test | |
208 | # commands in the documentation. | |
209 | ||
210 | GENERATE_TESTLIST = NO | |
211 | ||
fb75f5eb PE |
212 | # The GENERATE_BUGLIST tag can be used to enable (YES) or |
213 | # disable (NO) the bug list. This list is created by putting \bug | |
214 | # commands in the documentation. | |
215 | ||
216 | GENERATE_BUGLIST = YES | |
217 | ||
e03f70b3 PE |
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:". | |
ffe94f83 PE |
223 | # You can put \n's in the value part of an alias to insert newlines. |
224 | ||
04b7c941 | 225 | ALIASES = "doctodo=@todo\nDoc me! See docs/doxygen/TODO and http://gcc.gnu.org/ml/libstdc++/2002-02/msg00003.html for more." |
e03f70b3 | 226 | |
ffe94f83 PE |
227 | # The ENABLED_SECTIONS tag can be used to enable conditional |
228 | # documentation sections, marked by \if sectionname ... \endif. | |
229 | ||
230 | ENABLED_SECTIONS = @enabled_sections@ | |
fb75f5eb PE |
231 | |
232 | # The MAX_INITIALIZER_LINES tag determines the maximum number of lines | |
233 | # the initial value of a variable or define consist of for it to appear in | |
234 | # the documentation. If the initializer consists of more lines than specified | |
235 | # here it will be hidden. Use a value of 0 to hide initializers completely. | |
236 | # The appearance of the initializer of individual variables and defines in the | |
237 | # documentation can be controlled using \showinitializer or \hideinitializer | |
ffe94f83 | 238 | # command in the documentation regardless of this setting. |
fb75f5eb PE |
239 | |
240 | MAX_INITIALIZER_LINES = 30 | |
241 | ||
ffe94f83 | 242 | # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources |
fb75f5eb PE |
243 | # only. Doxygen will then generate output that is more tailored for C. |
244 | # For instance some of the names that are used will be different. The list | |
ffe94f83 | 245 | # of all members will be omitted, etc. |
fb75f5eb PE |
246 | |
247 | OPTIMIZE_OUTPUT_FOR_C = NO | |
248 | ||
249 | # Set the SHOW_USED_FILES tag to NO to disable the list of files generated | |
250 | # at the bottom of the documentation of classes and structs. If set to YES the | |
ffe94f83 | 251 | # list will mention the files that were used to generate the documentation. |
fb75f5eb PE |
252 | |
253 | SHOW_USED_FILES = YES | |
e03f70b3 PE |
254 | |
255 | #--------------------------------------------------------------------------- | |
256 | # configuration options related to warning and progress messages | |
257 | #--------------------------------------------------------------------------- | |
258 | ||
259 | # The QUIET tag can be used to turn on/off the messages that are generated | |
ffe94f83 | 260 | # by doxygen. Possible values are YES and NO. If left blank NO is used. |
e03f70b3 PE |
261 | |
262 | QUIET = YES | |
263 | ||
264 | # The WARNINGS tag can be used to turn on/off the warning messages that are | |
265 | # generated by doxygen. Possible values are YES and NO. If left blank | |
ffe94f83 | 266 | # NO is used. |
e03f70b3 | 267 | |
e03f70b3 PE |
268 | WARNINGS = NO |
269 | ||
270 | # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings | |
271 | # for undocumented members. If EXTRACT_ALL is set to YES then this flag will | |
ffe94f83 | 272 | # automatically be disabled. |
e03f70b3 | 273 | |
d4c6e01f | 274 | WARN_IF_UNDOCUMENTED = NO |
e03f70b3 PE |
275 | |
276 | # The WARN_FORMAT tag determines the format of the warning messages that | |
277 | # doxygen can produce. The string should contain the $file, $line, and $text | |
278 | # tags, which will be replaced by the file and line number from which the | |
ffe94f83 | 279 | # warning originated and the warning text. |
e03f70b3 PE |
280 | |
281 | WARN_FORMAT = "$file:$line: $text" | |
282 | ||
283 | # The WARN_LOGFILE tag can be used to specify a file to which warning | |
284 | # and error messages should be written. If left blank the output is written | |
ffe94f83 | 285 | # to stderr. |
e03f70b3 | 286 | |
fb75f5eb | 287 | WARN_LOGFILE = |
e03f70b3 PE |
288 | |
289 | #--------------------------------------------------------------------------- | |
290 | # configuration options related to the input files | |
291 | #--------------------------------------------------------------------------- | |
292 | ||
ffe94f83 | 293 | # The INPUT tag can be used to specify the files and/or directories that contain |
e03f70b3 PE |
294 | # documented source files. You may enter file names like "myfile.cpp" or |
295 | # directories like "/usr/src/myproject". Separate the files or directories | |
ffe94f83 PE |
296 | # with spaces. |
297 | ||
fd58f127 | 298 | INPUT = @srcdir@/docs/doxygen/doxygroups.cc \ |
ffe94f83 PE |
299 | @srcdir@/src \ |
300 | @srcdir@/libsupc++/exception \ | |
301 | @srcdir@/libsupc++/new \ | |
302 | @srcdir@/libsupc++/typeinfo \ | |
303 | include | |
304 | ||
305 | ||
e03f70b3 PE |
306 | |
307 | # If the value of the INPUT tag contains directories, you can use the | |
308 | # FILE_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 | |
ffe94f83 PE |
310 | # blank file matching one of the following patterns are included: |
311 | # *.c *.cc *.cxx *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp | |
312 | # *.h++ *.idl | |
e03f70b3 | 313 | |
ffe94f83 | 314 | FILE_PATTERNS = * |
e03f70b3 PE |
315 | |
316 | # The RECURSIVE tag can be used to turn specify whether or not subdirectories | |
317 | # should be searched for input files as well. Possible values are YES and NO. | |
ffe94f83 | 318 | # If left blank NO is used. |
e03f70b3 PE |
319 | |
320 | RECURSIVE = YES | |
321 | ||
322 | # The EXCLUDE tag can be used to specify files and/or directories that should | |
323 | # excluded from the INPUT source files. This way you can easily exclude a | |
ffe94f83 | 324 | # subdirectory from a directory tree whose root is specified with the INPUT tag. |
fb75f5eb | 325 | |
59f801a0 | 326 | EXCLUDE = Makefile CVS |
e03f70b3 PE |
327 | |
328 | # If the value of the INPUT tag contains directories, you can use the | |
329 | # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude | |
ffe94f83 | 330 | # certain files from those directories. |
e03f70b3 | 331 | |
ffe94f83 PE |
332 | EXCLUDE_PATTERNS = CVS \ |
333 | stamp-* | |
e03f70b3 PE |
334 | |
335 | # The EXAMPLE_PATH tag can be used to specify one or more files or | |
336 | # directories that contain example code fragments that are included (see | |
ffe94f83 | 337 | # the \include command). |
e03f70b3 PE |
338 | |
339 | EXAMPLE_PATH = | |
340 | ||
341 | # If the value of the EXAMPLE_PATH tag contains directories, you can use the | |
342 | # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp | |
343 | # and *.h) to filter out the source-files in the directories. If left | |
ffe94f83 | 344 | # blank all files are included. |
e03f70b3 PE |
345 | |
346 | EXAMPLE_PATTERNS = | |
347 | ||
ffe94f83 PE |
348 | # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be |
349 | # searched for input files to be used with the \include or \dontinclude | |
350 | # commands irrespective of the value of the RECURSIVE tag. | |
351 | # Possible values are YES and NO. If left blank NO is used. | |
352 | ||
353 | EXAMPLE_RECURSIVE = NO | |
354 | ||
e03f70b3 PE |
355 | # The IMAGE_PATH tag can be used to specify one or more files or |
356 | # directories that contain image that are included in the documentation (see | |
ffe94f83 | 357 | # the \image command). |
e03f70b3 PE |
358 | |
359 | IMAGE_PATH = | |
360 | ||
361 | # The INPUT_FILTER tag can be used to specify a program that doxygen should | |
362 | # invoke to filter for each input file. Doxygen will invoke the filter program | |
363 | # by executing (via popen()) the command <filter> <input-file>, where <filter> | |
364 | # is the value of the INPUT_FILTER tag, and <input-file> is the name of an | |
365 | # input file. Doxygen will then use the output that the filter program writes | |
ffe94f83 | 366 | # to standard output. |
e03f70b3 PE |
367 | |
368 | INPUT_FILTER = | |
369 | ||
370 | # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using | |
371 | # INPUT_FILTER) will be used to filter the input files when producing source | |
ffe94f83 | 372 | # files to browse. |
e03f70b3 | 373 | |
fb75f5eb | 374 | FILTER_SOURCE_FILES = NO |
e03f70b3 | 375 | |
ffe94f83 PE |
376 | #--------------------------------------------------------------------------- |
377 | # configuration options related to source browsing | |
378 | #--------------------------------------------------------------------------- | |
379 | ||
380 | # If the SOURCE_BROWSER tag is set to YES then a list of source files will | |
381 | # be generated. Documented entities will be cross-referenced with these sources. | |
382 | ||
383 | SOURCE_BROWSER = YES | |
384 | ||
385 | # Setting the INLINE_SOURCES tag to YES will include the body | |
386 | # of functions and classes directly in the documentation. | |
387 | ||
388 | INLINE_SOURCES = NO | |
389 | ||
390 | # If the REFERENCED_BY_RELATION tag is set to YES (the default) | |
391 | # then for each documented function all documented | |
392 | # functions referencing it will be listed. | |
393 | ||
394 | REFERENCED_BY_RELATION = YES | |
395 | ||
396 | # If the REFERENCES_RELATION tag is set to YES (the default) | |
397 | # then for each documented function all documented entities | |
398 | # called/used by that function will be listed. | |
399 | ||
400 | REFERENCES_RELATION = YES | |
401 | ||
e03f70b3 PE |
402 | #--------------------------------------------------------------------------- |
403 | # configuration options related to the alphabetical class index | |
404 | #--------------------------------------------------------------------------- | |
405 | ||
406 | # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index | |
407 | # of all compounds will be generated. Enable this if the project | |
ffe94f83 | 408 | # contains a lot of classes, structs, unions or interfaces. |
e03f70b3 PE |
409 | |
410 | ALPHABETICAL_INDEX = YES | |
411 | ||
412 | # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then | |
413 | # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns | |
ffe94f83 | 414 | # in which this list will be split (can be a number in the range [1..20]) |
e03f70b3 PE |
415 | |
416 | COLS_IN_ALPHA_INDEX = 5 | |
417 | ||
418 | # In case all classes in a project start with a common prefix, all | |
419 | # classes will be put under the same header in the alphabetical index. | |
420 | # The IGNORE_PREFIX tag can be used to specify one or more prefixes that | |
ffe94f83 | 421 | # should be ignored while generating the index headers. |
e03f70b3 PE |
422 | |
423 | IGNORE_PREFIX = | |
424 | ||
425 | #--------------------------------------------------------------------------- | |
426 | # configuration options related to the HTML output | |
427 | #--------------------------------------------------------------------------- | |
428 | ||
429 | # If the GENERATE_HTML tag is set to YES (the default) Doxygen will | |
ffe94f83 | 430 | # generate HTML output. |
e03f70b3 | 431 | |
ffe94f83 | 432 | GENERATE_HTML = @do_html@ |
e03f70b3 PE |
433 | |
434 | # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. | |
435 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
ffe94f83 | 436 | # put in front of it. If left blank `html' will be used as the default path. |
e03f70b3 | 437 | |
ffe94f83 | 438 | HTML_OUTPUT = @html_output_dir@ |
e03f70b3 PE |
439 | |
440 | # The HTML_HEADER tag can be used to specify a personal HTML header for | |
441 | # each generated HTML page. If it is left blank doxygen will generate a | |
442 | # standard header. | |
443 | ||
444 | HTML_HEADER = | |
445 | ||
446 | # The HTML_FOOTER tag can be used to specify a personal HTML footer for | |
447 | # each generated HTML page. If it is left blank doxygen will generate a | |
448 | # standard footer. | |
449 | ||
450 | HTML_FOOTER = | |
451 | ||
452 | # The HTML_STYLESHEET tag can be used to specify a user defined cascading | |
453 | # style sheet that is used by each HTML page. It can be used to | |
454 | # fine-tune the look of the HTML output. If the tag is left blank doxygen | |
ffe94f83 | 455 | # will generate a default style sheet |
e03f70b3 | 456 | |
ffe94f83 | 457 | HTML_STYLESHEET = @srcdir@/docs/doxygen/style.css |
e03f70b3 PE |
458 | |
459 | # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes, | |
460 | # files or namespaces will be aligned in HTML using tables. If set to | |
ffe94f83 | 461 | # NO a bullet list will be used. |
e03f70b3 PE |
462 | |
463 | HTML_ALIGN_MEMBERS = YES | |
464 | ||
465 | # If the GENERATE_HTMLHELP tag is set to YES, additional index files | |
466 | # will be generated that can be used as input for tools like the | |
467 | # Microsoft HTML help workshop to generate a compressed HTML help file (.chm) | |
ffe94f83 | 468 | # of the generated HTML documentation. |
e03f70b3 PE |
469 | |
470 | GENERATE_HTMLHELP = NO | |
471 | ||
fb75f5eb PE |
472 | # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag |
473 | # controls if a separate .chi index file is generated (YES) or that | |
474 | # it should be included in the master .chm file (NO). | |
475 | ||
476 | GENERATE_CHI = NO | |
477 | ||
478 | # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag | |
479 | # controls whether a binary table of contents is generated (YES) or a | |
480 | # normal table of contents (NO) in the .chm file. | |
481 | ||
482 | BINARY_TOC = NO | |
483 | ||
ffe94f83 PE |
484 | # The TOC_EXPAND flag can be set to YES to add extra items for group members |
485 | # to the contents of the Html help documentation and to the tree view. | |
fb75f5eb PE |
486 | |
487 | TOC_EXPAND = NO | |
488 | ||
e03f70b3 PE |
489 | # The DISABLE_INDEX tag can be used to turn on/off the condensed index at |
490 | # top of each HTML page. The value NO (the default) enables the index and | |
ffe94f83 | 491 | # the value YES disables it. |
e03f70b3 | 492 | |
2f9d51b8 | 493 | DISABLE_INDEX = YES |
e03f70b3 PE |
494 | |
495 | # This tag can be used to set the number of enum values (range [1..20]) | |
ffe94f83 | 496 | # that doxygen will group on one line in the generated HTML documentation. |
e03f70b3 | 497 | |
fb75f5eb | 498 | ENUM_VALUES_PER_LINE = 4 |
e03f70b3 | 499 | |
fb75f5eb | 500 | # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be |
e03f70b3 PE |
501 | # generated containing a tree-like index structure (just like the one that |
502 | # is generated for HTML Help). For this to work a browser that supports | |
ffe94f83 PE |
503 | # JavaScript and frames is required (for instance Mozilla, Netscape 4.0+, |
504 | # or Internet explorer 4.0+). Note that for large projects the tree generation | |
505 | # can take a very long time. In such cases it is better to disable this feature. | |
506 | # Windows users are probably better off using the HTML help feature. | |
e03f70b3 | 507 | |
3f3942e8 | 508 | GENERATE_TREEVIEW = NO |
e03f70b3 PE |
509 | |
510 | # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be | |
511 | # used to set the initial width (in pixels) of the frame in which the tree | |
ffe94f83 | 512 | # is shown. |
e03f70b3 | 513 | |
fb75f5eb | 514 | TREEVIEW_WIDTH = 250 |
e03f70b3 PE |
515 | |
516 | #--------------------------------------------------------------------------- | |
517 | # configuration options related to the LaTeX output | |
518 | #--------------------------------------------------------------------------- | |
519 | ||
520 | # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will | |
ffe94f83 | 521 | # generate Latex output. |
e03f70b3 PE |
522 | |
523 | GENERATE_LATEX = NO | |
524 | ||
525 | # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. | |
526 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
ffe94f83 | 527 | # put in front of it. If left blank `latex' will be used as the default path. |
e03f70b3 PE |
528 | |
529 | LATEX_OUTPUT = latex | |
530 | ||
531 | # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact | |
532 | # LaTeX documents. This may be useful for small projects and may help to | |
ffe94f83 | 533 | # save some trees in general. |
e03f70b3 PE |
534 | |
535 | COMPACT_LATEX = NO | |
536 | ||
537 | # The PAPER_TYPE tag can be used to set the paper type that is used | |
538 | # by the printer. Possible values are: a4, a4wide, letter, legal and | |
ffe94f83 | 539 | # executive. If left blank a4wide will be used. |
e03f70b3 PE |
540 | |
541 | PAPER_TYPE = letter | |
542 | ||
543 | # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX | |
ffe94f83 | 544 | # packages that should be included in the LaTeX output. |
e03f70b3 PE |
545 | |
546 | EXTRA_PACKAGES = | |
547 | ||
548 | # The LATEX_HEADER tag can be used to specify a personal LaTeX header for | |
549 | # the generated latex document. The header should contain everything until | |
550 | # the first chapter. If it is left blank doxygen will generate a | |
ffe94f83 | 551 | # standard header. Notice: only use this tag if you know what you are doing! |
e03f70b3 PE |
552 | |
553 | LATEX_HEADER = | |
554 | ||
555 | # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated | |
556 | # is prepared for conversion to pdf (using ps2pdf). The pdf file will | |
557 | # contain links (just like the HTML output) instead of page references | |
ffe94f83 | 558 | # This makes the output suitable for online browsing using a pdf viewer. |
e03f70b3 PE |
559 | |
560 | PDF_HYPERLINKS = NO | |
561 | ||
562 | # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of | |
563 | # plain latex in the generated Makefile. Set this option to YES to get a | |
ffe94f83 | 564 | # higher quality PDF documentation. |
e03f70b3 PE |
565 | |
566 | USE_PDFLATEX = NO | |
567 | ||
568 | # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. | |
569 | # command to the generated LaTeX files. This will instruct LaTeX to keep | |
570 | # running if errors occur, instead of asking the user for help. | |
ffe94f83 | 571 | # This option is also used when generating formulas in HTML. |
e03f70b3 PE |
572 | |
573 | LATEX_BATCHMODE = NO | |
574 | ||
575 | #--------------------------------------------------------------------------- | |
576 | # configuration options related to the RTF output | |
577 | #--------------------------------------------------------------------------- | |
578 | ||
579 | # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output | |
580 | # The RTF output is optimised for Word 97 and may not look very pretty with | |
581 | # other RTF readers or editors. | |
582 | ||
583 | GENERATE_RTF = NO | |
584 | ||
585 | # The RTF_OUTPUT tag is used to specify where the RTF docs will be put. | |
586 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
ffe94f83 | 587 | # put in front of it. If left blank `rtf' will be used as the default path. |
e03f70b3 PE |
588 | |
589 | RTF_OUTPUT = rtf | |
590 | ||
591 | # If the COMPACT_RTF tag is set to YES Doxygen generates more compact | |
592 | # RTF documents. This may be useful for small projects and may help to | |
ffe94f83 | 593 | # save some trees in general. |
e03f70b3 PE |
594 | |
595 | COMPACT_RTF = NO | |
596 | ||
597 | # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated | |
598 | # will contain hyperlink fields. The RTF file will | |
599 | # contain links (just like the HTML output) instead of page references. | |
ffe94f83 | 600 | # This makes the output suitable for online browsing using WORD or other |
e03f70b3 | 601 | # programs which support those fields. |
ffe94f83 | 602 | # Note: wordpad (write) and others do not support links. |
e03f70b3 PE |
603 | |
604 | RTF_HYPERLINKS = NO | |
605 | ||
606 | # Load stylesheet definitions from file. Syntax is similar to doxygen's | |
607 | # config file, i.e. a series of assigments. You only have to provide | |
ffe94f83 | 608 | # replacements, missing definitions are set to their default value. |
e03f70b3 PE |
609 | |
610 | RTF_STYLESHEET_FILE = | |
611 | ||
ffe94f83 PE |
612 | # Set optional variables used in the generation of an rtf document. |
613 | # Syntax is similar to doxygen's config file. | |
614 | ||
615 | RTF_EXTENSIONS_FILE = | |
616 | ||
e03f70b3 PE |
617 | #--------------------------------------------------------------------------- |
618 | # configuration options related to the man page output | |
619 | #--------------------------------------------------------------------------- | |
620 | ||
621 | # If the GENERATE_MAN tag is set to YES (the default) Doxygen will | |
ffe94f83 | 622 | # generate man pages |
e03f70b3 | 623 | |
ffe94f83 | 624 | GENERATE_MAN = @do_man@ |
e03f70b3 PE |
625 | |
626 | # The MAN_OUTPUT tag is used to specify where the man pages will be put. | |
627 | # If a relative path is entered the value of OUTPUT_DIRECTORY will be | |
ffe94f83 | 628 | # put in front of it. If left blank `man' will be used as the default path. |
e03f70b3 PE |
629 | |
630 | MAN_OUTPUT = man | |
631 | ||
632 | # The MAN_EXTENSION tag determines the extension that is added to | |
ffe94f83 | 633 | # the generated man pages (default is the subroutine's section .3) |
e03f70b3 PE |
634 | |
635 | MAN_EXTENSION = .3 | |
636 | ||
ffe94f83 PE |
637 | # If the MAN_LINKS tag is set to YES and Doxygen generates man output, |
638 | # then it will generate one additional man file for each entity | |
639 | # documented in the real man page(s). These additional files | |
640 | # only source the real man page, but without them the man command | |
641 | # would be unable to find the correct page. The default is NO. | |
642 | ||
643 | MAN_LINKS = NO | |
644 | ||
645 | #--------------------------------------------------------------------------- | |
646 | # configuration options related to the XML output | |
647 | #--------------------------------------------------------------------------- | |
648 | ||
649 | # If the GENERATE_XML tag is set to YES Doxygen will | |
650 | # generate an XML file that captures the structure of | |
651 | # the code including all documentation. Note that this | |
652 | # feature is still experimental and incomplete at the | |
653 | # moment. | |
654 | ||
655 | GENERATE_XML = NO | |
656 | ||
e03f70b3 PE |
657 | #--------------------------------------------------------------------------- |
658 | # Configuration options related to the preprocessor | |
659 | #--------------------------------------------------------------------------- | |
660 | ||
661 | # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will | |
662 | # evaluate all C-preprocessor directives found in the sources and include | |
ffe94f83 | 663 | # files. |
e03f70b3 PE |
664 | |
665 | ENABLE_PREPROCESSING = YES | |
666 | ||
667 | # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro | |
668 | # names in the source code. If set to NO (the default) only conditional | |
669 | # compilation will be performed. Macro expansion can be done in a controlled | |
ffe94f83 | 670 | # way by setting EXPAND_ONLY_PREDEF to YES. |
e03f70b3 | 671 | |
4df6abc6 | 672 | MACRO_EXPANSION = YES |
e03f70b3 PE |
673 | |
674 | # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES | |
675 | # then the macro expansion is limited to the macros specified with the | |
ffe94f83 | 676 | # PREDEFINED and EXPAND_AS_PREDEFINED tags. |
e03f70b3 | 677 | |
4df6abc6 | 678 | EXPAND_ONLY_PREDEF = YES |
e03f70b3 PE |
679 | |
680 | # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files | |
ffe94f83 | 681 | # in the INCLUDE_PATH (see below) will be search if a #include is found. |
e03f70b3 PE |
682 | |
683 | SEARCH_INCLUDES = YES | |
684 | ||
685 | # The INCLUDE_PATH tag can be used to specify one or more directories that | |
686 | # contain include files that are not input files but should be processed by | |
ffe94f83 | 687 | # the preprocessor. |
e03f70b3 PE |
688 | |
689 | INCLUDE_PATH = | |
690 | ||
691 | # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard | |
692 | # patterns (like *.h and *.hpp) to filter out the header-files in the | |
693 | # directories. If left blank, the patterns specified with FILE_PATTERNS will | |
ffe94f83 | 694 | # be used. |
e03f70b3 PE |
695 | |
696 | INCLUDE_FILE_PATTERNS = | |
697 | ||
698 | # The PREDEFINED tag can be used to specify one or more macro names that | |
699 | # are defined before the preprocessor is started (similar to the -D option of | |
700 | # gcc). The argument of the tag is a list of macros of the form: name | |
701 | # or name=definition (no spaces). If the definition and the = are | |
ffe94f83 | 702 | # omitted =1 is assumed. |
e03f70b3 | 703 | |
4df6abc6 PE |
704 | ### The deprecated functions are clearly marked as such in the code, but |
705 | ### the DEPRECATED macro must be defined for that code to be seen by doxygen. | |
706 | ### The class_requires macros are kludges because SKIP_FUNCTION_MACROS is | |
707 | ### completely broken, and the presence of the macros confuses the parser. | |
708 | ||
709 | PREDEFINED = _GLIBCPP_DEPRECATED \ | |
710 | __glibcpp_class_requires="//" \ | |
711 | __glibcpp_class_requires2="//" \ | |
712 | __glibcpp_class_requires3="//" \ | |
713 | __glibcpp_class_requires4="//" | |
e03f70b3 PE |
714 | |
715 | # If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then | |
4df6abc6 | 716 | # this tag can be used to specify a list of macro names that should be expanded. |
e03f70b3 | 717 | # The macro definition that is found in the sources will be used. |
ffe94f83 | 718 | # Use the PREDEFINED tag if you want to use a different macro definition. |
e03f70b3 PE |
719 | |
720 | EXPAND_AS_DEFINED = | |
721 | ||
ffe94f83 PE |
722 | # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then |
723 | # doxygen's preprocessor will remove all function-like macros that are alone | |
724 | # on a line and do not end with a semicolon. Such function macros are typically | |
725 | # used for boiler-plate code, and will confuse the parser if not removed. | |
726 | ||
727 | SKIP_FUNCTION_MACROS = YES | |
728 | ||
e03f70b3 PE |
729 | #--------------------------------------------------------------------------- |
730 | # Configuration::addtions related to external references | |
731 | #--------------------------------------------------------------------------- | |
732 | ||
ffe94f83 | 733 | # The TAGFILES tag can be used to specify one or more tagfiles. |
e03f70b3 | 734 | |
fb75f5eb | 735 | TAGFILES = |
e03f70b3 PE |
736 | |
737 | # When a file name is specified after GENERATE_TAGFILE, doxygen will create | |
ffe94f83 | 738 | # a tag file that is based on the input files it reads. |
e03f70b3 PE |
739 | |
740 | GENERATE_TAGFILE = | |
741 | ||
742 | # If the ALLEXTERNALS tag is set to YES all external classes will be listed | |
743 | # in the class index. If set to NO only the inherited external classes | |
ffe94f83 | 744 | # will be listed. |
e03f70b3 PE |
745 | |
746 | ALLEXTERNALS = YES | |
747 | ||
748 | # The PERL_PATH should be the absolute path and name of the perl script | |
ffe94f83 | 749 | # interpreter (i.e. the result of `which perl'). |
e03f70b3 PE |
750 | |
751 | PERL_PATH = /usr/bin/perl | |
752 | ||
753 | #--------------------------------------------------------------------------- | |
754 | # Configuration options related to the dot tool | |
755 | #--------------------------------------------------------------------------- | |
756 | ||
ffe94f83 PE |
757 | # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will |
758 | # generate a inheritance diagram (in Html, RTF and LaTeX) for classes with base or | |
759 | # super classes. Setting the tag to NO turns the diagrams off. Note that this | |
760 | # option is superceded by the HAVE_DOT option below. This is only a fallback. It is | |
761 | # recommended to install and use dot, since it yield more powerful graphs. | |
762 | ||
763 | CLASS_DIAGRAMS = YES | |
764 | ||
e03f70b3 PE |
765 | # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is |
766 | # available from the path. This tool is part of Graphviz, a graph visualization | |
767 | # toolkit from AT&T and Lucent Bell Labs. The other options in this section | |
ffe94f83 | 768 | # have no effect if this option is set to NO (the default) |
e03f70b3 | 769 | |
fb75f5eb | 770 | HAVE_DOT = YES |
e03f70b3 PE |
771 | |
772 | # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen | |
773 | # will generate a graph for each documented class showing the direct and | |
774 | # indirect inheritance relations. Setting this tag to YES will force the | |
775 | # the CLASS_DIAGRAMS tag to NO. | |
776 | ||
777 | CLASS_GRAPH = YES | |
778 | ||
779 | # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen | |
780 | # will generate a graph for each documented class showing the direct and | |
781 | # indirect implementation dependencies (inheritance, containment, and | |
ffe94f83 | 782 | # class references variables) of the class with other documented classes. |
e03f70b3 PE |
783 | |
784 | COLLABORATION_GRAPH = YES | |
785 | ||
ffe94f83 PE |
786 | # If set to YES, the inheritance and collaboration graphs will show the |
787 | # relations between templates and their instances. | |
788 | ||
789 | TEMPLATE_RELATIONS = YES | |
790 | ||
791 | # If set to YES, the inheritance and collaboration graphs will hide | |
792 | # inheritance and usage relations if the target is undocumented | |
793 | # or is not a class. | |
794 | ||
795 | HIDE_UNDOC_RELATIONS = YES | |
796 | ||
797 | # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT | |
798 | # tags are set to YES then doxygen will generate a graph for each documented | |
799 | # file showing the direct and indirect include dependencies of the file with | |
800 | # other documented files. | |
e03f70b3 PE |
801 | |
802 | INCLUDE_GRAPH = YES | |
803 | ||
ffe94f83 PE |
804 | # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and |
805 | # HAVE_DOT tags are set to YES then doxygen will generate a graph for each | |
806 | # documented header file showing the documented files that directly or | |
807 | # indirectly include this file. | |
e03f70b3 PE |
808 | |
809 | INCLUDED_BY_GRAPH = YES | |
810 | ||
811 | # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen | |
ffe94f83 | 812 | # will graphical hierarchy of all classes instead of a textual one. |
e03f70b3 PE |
813 | |
814 | GRAPHICAL_HIERARCHY = YES | |
815 | ||
816 | # The tag DOT_PATH can be used to specify the path where the dot tool can be | |
ffe94f83 | 817 | # found. If left blank, it is assumed the dot tool can be found on the path. |
e03f70b3 PE |
818 | |
819 | DOT_PATH = | |
820 | ||
ffe94f83 PE |
821 | # The DOTFILE_DIRS tag can be used to specify one or more directories that |
822 | # contain dot files that are included in the documentation (see the | |
823 | # \dotfile command). | |
824 | ||
825 | DOTFILE_DIRS = | |
826 | ||
e03f70b3 PE |
827 | # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width |
828 | # (in pixels) of the graphs generated by dot. If a graph becomes larger than | |
829 | # this value, doxygen will try to truncate the graph, so that it fits within | |
830 | # the specified constraint. Beware that most browsers cannot cope with very | |
ffe94f83 | 831 | # large images. |
e03f70b3 PE |
832 | |
833 | MAX_DOT_GRAPH_WIDTH = 1024 | |
834 | ||
835 | # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height | |
836 | # (in pixels) of the graphs generated by dot. If a graph becomes larger than | |
837 | # this value, doxygen will try to truncate the graph, so that it fits within | |
838 | # the specified constraint. Beware that most browsers cannot cope with very | |
ffe94f83 | 839 | # large images. |
e03f70b3 PE |
840 | |
841 | MAX_DOT_GRAPH_HEIGHT = 1024 | |
842 | ||
843 | # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will | |
844 | # generate a legend page explaining the meaning of the various boxes and | |
ffe94f83 | 845 | # arrows in the dot generated graphs. |
e03f70b3 | 846 | |
fb75f5eb PE |
847 | GENERATE_LEGEND = YES |
848 | ||
849 | # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will | |
850 | # remove the intermedate dot files that are used to generate | |
ffe94f83 | 851 | # the various graphs. |
fb75f5eb PE |
852 | |
853 | DOT_CLEANUP = YES | |
e03f70b3 PE |
854 | |
855 | #--------------------------------------------------------------------------- | |
856 | # Configuration::addtions related to the search engine | |
857 | #--------------------------------------------------------------------------- | |
858 | ||
859 | # The SEARCHENGINE tag specifies whether or not a search engine should be | |
ffe94f83 | 860 | # used. If set to NO the values of all tags below this one will be ignored. |
e03f70b3 PE |
861 | |
862 | SEARCHENGINE = NO | |
863 | ||
864 | # The CGI_NAME tag should be the name of the CGI script that | |
865 | # starts the search engine (doxysearch) with the correct parameters. | |
ffe94f83 | 866 | # A script with this name will be generated by doxygen. |
e03f70b3 PE |
867 | |
868 | CGI_NAME = search.cgi | |
869 | ||
870 | # The CGI_URL tag should be the absolute URL to the directory where the | |
871 | # cgi binaries are located. See the documentation of your http daemon for | |
ffe94f83 | 872 | # details. |
e03f70b3 PE |
873 | |
874 | CGI_URL = | |
875 | ||
876 | # The DOC_URL tag should be the absolute URL to the directory where the | |
877 | # documentation is located. If left blank the absolute path to the | |
ffe94f83 | 878 | # documentation, with file:// prepended to it, will be used. |
e03f70b3 PE |
879 | |
880 | DOC_URL = | |
881 | ||
882 | # The DOC_ABSPATH tag should be the absolute path to the directory where the | |
883 | # documentation is located. If left blank the directory on the local machine | |
ffe94f83 | 884 | # will be used. |
e03f70b3 PE |
885 | |
886 | DOC_ABSPATH = | |
887 | ||
888 | # The BIN_ABSPATH tag must point to the directory where the doxysearch binary | |
ffe94f83 | 889 | # is installed. |
e03f70b3 PE |
890 | |
891 | BIN_ABSPATH = /usr/local/bin/ | |
892 | ||
893 | # The EXT_DOC_PATHS tag can be used to specify one or more paths to | |
894 | # documentation generated for other projects. This allows doxysearch to search | |
ffe94f83 | 895 | # the documentation for these projects as well. |
e03f70b3 PE |
896 | |
897 | EXT_DOC_PATHS = | |
898 | ||
ffe94f83 | 899 | ### End of file. |
3f3942e8 | 900 |