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