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.gas.h \
331 @top_srcdir@/beecrypt/beecrypt.win.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/mp32barrett.c \
373 @top_srcdir@/beecrypt/mp32barrett.h \
374 @top_srcdir@/beecrypt/mp32.c \
375 @top_srcdir@/beecrypt/mp32.h \
376 @top_srcdir@/beecrypt/mp32number.c \
377 @top_srcdir@/beecrypt/mp32number.h \
378 @top_srcdir@/beecrypt/mp32opt.h \
379 @top_srcdir@/beecrypt/mp32prime.c \
380 @top_srcdir@/beecrypt/mp32prime.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@/beecrypt/types.h \
397 @top_srcdir@/build/build.c \
398 @top_srcdir@/build/buildio.h \
399 @top_srcdir@/build/expression.c \
400 @top_srcdir@/build/files.c \
401 @top_srcdir@/build/misc.c \
402 @top_srcdir@/build/names.c \
403 @top_srcdir@/build/pack.c \
404 @top_srcdir@/build/parseBuildInstallClean.c \
405 @top_srcdir@/build/parseChangelog.c \
406 @top_srcdir@/build/parseDescription.c \
407 @top_srcdir@/build/parseFiles.c \
408 @top_srcdir@/build/parsePreamble.c \
409 @top_srcdir@/build/parsePrep.c \
410 @top_srcdir@/build/parseReqs.c \
411 @top_srcdir@/build/parseScript.c \
412 @top_srcdir@/build/parseSpec.c \
413 @top_srcdir@/build/poptBT.c \
414 @top_srcdir@/build/reqprov.c \
415 @top_srcdir@/build/rpmbuild.h \
416 @top_srcdir@/build/rpmspec.h \
417 @top_srcdir@/build/spec.c \
418 @top_srcdir@/doc/manual/builddependencies \
419 @top_srcdir@/doc/manual/buildroot \
420 @top_srcdir@/doc/manual/conditionalbuilds \
421 @top_srcdir@/doc/manual/dependencies \
422 @top_srcdir@/doc/manual/format \
423 @top_srcdir@/doc/manual/hregions \
424 @top_srcdir@/doc/manual/macros \
425 @top_srcdir@/doc/manual/multiplebuilds \
426 @top_srcdir@/doc/manual/queryformat \
427 @top_srcdir@/doc/manual/signatures \
428 @top_srcdir@/doc/manual/relocatable \
429 @top_srcdir@/doc/manual/spec \
430 @top_srcdir@/doc/manual/triggers \
431 @top_srcdir@/doc/manual/tsort \
432 @top_srcdir@/lib/cpio.c \
433 @top_srcdir@/lib/cpio.h \
434 @top_srcdir@/lib/depends.c \
435 @top_srcdir@/lib/formats.c \
436 @top_srcdir@/lib/fs.c \
437 @top_srcdir@/lib/fsm.c \
438 @top_srcdir@/lib/fsm.h \
439 @top_srcdir@/lib/manifest.c \
440 @top_srcdir@/lib/manifest.h \
441 @top_srcdir@/lib/misc.c \
442 @top_srcdir@/lib/misc.h \
443 @top_srcdir@/lib/package.c \
444 @top_srcdir@/lib/poptALL.c \
445 @top_srcdir@/lib/poptI.c \
446 @top_srcdir@/lib/poptQV.c \
447 @top_srcdir@/lib/psm.c \
448 @top_srcdir@/lib/psm.h \
449 @top_srcdir@/lib/query.c \
450 @top_srcdir@/lib/rpmal.c \
451 @top_srcdir@/lib/rpmal.h \
452 @top_srcdir@/lib/rpmchecksig.c \
453 @top_srcdir@/lib/rpmds.c \
454 @top_srcdir@/lib/rpmds.h \
455 @top_srcdir@/lib/rpmcli.h \
456 @top_srcdir@/lib/rpminstall.c \
457 @top_srcdir@/lib/rpmlead.c \
458 @top_srcdir@/lib/rpmlead.h \
459 @top_srcdir@/lib/rpmlib.h \
460 @top_srcdir@/lib/rpmlibprov.c \
461 @top_srcdir@/lib/rpmps.c \
462 @top_srcdir@/lib/rpmps.h \
463 @top_srcdir@/lib/rpmrc.c \
464 @top_srcdir@/lib/rpmte.c \
465 @top_srcdir@/lib/rpmte.h \
466 @top_srcdir@/lib/rpmts.c \
467 @top_srcdir@/lib/rpmts.h \
468 @top_srcdir@/lib/rpmvercmp.c \
469 @top_srcdir@/lib/signature.c \
470 @top_srcdir@/lib/signature.h \
471 @top_srcdir@/lib/stringbuf.c \
472 @top_srcdir@/lib/stringbuf.h \
473 @top_srcdir@/lib/transaction.c \
474 @top_srcdir@/lib/verify.c \
475 @top_srcdir@/rpmdb/db3.c \
476 @top_srcdir@/rpmdb/dbconfig.c \
477 @top_srcdir@/rpmdb/fprint.c \
478 @top_srcdir@/rpmdb/fprint.h \
479 @top_srcdir@/rpmdb/hdrNVR.c \
480 @top_srcdir@/rpmdb/hdrinline.h \
481 @top_srcdir@/rpmdb/header.c \
482 @top_srcdir@/rpmdb/header.h \
483 @top_srcdir@/rpmdb/header_internal.c \
484 @top_srcdir@/rpmdb/header_internal.h \
485 @top_srcdir@/rpmdb/legacy.c \
486 @top_srcdir@/rpmdb/legacy.h \
487 @top_srcdir@/rpmdb/merge.c \
488 @top_srcdir@/rpmdb/poptDB.c \
489 @top_srcdir@/rpmdb/rpmhash.c \
490 @top_srcdir@/rpmdb/rpmhash.h \
491 @top_srcdir@/rpmdb/rpmdb.c \
492 @top_srcdir@/rpmdb/rpmdb.h \
493 @top_srcdir@/rpmdb/tagname.c \
494 @top_srcdir@/rpmdb/tagtbl.c \
495 @top_srcdir@/rpmio/digest.c \
496 @top_srcdir@/rpmio/fts.c \
497 @top_srcdir@/rpmio/fts.h \
498 @top_srcdir@/rpmio/macro.c \
499 @top_srcdir@/rpmio/rpmlog.c \
500 @top_srcdir@/rpmio/rpmlog.h \
501 @top_srcdir@/rpmio/rpmerr.h \
502 @top_srcdir@/rpmio/rpmio.c \
503 @top_srcdir@/rpmio/rpmio.h \
504 @top_srcdir@/rpmio/rpmio_internal.h \
505 @top_srcdir@/rpmio/rpmmacro.h \
506 @top_srcdir@/rpmio/rpmmalloc.c \
507 @top_srcdir@/rpmio/rpmmessages.h \
508 @top_srcdir@/rpmio/rpmpgp.c \
509 @top_srcdir@/rpmio/rpmpgp.h \
510 @top_srcdir@/rpmio/rpmrpc.c \
511 @top_srcdir@/rpmio/rpmurl.h \
512 @top_srcdir@/rpmio/strcasecmp.c \
513 @top_srcdir@/rpmio/stubs.c \
514 @top_srcdir@/rpmio/ugid.c \
515 @top_srcdir@/rpmio/ugid.h \
516 @top_srcdir@/rpmio/url.c \
517 @top_srcdir@/popt/findme.c \
518 @top_srcdir@/popt/findme.h \
519 @top_srcdir@/popt/popt.c \
520 @top_srcdir@/popt/popt.h \
521 @top_srcdir@/popt/poptconfig.c \
522 @top_srcdir@/popt/popthelp.c \
523 @top_srcdir@/popt/poptint.h \
524 @top_srcdir@/popt/poptparse.c \
525 @top_srcdir@/python/_rpmdb.c \
526 @top_srcdir@/python/hash.c \
527 @top_srcdir@/python/hash.h \
528 @top_srcdir@/python/header-py.c \
529 @top_srcdir@/python/header-py.h \
530 @top_srcdir@/python/rpmal-py.c \
531 @top_srcdir@/python/rpmal-py.h \
532 @top_srcdir@/python/rpmdb-py.c \
533 @top_srcdir@/python/rpmdb-py.h \
534 @top_srcdir@/python/rpmds-py.c \
535 @top_srcdir@/python/rpmds-py.h \
536 @top_srcdir@/python/rpmfd-py.c \
537 @top_srcdir@/python/rpmfd-py.h \
538 @top_srcdir@/python/rpmfi-py.c \
539 @top_srcdir@/python/rpmfi-py.h \
540 @top_srcdir@/python/rpmmi-py.c \
541 @top_srcdir@/python/rpmmi-py.h \
542 @top_srcdir@/python/rpmmodule.c \
543 @top_srcdir@/python/rpmrc-py.c \
544 @top_srcdir@/python/rpmrc-py.h \
545 @top_srcdir@/python/rpmte-py.c \
546 @top_srcdir@/python/rpmte-py.h \
547 @top_srcdir@/python/rpmts-py.c \
548 @top_srcdir@/python/rpmts-py.h \
549 @top_srcdir@/python/upgrade.c \
550 @top_srcdir@/python/upgrade.h \
551 @top_srcdir@/tools/dump.c \
552 @top_srcdir@/tools/dumpdb.c \
553 @top_srcdir@/tools/javadeps.c \
554 @top_srcdir@/tools/rpmarchive.c \
555 @top_srcdir@/tools/rpmcache.c \
556 @top_srcdir@/tools/rpmgraph.c \
557 @top_srcdir@/tools/rpmheader.c \
558 @top_srcdir@/tools/rpminject.c \
559 @top_srcdir@/tools/rpmlead.c \
560 @top_srcdir@/tools/rpmsignature.c
562 # If the value of the INPUT tag contains directories, you can use the
563 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
564 # and *.h) to filter out the source-files in the directories. If left
565 # blank the following patterns are tested:
566 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
569 FILE_PATTERNS = *.c *.h
571 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
572 # should be searched for input files as well. Possible values are YES and NO.
573 # If left blank NO is used.
577 # The EXCLUDE tag can be used to specify files and/or directories that should
578 # excluded from the INPUT source files. This way you can easily exclude a
579 # subdirectory from a directory tree whose root is specified with the INPUT tag.
583 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
584 # that are symbolic links (a Unix filesystem feature) are excluded from the input.
586 EXCLUDE_SYMLINKS = NO
588 # If the value of the INPUT tag contains directories, you can use the
589 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
590 # certain files from those directories.
594 # The EXAMPLE_PATH tag can be used to specify one or more files or
595 # directories that contain example code fragments that are included (see
596 # the \include command).
598 EXAMPLE_PATH = @top_srcdir@/doc/manual
600 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
601 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
602 # and *.h) to filter out the source-files in the directories. If left
603 # blank all files are included.
607 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
608 # searched for input files to be used with the \include or \dontinclude
609 # commands irrespective of the value of the RECURSIVE tag.
610 # Possible values are YES and NO. If left blank NO is used.
612 EXAMPLE_RECURSIVE = NO
614 # The IMAGE_PATH tag can be used to specify one or more files or
615 # directories that contain image that are included in the documentation (see
616 # the \image command).
620 # The INPUT_FILTER tag can be used to specify a program that doxygen should
621 # invoke to filter for each input file. Doxygen will invoke the filter program
622 # by executing (via popen()) the command <filter> <input-file>, where <filter>
623 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
624 # input file. Doxygen will then use the output that the filter program writes
625 # to standard output.
629 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
630 # INPUT_FILTER) will be used to filter the input files when producing source
633 FILTER_SOURCE_FILES = NO
635 #---------------------------------------------------------------------------
636 # configuration options related to source browsing
637 #---------------------------------------------------------------------------
639 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
640 # be generated. Documented entities will be cross-referenced with these sources.
644 # Setting the INLINE_SOURCES tag to YES will include the body
645 # of functions and classes directly in the documentation.
649 # If the REFERENCED_BY_RELATION tag is set to YES (the default)
650 # then for each documented function all documented
651 # functions referencing it will be listed.
653 REFERENCED_BY_RELATION = YES
655 # If the REFERENCES_RELATION tag is set to YES (the default)
656 # then for each documented function all documented entities
657 # called/used by that function will be listed.
659 REFERENCES_RELATION = YES
661 #---------------------------------------------------------------------------
662 # configuration options related to the alphabetical class index
663 #---------------------------------------------------------------------------
665 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
666 # of all compounds will be generated. Enable this if the project
667 # contains a lot of classes, structs, unions or interfaces.
669 ALPHABETICAL_INDEX = NO
671 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
672 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
673 # in which this list will be split (can be a number in the range [1..20])
675 COLS_IN_ALPHA_INDEX = 5
677 # In case all classes in a project start with a common prefix, all
678 # classes will be put under the same header in the alphabetical index.
679 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
680 # should be ignored while generating the index headers.
684 #---------------------------------------------------------------------------
685 # configuration options related to the HTML output
686 #---------------------------------------------------------------------------
688 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
689 # generate HTML output.
693 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
694 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
695 # put in front of it. If left blank `html' will be used as the default path.
699 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
700 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
701 # doxygen will generate files with .html extension.
703 HTML_FILE_EXTENSION = .html
705 # The HTML_HEADER tag can be used to specify a personal HTML header for
706 # each generated HTML page. If it is left blank doxygen will generate a
711 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
712 # each generated HTML page. If it is left blank doxygen will generate a
717 # The HTML_STYLESHEET tag can be used to specify a user defined cascading
718 # style sheet that is used by each HTML page. It can be used to
719 # fine-tune the look of the HTML output. If the tag is left blank doxygen
720 # will generate a default style sheet
724 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
725 # files or namespaces will be aligned in HTML using tables. If set to
726 # NO a bullet list will be used.
728 HTML_ALIGN_MEMBERS = YES
730 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
731 # will be generated that can be used as input for tools like the
732 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
733 # of the generated HTML documentation.
735 GENERATE_HTMLHELP = NO
737 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
738 # controls if a separate .chi index file is generated (YES) or that
739 # it should be included in the master .chm file (NO).
743 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
744 # controls whether a binary table of contents is generated (YES) or a
745 # normal table of contents (NO) in the .chm file.
749 # The TOC_EXPAND flag can be set to YES to add extra items for group members
750 # to the contents of the Html help documentation and to the tree view.
754 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
755 # top of each HTML page. The value NO (the default) enables the index and
756 # the value YES disables it.
760 # This tag can be used to set the number of enum values (range [1..20])
761 # that doxygen will group on one line in the generated HTML documentation.
763 ENUM_VALUES_PER_LINE = 4
765 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
766 # generated containing a tree-like index structure (just like the one that
767 # is generated for HTML Help). For this to work a browser that supports
768 # JavaScript and frames is required (for instance Mozilla, Netscape 4.0+,
769 # or Internet explorer 4.0+). Note that for large projects the tree generation
770 # can take a very long time. In such cases it is better to disable this feature.
771 # Windows users are probably better off using the HTML help feature.
773 GENERATE_TREEVIEW = NO
775 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
776 # used to set the initial width (in pixels) of the frame in which the tree
781 #---------------------------------------------------------------------------
782 # configuration options related to the LaTeX output
783 #---------------------------------------------------------------------------
785 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
786 # generate Latex output.
790 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
791 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
792 # put in front of it. If left blank `latex' will be used as the default path.
796 # 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.
798 LATEX_CMD_NAME = latex
800 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
801 # generate index for LaTeX. If left blank `makeindex' will be used as the
802 # default command name.
804 MAKEINDEX_CMD_NAME = makeindex
806 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
807 # LaTeX documents. This may be useful for small projects and may help to
808 # save some trees in general.
812 # The PAPER_TYPE tag can be used to set the paper type that is used
813 # by the printer. Possible values are: a4, a4wide, letter, legal and
814 # executive. If left blank a4wide will be used.
818 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
819 # packages that should be included in the LaTeX output.
823 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
824 # the generated latex document. The header should contain everything until
825 # the first chapter. If it is left blank doxygen will generate a
826 # standard header. Notice: only use this tag if you know what you are doing!
830 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
831 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
832 # contain links (just like the HTML output) instead of page references
833 # This makes the output suitable for online browsing using a pdf viewer.
837 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
838 # plain latex in the generated Makefile. Set this option to YES to get a
839 # higher quality PDF documentation.
843 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
844 # command to the generated LaTeX files. This will instruct LaTeX to keep
845 # running if errors occur, instead of asking the user for help.
846 # This option is also used when generating formulas in HTML.
850 #---------------------------------------------------------------------------
851 # configuration options related to the RTF output
852 #---------------------------------------------------------------------------
854 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
855 # The RTF output is optimised for Word 97 and may not look very pretty with
856 # other RTF readers or editors.
860 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
861 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
862 # put in front of it. If left blank `rtf' will be used as the default path.
866 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
867 # RTF documents. This may be useful for small projects and may help to
868 # save some trees in general.
872 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
873 # will contain hyperlink fields. The RTF file will
874 # contain links (just like the HTML output) instead of page references.
875 # This makes the output suitable for online browsing using WORD or other
876 # programs which support those fields.
877 # Note: wordpad (write) and others do not support links.
881 # Load stylesheet definitions from file. Syntax is similar to doxygen's
882 # config file, i.e. a series of assigments. You only have to provide
883 # replacements, missing definitions are set to their default value.
885 RTF_STYLESHEET_FILE =
887 # Set optional variables used in the generation of an rtf document.
888 # Syntax is similar to doxygen's config file.
890 RTF_EXTENSIONS_FILE =
892 #---------------------------------------------------------------------------
893 # configuration options related to the man page output
894 #---------------------------------------------------------------------------
896 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
901 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
902 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
903 # put in front of it. If left blank `man' will be used as the default path.
907 # The MAN_EXTENSION tag determines the extension that is added to
908 # the generated man pages (default is the subroutine's section .3)
912 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
913 # then it will generate one additional man file for each entity
914 # documented in the real man page(s). These additional files
915 # only source the real man page, but without them the man command
916 # would be unable to find the correct page. The default is NO.
920 #---------------------------------------------------------------------------
921 # configuration options related to the XML output
922 #---------------------------------------------------------------------------
924 # If the GENERATE_XML tag is set to YES Doxygen will
925 # generate an XML file that captures the structure of
926 # the code including all documentation. Note that this
927 # feature is still experimental and incomplete at the
932 #---------------------------------------------------------------------------
933 # configuration options for the AutoGen Definitions output
934 #---------------------------------------------------------------------------
936 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
937 # generate an AutoGen Definitions (see autogen.sf.net) file
938 # that captures the structure of the code including all
939 # documentation. Note that this feature is still experimental
940 # and incomplete at the moment.
942 GENERATE_AUTOGEN_DEF = NO
944 #---------------------------------------------------------------------------
945 # Configuration options related to the preprocessor
946 #---------------------------------------------------------------------------
948 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
949 # evaluate all C-preprocessor directives found in the sources and include
952 ENABLE_PREPROCESSING = YES
954 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
955 # names in the source code. If set to NO (the default) only conditional
956 # compilation will be performed. Macro expansion can be done in a controlled
957 # way by setting EXPAND_ONLY_PREDEF to YES.
959 MACRO_EXPANSION = YES
961 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
962 # then the macro expansion is limited to the macros specified with the
963 # PREDEFINED and EXPAND_AS_PREDEFINED tags.
965 EXPAND_ONLY_PREDEF = NO
967 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
968 # in the INCLUDE_PATH (see below) will be search if a #include is found.
970 SEARCH_INCLUDES = YES
972 # The INCLUDE_PATH tag can be used to specify one or more directories that
973 # contain include files that are not input files but should be processed by
978 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
979 # patterns (like *.h and *.hpp) to filter out the header-files in the
980 # directories. If left blank, the patterns specified with FILE_PATTERNS will
983 INCLUDE_FILE_PATTERNS =
985 # The PREDEFINED tag can be used to specify one or more macro names that
986 # are defined before the preprocessor is started (similar to the -D option of
987 # gcc). The argument of the tag is a list of macros of the form: name
988 # or name=definition (no spaces). If the definition and the = are
989 # omitted =1 is assumed.
993 # If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then
994 # this tag can be used to specify a list of macro names that should be expanded.
995 # The macro definition that is found in the sources will be used.
996 # Use the PREDEFINED tag if you want to use a different macro definition.
1000 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1001 # doxygen's preprocessor will remove all function-like macros that are alone
1002 # on a line and do not end with a semicolon. Such function macros are typically
1003 # used for boiler-plate code, and will confuse the parser if not removed.
1005 SKIP_FUNCTION_MACROS = YES
1007 #---------------------------------------------------------------------------
1008 # Configuration::addtions related to external references
1009 #---------------------------------------------------------------------------
1011 # The TAGFILES tag can be used to specify one or more tagfiles.
1015 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1016 # a tag file that is based on the input files it reads.
1018 GENERATE_TAGFILE = Doxytags
1020 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1021 # in the class index. If set to NO only the inherited external classes
1026 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1027 # in the modules index. If set to NO, only the current project's groups will
1030 EXTERNAL_GROUPS = YES
1032 # The PERL_PATH should be the absolute path and name of the perl script
1033 # interpreter (i.e. the result of `which perl').
1035 PERL_PATH = /usr/bin/perl
1037 #---------------------------------------------------------------------------
1038 # Configuration options related to the dot tool
1039 #---------------------------------------------------------------------------
1041 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1042 # generate a inheritance diagram (in Html, RTF and LaTeX) for classes with base or
1043 # super classes. Setting the tag to NO turns the diagrams off. Note that this
1044 # option is superceded by the HAVE_DOT option below. This is only a fallback. It is
1045 # recommended to install and use dot, since it yield more powerful graphs.
1047 CLASS_DIAGRAMS = YES
1049 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1050 # available from the path. This tool is part of Graphviz, a graph visualization
1051 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
1052 # have no effect if this option is set to NO (the default)
1056 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1057 # will generate a graph for each documented class showing the direct and
1058 # indirect inheritance relations. Setting this tag to YES will force the
1059 # the CLASS_DIAGRAMS tag to NO.
1063 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1064 # will generate a graph for each documented class showing the direct and
1065 # indirect implementation dependencies (inheritance, containment, and
1066 # class references variables) of the class with other documented classes.
1068 COLLABORATION_GRAPH = YES
1070 # If set to YES, the inheritance and collaboration graphs will show the
1071 # relations between templates and their instances.
1073 TEMPLATE_RELATIONS = YES
1075 # If set to YES, the inheritance and collaboration graphs will hide
1076 # inheritance and usage relations if the target is undocumented
1077 # or is not a class.
1079 HIDE_UNDOC_RELATIONS = YES
1081 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1082 # tags are set to YES then doxygen will generate a graph for each documented
1083 # file showing the direct and indirect include dependencies of the file with
1084 # other documented files.
1088 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1089 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1090 # documented header file showing the documented files that directly or
1091 # indirectly include this file.
1093 INCLUDED_BY_GRAPH = YES
1095 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1096 # will graphical hierarchy of all classes instead of a textual one.
1098 GRAPHICAL_HIERARCHY = YES
1100 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1101 # generated by dot. Possible values are png, jpg, or gif
1102 # If left blank png will be used.
1104 DOT_IMAGE_FORMAT = png
1106 # The tag DOT_PATH can be used to specify the path where the dot tool can be
1107 # found. If left blank, it is assumed the dot tool can be found on the path.
1111 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1112 # contain dot files that are included in the documentation (see the
1113 # \dotfile command).
1117 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1118 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1119 # this value, doxygen will try to truncate the graph, so that it fits within
1120 # the specified constraint. Beware that most browsers cannot cope with very
1123 MAX_DOT_GRAPH_WIDTH = 1024
1125 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1126 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1127 # this value, doxygen will try to truncate the graph, so that it fits within
1128 # the specified constraint. Beware that most browsers cannot cope with very
1131 MAX_DOT_GRAPH_HEIGHT = 1024
1133 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1134 # generate a legend page explaining the meaning of the various boxes and
1135 # arrows in the dot generated graphs.
1137 GENERATE_LEGEND = YES
1139 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1140 # remove the intermedate dot files that are used to generate
1141 # the various graphs.
1145 #---------------------------------------------------------------------------
1146 # Configuration::addtions related to the search engine
1147 #---------------------------------------------------------------------------
1149 # The SEARCHENGINE tag specifies whether or not a search engine should be
1150 # used. If set to NO the values of all tags below this one will be ignored.
1154 # The CGI_NAME tag should be the name of the CGI script that
1155 # starts the search engine (doxysearch) with the correct parameters.
1156 # A script with this name will be generated by doxygen.
1158 CGI_NAME = search.cgi
1160 # The CGI_URL tag should be the absolute URL to the directory where the
1161 # cgi binaries are located. See the documentation of your http daemon for
1166 # The DOC_URL tag should be the absolute URL to the directory where the
1167 # documentation is located. If left blank the absolute path to the
1168 # documentation, with file:// prepended to it, will be used.
1172 # The DOC_ABSPATH tag should be the absolute path to the directory where the
1173 # documentation is located. If left blank the directory on the local machine
1178 # The BIN_ABSPATH tag must point to the directory where the doxysearch binary
1181 BIN_ABSPATH = /usr/local/bin/
1183 # The EXT_DOC_PATHS tag can be used to specify one or more paths to
1184 # documentation generated for other projects. This allows doxysearch to search
1185 # the documentation for these projects as well.