1# Doxyfile 1.5.1 2 3# This file describes the settings to be used by the documentation system 4# doxygen (www.doxygen.org) for a project 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# Project related 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 20PROJECT_NAME = libevent 21 22# Place all output under 'doxygen/' 23 24OUTPUT_DIRECTORY = doxygen/ 25 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. 31 32JAVADOC_AUTOBRIEF = YES 33 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. 38 39OPTIMIZE_OUTPUT_FOR_C = YES 40 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 44# declaration order. 45 46SORT_BRIEF_DOCS = YES 47 48#--------------------------------------------------------------------------- 49# configuration options related to the input files 50#--------------------------------------------------------------------------- 51 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 55# with spaces. 56 57INPUT = event.h evdns.h evhttp.h evrpc.h \ 58 include/event2/buffer.h include/event2/thread.h \ 59 include/event2/tag.h include/event2/bufferevent.h \ 60 include/event2/util.h \ 61 include/event2/dns.h include/event2/dns_struct.h \ 62 include/event2/dns_compat.h \ 63 include/event2/http.h include/event2/http_struct.h \ 64 include/event2/http_compat.h 65 66#--------------------------------------------------------------------------- 67# configuration options related to the HTML output 68#--------------------------------------------------------------------------- 69 70# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 71# generate HTML output. 72 73GENERATE_HTML = YES 74 75#--------------------------------------------------------------------------- 76# configuration options related to the LaTeX output 77#--------------------------------------------------------------------------- 78 79# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 80# generate Latex output. 81 82GENERATE_LATEX = YES 83 84# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 85# If a relative path is entered the value of OUTPUT_DIRECTORY will be 86# put in front of it. If left blank `latex' will be used as the default path. 87 88LATEX_OUTPUT = latex 89 90# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 91# invoked. If left blank `latex' will be used as the default command name. 92 93LATEX_CMD_NAME = latex 94 95# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 96# generate index for LaTeX. If left blank `makeindex' will be used as the 97# default command name. 98 99MAKEINDEX_CMD_NAME = makeindex 100 101# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 102# LaTeX documents. This may be useful for small projects and may help to 103# save some trees in general. 104 105COMPACT_LATEX = NO 106 107# The PAPER_TYPE tag can be used to set the paper type that is used 108# by the printer. Possible values are: a4, a4wide, letter, legal and 109# executive. If left blank a4wide will be used. 110 111PAPER_TYPE = a4wide 112 113# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 114# packages that should be included in the LaTeX output. 115 116EXTRA_PACKAGES = 117 118# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 119# the generated latex document. The header should contain everything until 120# the first chapter. If it is left blank doxygen will generate a 121# standard header. Notice: only use this tag if you know what you are doing! 122 123LATEX_HEADER = 124 125# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 126# is prepared for conversion to pdf (using ps2pdf). The pdf file will 127# contain links (just like the HTML output) instead of page references 128# This makes the output suitable for online browsing using a pdf viewer. 129 130PDF_HYPERLINKS = NO 131 132# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 133# plain latex in the generated Makefile. Set this option to YES to get a 134# higher quality PDF documentation. 135 136USE_PDFLATEX = NO 137 138# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 139# command to the generated LaTeX files. This will instruct LaTeX to keep 140# running if errors occur, instead of asking the user for help. 141# This option is also used when generating formulas in HTML. 142 143LATEX_BATCHMODE = NO 144 145# If LATEX_HIDE_INDICES is set to YES then doxygen will not 146# include the index chapters (such as File Index, Compound Index, etc.) 147# in the output. 148 149LATEX_HIDE_INDICES = NO 150 151#--------------------------------------------------------------------------- 152# configuration options related to the man page output 153#--------------------------------------------------------------------------- 154 155# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 156# generate man pages 157 158GENERATE_MAN = YES 159 160# The MAN_EXTENSION tag determines the extension that is added to 161# the generated man pages (default is the subroutine's section .3) 162 163MAN_EXTENSION = .3 164 165# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 166# then it will generate one additional man file for each entity 167# documented in the real man page(s). These additional files 168# only source the real man page, but without them the man command 169# would be unable to find the correct page. The default is NO. 170 171MAN_LINKS = YES 172 173#--------------------------------------------------------------------------- 174# Configuration options related to the preprocessor 175#--------------------------------------------------------------------------- 176 177# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 178# evaluate all C-preprocessor directives found in the sources and include 179# files. 180 181ENABLE_PREPROCESSING = YES 182 183# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 184# names in the source code. If set to NO (the default) only conditional 185# compilation will be performed. Macro expansion can be done in a controlled 186# way by setting EXPAND_ONLY_PREDEF to YES. 187 188MACRO_EXPANSION = NO 189 190# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 191# then the macro expansion is limited to the macros specified with the 192# PREDEFINED and EXPAND_AS_DEFINED tags. 193 194EXPAND_ONLY_PREDEF = NO 195 196# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 197# in the INCLUDE_PATH (see below) will be search if a #include is found. 198 199SEARCH_INCLUDES = YES 200 201# The INCLUDE_PATH tag can be used to specify one or more directories that 202# contain include files that are not input files but should be processed by 203# the preprocessor. 204 205INCLUDE_PATH = 206 207# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 208# patterns (like *.h and *.hpp) to filter out the header-files in the 209# directories. If left blank, the patterns specified with FILE_PATTERNS will 210# be used. 211 212INCLUDE_FILE_PATTERNS = 213 214# The PREDEFINED tag can be used to specify one or more macro names that 215# are defined before the preprocessor is started (similar to the -D option of 216# gcc). The argument of the tag is a list of macros of the form: name 217# or name=definition (no spaces). If the definition and the = are 218# omitted =1 is assumed. To prevent a macro definition from being 219# undefined via #undef or recursively expanded use the := operator 220# instead of the = operator. 221 222PREDEFINED = TAILQ_ENTRY RB_ENTRY _EVENT_DEFINED_TQENTRY 223 224# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 225# this tag can be used to specify a list of macro names that should be expanded. 226# The macro definition that is found in the sources will be used. 227# Use the PREDEFINED tag if you want to use a different macro definition. 228 229EXPAND_AS_DEFINED = 230 231# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 232# doxygen's preprocessor will remove all function-like macros that are alone 233# on a line, have an all uppercase name, and do not end with a semicolon. Such 234# function macros are typically used for boiler-plate code, and will confuse 235# the parser if not removed. 236 237SKIP_FUNCTION_MACROS = YES 238