3 # This file describes the settings to be used by the documentation system
4 # doxygen (www.doxygen.org) for a project
6 # All text after a hash (#) is considered a comment and will be ignored
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 (" ")
13 #---------------------------------------------------------------------------
14 # General configuration options
15 #---------------------------------------------------------------------------
17 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
18 # by quotes) that should identify the project.
20 PROJECT_NAME = @PACKAGE@
22 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
23 # This could be handy for archiving the generated documentation or
24 # if some version control system is used.
26 PROJECT_NUMBER = @VERSION@
28 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
29 # base path where the generated documentation will be put.
30 # If a relative path is entered, it will be relative to the location
31 # where doxygen was started. If left blank the current directory will be used.
33 OUTPUT_DIRECTORY = @WITH_APIDOCS_TARGET@
35 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
36 # documentation generated by doxygen is written. Doxygen will use this
37 # information to generate all constant output in the proper language.
38 # The default language is English, other supported languages are:
39 # Brazilian, Chinese, Croatian, Czech, Danish, Dutch, Finnish, French,
40 # German, Greek, Hungarian, Italian, Japanese, Korean, Norwegian, Polish,
41 # Portuguese, Romanian, Russian, Slovak, Slovene, Spanish and Swedish.
43 OUTPUT_LANGUAGE = English
45 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
46 # documentation are documented, even if no documentation was available.
47 # Private class members and static file members will be hidden unless
48 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
52 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
53 # will be included in the documentation.
57 # If the EXTRACT_STATIC tag is set to YES all static members of a file
58 # will be included in the documentation.
62 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
63 # defined locally in source files will be included in the documentation.
64 # If set to NO only classes defined in header files are included.
66 EXTRACT_LOCAL_CLASSES = YES
68 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
69 # undocumented members of documented classes, files or namespaces.
70 # If set to NO (the default) these members will be included in the
71 # various overviews, but no documentation section is generated.
72 # This option has no effect if EXTRACT_ALL is enabled.
74 HIDE_UNDOC_MEMBERS = NO
76 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
77 # undocumented classes that are normally visible in the class hierarchy.
78 # If set to NO (the default) these class will be included in the various
79 # overviews. This option has no effect if EXTRACT_ALL is enabled.
81 HIDE_UNDOC_CLASSES = NO
83 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
84 # include brief member descriptions after the members that are listed in
85 # the file and class documentation (similar to JavaDoc).
86 # Set to NO to disable this.
88 BRIEF_MEMBER_DESC = YES
90 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
91 # the brief description of a member or function before the detailed description.
92 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
93 # brief descriptions will be completely suppressed.
97 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
98 # Doxygen will generate a detailed section even if there is only a brief
101 ALWAYS_DETAILED_SEC = NO
103 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited
104 # members of a class in the documentation of that class as if those members were
105 # ordinary class members. Constructors, destructors and assignment operators of
106 # the base classes will not be shown.
108 INLINE_INHERITED_MEMB = NO
110 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
111 # path before files name in the file list and in the header files. If set
112 # to NO the shortest path that makes the file name unique will be used.
114 FULL_PATH_NAMES = YES
116 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
117 # can be used to strip a user defined part of the path. Stripping is
118 # only done if one of the specified strings matches the left-hand part of
119 # the path. It is allowed to use relative paths in the argument list.
121 STRIP_FROM_PATH = @top_srcdir@/
123 # The INTERNAL_DOCS tag determines if documentation
124 # that is typed after a \internal command is included. If the tag is set
125 # to NO (the default) then the documentation will be excluded.
126 # Set it to YES to include the internal documentation.
130 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
131 # doxygen to hide any special comment blocks from generated source code
132 # fragments. Normal C and C++ comments will always remain visible.
134 STRIP_CODE_COMMENTS = YES
136 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
137 # file names in lower case letters. If set to YES upper case letters are also
138 # allowed. This is useful if you have classes or files whose names only differ
139 # in case and if your file system supports case sensitive file names. Windows
140 # users are adviced to set this option to NO.
142 CASE_SENSE_NAMES = YES
144 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
145 # (but less readable) file names. This can be useful is your file systems
146 # doesn't support long names like on DOS, Mac, or CD-ROM.
150 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
151 # will show members with their full class and namespace scopes in the
152 # documentation. If set to YES the scope will be hidden.
154 HIDE_SCOPE_NAMES = NO
156 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
157 # will generate a verbatim copy of the header file for each class for
158 # which an include is specified. Set to NO to disable this.
160 VERBATIM_HEADERS = YES
162 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
163 # will put list of the files that are included by a file in the documentation
166 SHOW_INCLUDE_FILES = YES
168 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
169 # will interpret the first line (until the first dot) of a JavaDoc-style
170 # comment as the brief description. If set to NO, the JavaDoc
171 # comments will behave just like the Qt-style comments (thus requiring an
172 # explict @brief command for a brief description.
174 JAVADOC_AUTOBRIEF = YES
176 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
177 # member inherits the documentation from any documented member that it
182 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
183 # is inserted in the documentation for inline members.
187 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
188 # will sort the (detailed) documentation of file and class members
189 # alphabetically by member name. If set to NO the members will appear in
192 SORT_MEMBER_DOCS = YES
194 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
195 # tag is set to YES, then doxygen will reuse the documentation of the first
196 # member in the group (if any) for the other members of the group. By default
197 # all members of a group must be documented explicitly.
199 DISTRIBUTE_GROUP_DOC = NO
201 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
202 # Doxygen uses this value to replace tabs by spaces in code fragments.
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 # The GENERATE_BUGLIST tag can be used to enable (YES) or
219 # disable (NO) the bug list. This list is created by putting \bug
220 # commands in the documentation.
222 GENERATE_BUGLIST = YES
224 # This tag can be used to specify a number of aliases that acts
225 # as commands in the documentation. An alias has the form "name=value".
226 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
227 # put the command \sideeffect (or @sideeffect) in the documentation, which
228 # will result in a user defined paragraph with heading "Side Effects:".
229 # You can put \n's in the value part of an alias to insert newlines.
233 # The ENABLED_SECTIONS tag can be used to enable conditional
234 # documentation sections, marked by \if sectionname ... \endif.
238 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
239 # the initial value of a variable or define consist of for it to appear in
240 # the documentation. If the initializer consists of more lines than specified
241 # here it will be hidden. Use a value of 0 to hide initializers completely.
242 # The appearance of the initializer of individual variables and defines in the
243 # documentation can be controlled using \showinitializer or \hideinitializer
244 # command in the documentation regardless of this setting.
246 MAX_INITIALIZER_LINES = 30
248 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
249 # only. Doxygen will then generate output that is more tailored for C.
250 # For instance some of the names that are used will be different. The list
251 # of all members will be omitted, etc.
253 OPTIMIZE_OUTPUT_FOR_C = YES
255 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
256 # only. Doxygen will then generate output that is more tailored for Java.
257 # For instance namespaces will be presented as packages, qualified scopes
258 # will look different, etc.
260 OPTIMIZE_OUTPUT_JAVA = NO
262 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
263 # at the bottom of the documentation of classes and structs. If set to YES the
264 # list will mention the files that were used to generate the documentation.
266 SHOW_USED_FILES = YES
268 #---------------------------------------------------------------------------
269 # configuration options related to warning and progress messages
270 #---------------------------------------------------------------------------
272 # The QUIET tag can be used to turn on/off the messages that are generated
273 # by doxygen. Possible values are YES and NO. If left blank NO is used.
277 # The WARNINGS tag can be used to turn on/off the warning messages that are
278 # generated by doxygen. Possible values are YES and NO. If left blank
283 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
284 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
285 # automatically be disabled.
287 WARN_IF_UNDOCUMENTED = YES
289 # The WARN_FORMAT tag determines the format of the warning messages that
290 # doxygen can produce. The string should contain the $file, $line, and $text
291 # tags, which will be replaced by the file and line number from which the
292 # warning originated and the warning text.
294 WARN_FORMAT = "$file:$line: $text"
296 # The WARN_LOGFILE tag can be used to specify a file to which warning
297 # and error messages should be written. If left blank the output is written
302 #---------------------------------------------------------------------------
303 # configuration options related to the input files
304 #---------------------------------------------------------------------------
306 # The INPUT tag can be used to specify the files and/or directories that contain
307 # documented source files. You may enter file names like "myfile.cpp" or
308 # directories like "/usr/src/myproject". Separate the files or directories
312 @top_srcdir@/Doxyheader \
313 @top_srcdir@/build.c \
314 @top_srcdir@/build.h \
315 @top_srcdir@/config.h \
316 @top_srcdir@/debug.h \
317 @top_srcdir@/macros \
318 @top_srcdir@/rpmqv.c \
319 @top_srcdir@/rpmpopt-@VERSION@ \
321 @top_srcdir@/rpm2cpio.c \
322 @top_srcdir@/system.h \
323 @top_srcdir@/beecrypt/aes.c \
324 @top_srcdir@/beecrypt/aes.h \
325 @top_srcdir@/beecrypt/aesopt.h \
326 @top_srcdir@/beecrypt/base64.c \
327 @top_srcdir@/beecrypt/base64.h \
328 @top_srcdir@/beecrypt/beecrypt.c \
329 @top_srcdir@/beecrypt/beecrypt.h \
330 @top_srcdir@/beecrypt/beecrypt.api.h \
331 @top_srcdir@/beecrypt/beecrypt.gnu.h \
332 @top_srcdir@/beecrypt/blockmode.c \
333 @top_srcdir@/beecrypt/blockmode.h \
334 @top_srcdir@/beecrypt/blockpad.c \
335 @top_srcdir@/beecrypt/blockpad.h \
336 @top_srcdir@/beecrypt/blowfish.c \
337 @top_srcdir@/beecrypt/blowfish.h \
338 @top_srcdir@/beecrypt/blowfishopt.h \
339 @top_srcdir@/beecrypt/config.h \
340 @top_srcdir@/beecrypt/dhaes.c \
341 @top_srcdir@/beecrypt/dhaes.h \
342 @top_srcdir@/beecrypt/dldp.c \
343 @top_srcdir@/beecrypt/dldp.h \
344 @top_srcdir@/beecrypt/dlkp.c \
345 @top_srcdir@/beecrypt/dlkp.h \
346 @top_srcdir@/beecrypt/dlpk.c \
347 @top_srcdir@/beecrypt/dlpk.h \
348 @top_srcdir@/beecrypt/dlsvdp-dh.c \
349 @top_srcdir@/beecrypt/dlsvdp-dh.h \
350 @top_srcdir@/beecrypt/elgamal.c \
351 @top_srcdir@/beecrypt/elgamal.h \
352 @top_srcdir@/beecrypt/endianness.c \
353 @top_srcdir@/beecrypt/endianness.h \
354 @top_srcdir@/beecrypt/entropy.c \
355 @top_srcdir@/beecrypt/entropy.h \
356 @top_srcdir@/beecrypt/fips186.c \
357 @top_srcdir@/beecrypt/fips186.h \
358 @top_srcdir@/beecrypt/hmac.c \
359 @top_srcdir@/beecrypt/hmac.h \
360 @top_srcdir@/beecrypt/hmacmd5.c \
361 @top_srcdir@/beecrypt/hmacmd5.h \
362 @top_srcdir@/beecrypt/hmacsha1.c \
363 @top_srcdir@/beecrypt/hmacsha1.h \
364 @top_srcdir@/beecrypt/hmacsha256.c \
365 @top_srcdir@/beecrypt/hmacsha256.h \
366 @top_srcdir@/beecrypt/javaglue.c \
367 @top_srcdir@/beecrypt/javaglue.h \
368 @top_srcdir@/beecrypt/md5.c \
369 @top_srcdir@/beecrypt/md5.h \
370 @top_srcdir@/beecrypt/memchunk.c \
371 @top_srcdir@/beecrypt/memchunk.h \
372 @top_srcdir@/beecrypt/mpbarrett.c \
373 @top_srcdir@/beecrypt/mpbarrett.h \
374 @top_srcdir@/beecrypt/mp.c \
375 @top_srcdir@/beecrypt/mp.h \
376 @top_srcdir@/beecrypt/mpnumber.c \
377 @top_srcdir@/beecrypt/mpnumber.h \
378 @top_srcdir@/beecrypt/mpopt.h \
379 @top_srcdir@/beecrypt/mpprime.c \
380 @top_srcdir@/beecrypt/mpprime.h \
381 @top_srcdir@/beecrypt/mtprng.c \
382 @top_srcdir@/beecrypt/mtprng.h \
383 @top_srcdir@/beecrypt/rsa.c \
384 @top_srcdir@/beecrypt/rsa.h \
385 @top_srcdir@/beecrypt/rsakp.c \
386 @top_srcdir@/beecrypt/rsakp.h \
387 @top_srcdir@/beecrypt/rsapk.c \
388 @top_srcdir@/beecrypt/rsapk.h \
389 @top_srcdir@/beecrypt/sha1.c \
390 @top_srcdir@/beecrypt/sha1.h \
391 @top_srcdir@/beecrypt/sha1opt.h \
392 @top_srcdir@/beecrypt/sha256.c \
393 @top_srcdir@/beecrypt/sha256.h \
394 @top_srcdir@/beecrypt/timestamp.c \
395 @top_srcdir@/beecrypt/timestamp.h \
396 @top_srcdir@/build/build.c \
397 @top_srcdir@/build/buildio.h \
398 @top_srcdir@/build/expression.c \
399 @top_srcdir@/build/files.c \
400 @top_srcdir@/build/misc.c \
401 @top_srcdir@/build/names.c \
402 @top_srcdir@/build/pack.c \
403 @top_srcdir@/build/parseBuildInstallClean.c \
404 @top_srcdir@/build/parseChangelog.c \
405 @top_srcdir@/build/parseDescription.c \
406 @top_srcdir@/build/parseFiles.c \
407 @top_srcdir@/build/parsePreamble.c \
408 @top_srcdir@/build/parsePrep.c \
409 @top_srcdir@/build/parseReqs.c \
410 @top_srcdir@/build/parseScript.c \
411 @top_srcdir@/build/parseSpec.c \
412 @top_srcdir@/build/poptBT.c \
413 @top_srcdir@/build/reqprov.c \
414 @top_srcdir@/build/rpmbuild.h \
415 @top_srcdir@/build/rpmfc.c \
416 @top_srcdir@/build/rpmfc.h \
417 @top_srcdir@/build/rpmspec.h \
418 @top_srcdir@/build/spec.c \
419 @top_srcdir@/doc/manual/builddependencies \
420 @top_srcdir@/doc/manual/buildroot \
421 @top_srcdir@/doc/manual/conditionalbuilds \
422 @top_srcdir@/doc/manual/dependencies \
423 @top_srcdir@/doc/manual/format \
424 @top_srcdir@/doc/manual/hregions \
425 @top_srcdir@/doc/manual/macros \
426 @top_srcdir@/doc/manual/multiplebuilds \
427 @top_srcdir@/doc/manual/queryformat \
428 @top_srcdir@/doc/manual/signatures \
429 @top_srcdir@/doc/manual/relocatable \
430 @top_srcdir@/doc/manual/spec \
431 @top_srcdir@/doc/manual/triggers \
432 @top_srcdir@/doc/manual/tsort \
433 @top_srcdir@/file/src/apprentice.c \
434 @top_srcdir@/file/src/ascmagic.c \
435 @top_srcdir@/file/src/compress.c \
436 @top_srcdir@/file/src/file.c \
437 @top_srcdir@/file/src/file.h \
438 @top_srcdir@/file/src/fsmagic.c \
439 @top_srcdir@/file/src/names.h \
440 @top_srcdir@/file/src/print.c \
441 @top_srcdir@/file/src/readelf.c \
442 @top_srcdir@/file/src/readelf.h \
443 @top_srcdir@/file/src/softmagic.c \
444 @top_srcdir@/file/src/tar.h \
445 @top_srcdir@/lib/cpio.c \
446 @top_srcdir@/lib/cpio.h \
447 @top_srcdir@/lib/depends.c \
448 @top_srcdir@/lib/formats.c \
449 @top_srcdir@/lib/fs.c \
450 @top_srcdir@/lib/fsm.c \
451 @top_srcdir@/lib/fsm.h \
452 @top_srcdir@/lib/manifest.c \
453 @top_srcdir@/lib/manifest.h \
454 @top_srcdir@/lib/misc.c \
455 @top_srcdir@/lib/misc.h \
456 @top_srcdir@/lib/package.c \
457 @top_srcdir@/lib/poptALL.c \
458 @top_srcdir@/lib/poptI.c \
459 @top_srcdir@/lib/poptQV.c \
460 @top_srcdir@/lib/psm.c \
461 @top_srcdir@/lib/psm.h \
462 @top_srcdir@/lib/query.c \
463 @top_srcdir@/lib/rpmal.c \
464 @top_srcdir@/lib/rpmal.h \
465 @top_srcdir@/lib/rpmchecksig.c \
466 @top_srcdir@/lib/rpmcli.h \
467 @top_srcdir@/lib/rpmds.c \
468 @top_srcdir@/lib/rpmds.h \
469 @top_srcdir@/lib/rpmfi.c \
470 @top_srcdir@/lib/rpmfi.h \
471 @top_srcdir@/lib/rpminstall.c \
472 @top_srcdir@/lib/rpmlead.c \
473 @top_srcdir@/lib/rpmlead.h \
474 @top_srcdir@/lib/rpmlib.h \
475 @top_srcdir@/lib/rpmlibprov.c \
476 @top_srcdir@/lib/rpmps.c \
477 @top_srcdir@/lib/rpmps.h \
478 @top_srcdir@/lib/rpmrc.c \
479 @top_srcdir@/lib/rpmte.c \
480 @top_srcdir@/lib/rpmte.h \
481 @top_srcdir@/lib/rpmts.c \
482 @top_srcdir@/lib/rpmts.h \
483 @top_srcdir@/lib/rpmvercmp.c \
484 @top_srcdir@/lib/signature.c \
485 @top_srcdir@/lib/signature.h \
486 @top_srcdir@/lib/stringbuf.c \
487 @top_srcdir@/lib/stringbuf.h \
488 @top_srcdir@/lib/transaction.c \
489 @top_srcdir@/lib/verify.c \
490 @top_srcdir@/rpmdb/db3.c \
491 @top_srcdir@/rpmdb/dbconfig.c \
492 @top_srcdir@/rpmdb/fprint.c \
493 @top_srcdir@/rpmdb/fprint.h \
494 @top_srcdir@/rpmdb/hdrNVR.c \
495 @top_srcdir@/rpmdb/hdrinline.h \
496 @top_srcdir@/rpmdb/header.c \
497 @top_srcdir@/rpmdb/header.h \
498 @top_srcdir@/rpmdb/header_internal.c \
499 @top_srcdir@/rpmdb/header_internal.h \
500 @top_srcdir@/rpmdb/legacy.c \
501 @top_srcdir@/rpmdb/legacy.h \
502 @top_srcdir@/rpmdb/merge.c \
503 @top_srcdir@/rpmdb/poptDB.c \
504 @top_srcdir@/rpmdb/rpmhash.c \
505 @top_srcdir@/rpmdb/rpmhash.h \
506 @top_srcdir@/rpmdb/rpmdb.c \
507 @top_srcdir@/rpmdb/rpmdb.h \
508 @top_srcdir@/rpmdb/tagname.c \
509 @top_srcdir@/rpmdb/tagtbl.c \
510 @top_srcdir@/rpmio/argv.c \
511 @top_srcdir@/rpmio/argv.h \
512 @top_srcdir@/rpmio/digest.c \
513 @top_srcdir@/rpmio/fts.c \
514 @top_srcdir@/rpmio/fts.h \
515 @top_srcdir@/rpmio/macro.c \
516 @top_srcdir@/rpmio/rpmlog.c \
517 @top_srcdir@/rpmio/rpmlog.h \
518 @top_srcdir@/rpmio/rpmerr.h \
519 @top_srcdir@/rpmio/rpmio.c \
520 @top_srcdir@/rpmio/rpmio.h \
521 @top_srcdir@/rpmio/rpmio_internal.h \
522 @top_srcdir@/rpmio/rpmmacro.h \
523 @top_srcdir@/rpmio/rpmmalloc.c \
524 @top_srcdir@/rpmio/rpmmessages.h \
525 @top_srcdir@/rpmio/rpmpgp.c \
526 @top_srcdir@/rpmio/rpmpgp.h \
527 @top_srcdir@/rpmio/rpmrpc.c \
528 @top_srcdir@/rpmio/rpmsq.c \
529 @top_srcdir@/rpmio/rpmsq.h \
530 @top_srcdir@/rpmio/rpmsw.c \
531 @top_srcdir@/rpmio/rpmsw.h \
532 @top_srcdir@/rpmio/rpmurl.h \
533 @top_srcdir@/rpmio/strcasecmp.c \
534 @top_srcdir@/rpmio/stubs.c \
535 @top_srcdir@/rpmio/ugid.c \
536 @top_srcdir@/rpmio/ugid.h \
537 @top_srcdir@/rpmio/url.c \
538 @top_srcdir@/popt/findme.c \
539 @top_srcdir@/popt/findme.h \
540 @top_srcdir@/popt/popt.c \
541 @top_srcdir@/popt/popt.h \
542 @top_srcdir@/popt/poptconfig.c \
543 @top_srcdir@/popt/popthelp.c \
544 @top_srcdir@/popt/poptint.h \
545 @top_srcdir@/popt/poptparse.c \
546 @top_srcdir@/python/_rpmdb.c \
547 @top_srcdir@/python/header-py.c \
548 @top_srcdir@/python/header-py.h \
549 @top_srcdir@/python/rpmal-py.c \
550 @top_srcdir@/python/rpmal-py.h \
551 @top_srcdir@/python/rpmbc-py.c \
552 @top_srcdir@/python/rpmbc-py.h \
553 @top_srcdir@/python/rpmdb-py.c \
554 @top_srcdir@/python/rpmdb-py.h \
555 @top_srcdir@/python/rpmds-py.c \
556 @top_srcdir@/python/rpmds-py.h \
557 @top_srcdir@/python/rpmfd-py.c \
558 @top_srcdir@/python/rpmfd-py.h \
559 @top_srcdir@/python/rpmfi-py.c \
560 @top_srcdir@/python/rpmfi-py.h \
561 @top_srcdir@/python/rpmfts-py.c \
562 @top_srcdir@/python/rpmfts-py.h \
563 @top_srcdir@/python/rpmmi-py.c \
564 @top_srcdir@/python/rpmmi-py.h \
565 @top_srcdir@/python/rpmmodule.c \
566 @top_srcdir@/python/rpmrc-py.c \
567 @top_srcdir@/python/rpmrc-py.h \
568 @top_srcdir@/python/rpmte-py.c \
569 @top_srcdir@/python/rpmte-py.h \
570 @top_srcdir@/python/rpmts-py.c \
571 @top_srcdir@/python/rpmts-py.h \
572 @top_srcdir@/tools/dump.c \
573 @top_srcdir@/tools/dumpdb.c \
574 @top_srcdir@/tools/javadeps.c \
575 @top_srcdir@/tools/rpmarchive.c \
576 @top_srcdir@/tools/rpmcache.c \
577 @top_srcdir@/tools/rpmdeps.c \
578 @top_srcdir@/tools/rpmgraph.c \
579 @top_srcdir@/tools/rpmheader.c \
580 @top_srcdir@/tools/rpminject.c \
581 @top_srcdir@/tools/rpmlead.c \
582 @top_srcdir@/tools/rpmsignature.c \
583 @top_srcdir@/zlib/adler32.c \
584 @top_srcdir@/zlib/crc32.c \
585 @top_srcdir@/zlib/crc32.h \
586 @top_srcdir@/zlib/deflate.c \
587 @top_srcdir@/zlib/deflate.h \
588 @top_srcdir@/zlib/gzio.c \
589 @top_srcdir@/zlib/infback.c \
590 @top_srcdir@/zlib/inffast.c \
591 @top_srcdir@/zlib/inffast.h \
592 @top_srcdir@/zlib/inffixed.h \
593 @top_srcdir@/zlib/inflate.c \
594 @top_srcdir@/zlib/inflate.h \
595 @top_srcdir@/zlib/inftrees.c \
596 @top_srcdir@/zlib/inftrees.h \
597 @top_srcdir@/zlib/maketree.c \
598 @top_srcdir@/zlib/minigzip.c \
599 @top_srcdir@/zlib/trees.c \
600 @top_srcdir@/zlib/trees.h \
601 @top_srcdir@/zlib/uncompr.c \
602 @top_srcdir@/zlib/zconf.h \
603 @top_srcdir@/zlib/zlib.h \
604 @top_srcdir@/zlib/zutil.c \
605 @top_srcdir@/zlib/zutil.h
608 # XX file name collision here
609 # @top_srcdir@/zlib/compress.c
611 # If the value of the INPUT tag contains directories, you can use the
612 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
613 # and *.h) to filter out the source-files in the directories. If left
614 # blank the following patterns are tested:
615 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
618 FILE_PATTERNS = *.c *.h
620 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
621 # should be searched for input files as well. Possible values are YES and NO.
622 # If left blank NO is used.
626 # The EXCLUDE tag can be used to specify files and/or directories that should
627 # excluded from the INPUT source files. This way you can easily exclude a
628 # subdirectory from a directory tree whose root is specified with the INPUT tag.
632 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
633 # that are symbolic links (a Unix filesystem feature) are excluded from the input.
635 EXCLUDE_SYMLINKS = NO
637 # If the value of the INPUT tag contains directories, you can use the
638 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
639 # certain files from those directories.
643 # The EXAMPLE_PATH tag can be used to specify one or more files or
644 # directories that contain example code fragments that are included (see
645 # the \include command).
647 EXAMPLE_PATH = @top_srcdir@/doc/manual
649 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
650 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
651 # and *.h) to filter out the source-files in the directories. If left
652 # blank all files are included.
656 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
657 # searched for input files to be used with the \include or \dontinclude
658 # commands irrespective of the value of the RECURSIVE tag.
659 # Possible values are YES and NO. If left blank NO is used.
661 EXAMPLE_RECURSIVE = NO
663 # The IMAGE_PATH tag can be used to specify one or more files or
664 # directories that contain image that are included in the documentation (see
665 # the \image command).
669 # The INPUT_FILTER tag can be used to specify a program that doxygen should
670 # invoke to filter for each input file. Doxygen will invoke the filter program
671 # by executing (via popen()) the command <filter> <input-file>, where <filter>
672 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
673 # input file. Doxygen will then use the output that the filter program writes
674 # to standard output.
678 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
679 # INPUT_FILTER) will be used to filter the input files when producing source
682 FILTER_SOURCE_FILES = NO
684 #---------------------------------------------------------------------------
685 # configuration options related to source browsing
686 #---------------------------------------------------------------------------
688 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
689 # be generated. Documented entities will be cross-referenced with these sources.
693 # Setting the INLINE_SOURCES tag to YES will include the body
694 # of functions and classes directly in the documentation.
698 # If the REFERENCED_BY_RELATION tag is set to YES (the default)
699 # then for each documented function all documented
700 # functions referencing it will be listed.
702 REFERENCED_BY_RELATION = YES
704 # If the REFERENCES_RELATION tag is set to YES (the default)
705 # then for each documented function all documented entities
706 # called/used by that function will be listed.
708 REFERENCES_RELATION = YES
710 #---------------------------------------------------------------------------
711 # configuration options related to the alphabetical class index
712 #---------------------------------------------------------------------------
714 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
715 # of all compounds will be generated. Enable this if the project
716 # contains a lot of classes, structs, unions or interfaces.
718 ALPHABETICAL_INDEX = NO
720 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
721 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
722 # in which this list will be split (can be a number in the range [1..20])
724 COLS_IN_ALPHA_INDEX = 5
726 # In case all classes in a project start with a common prefix, all
727 # classes will be put under the same header in the alphabetical index.
728 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
729 # should be ignored while generating the index headers.
733 #---------------------------------------------------------------------------
734 # configuration options related to the HTML output
735 #---------------------------------------------------------------------------
737 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
738 # generate HTML output.
742 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
743 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
744 # put in front of it. If left blank `html' will be used as the default path.
748 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
749 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
750 # doxygen will generate files with .html extension.
752 HTML_FILE_EXTENSION = .html
754 # The HTML_HEADER tag can be used to specify a personal HTML header for
755 # each generated HTML page. If it is left blank doxygen will generate a
760 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
761 # each generated HTML page. If it is left blank doxygen will generate a
766 # The HTML_STYLESHEET tag can be used to specify a user defined cascading
767 # style sheet that is used by each HTML page. It can be used to
768 # fine-tune the look of the HTML output. If the tag is left blank doxygen
769 # will generate a default style sheet
773 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
774 # files or namespaces will be aligned in HTML using tables. If set to
775 # NO a bullet list will be used.
777 HTML_ALIGN_MEMBERS = YES
779 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
780 # will be generated that can be used as input for tools like the
781 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
782 # of the generated HTML documentation.
784 GENERATE_HTMLHELP = NO
786 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
787 # controls if a separate .chi index file is generated (YES) or that
788 # it should be included in the master .chm file (NO).
792 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
793 # controls whether a binary table of contents is generated (YES) or a
794 # normal table of contents (NO) in the .chm file.
798 # The TOC_EXPAND flag can be set to YES to add extra items for group members
799 # to the contents of the Html help documentation and to the tree view.
803 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
804 # top of each HTML page. The value NO (the default) enables the index and
805 # the value YES disables it.
809 # This tag can be used to set the number of enum values (range [1..20])
810 # that doxygen will group on one line in the generated HTML documentation.
812 ENUM_VALUES_PER_LINE = 4
814 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
815 # generated containing a tree-like index structure (just like the one that
816 # is generated for HTML Help). For this to work a browser that supports
817 # JavaScript and frames is required (for instance Mozilla, Netscape 4.0+,
818 # or Internet explorer 4.0+). Note that for large projects the tree generation
819 # can take a very long time. In such cases it is better to disable this feature.
820 # Windows users are probably better off using the HTML help feature.
822 GENERATE_TREEVIEW = NO
824 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
825 # used to set the initial width (in pixels) of the frame in which the tree
830 #---------------------------------------------------------------------------
831 # configuration options related to the LaTeX output
832 #---------------------------------------------------------------------------
834 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
835 # generate Latex output.
839 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
840 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
841 # put in front of it. If left blank `latex' will be used as the default path.
845 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be invoked. If left blank `latex' will be used as the default command name.
847 LATEX_CMD_NAME = latex
849 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
850 # generate index for LaTeX. If left blank `makeindex' will be used as the
851 # default command name.
853 MAKEINDEX_CMD_NAME = makeindex
855 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
856 # LaTeX documents. This may be useful for small projects and may help to
857 # save some trees in general.
861 # The PAPER_TYPE tag can be used to set the paper type that is used
862 # by the printer. Possible values are: a4, a4wide, letter, legal and
863 # executive. If left blank a4wide will be used.
867 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
868 # packages that should be included in the LaTeX output.
872 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
873 # the generated latex document. The header should contain everything until
874 # the first chapter. If it is left blank doxygen will generate a
875 # standard header. Notice: only use this tag if you know what you are doing!
879 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
880 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
881 # contain links (just like the HTML output) instead of page references
882 # This makes the output suitable for online browsing using a pdf viewer.
886 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
887 # plain latex in the generated Makefile. Set this option to YES to get a
888 # higher quality PDF documentation.
892 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
893 # command to the generated LaTeX files. This will instruct LaTeX to keep
894 # running if errors occur, instead of asking the user for help.
895 # This option is also used when generating formulas in HTML.
899 #---------------------------------------------------------------------------
900 # configuration options related to the RTF output
901 #---------------------------------------------------------------------------
903 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
904 # The RTF output is optimised for Word 97 and may not look very pretty with
905 # other RTF readers or editors.
909 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
910 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
911 # put in front of it. If left blank `rtf' will be used as the default path.
915 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
916 # RTF documents. This may be useful for small projects and may help to
917 # save some trees in general.
921 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
922 # will contain hyperlink fields. The RTF file will
923 # contain links (just like the HTML output) instead of page references.
924 # This makes the output suitable for online browsing using WORD or other
925 # programs which support those fields.
926 # Note: wordpad (write) and others do not support links.
930 # Load stylesheet definitions from file. Syntax is similar to doxygen's
931 # config file, i.e. a series of assigments. You only have to provide
932 # replacements, missing definitions are set to their default value.
934 RTF_STYLESHEET_FILE =
936 # Set optional variables used in the generation of an rtf document.
937 # Syntax is similar to doxygen's config file.
939 RTF_EXTENSIONS_FILE =
941 #---------------------------------------------------------------------------
942 # configuration options related to the man page output
943 #---------------------------------------------------------------------------
945 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
950 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
951 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
952 # put in front of it. If left blank `man' will be used as the default path.
956 # The MAN_EXTENSION tag determines the extension that is added to
957 # the generated man pages (default is the subroutine's section .3)
961 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
962 # then it will generate one additional man file for each entity
963 # documented in the real man page(s). These additional files
964 # only source the real man page, but without them the man command
965 # would be unable to find the correct page. The default is NO.
969 #---------------------------------------------------------------------------
970 # configuration options related to the XML output
971 #---------------------------------------------------------------------------
973 # If the GENERATE_XML tag is set to YES Doxygen will
974 # generate an XML file that captures the structure of
975 # the code including all documentation. Note that this
976 # feature is still experimental and incomplete at the
981 #---------------------------------------------------------------------------
982 # configuration options for the AutoGen Definitions output
983 #---------------------------------------------------------------------------
985 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
986 # generate an AutoGen Definitions (see autogen.sf.net) file
987 # that captures the structure of the code including all
988 # documentation. Note that this feature is still experimental
989 # and incomplete at the moment.
991 GENERATE_AUTOGEN_DEF = NO
993 #---------------------------------------------------------------------------
994 # Configuration options related to the preprocessor
995 #---------------------------------------------------------------------------
997 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
998 # evaluate all C-preprocessor directives found in the sources and include
1001 ENABLE_PREPROCESSING = YES
1003 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1004 # names in the source code. If set to NO (the default) only conditional
1005 # compilation will be performed. Macro expansion can be done in a controlled
1006 # way by setting EXPAND_ONLY_PREDEF to YES.
1008 MACRO_EXPANSION = YES
1010 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1011 # then the macro expansion is limited to the macros specified with the
1012 # PREDEFINED and EXPAND_AS_PREDEFINED tags.
1014 EXPAND_ONLY_PREDEF = NO
1016 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1017 # in the INCLUDE_PATH (see below) will be search if a #include is found.
1019 SEARCH_INCLUDES = YES
1021 # The INCLUDE_PATH tag can be used to specify one or more directories that
1022 # contain include files that are not input files but should be processed by
1027 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1028 # patterns (like *.h and *.hpp) to filter out the header-files in the
1029 # directories. If left blank, the patterns specified with FILE_PATTERNS will
1032 INCLUDE_FILE_PATTERNS =
1034 # The PREDEFINED tag can be used to specify one or more macro names that
1035 # are defined before the preprocessor is started (similar to the -D option of
1036 # gcc). The argument of the tag is a list of macros of the form: name
1037 # or name=definition (no spaces). If the definition and the = are
1038 # omitted =1 is assumed.
1042 # If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then
1043 # this tag can be used to specify a list of macro names that should be expanded.
1044 # The macro definition that is found in the sources will be used.
1045 # Use the PREDEFINED tag if you want to use a different macro definition.
1049 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1050 # doxygen's preprocessor will remove all function-like macros that are alone
1051 # on a line and do not end with a semicolon. Such function macros are typically
1052 # used for boiler-plate code, and will confuse the parser if not removed.
1054 SKIP_FUNCTION_MACROS = YES
1056 #---------------------------------------------------------------------------
1057 # Configuration::addtions related to external references
1058 #---------------------------------------------------------------------------
1060 # The TAGFILES tag can be used to specify one or more tagfiles.
1064 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1065 # a tag file that is based on the input files it reads.
1067 GENERATE_TAGFILE = Doxytags
1069 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1070 # in the class index. If set to NO only the inherited external classes
1075 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1076 # in the modules index. If set to NO, only the current project's groups will
1079 EXTERNAL_GROUPS = YES
1081 # The PERL_PATH should be the absolute path and name of the perl script
1082 # interpreter (i.e. the result of `which perl').
1084 PERL_PATH = /usr/bin/perl
1086 #---------------------------------------------------------------------------
1087 # Configuration options related to the dot tool
1088 #---------------------------------------------------------------------------
1090 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1091 # generate a inheritance diagram (in Html, RTF and LaTeX) for classes with base or
1092 # super classes. Setting the tag to NO turns the diagrams off. Note that this
1093 # option is superceded by the HAVE_DOT option below. This is only a fallback. It is
1094 # recommended to install and use dot, since it yield more powerful graphs.
1096 CLASS_DIAGRAMS = YES
1098 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1099 # available from the path. This tool is part of Graphviz, a graph visualization
1100 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
1101 # have no effect if this option is set to NO (the default)
1105 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1106 # will generate a graph for each documented class showing the direct and
1107 # indirect inheritance relations. Setting this tag to YES will force the
1108 # the CLASS_DIAGRAMS tag to NO.
1112 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1113 # will generate a graph for each documented class showing the direct and
1114 # indirect implementation dependencies (inheritance, containment, and
1115 # class references variables) of the class with other documented classes.
1117 COLLABORATION_GRAPH = YES
1119 # If set to YES, the inheritance and collaboration graphs will show the
1120 # relations between templates and their instances.
1122 TEMPLATE_RELATIONS = YES
1124 # If set to YES, the inheritance and collaboration graphs will hide
1125 # inheritance and usage relations if the target is undocumented
1126 # or is not a class.
1128 HIDE_UNDOC_RELATIONS = YES
1130 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1131 # tags are set to YES then doxygen will generate a graph for each documented
1132 # file showing the direct and indirect include dependencies of the file with
1133 # other documented files.
1137 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1138 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1139 # documented header file showing the documented files that directly or
1140 # indirectly include this file.
1142 INCLUDED_BY_GRAPH = YES
1144 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1145 # will graphical hierarchy of all classes instead of a textual one.
1147 GRAPHICAL_HIERARCHY = YES
1149 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1150 # generated by dot. Possible values are png, jpg, or gif
1151 # If left blank png will be used.
1153 DOT_IMAGE_FORMAT = png
1155 # The tag DOT_PATH can be used to specify the path where the dot tool can be
1156 # found. If left blank, it is assumed the dot tool can be found on the path.
1160 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1161 # contain dot files that are included in the documentation (see the
1162 # \dotfile command).
1166 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1167 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1168 # this value, doxygen will try to truncate the graph, so that it fits within
1169 # the specified constraint. Beware that most browsers cannot cope with very
1172 MAX_DOT_GRAPH_WIDTH = 1024
1174 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1175 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1176 # this value, doxygen will try to truncate the graph, so that it fits within
1177 # the specified constraint. Beware that most browsers cannot cope with very
1180 MAX_DOT_GRAPH_HEIGHT = 1024
1182 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1183 # generate a legend page explaining the meaning of the various boxes and
1184 # arrows in the dot generated graphs.
1186 GENERATE_LEGEND = YES
1188 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1189 # remove the intermedate dot files that are used to generate
1190 # the various graphs.
1194 #---------------------------------------------------------------------------
1195 # Configuration::addtions related to the search engine
1196 #---------------------------------------------------------------------------
1198 # The SEARCHENGINE tag specifies whether or not a search engine should be
1199 # used. If set to NO the values of all tags below this one will be ignored.
1203 # The CGI_NAME tag should be the name of the CGI script that
1204 # starts the search engine (doxysearch) with the correct parameters.
1205 # A script with this name will be generated by doxygen.
1207 CGI_NAME = search.cgi
1209 # The CGI_URL tag should be the absolute URL to the directory where the
1210 # cgi binaries are located. See the documentation of your http daemon for
1215 # The DOC_URL tag should be the absolute URL to the directory where the
1216 # documentation is located. If left blank the absolute path to the
1217 # documentation, with file:// prepended to it, will be used.
1221 # The DOC_ABSPATH tag should be the absolute path to the directory where the
1222 # documentation is located. If left blank the directory on the local machine
1227 # The BIN_ABSPATH tag must point to the directory where the doxysearch binary
1230 BIN_ABSPATH = /usr/local/bin/
1232 # The EXT_DOC_PATHS tag can be used to specify one or more paths to
1233 # documentation generated for other projects. This allows doxysearch to search
1234 # the documentation for these projects as well.