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 # Project related 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, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch,
40 # Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en
41 # (Japanese with English messages), Korean, Norwegian, Polish, Portuguese,
42 # Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
44 OUTPUT_LANGUAGE = English
46 # This tag can be used to specify the encoding used in the generated output.
47 # The encoding is not always determined by the language that is chosen,
48 # but also whether or not the output is meant for Windows or non-Windows users.
49 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES
50 # forces the Windows encoding (this is the default for the Windows binary),
51 # whereas setting the tag to NO uses a Unix-style encoding (the default for
52 # all platforms other than Windows).
54 USE_WINDOWS_ENCODING = NO
56 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
57 # include brief member descriptions after the members that are listed in
58 # the file and class documentation (similar to JavaDoc).
59 # Set to NO to disable this.
61 BRIEF_MEMBER_DESC = YES
63 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
64 # the brief description of a member or function before the detailed description.
65 # Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
66 # brief descriptions will be completely suppressed.
70 # This tag implements a quasi-intelligent brief description abbreviator
71 # that is used to form the text in various listings. Each string
72 # in this list, if found as the leading text of the brief description, will be
73 # stripped from the text and the result after processing the whole list, is used
74 # as the annotated text. Otherwise, the brief description is used as-is. If left
75 # blank, the following values are used ("$name" is automatically replaced with the
76 # name of the entity): "The $name class" "The $name widget" "The $name file"
77 # "is" "provides" "specifies" "contains" "represents" "a" "an" "the"
81 # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
82 # Doxygen will generate a detailed section even if there is only a brief
85 ALWAYS_DETAILED_SEC = NO
87 # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all inherited
88 # members of a class in the documentation of that class as if those members were
89 # ordinary class members. Constructors, destructors and assignment operators of
90 # the base classes will not be shown.
92 INLINE_INHERITED_MEMB = NO
94 # If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
95 # path before files name in the file list and in the header files. If set
96 # to NO the shortest path that makes the file name unique will be used.
100 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
101 # can be used to strip a user-defined part of the path. Stripping is
102 # only done if one of the specified strings matches the left-hand part of
103 # the path. It is allowed to use relative paths in the argument list.
105 STRIP_FROM_PATH = @top_srcdir@/
107 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
108 # (but less readable) file names. This can be useful is your file systems
109 # doesn't support long names like on DOS, Mac, or CD-ROM.
113 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
114 # will interpret the first line (until the first dot) of a JavaDoc-style
115 # comment as the brief description. If set to NO, the JavaDoc
116 # comments will behave just like the Qt-style comments (thus requiring an
117 # explicit @brief command for a brief description.
119 JAVADOC_AUTOBRIEF = YES
121 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
122 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
123 # comments) as a brief description. This used to be the default behaviour.
124 # The new default is to treat a multi-line C++ comment block as a detailed
125 # description. Set this tag to YES if you prefer the old behaviour instead.
127 MULTILINE_CPP_IS_BRIEF = NO
129 # If the DETAILS_AT_TOP tag is set to YES then Doxygen
130 # will output the detailed description near the top, like JavaDoc.
131 # If set to NO, the detailed description appears after the member
136 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
137 # member inherits the documentation from any documented member that it
142 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
143 # tag is set to YES, then doxygen will reuse the documentation of the first
144 # member in the group (if any) for the other members of the group. By default
145 # all members of a group must be documented explicitly.
147 DISTRIBUTE_GROUP_DOC = NO
149 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
150 # Doxygen uses this value to replace tabs by spaces in code fragments.
154 # This tag can be used to specify a number of aliases that acts
155 # as commands in the documentation. An alias has the form "name=value".
156 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
157 # put the command \sideeffect (or @sideeffect) in the documentation, which
158 # will result in a user-defined paragraph with heading "Side Effects:".
159 # You can put \n's in the value part of an alias to insert newlines.
163 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
164 # only. Doxygen will then generate output that is more tailored for C.
165 # For instance, some of the names that are used will be different. The list
166 # of all members will be omitted, etc.
168 OPTIMIZE_OUTPUT_FOR_C = YES
170 # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java sources
171 # only. Doxygen will then generate output that is more tailored for Java.
172 # For instance, namespaces will be presented as packages, qualified scopes
173 # will look different, etc.
175 OPTIMIZE_OUTPUT_JAVA = NO
177 # Set the SUBGROUPING tag to YES (the default) to allow class member groups of
178 # the same type (for instance a group of public functions) to be put as a
179 # subgroup of that type (e.g. under the Public Functions section). Set it to
180 # NO to prevent subgrouping. Alternatively, this can be done per class using
181 # the \nosubgrouping command.
185 #---------------------------------------------------------------------------
186 # Build related configuration options
187 #---------------------------------------------------------------------------
189 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
190 # documentation are documented, even if no documentation was available.
191 # Private class members and static file members will be hidden unless
192 # the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
196 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
197 # will be included in the documentation.
201 # If the EXTRACT_STATIC tag is set to YES all static members of a file
202 # will be included in the documentation.
206 # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
207 # defined locally in source files will be included in the documentation.
208 # If set to NO only classes defined in header files are included.
210 EXTRACT_LOCAL_CLASSES = YES
212 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
213 # undocumented members of documented classes, files or namespaces.
214 # If set to NO (the default) these members will be included in the
215 # various overviews, but no documentation section is generated.
216 # This option has no effect if EXTRACT_ALL is enabled.
218 HIDE_UNDOC_MEMBERS = NO
220 # If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
221 # undocumented classes that are normally visible in the class hierarchy.
222 # If set to NO (the default) these classes will be included in the various
223 # overviews. This option has no effect if EXTRACT_ALL is enabled.
225 HIDE_UNDOC_CLASSES = NO
227 # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
228 # friend (class|struct|union) declarations.
229 # If set to NO (the default) these declarations will be included in the
232 HIDE_FRIEND_COMPOUNDS = NO
234 # If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
235 # documentation blocks found inside the body of a function.
236 # If set to NO (the default) these blocks will be appended to the
237 # function's detailed documentation block.
239 HIDE_IN_BODY_DOCS = NO
241 # The INTERNAL_DOCS tag determines if documentation
242 # that is typed after a \internal command is included. If the tag is set
243 # to NO (the default) then the documentation will be excluded.
244 # Set it to YES to include the internal documentation.
248 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
249 # file names in lower-case letters. If set to YES upper-case letters are also
250 # allowed. This is useful if you have classes or files whose names only differ
251 # in case and if your file system supports case sensitive file names. Windows
252 # users are advised to set this option to NO.
254 CASE_SENSE_NAMES = YES
256 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
257 # will show members with their full class and namespace scopes in the
258 # documentation. If set to YES the scope will be hidden.
260 HIDE_SCOPE_NAMES = NO
262 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
263 # will put a list of the files that are included by a file in the documentation
266 SHOW_INCLUDE_FILES = YES
268 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
269 # is inserted in the documentation for inline members.
273 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
274 # will sort the (detailed) documentation of file and class members
275 # alphabetically by member name. If set to NO the members will appear in
278 SORT_MEMBER_DOCS = YES
280 # The GENERATE_TODOLIST tag can be used to enable (YES) or
281 # disable (NO) the todo list. This list is created by putting \todo
282 # commands in the documentation.
284 GENERATE_TODOLIST = YES
286 # The GENERATE_TESTLIST tag can be used to enable (YES) or
287 # disable (NO) the test list. This list is created by putting \test
288 # commands in the documentation.
290 GENERATE_TESTLIST = YES
292 # The GENERATE_BUGLIST tag can be used to enable (YES) or
293 # disable (NO) the bug list. This list is created by putting \bug
294 # commands in the documentation.
296 GENERATE_BUGLIST = YES
298 # The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
299 # disable (NO) the deprecated list. This list is created by putting
300 # \deprecated commands in the documentation.
302 GENERATE_DEPRECATEDLIST= YES
304 # The ENABLED_SECTIONS tag can be used to enable conditional
305 # documentation sections, marked by \if sectionname ... \endif.
309 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
310 # the initial value of a variable or define consists of for it to appear in
311 # the documentation. If the initializer consists of more lines than specified
312 # here it will be hidden. Use a value of 0 to hide initializers completely.
313 # The appearance of the initializer of individual variables and defines in the
314 # documentation can be controlled using \showinitializer or \hideinitializer
315 # command in the documentation regardless of this setting.
317 MAX_INITIALIZER_LINES = 30
319 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated
320 # at the bottom of the documentation of classes and structs. If set to YES the
321 # list will mention the files that were used to generate the documentation.
323 SHOW_USED_FILES = YES
325 #---------------------------------------------------------------------------
326 # configuration options related to warning and progress messages
327 #---------------------------------------------------------------------------
329 # The QUIET tag can be used to turn on/off the messages that are generated
330 # by doxygen. Possible values are YES and NO. If left blank NO is used.
334 # The WARNINGS tag can be used to turn on/off the warning messages that are
335 # generated by doxygen. Possible values are YES and NO. If left blank
340 # If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
341 # for undocumented members. If EXTRACT_ALL is set to YES then this flag will
342 # automatically be disabled.
344 WARN_IF_UNDOCUMENTED = YES
346 # If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
347 # potential errors in the documentation, such as not documenting some
348 # parameters in a documented function, or documenting parameters that
349 # don't exist or using markup commands wrongly.
351 WARN_IF_DOC_ERROR = YES
353 # The WARN_FORMAT tag determines the format of the warning messages that
354 # doxygen can produce. The string should contain the $file, $line, and $text
355 # tags, which will be replaced by the file and line number from which the
356 # warning originated and the warning text.
358 WARN_FORMAT = "$file:$line: $text"
360 # The WARN_LOGFILE tag can be used to specify a file to which warning
361 # and error messages should be written. If left blank the output is written
366 #---------------------------------------------------------------------------
367 # configuration options related to the input files
368 #---------------------------------------------------------------------------
370 # The INPUT tag can be used to specify the files and/or directories that contain
371 # documented source files. You may enter file names like "myfile.cpp" or
372 # directories like "/usr/src/myproject". Separate the files or directories
375 INPUT = @top_srcdir@/Doxyheader \
376 @top_srcdir@/build.c \
377 @top_srcdir@/build.h \
378 @top_srcdir@/config.h \
379 @top_srcdir@/debug.h \
380 @top_srcdir@/macros \
381 @top_srcdir@/rpmqv.c \
382 @top_srcdir@/rpmpopt-@VERSION@ \
384 @top_srcdir@/rpm2cpio.c \
385 @top_srcdir@/system.h \
386 @top_srcdir@/build/build.c \
387 @top_srcdir@/build/buildio.h \
388 @top_srcdir@/build/expression.c \
389 @top_srcdir@/build/files.c \
390 @top_srcdir@/build/misc.c \
391 @top_srcdir@/build/names.c \
392 @top_srcdir@/build/pack.c \
393 @top_srcdir@/build/parseBuildInstallClean.c \
394 @top_srcdir@/build/parseChangelog.c \
395 @top_srcdir@/build/parseDescription.c \
396 @top_srcdir@/build/parseFiles.c \
397 @top_srcdir@/build/parsePreamble.c \
398 @top_srcdir@/build/parsePrep.c \
399 @top_srcdir@/build/parseReqs.c \
400 @top_srcdir@/build/parseScript.c \
401 @top_srcdir@/build/parseSpec.c \
402 @top_srcdir@/build/poptBT.c \
403 @top_srcdir@/build/reqprov.c \
404 @top_srcdir@/build/rpmbuild.h \
405 @top_srcdir@/build/rpmfc.c \
406 @top_srcdir@/build/rpmfc.h \
407 @top_srcdir@/build/rpmspec.h \
408 @top_srcdir@/build/spec.c \
409 @top_srcdir@/doc/manual/builddependencies \
410 @top_srcdir@/doc/manual/buildroot \
411 @top_srcdir@/doc/manual/conditionalbuilds \
412 @top_srcdir@/doc/manual/dependencies \
413 @top_srcdir@/doc/manual/format \
414 @top_srcdir@/doc/manual/hregions \
415 @top_srcdir@/doc/manual/macros \
416 @top_srcdir@/doc/manual/multiplebuilds \
417 @top_srcdir@/doc/manual/queryformat \
418 @top_srcdir@/doc/manual/signatures \
419 @top_srcdir@/doc/manual/relocatable \
420 @top_srcdir@/doc/manual/spec \
421 @top_srcdir@/doc/manual/triggers \
422 @top_srcdir@/doc/manual/tsort \
423 @top_srcdir@/file/src/apprentice.c \
424 @top_srcdir@/file/src/ascmagic.c \
425 @top_srcdir@/file/src/compress.c \
426 @top_srcdir@/file/src/file.c \
427 @top_srcdir@/file/src/file.h \
428 @top_srcdir@/file/src/fsmagic.c \
429 @top_srcdir@/file/src/names.h \
430 @top_srcdir@/file/src/print.c \
431 @top_srcdir@/file/src/readelf.c \
432 @top_srcdir@/file/src/readelf.h \
433 @top_srcdir@/file/src/softmagic.c \
434 @top_srcdir@/file/src/tar.h \
435 @top_srcdir@/lib/cpio.c \
436 @top_srcdir@/lib/cpio.h \
437 @top_srcdir@/lib/depends.c \
438 @top_srcdir@/lib/formats.c \
439 @top_srcdir@/lib/fs.c \
440 @top_srcdir@/lib/fsm.c \
441 @top_srcdir@/lib/fsm.h \
442 @top_srcdir@/lib/manifest.c \
443 @top_srcdir@/lib/manifest.h \
444 @top_srcdir@/lib/misc.c \
445 @top_srcdir@/lib/misc.h \
446 @top_srcdir@/lib/package.c \
447 @top_srcdir@/lib/poptALL.c \
448 @top_srcdir@/lib/poptI.c \
449 @top_srcdir@/lib/poptQV.c \
450 @top_srcdir@/lib/psm.c \
451 @top_srcdir@/lib/psm.h \
452 @top_srcdir@/lib/query.c \
453 @top_srcdir@/lib/rpmal.c \
454 @top_srcdir@/lib/rpmal.h \
455 @top_srcdir@/lib/rpmchecksig.c \
456 @top_srcdir@/lib/rpmcli.h \
457 @top_srcdir@/lib/rpmds.c \
458 @top_srcdir@/lib/rpmds.h \
459 @top_srcdir@/lib/rpmfi.c \
460 @top_srcdir@/lib/rpmfi.h \
461 @top_srcdir@/lib/rpmgi.c \
462 @top_srcdir@/lib/rpmgi.h \
463 @top_srcdir@/lib/rpminstall.c \
464 @top_srcdir@/lib/rpmlead.c \
465 @top_srcdir@/lib/rpmlead.h \
466 @top_srcdir@/lib/rpmlib.h \
467 @top_srcdir@/lib/rpmlibprov.c \
468 @top_srcdir@/lib/rpmps.c \
469 @top_srcdir@/lib/rpmps.h \
470 @top_srcdir@/lib/rpmrc.c \
471 @top_srcdir@/lib/rpmsx.c \
472 @top_srcdir@/lib/rpmsx.h \
473 @top_srcdir@/lib/rpmte.c \
474 @top_srcdir@/lib/rpmte.h \
475 @top_srcdir@/lib/rpmts.c \
476 @top_srcdir@/lib/rpmts.h \
477 @top_srcdir@/lib/rpmvercmp.c \
478 @top_srcdir@/lib/signature.c \
479 @top_srcdir@/lib/signature.h \
480 @top_srcdir@/lib/stringbuf.c \
481 @top_srcdir@/lib/stringbuf.h \
482 @top_srcdir@/lib/transaction.c \
483 @top_srcdir@/lib/verify.c \
484 @top_srcdir@/lua/lapi.c \
485 @top_srcdir@/lua/lapi.h \
486 @top_srcdir@/lua/lcode.c \
487 @top_srcdir@/lua/lcode.h \
488 @top_srcdir@/lua/ldebug.c \
489 @top_srcdir@/lua/ldebug.h \
490 @top_srcdir@/lua/ldo.c \
491 @top_srcdir@/lua/ldo.h \
492 @top_srcdir@/lua/ldump.c \
493 @top_srcdir@/lua/lfunc.c \
494 @top_srcdir@/lua/lfunc.h \
495 @top_srcdir@/lua/lgc.c \
496 @top_srcdir@/lua/lgc.h \
497 @top_srcdir@/lua/llex.c \
498 @top_srcdir@/lua/llex.h \
499 @top_srcdir@/lua/llimits.h \
500 @top_srcdir@/lua/lmem.c \
501 @top_srcdir@/lua/lmem.h \
502 @top_srcdir@/lua/lobject.c \
503 @top_srcdir@/lua/lobject.h \
504 @top_srcdir@/lua/lopcodes.c \
505 @top_srcdir@/lua/lopcodes.h \
506 @top_srcdir@/lua/lparser.c \
507 @top_srcdir@/lua/lparser.h \
508 @top_srcdir@/lua/lstate.c \
509 @top_srcdir@/lua/lstate.h \
510 @top_srcdir@/lua/lstring.c \
511 @top_srcdir@/lua/lstring.h \
512 @top_srcdir@/lua/ltable.c \
513 @top_srcdir@/lua/ltable.h \
514 @top_srcdir@/lua/ltests.c \
515 @top_srcdir@/lua/ltm.c \
516 @top_srcdir@/lua/ltm.h \
517 @top_srcdir@/lua/lundump.c \
518 @top_srcdir@/lua/lundump.h \
519 @top_srcdir@/lua/lvm.c \
520 @top_srcdir@/lua/lvm.h \
521 @top_srcdir@/lua/lzio.c \
522 @top_srcdir@/lua/lzio.h \
523 @top_srcdir@/rpmdb/db3.c \
524 @top_srcdir@/rpmdb/dbconfig.c \
525 @top_srcdir@/rpmdb/fprint.c \
526 @top_srcdir@/rpmdb/fprint.h \
527 @top_srcdir@/rpmdb/hdrNVR.c \
528 @top_srcdir@/rpmdb/hdrinline.h \
529 @top_srcdir@/rpmdb/header.c \
530 @top_srcdir@/rpmdb/header.h \
531 @top_srcdir@/rpmdb/header_internal.c \
532 @top_srcdir@/rpmdb/header_internal.h \
533 @top_srcdir@/rpmdb/legacy.c \
534 @top_srcdir@/rpmdb/legacy.h \
535 @top_srcdir@/rpmdb/merge.c \
536 @top_srcdir@/rpmdb/poptDB.c \
537 @top_srcdir@/rpmdb/rpmhash.c \
538 @top_srcdir@/rpmdb/rpmhash.h \
539 @top_srcdir@/rpmdb/rpmdb.c \
540 @top_srcdir@/rpmdb/rpmdb.h \
541 @top_srcdir@/rpmdb/tagname.c \
542 @top_srcdir@/rpmdb/tagtbl.c \
543 @top_srcdir@/rpmio/argv.c \
544 @top_srcdir@/rpmio/argv.h \
545 @top_srcdir@/rpmio/digest.c \
546 @top_srcdir@/rpmio/fts.c \
547 @top_srcdir@/rpmio/fts.h \
548 @top_srcdir@/rpmio/macro.c \
549 @top_srcdir@/rpmio/rpmlog.c \
550 @top_srcdir@/rpmio/rpmlog.h \
551 @top_srcdir@/rpmio/rpmerr.h \
552 @top_srcdir@/rpmio/rpmio.c \
553 @top_srcdir@/rpmio/rpmio.h \
554 @top_srcdir@/rpmio/rpmio_internal.h \
555 @top_srcdir@/rpmio/rpmmacro.h \
556 @top_srcdir@/rpmio/rpmmalloc.c \
557 @top_srcdir@/rpmio/rpmmessages.h \
558 @top_srcdir@/rpmio/rpmpgp.c \
559 @top_srcdir@/rpmio/rpmpgp.h \
560 @top_srcdir@/rpmio/rpmrpc.c \
561 @top_srcdir@/rpmio/rpmsq.c \
562 @top_srcdir@/rpmio/rpmsq.h \
563 @top_srcdir@/rpmio/rpmsw.c \
564 @top_srcdir@/rpmio/rpmsw.h \
565 @top_srcdir@/rpmio/rpmurl.h \
566 @top_srcdir@/rpmio/strcasecmp.c \
567 @top_srcdir@/rpmio/stubs.c \
568 @top_srcdir@/rpmio/ugid.c \
569 @top_srcdir@/rpmio/ugid.h \
570 @top_srcdir@/rpmio/url.c \
571 @top_srcdir@/popt/findme.c \
572 @top_srcdir@/popt/findme.h \
573 @top_srcdir@/popt/popt.c \
574 @top_srcdir@/popt/popt.h \
575 @top_srcdir@/popt/poptconfig.c \
576 @top_srcdir@/popt/popthelp.c \
577 @top_srcdir@/popt/poptint.h \
578 @top_srcdir@/popt/poptparse.c \
579 @top_srcdir@/python/header-py.c \
580 @top_srcdir@/python/header-py.h \
581 @top_srcdir@/python/rpmal-py.c \
582 @top_srcdir@/python/rpmal-py.h \
583 @top_srcdir@/python/rpmdb-py.c \
584 @top_srcdir@/python/rpmdb-py.h \
585 @top_srcdir@/python/rpmds-py.c \
586 @top_srcdir@/python/rpmds-py.h \
587 @top_srcdir@/python/rpmfd-py.c \
588 @top_srcdir@/python/rpmfd-py.h \
589 @top_srcdir@/python/rpmfi-py.c \
590 @top_srcdir@/python/rpmfi-py.h \
591 @top_srcdir@/python/rpmfts-py.c \
592 @top_srcdir@/python/rpmfts-py.h \
593 @top_srcdir@/python/rpmmi-py.c \
594 @top_srcdir@/python/rpmmi-py.h \
595 @top_srcdir@/python/rpmmodule.c \
596 @top_srcdir@/python/rpmrc-py.c \
597 @top_srcdir@/python/rpmrc-py.h \
598 @top_srcdir@/python/rpmte-py.c \
599 @top_srcdir@/python/rpmte-py.h \
600 @top_srcdir@/python/rpmts-py.c \
601 @top_srcdir@/python/rpmts-py.h \
602 @top_srcdir@/tools/dumpdb.c \
603 @top_srcdir@/tools/javadeps.c \
604 @top_srcdir@/tools/rpmcache.c \
605 @top_srcdir@/tools/rpmdeps.c \
606 @top_srcdir@/tools/rpmgraph.c \
607 @top_srcdir@/tools/rpminject.c \
608 @top_srcdir@/tools/rpmtool.c \
609 @top_srcdir@/tools/rpmxml.c \
610 @top_srcdir@/tools/rpmxp.c
612 # If the value of the INPUT tag contains directories, you can use the
613 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
614 # and *.h) to filter out the source-files in the directories. If left
615 # blank the following patterns are tested:
616 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
617 # *.h++ *.idl *.odl *.cs *.php *.php3 *.inc
619 FILE_PATTERNS = *.c \
622 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
623 # should be searched for input files as well. Possible values are YES and NO.
624 # If left blank NO is used.
628 # The EXCLUDE tag can be used to specify files and/or directories that should
629 # excluded from the INPUT source files. This way you can easily exclude a
630 # subdirectory from a directory tree whose root is specified with the INPUT tag.
634 # The EXCLUDE_SYMLINKS tag can be used select whether or not files or directories
635 # that are symbolic links (a Unix filesystem feature) are excluded from the input.
637 EXCLUDE_SYMLINKS = NO
639 # If the value of the INPUT tag contains directories, you can use the
640 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
641 # certain files from those directories.
645 # The EXAMPLE_PATH tag can be used to specify one or more files or
646 # directories that contain example code fragments that are included (see
647 # the \include command).
649 EXAMPLE_PATH = @top_srcdir@/doc/manual
651 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
652 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
653 # and *.h) to filter out the source-files in the directories. If left
654 # blank all files are included.
658 # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
659 # searched for input files to be used with the \include or \dontinclude
660 # commands irrespective of the value of the RECURSIVE tag.
661 # Possible values are YES and NO. If left blank NO is used.
663 EXAMPLE_RECURSIVE = NO
665 # The IMAGE_PATH tag can be used to specify one or more files or
666 # directories that contain image that are included in the documentation (see
667 # the \image command).
671 # The INPUT_FILTER tag can be used to specify a program that doxygen should
672 # invoke to filter for each input file. Doxygen will invoke the filter program
673 # by executing (via popen()) the command <filter> <input-file>, where <filter>
674 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
675 # input file. Doxygen will then use the output that the filter program writes
676 # to standard output.
680 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
681 # INPUT_FILTER) will be used to filter the input files when producing source
682 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
684 FILTER_SOURCE_FILES = NO
686 #---------------------------------------------------------------------------
687 # configuration options related to source browsing
688 #---------------------------------------------------------------------------
690 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
691 # be generated. Documented entities will be cross-referenced with these sources.
692 # Note: To get rid of all source code in the generated output, make sure also
693 # VERBATIM_HEADERS is set to NO.
697 # Setting the INLINE_SOURCES tag to YES will include the body
698 # of functions and classes directly in the documentation.
702 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
703 # doxygen to hide any special comment blocks from generated source code
704 # fragments. Normal C and C++ comments will always remain visible.
706 STRIP_CODE_COMMENTS = YES
708 # If the REFERENCED_BY_RELATION tag is set to YES (the default)
709 # then for each documented function all documented
710 # functions referencing it will be listed.
712 REFERENCED_BY_RELATION = YES
714 # If the REFERENCES_RELATION tag is set to YES (the default)
715 # then for each documented function all documented entities
716 # called/used by that function will be listed.
718 REFERENCES_RELATION = YES
720 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
721 # will generate a verbatim copy of the header file for each class for
722 # which an include is specified. Set to NO to disable this.
724 VERBATIM_HEADERS = YES
726 #---------------------------------------------------------------------------
727 # configuration options related to the alphabetical class index
728 #---------------------------------------------------------------------------
730 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
731 # of all compounds will be generated. Enable this if the project
732 # contains a lot of classes, structs, unions or interfaces.
734 ALPHABETICAL_INDEX = NO
736 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
737 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
738 # in which this list will be split (can be a number in the range [1..20])
740 COLS_IN_ALPHA_INDEX = 5
742 # In case all classes in a project start with a common prefix, all
743 # classes will be put under the same header in the alphabetical index.
744 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
745 # should be ignored while generating the index headers.
749 #---------------------------------------------------------------------------
750 # configuration options related to the HTML output
751 #---------------------------------------------------------------------------
753 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
754 # generate HTML output.
758 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
759 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
760 # put in front of it. If left blank `html' will be used as the default path.
764 # The HTML_FILE_EXTENSION tag can be used to specify the file extension for
765 # each generated HTML page (for example: .htm,.php,.asp). If it is left blank
766 # doxygen will generate files with .html extension.
768 HTML_FILE_EXTENSION = .html
770 # The HTML_HEADER tag can be used to specify a personal HTML header for
771 # each generated HTML page. If it is left blank doxygen will generate a
776 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
777 # each generated HTML page. If it is left blank doxygen will generate a
782 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
783 # style sheet that is used by each HTML page. It can be used to
784 # fine-tune the look of the HTML output. If the tag is left blank doxygen
785 # will generate a default style sheet. Note that doxygen will try to copy
786 # the style sheet file to the HTML output directory, so don't put your own
787 # stylesheet in the HTML output directory as well, or it will be erased!
791 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
792 # files or namespaces will be aligned in HTML using tables. If set to
793 # NO a bullet list will be used.
795 HTML_ALIGN_MEMBERS = YES
797 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
798 # will be generated that can be used as input for tools like the
799 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
800 # of the generated HTML documentation.
802 GENERATE_HTMLHELP = NO
804 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
805 # be used to specify the file name of the resulting .chm file. You
806 # can add a path in front of the file if the result should not be
807 # written to the html output directory.
811 # If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
812 # be used to specify the location (absolute path including file name) of
813 # the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
814 # the HTML help compiler on the generated index.hhp.
818 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
819 # controls if a separate .chi index file is generated (YES) or that
820 # it should be included in the master .chm file (NO).
824 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
825 # controls whether a binary table of contents is generated (YES) or a
826 # normal table of contents (NO) in the .chm file.
830 # The TOC_EXPAND flag can be set to YES to add extra items for group members
831 # to the contents of the HTML help documentation and to the tree view.
835 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
836 # top of each HTML page. The value NO (the default) enables the index and
837 # the value YES disables it.
841 # This tag can be used to set the number of enum values (range [1..20])
842 # that doxygen will group on one line in the generated HTML documentation.
844 ENUM_VALUES_PER_LINE = 4
846 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
847 # generated containing a tree-like index structure (just like the one that
848 # is generated for HTML Help). For this to work a browser that supports
849 # JavaScript, DHTML, CSS and frames is required (for instance Mozilla 1.0+,
850 # Netscape 6.0+, Internet explorer 5.0+, or Konqueror). Windows users are
851 # probably better off using the HTML help feature.
853 GENERATE_TREEVIEW = NO
855 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
856 # used to set the initial width (in pixels) of the frame in which the tree
861 #---------------------------------------------------------------------------
862 # configuration options related to the LaTeX output
863 #---------------------------------------------------------------------------
865 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
866 # generate Latex output.
870 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
871 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
872 # put in front of it. If left blank `latex' will be used as the default path.
876 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
877 # invoked. If left blank `latex' will be used as the default command name.
879 LATEX_CMD_NAME = latex
881 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
882 # generate index for LaTeX. If left blank `makeindex' will be used as the
883 # default command name.
885 MAKEINDEX_CMD_NAME = makeindex
887 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
888 # LaTeX documents. This may be useful for small projects and may help to
889 # save some trees in general.
893 # The PAPER_TYPE tag can be used to set the paper type that is used
894 # by the printer. Possible values are: a4, a4wide, letter, legal and
895 # executive. If left blank a4wide will be used.
899 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
900 # packages that should be included in the LaTeX output.
904 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
905 # the generated latex document. The header should contain everything until
906 # the first chapter. If it is left blank doxygen will generate a
907 # standard header. Notice: only use this tag if you know what you are doing!
911 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
912 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
913 # contain links (just like the HTML output) instead of page references
914 # This makes the output suitable for online browsing using a pdf viewer.
918 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
919 # plain latex in the generated Makefile. Set this option to YES to get a
920 # higher quality PDF documentation.
924 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
925 # command to the generated LaTeX files. This will instruct LaTeX to keep
926 # running if errors occur, instead of asking the user for help.
927 # This option is also used when generating formulas in HTML.
931 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
932 # include the index chapters (such as File Index, Compound Index, etc.)
935 LATEX_HIDE_INDICES = NO
937 #---------------------------------------------------------------------------
938 # configuration options related to the RTF output
939 #---------------------------------------------------------------------------
941 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
942 # The RTF output is optimized for Word 97 and may not look very pretty with
943 # other RTF readers or editors.
947 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
948 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
949 # put in front of it. If left blank `rtf' will be used as the default path.
953 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
954 # RTF documents. This may be useful for small projects and may help to
955 # save some trees in general.
959 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
960 # will contain hyperlink fields. The RTF file will
961 # contain links (just like the HTML output) instead of page references.
962 # This makes the output suitable for online browsing using WORD or other
963 # programs which support those fields.
964 # Note: wordpad (write) and others do not support links.
968 # Load stylesheet definitions from file. Syntax is similar to doxygen's
969 # config file, i.e. a series of assignments. You only have to provide
970 # replacements, missing definitions are set to their default value.
972 RTF_STYLESHEET_FILE =
974 # Set optional variables used in the generation of an rtf document.
975 # Syntax is similar to doxygen's config file.
977 RTF_EXTENSIONS_FILE =
979 #---------------------------------------------------------------------------
980 # configuration options related to the man page output
981 #---------------------------------------------------------------------------
983 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
988 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
989 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
990 # put in front of it. If left blank `man' will be used as the default path.
994 # The MAN_EXTENSION tag determines the extension that is added to
995 # the generated man pages (default is the subroutine's section .3)
999 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1000 # then it will generate one additional man file for each entity
1001 # documented in the real man page(s). These additional files
1002 # only source the real man page, but without them the man command
1003 # would be unable to find the correct page. The default is NO.
1007 #---------------------------------------------------------------------------
1008 # configuration options related to the XML output
1009 #---------------------------------------------------------------------------
1011 # If the GENERATE_XML tag is set to YES Doxygen will
1012 # generate an XML file that captures the structure of
1013 # the code including all documentation.
1017 # The XML_OUTPUT tag is used to specify where the XML pages will be put.
1018 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1019 # put in front of it. If left blank `xml' will be used as the default path.
1023 # The XML_SCHEMA tag can be used to specify an XML schema,
1024 # which can be used by a validating XML parser to check the
1025 # syntax of the XML files.
1029 # The XML_DTD tag can be used to specify an XML DTD,
1030 # which can be used by a validating XML parser to check the
1031 # syntax of the XML files.
1035 # If the XML_PROGRAMLISTING tag is set to YES Doxygen will
1036 # dump the program listings (including syntax highlighting
1037 # and cross-referencing information) to the XML output. Note that
1038 # enabling this will significantly increase the size of the XML output.
1040 XML_PROGRAMLISTING = YES
1042 #---------------------------------------------------------------------------
1043 # configuration options for the AutoGen Definitions output
1044 #---------------------------------------------------------------------------
1046 # If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
1047 # generate an AutoGen Definitions (see autogen.sf.net) file
1048 # that captures the structure of the code including all
1049 # documentation. Note that this feature is still experimental
1050 # and incomplete at the moment.
1052 GENERATE_AUTOGEN_DEF = NO
1054 #---------------------------------------------------------------------------
1055 # configuration options related to the Perl module output
1056 #---------------------------------------------------------------------------
1058 # If the GENERATE_PERLMOD tag is set to YES Doxygen will
1059 # generate a Perl module file that captures the structure of
1060 # the code including all documentation. Note that this
1061 # feature is still experimental and incomplete at the
1064 GENERATE_PERLMOD = NO
1066 # If the PERLMOD_LATEX tag is set to YES Doxygen will generate
1067 # the necessary Makefile rules, Perl scripts and LaTeX code to be able
1068 # to generate PDF and DVI output from the Perl module output.
1072 # If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
1073 # nicely formatted so it can be parsed by a human reader. This is useful
1074 # if you want to understand what is going on. On the other hand, if this
1075 # tag is set to NO the size of the Perl module output will be much smaller
1076 # and Perl will parse it just the same.
1078 PERLMOD_PRETTY = YES
1080 # The names of the make variables in the generated doxyrules.make file
1081 # are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
1082 # This is useful so different doxyrules.make files included by the same
1083 # Makefile don't overwrite each other's variables.
1085 PERLMOD_MAKEVAR_PREFIX =
1087 #---------------------------------------------------------------------------
1088 # Configuration options related to the preprocessor
1089 #---------------------------------------------------------------------------
1091 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1092 # evaluate all C-preprocessor directives found in the sources and include
1095 ENABLE_PREPROCESSING = YES
1097 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1098 # names in the source code. If set to NO (the default) only conditional
1099 # compilation will be performed. Macro expansion can be done in a controlled
1100 # way by setting EXPAND_ONLY_PREDEF to YES.
1102 MACRO_EXPANSION = YES
1104 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1105 # then the macro expansion is limited to the macros specified with the
1106 # PREDEFINED and EXPAND_AS_PREDEFINED tags.
1108 EXPAND_ONLY_PREDEF = NO
1110 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1111 # in the INCLUDE_PATH (see below) will be search if a #include is found.
1113 SEARCH_INCLUDES = YES
1115 # The INCLUDE_PATH tag can be used to specify one or more directories that
1116 # contain include files that are not input files but should be processed by
1121 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1122 # patterns (like *.h and *.hpp) to filter out the header-files in the
1123 # directories. If left blank, the patterns specified with FILE_PATTERNS will
1126 INCLUDE_FILE_PATTERNS =
1128 # The PREDEFINED tag can be used to specify one or more macro names that
1129 # are defined before the preprocessor is started (similar to the -D option of
1130 # gcc). The argument of the tag is a list of macros of the form: name
1131 # or name=definition (no spaces). If the definition and the = are
1132 # omitted =1 is assumed.
1136 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1137 # this tag can be used to specify a list of macro names that should be expanded.
1138 # The macro definition that is found in the sources will be used.
1139 # Use the PREDEFINED tag if you want to use a different macro definition.
1143 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1144 # doxygen's preprocessor will remove all function-like macros that are alone
1145 # on a line, have an all uppercase name, and do not end with a semicolon. Such
1146 # function macros are typically used for boiler-plate code, and will confuse the
1147 # parser if not removed.
1149 SKIP_FUNCTION_MACROS = YES
1151 #---------------------------------------------------------------------------
1152 # Configuration::addtions related to external references
1153 #---------------------------------------------------------------------------
1155 # The TAGFILES option can be used to specify one or more tagfiles.
1156 # Optionally an initial location of the external documentation
1157 # can be added for each tagfile. The format of a tag file without
1158 # this location is as follows:
1159 # TAGFILES = file1 file2 ...
1160 # Adding location for the tag files is done as follows:
1161 # TAGFILES = file1=loc1 "file2 = loc2" ...
1162 # where "loc1" and "loc2" can be relative or absolute paths or
1163 # URLs. If a location is present for each tag, the installdox tool
1164 # does not have to be run to correct the links.
1165 # Note that each tag file must have a unique name
1166 # (where the name does NOT include the path)
1167 # If a tag file is not located in the directory in which doxygen
1168 # is run, you must also specify the path to the tagfile here.
1172 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1173 # a tag file that is based on the input files it reads.
1175 GENERATE_TAGFILE = Doxytags
1177 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
1178 # in the class index. If set to NO only the inherited external classes
1183 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed
1184 # in the modules index. If set to NO, only the current project's groups will
1187 EXTERNAL_GROUPS = YES
1189 # The PERL_PATH should be the absolute path and name of the perl script
1190 # interpreter (i.e. the result of `which perl').
1192 PERL_PATH = /usr/bin/perl
1194 #---------------------------------------------------------------------------
1195 # Configuration options related to the dot tool
1196 #---------------------------------------------------------------------------
1198 # If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will
1199 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base or
1200 # super classes. Setting the tag to NO turns the diagrams off. Note that this
1201 # option is superseded by the HAVE_DOT option below. This is only a fallback. It is
1202 # recommended to install and use dot, since it yields more powerful graphs.
1204 CLASS_DIAGRAMS = YES
1206 # If set to YES, the inheritance and collaboration graphs will hide
1207 # inheritance and usage relations if the target is undocumented
1208 # or is not a class.
1210 HIDE_UNDOC_RELATIONS = YES
1212 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
1213 # available from the path. This tool is part of Graphviz, a graph visualization
1214 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
1215 # have no effect if this option is set to NO (the default)
1219 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
1220 # will generate a graph for each documented class showing the direct and
1221 # indirect inheritance relations. Setting this tag to YES will force the
1222 # the CLASS_DIAGRAMS tag to NO.
1226 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
1227 # will generate a graph for each documented class showing the direct and
1228 # indirect implementation dependencies (inheritance, containment, and
1229 # class references variables) of the class with other documented classes.
1231 COLLABORATION_GRAPH = YES
1233 # If the UML_LOOK tag is set to YES doxygen will generate inheritance and
1234 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1239 # If set to YES, the inheritance and collaboration graphs will show the
1240 # relations between templates and their instances.
1242 TEMPLATE_RELATIONS = YES
1244 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT
1245 # tags are set to YES then doxygen will generate a graph for each documented
1246 # file showing the direct and indirect include dependencies of the file with
1247 # other documented files.
1251 # If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and
1252 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1253 # documented header file showing the documented files that directly or
1254 # indirectly include this file.
1256 INCLUDED_BY_GRAPH = YES
1258 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will
1259 # generate a call dependency graph for every global function or class method.
1260 # Note that enabling this option will significantly increase the time of a run.
1261 # So in most cases it will be better to enable call graphs for selected
1262 # functions only using the \callgraph command.
1266 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen
1267 # will graphical hierarchy of all classes instead of a textual one.
1269 GRAPHICAL_HIERARCHY = YES
1271 # The DOT_IMAGE_FORMAT tag can be used to set the image format of the images
1272 # generated by dot. Possible values are png, jpg, or gif
1273 # If left blank png will be used.
1275 DOT_IMAGE_FORMAT = png
1277 # The tag DOT_PATH can be used to specify the path where the dot tool can be
1278 # found. If left blank, it is assumed the dot tool can be found on the path.
1282 # The DOTFILE_DIRS tag can be used to specify one or more directories that
1283 # contain dot files that are included in the documentation (see the
1284 # \dotfile command).
1288 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
1289 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1290 # this value, doxygen will try to truncate the graph, so that it fits within
1291 # the specified constraint. Beware that most browsers cannot cope with very
1294 MAX_DOT_GRAPH_WIDTH = 1024
1296 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
1297 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
1298 # this value, doxygen will try to truncate the graph, so that it fits within
1299 # the specified constraint. Beware that most browsers cannot cope with very
1302 MAX_DOT_GRAPH_HEIGHT = 1024
1304 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the
1305 # graphs generated by dot. A depth value of 3 means that only nodes reachable
1306 # from the root by following a path via at most 3 edges will be shown. Nodes that
1307 # lay further from the root node will be omitted. Note that setting this option to
1308 # 1 or 2 may greatly reduce the computation time needed for large code bases. Also
1309 # note that a graph may be further truncated if the graph's image dimensions are
1310 # not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH and MAX_DOT_GRAPH_HEIGHT).
1311 # If 0 is used for the depth value (the default), the graph is not depth-constrained.
1313 MAX_DOT_GRAPH_DEPTH = 0
1315 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
1316 # generate a legend page explaining the meaning of the various boxes and
1317 # arrows in the dot generated graphs.
1319 GENERATE_LEGEND = YES
1321 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
1322 # remove the intermediate dot files that are used to generate
1323 # the various graphs.
1327 #---------------------------------------------------------------------------
1328 # Configuration::addtions related to the search engine
1329 #---------------------------------------------------------------------------
1331 # The SEARCHENGINE tag specifies whether or not a search engine should be
1332 # used. If set to NO the values of all tags below this one will be ignored.