1 # Doxyfile 1.2.9.1 -*- coding: euc-jp; -*-
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 = %PROJECT_NAME%
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 = @PACKAGE_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 = %USR_JA_DEV%
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, Hungarian, Italian, Japanese, Korean, Norwegian, Polish,
41 # Portuguese, Romanian, Russian, Slovak, Slovene, Spanish and Swedish.
43 OUTPUT_LANGUAGE = %OUTPUT_LANGUAGE%
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 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.
68 HIDE_UNDOC_MEMBERS = yes
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.
75 HIDE_UNDOC_CLASSES = NO
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.
82 BRIEF_MEMBER_DESC = yes
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.
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
95 ALWAYS_DETAILED_SEC = no
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.
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.
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.
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.
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 # with a discussion with Handa, decided to set to NO Jan/8/2002
129 # Setting the INLINE_SOURCES tag to YES will include the body
130 # of functions and classes directly in the documentation.
132 # This should be no 10/Jan
136 # Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
137 # doxygen to hide any special comment blocks from generated source code
138 # fragments. Normal C and C++ comments will always remain visible.
140 STRIP_CODE_COMMENTS = YES
142 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
143 # file names in lower case letters. If set to YES upper case letters are also
144 # allowed. This is useful if you have classes or files whose names only differ
145 # in case and if your file system supports case sensitive file names. Windows
146 # users are adviced to set this option to NO.
148 CASE_SENSE_NAMES = YES
150 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
151 # (but less readable) file names. This can be useful is your file systems
152 # doesn't support long names like on DOS, Mac, or CD-ROM.
156 # If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
157 # will show members with their full class and namespace scopes in the
158 # documentation. If set to YES the scope will be hidden.
160 HIDE_SCOPE_NAMES = NO
162 # If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
163 # will generate a verbatim copy of the header file for each class for
164 # which an include is specified. Set to NO to disable this.
166 VERBATIM_HEADERS = yes
168 # If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
169 # will put list of the files that are included by a file in the documentation
172 SHOW_INCLUDE_FILES = yes
174 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
175 # will interpret the first line (until the first dot) of a JavaDoc-style
176 # comment as the brief description. If set to NO, the JavaDoc
177 # comments will behave just like the Qt-style comments (thus requiring an
178 # explict @brief command for a brief description.
180 JAVADOC_AUTOBRIEF = NO
182 # If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
183 # member inherits the documentation from any documented member that it
188 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
189 # is inserted in the documentation for inline members.
193 # If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
194 # will sort the (detailed) documentation of file and class members
195 # alphabetically by member name. If set to NO the members will appear in
197 ### # this seems to affect the order of module list. Dec14 Nishikimi
199 SORT_MEMBER_DOCS = no
201 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
202 # tag is set to YES, then doxygen will reuse the documentation of the first
203 # member in the group (if any) for the other members of the group. By default
204 # all members of a group must be documented explicitly.
206 DISTRIBUTE_GROUP_DOC = no
208 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
209 # Doxygen uses this value to replace tabs by spaces in code fragments.
213 # The ENABLED_SECTIONS tag can be used to enable conditional
214 # documentation sections, marked by \if sectionname ... \endif.
218 # The GENERATE_TODOLIST tag can be used to enable (YES) or
219 # disable (NO) the todo list. This list is created by putting \todo
220 # commands in the documentation.
222 GENERATE_TODOLIST = YES
224 # The GENERATE_TESTLIST tag can be used to enable (YES) or
225 # disable (NO) the test list. This list is created by putting \test
226 # commands in the documentation.
228 GENERATE_TESTLIST = YES
230 # The GENERATE_BUGLIST tag can be used to enable (YES) or
231 # disable (NO) the bug list. This list is created by putting \bug
232 # commands in the documentation.
234 GENERATE_BUGLIST = YES
236 # This tag can be used to specify a number of aliases that acts
237 # as commands in the documentation. An alias has the form "name=value".
238 # For example adding "sideeffect=\par Side Effects:\n" will allow you to
239 # put the command \sideeffect (or @sideeffect) in the documentation, which
240 # will result in a user defined paragraph with heading "Side Effects:".
241 # You can put \n's in the value part of an alias to insert newlines.
245 # The MAX_INITIALIZER_LINES tag determines the maximum number of lines
246 # the initial value of a variable or define consist of for it to appear in
247 # the documentation. If the initializer consists of more lines than specified
248 # here it will be hidden. Use a value of 0 to hide initializers completely.
249 # The appearance of the initializer of individual variables and defines in the
250 # documentation can be controlled using \showinitializer or \hideinitializer
251 # command in the documentation regardless of this setting.
253 MAX_INITIALIZER_LINES = 30
255 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources
256 # only. Doxygen will then generate output that is more tailored for C.
257 # For instance some of the names that are used will be different. The list
258 # of all members will be omitted, etc.
260 OPTIMIZE_OUTPUT_FOR_C = yes
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.
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 = "$text in $file line $line"
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
300 WARN_LOGFILE = warning
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
311 INPUT = "data-%USR_JA_DEV%/mainpage.txt"
312 INPUT += "@M17NLIB@/src/m17n-core.h"
313 INPUT += "@M17NLIB@/src/m17n.h"
314 INPUT += "@M17NLIB@/src/m17n-win.h"
315 INPUT += "@M17NLIB@/src/m17n-X.h"
316 INPUT += "@M17NLIB@/src/m17n-err.h"
317 INPUT += "@M17NLIB@/src/"
318 INPUT += "data-%USR_JA_DEV%/dbformat.txt"
320 # If the value of the INPUT tag contains directories, you can use the
321 # FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
322 # and *.h) to filter out the source-files in the directories. If left
323 # blank all files are included.
328 # The RECURSIVE tag can be used to turn specify whether or not subdirectories
329 # should be searched for input files as well. Possible values are YES and NO.
330 # If left blank NO is used.
334 # The EXCLUDE tag can be used to specify files and/or directories that should
335 # excluded from the INPUT source files. This way you can easily exclude a
336 # subdirectory from a directory tree whose root is specified with the INPUT tag.
340 # If the value of the INPUT tag contains directories, you can use the
341 # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
342 # certain files from those directories.
344 EXCLUDE_PATTERNS = font-flt.c font-ft.c link*.c
346 # The EXAMPLE_PATH tag can be used to specify one or more files or
347 # directories that contain example code fragments that are included (see
348 # the \include command).
350 EXAMPLE_PATH = data-%USR_JA_DEV%
352 # If the value of the EXAMPLE_PATH tag contains directories, you can use the
353 # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
354 # and *.h) to filter out the source-files in the directories. If left
355 # blank all files are included.
359 # The IMAGE_PATH tag can be used to specify one or more files or
360 # directories that contain image that are included in the documentation (see
361 # the \image command).
363 IMAGE_PATH = /project/mule/m17n-lib/docs/doxygen/images
365 # The INPUT_FILTER tag can be used to specify a program that doxygen should
366 # invoke to filter for each input file. Doxygen will invoke the filter program
367 # by executing (via popen()) the command <filter> <input-file>, where <filter>
368 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
369 # input file. Doxygen will then use the output that the filter program writes
370 # to standard output.
372 INPUT_FILTER = @abs_srcdir@/utils/%USR_JA_DEV%_filter.rb
374 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
375 # INPUT_FILTER) will be used to filter the input files when producing source
378 FILTER_SOURCE_FILES =
380 #---------------------------------------------------------------------------
381 # configuration options related to the alphabetical class index
382 #---------------------------------------------------------------------------
384 # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
385 # of all compounds will be generated. Enable this if the project
386 # contains a lot of classes, structs, unions or interfaces.
388 ALPHABETICAL_INDEX = yes
390 # If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
391 # the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
392 # in which this list will be split (can be a number in the range [1..20])
394 COLS_IN_ALPHA_INDEX = 5
396 # In case all classes in a project start with a common prefix, all
397 # classes will be put under the same header in the alphabetical index.
398 # The IGNORE_PREFIX tag can be used to specify one or more prefixes that
399 # should be ignored while generating the index headers.
403 #---------------------------------------------------------------------------
404 # configuration options related to the HTML output
405 #---------------------------------------------------------------------------
407 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
408 # generate HTML output.
410 GENERATE_HTML = %GENERATE_HTML%
412 # The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
413 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
414 # put in front of it. If left blank `html' will be used as the default path.
418 # The HTML_HEADER tag can be used to specify a personal HTML header for
419 # each generated HTML page. If it is left blank doxygen will generate a
422 HTML_HEADER = @abs_srcdir@/header.html
424 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
425 # each generated HTML page. If it is left blank doxygen will generate a
428 HTML_FOOTER = @abs_srcdir@/footer.html
430 # The HTML_STYLESHEET tag can be used to specify a user defined cascading
431 # style sheet that is used by each HTML page. It can be used to
432 # fine-tune the look of the HTML output. If the tag is left blank doxygen
433 # will generate a default style sheet
435 HTML_STYLESHEET = @abs_srcdir@/m17n-lib.css
437 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
438 # files or namespaces will be aligned in HTML using tables. If set to
439 # NO a bullet list will be used.
441 HTML_ALIGN_MEMBERS = yes
443 # If the GENERATE_HTMLHELP tag is set to YES, additional index files
444 # will be generated that can be used as input for tools like the
445 # Microsoft HTML help workshop to generate a compressed HTML help file (.chm)
446 # of the generated HTML documentation.
448 GENERATE_HTMLHELP = NO
450 # If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
451 # controls if a separate .chi index file is generated (YES) or that
452 # it should be included in the master .chm file (NO).
456 # If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
457 # controls whether a binary table of contents is generated (YES) or a
458 # normal table of contents (NO) in the .chm file.
462 # The TOC_EXPAND flag can be set to YES to add extra items for group members
463 # to the contents of the Html help documentation and to the tree view.
467 # The DISABLE_INDEX tag can be used to turn on/off the condensed index at
468 # top of each HTML page. The value NO (the default) enables the index and
469 # the value YES disables it.
473 # This tag can be used to set the number of enum values (range [1..20])
474 # that doxygen will group on one line in the generated HTML documentation.
476 ENUM_VALUES_PER_LINE = 4
478 # If the GENERATE_TREEVIEW tag is set to YES, a side panel will be
479 # generated containing a tree-like index structure (just like the one that
480 # is generated for HTML Help). For this to work a browser that supports
481 # JavaScript and frames is required (for instance Netscape 4.0+
482 # or Internet explorer 4.0+).
484 GENERATE_TREEVIEW = no
486 # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
487 # used to set the initial width (in pixels) of the frame in which the tree
492 #---------------------------------------------------------------------------
493 # configuration options related to the LaTeX output
494 #---------------------------------------------------------------------------
496 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
497 # generate Latex output.
499 GENERATE_LATEX = %GENERATE_LATEX%
501 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
502 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
503 # put in front of it. If left blank `latex' will be used as the default path.
507 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
508 # LaTeX documents. This may be useful for small projects and may help to
509 # save some trees in general.
513 # The PAPER_TYPE tag can be used to set the paper type that is used
514 # by the printer. Possible values are: a4, a4wide, letter, legal and
515 # executive. If left blank a4wide will be used.
519 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
520 # packages that should be included in the LaTeX output.
522 EXTRA_PACKAGES = m17n-lib times
524 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
525 # the generated latex document. The header should contain everything until
526 # the first chapter. If it is left blank doxygen will generate a
527 # standard header. Notice: only use this tag if you know what you are doing!
531 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
532 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
533 # contain links (just like the HTML output) instead of page references
534 # This makes the output suitable for online browsing using a pdf viewer.
538 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
539 # plain latex in the generated Makefile. Set this option to YES to get a
540 # higher quality PDF documentation.
544 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
545 # command to the generated LaTeX files. This will instruct LaTeX to keep
546 # running if errors occur, instead of asking the user for help.
547 # This option is also used when generating formulas in HTML.
551 #---------------------------------------------------------------------------
552 # configuration options related to the RTF output
553 #---------------------------------------------------------------------------
555 # If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
556 # The RTF output is optimised for Word 97 and may not look very pretty with
557 # other RTF readers or editors.
561 # The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
562 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
563 # put in front of it. If left blank `rtf' will be used as the default path.
567 # If the COMPACT_RTF tag is set to YES Doxygen generates more compact
568 # RTF documents. This may be useful for small projects and may help to
569 # save some trees in general.
573 # If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
574 # will contain hyperlink fields. The RTF file will
575 # contain links (just like the HTML output) instead of page references.
576 # This makes the output suitable for online browsing using WORD or other
577 # programs which support those fields.
578 # Note: wordpad (write) and others do not support links.
582 # Load stylesheet definitions from file. Syntax is similar to doxygen's
583 # config file, i.e. a series of assigments. You only have to provide
584 # replacements, missing definitions are set to their default value.
586 RTF_STYLESHEET_FILE =
588 # Set optional variables used in the generation of an rtf document.
589 # Syntax is similar to doxygen's config file.
591 RTF_EXTENSIONS_FILE =
593 #---------------------------------------------------------------------------
594 # configuration options related to the man page output
595 #---------------------------------------------------------------------------
597 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
600 GENERATE_MAN = %GENERATE_MAN%
602 # The MAN_OUTPUT tag is used to specify where the man pages will be put.
603 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
604 # put in front of it. If left blank `man' will be used as the default path.
608 # The MAN_EXTENSION tag determines the extension that is added to
609 # the generated man pages (default is the subroutine's section .3)
613 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
614 # then it will generate one additional man file for each entity
615 # documented in the real man page(s). These additional files
616 # only source the real man page, but without them the man command
617 # would be unable to find the correct page. The default is NO.
621 #---------------------------------------------------------------------------
622 # configuration options related to the XML output
623 #---------------------------------------------------------------------------
625 # If the GENERATE_XML tag is set to YES Doxygen will
626 # generate an XML file that captures the structure of
627 # the code including all documentation. Note that this
628 # feature is still experimental and incomplete at the
633 #---------------------------------------------------------------------------
634 # Configuration options related to the preprocessor
635 #---------------------------------------------------------------------------
637 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
638 # evaluate all C-preprocessor directives found in the sources and include
641 ENABLE_PREPROCESSING = YES
643 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
644 # names in the source code. If set to NO (the default) only conditional
645 # compilation will be performed. Macro expansion can be done in a controlled
646 # way by setting EXPAND_ONLY_PREDEF to YES.
650 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
651 # then the macro expansion is limited to the macros specified with the
652 # PREDEFINED and EXPAND_AS_PREDEFINED tags.
654 EXPAND_ONLY_PREDEF = YES
656 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
657 # in the INCLUDE_PATH (see below) will be search if a #include is found.
659 SEARCH_INCLUDES = YES
661 # The INCLUDE_PATH tag can be used to specify one or more directories that
662 # contain include files that are not input files but should be processed by
667 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
668 # patterns (like *.h and *.hpp) to filter out the header-files in the
669 # directories. If left blank, the patterns specified with FILE_PATTERNS will
672 INCLUDE_FILE_PATTERNS =
674 # The PREDEFINED tag can be used to specify one or more macro names that
675 # are defined before the preprocessor is started (similar to the -D option of
676 # gcc). The argument of the tag is a list of macros of the form: name
677 # or name=definition (no spaces). If the definition and the = are
678 # omitted =1 is assumed.
680 PREDEFINED = FOR_DOXYGEN
681 #PREDEFINED += DOXYGEN_INTERNAL_MODULE
683 # If the MACRO_EXPANSION and EXPAND_PREDEF_ONLY tags are set to YES then
684 # this tag can be used to specify a list of macro names that should be expanded.
685 # The macro definition that is found in the sources will be used.
686 # Use the PREDEFINED tag if you want to use a different macro definition.
690 #---------------------------------------------------------------------------
691 # Configuration::addtions related to external references
692 #---------------------------------------------------------------------------
694 # The TAGFILES tag can be used to specify one or more tagfiles.
698 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
699 # a tag file that is based on the input files it reads.
701 GENERATE_TAGFILE = m17n.tag
703 # If the ALLEXTERNALS tag is set to YES all external classes will be listed
704 # in the class index. If set to NO only the inherited external classes
709 # The PERL_PATH should be the absolute path and name of the perl script
710 # interpreter (i.e. the result of `which perl').
714 #---------------------------------------------------------------------------
715 # Configuration options related to the dot tool
716 #---------------------------------------------------------------------------
718 # If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is
719 # available from the path. This tool is part of Graphviz, a graph visualization
720 # toolkit from AT&T and Lucent Bell Labs. The other options in this section
721 # have no effect if this option is set to NO (the default)
725 # If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen
726 # will generate a graph for each documented class showing the direct and
727 # indirect inheritance relations. Setting this tag to YES will force the
728 # the CLASS_DIAGRAMS tag to NO.
732 # If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen
733 # will generate a graph for each documented class showing the direct and
734 # indirect implementation dependencies (inheritance, containment, and
735 # class references variables) of the class with other documented classes.
737 COLLABORATION_GRAPH = YES
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.
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.
751 INCLUDED_BY_GRAPH = YES
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.
756 GRAPHICAL_HIERARCHY = yes
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.
763 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width
764 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
765 # this value, doxygen will try to truncate the graph, so that it fits within
766 # the specified constraint. Beware that most browsers cannot cope with very
769 MAX_DOT_GRAPH_WIDTH = 1024
771 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height
772 # (in pixels) of the graphs generated by dot. If a graph becomes larger than
773 # this value, doxygen will try to truncate the graph, so that it fits within
774 # the specified constraint. Beware that most browsers cannot cope with very
777 MAX_DOT_GRAPH_HEIGHT = 1024
779 # If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will
780 # generate a legend page explaining the meaning of the various boxes and
781 # arrows in the dot generated graphs.
783 GENERATE_LEGEND = YES
785 # If the DOT_CLEANUP tag is set to YES (the default) Doxygen will
786 # remove the intermedate dot files that are used to generate
787 # the various graphs.
791 #---------------------------------------------------------------------------
792 # Configuration::addtions related to the search engine
793 #---------------------------------------------------------------------------
795 # The SEARCHENGINE tag specifies whether or not a search engine should be
796 # used. If set to NO the values of all tags below this one will be ignored.
800 # The CGI_NAME tag should be the name of the CGI script that
801 # starts the search engine (doxysearch) with the correct parameters.
802 # A script with this name will be generated by doxygen.
804 CGI_NAME = m17n-lib-cgi
806 # The CGI_URL tag should be the absolute URL to the directory where the
807 # cgi binaries are located. See the documentation of your http daemon for
810 CGI_URL = http://mule.m17n.org/cgi-bin
812 # The DOC_URL tag should be the absolute URL to the directory where the
813 # documentation is located. If left blank the absolute path to the
814 # documentation, with file:// prepended to it, will be used.
816 DOC_URL = http://mule.m17n.org/m17n-lib/%USR_JA_DEV%/html/
818 # The DOC_ABSPATH tag should be the absolute path to the directory where the
819 # documentation is located. If left blank the directory on the local machine
822 DOC_ABSPATH = @abs_srcdir@/%USR_JA_DEV%/html
824 # The BIN_ABSPATH tag must point to the directory where the doxysearch binary
827 BIN_ABSPATH = /usr/local/bin
829 # The EXT_DOC_PATHS tag can be used to specify one or more paths to
830 # documentation generated for other projects. This allows doxysearch to search
831 # the documentation for these projects as well.