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 = libevent
22 # Place all output under 'doxygen/'
24 OUTPUT_DIRECTORY = doxygen/
26 # If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
27 # will interpret the first line (until the first dot) of a JavaDoc-style
28 # comment as the brief description. If set to NO, the JavaDoc
29 # comments will behave just like the Qt-style comments (thus requiring an
30 # explicit @brief command for a brief description.
32 JAVADOC_AUTOBRIEF = YES
34 # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
35 # sources only. Doxygen will then generate output that is more tailored for C.
36 # For instance, some of the names that are used will be different. The list
37 # of all members will be omitted, etc.
39 OPTIMIZE_OUTPUT_FOR_C = YES
41 # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
42 # brief documentation of file, namespace and class members alphabetically
43 # by member name. If set to NO (the default) the members will appear in
48 #---------------------------------------------------------------------------
49 # configuration options related to the input files
50 #---------------------------------------------------------------------------
52 # The INPUT tag can be used to specify the files and/or directories that contain
53 # documented source files. You may enter file names like "myfile.cpp" or
54 # directories like "/usr/src/myproject". Separate the files or directories
57 INPUT = event.h evdns.h evhttp.h evrpc.h \
58 include/event2/event.h include/event2/event_struct.h \
59 include/event2/event_compat.h \
60 include/event2/buffer_compat.h \
61 include/event2/buffer.h include/event2/thread.h \
62 include/event2/tag.h include/event2/bufferevent.h \
63 include/event2/bufferevent_struct.h \
64 include/event2/bufferevent_compat.h \
65 include/event2/util.h \
66 include/event2/rpc.h include/event2/rpc_struct.h \
67 include/event2/rpc_compat.h \
68 include/event2/dns.h include/event2/dns_struct.h \
69 include/event2/dns_compat.h \
70 include/event2/http.h include/event2/http_struct.h \
71 include/event2/http_compat.h
73 #---------------------------------------------------------------------------
74 # configuration options related to the HTML output
75 #---------------------------------------------------------------------------
77 # If the GENERATE_HTML tag is set to YES (the default) Doxygen will
78 # generate HTML output.
82 #---------------------------------------------------------------------------
83 # configuration options related to the LaTeX output
84 #---------------------------------------------------------------------------
86 # If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
87 # generate Latex output.
91 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
92 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
93 # put in front of it. If left blank `latex' will be used as the default path.
97 # The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
98 # invoked. If left blank `latex' will be used as the default command name.
100 LATEX_CMD_NAME = latex
102 # The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
103 # generate index for LaTeX. If left blank `makeindex' will be used as the
104 # default command name.
106 MAKEINDEX_CMD_NAME = makeindex
108 # If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
109 # LaTeX documents. This may be useful for small projects and may help to
110 # save some trees in general.
114 # The PAPER_TYPE tag can be used to set the paper type that is used
115 # by the printer. Possible values are: a4, a4wide, letter, legal and
116 # executive. If left blank a4wide will be used.
120 # The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
121 # packages that should be included in the LaTeX output.
125 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
126 # the generated latex document. The header should contain everything until
127 # the first chapter. If it is left blank doxygen will generate a
128 # standard header. Notice: only use this tag if you know what you are doing!
132 # If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
133 # is prepared for conversion to pdf (using ps2pdf). The pdf file will
134 # contain links (just like the HTML output) instead of page references
135 # This makes the output suitable for online browsing using a pdf viewer.
139 # If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
140 # plain latex in the generated Makefile. Set this option to YES to get a
141 # higher quality PDF documentation.
145 # If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
146 # command to the generated LaTeX files. This will instruct LaTeX to keep
147 # running if errors occur, instead of asking the user for help.
148 # This option is also used when generating formulas in HTML.
152 # If LATEX_HIDE_INDICES is set to YES then doxygen will not
153 # include the index chapters (such as File Index, Compound Index, etc.)
156 LATEX_HIDE_INDICES = NO
158 #---------------------------------------------------------------------------
159 # configuration options related to the man page output
160 #---------------------------------------------------------------------------
162 # If the GENERATE_MAN tag is set to YES (the default) Doxygen will
167 # The MAN_EXTENSION tag determines the extension that is added to
168 # the generated man pages (default is the subroutine's section .3)
172 # If the MAN_LINKS tag is set to YES and Doxygen generates man output,
173 # then it will generate one additional man file for each entity
174 # documented in the real man page(s). These additional files
175 # only source the real man page, but without them the man command
176 # would be unable to find the correct page. The default is NO.
180 #---------------------------------------------------------------------------
181 # Configuration options related to the preprocessor
182 #---------------------------------------------------------------------------
184 # If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
185 # evaluate all C-preprocessor directives found in the sources and include
188 ENABLE_PREPROCESSING = YES
190 # If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
191 # names in the source code. If set to NO (the default) only conditional
192 # compilation will be performed. Macro expansion can be done in a controlled
193 # way by setting EXPAND_ONLY_PREDEF to YES.
197 # If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
198 # then the macro expansion is limited to the macros specified with the
199 # PREDEFINED and EXPAND_AS_DEFINED tags.
201 EXPAND_ONLY_PREDEF = NO
203 # If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
204 # in the INCLUDE_PATH (see below) will be search if a #include is found.
206 SEARCH_INCLUDES = YES
208 # The INCLUDE_PATH tag can be used to specify one or more directories that
209 # contain include files that are not input files but should be processed by
214 # You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
215 # patterns (like *.h and *.hpp) to filter out the header-files in the
216 # directories. If left blank, the patterns specified with FILE_PATTERNS will
219 INCLUDE_FILE_PATTERNS =
221 # The PREDEFINED tag can be used to specify one or more macro names that
222 # are defined before the preprocessor is started (similar to the -D option of
223 # gcc). The argument of the tag is a list of macros of the form: name
224 # or name=definition (no spaces). If the definition and the = are
225 # omitted =1 is assumed. To prevent a macro definition from being
226 # undefined via #undef or recursively expanded use the := operator
227 # instead of the = operator.
229 PREDEFINED = TAILQ_ENTRY RB_ENTRY _EVENT_DEFINED_TQENTRY
231 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
232 # this tag can be used to specify a list of macro names that should be expanded.
233 # The macro definition that is found in the sources will be used.
234 # Use the PREDEFINED tag if you want to use a different macro definition.
238 # If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
239 # doxygen's preprocessor will remove all function-like macros that are alone
240 # on a line, have an all uppercase name, and do not end with a semicolon. Such
241 # function macros are typically used for boiler-plate code, and will confuse
242 # the parser if not removed.
244 SKIP_FUNCTION_MACROS = YES