1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/ipc/chromium/src/third_party/libevent/Doxyfile Wed Dec 31 06:09:35 2014 +0100
1.3 @@ -0,0 +1,257 @@
1.4 +# Doxyfile 1.5.1
1.5 +
1.6 +# This file describes the settings to be used by the documentation system
1.7 +# doxygen (www.doxygen.org) for a project
1.8 +#
1.9 +# All text after a hash (#) is considered a comment and will be ignored
1.10 +# The format is:
1.11 +# TAG = value [value, ...]
1.12 +# For lists items can also be appended using:
1.13 +# TAG += value [value, ...]
1.14 +# Values that contain spaces should be placed between quotes (" ")
1.15 +
1.16 +#---------------------------------------------------------------------------
1.17 +# Project related configuration options
1.18 +#---------------------------------------------------------------------------
1.19 +
1.20 +# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
1.21 +# by quotes) that should identify the project.
1.22 +
1.23 +PROJECT_NAME = libevent
1.24 +
1.25 +# Place all output under 'doxygen/'
1.26 +
1.27 +OUTPUT_DIRECTORY = doxygen/
1.28 +
1.29 +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
1.30 +# will interpret the first line (until the first dot) of a JavaDoc-style
1.31 +# comment as the brief description. If set to NO, the JavaDoc
1.32 +# comments will behave just like the Qt-style comments (thus requiring an
1.33 +# explicit @brief command for a brief description.
1.34 +
1.35 +JAVADOC_AUTOBRIEF = YES
1.36 +
1.37 +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
1.38 +# sources only. Doxygen will then generate output that is more tailored for C.
1.39 +# For instance, some of the names that are used will be different. The list
1.40 +# of all members will be omitted, etc.
1.41 +
1.42 +OPTIMIZE_OUTPUT_FOR_C = YES
1.43 +
1.44 +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
1.45 +# brief documentation of file, namespace and class members alphabetically
1.46 +# by member name. If set to NO (the default) the members will appear in
1.47 +# declaration order.
1.48 +
1.49 +SORT_BRIEF_DOCS = YES
1.50 +
1.51 +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
1.52 +# can be used to strip a user-defined part of the path. Stripping is
1.53 +# only done if one of the specified strings matches the left-hand part of
1.54 +# the path. The tag can be used to show relative paths in the file list.
1.55 +# If left blank the directory from which doxygen is run is used as the
1.56 +# path to strip.
1.57 +
1.58 +STRIP_FROM_PATH = include/
1.59 +
1.60 +#---------------------------------------------------------------------------
1.61 +# configuration options related to the input files
1.62 +#---------------------------------------------------------------------------
1.63 +
1.64 +# The INPUT tag can be used to specify the files and/or directories that contain
1.65 +# documented source files. You may enter file names like "myfile.cpp" or
1.66 +# directories like "/usr/src/myproject". Separate the files or directories
1.67 +# with spaces.
1.68 +
1.69 +INPUT = \
1.70 + include/event2/buffer.h \
1.71 + include/event2/buffer_compat.h \
1.72 + include/event2/bufferevent.h \
1.73 + include/event2/bufferevent_compat.h \
1.74 + include/event2/bufferevent_ssl.h \
1.75 + include/event2/dns.h \
1.76 + include/event2/dns_compat.h \
1.77 + include/event2/event.h \
1.78 + include/event2/event_compat.h \
1.79 + include/event2/http.h \
1.80 + include/event2/http_compat.h \
1.81 + include/event2/listener.h \
1.82 + include/event2/rpc.h \
1.83 + include/event2/rpc_compat.h \
1.84 + include/event2/tag.h \
1.85 + include/event2/tag_compat.h \
1.86 + include/event2/thread.h \
1.87 + include/event2/util.h
1.88 +
1.89 +#---------------------------------------------------------------------------
1.90 +# configuration options related to the HTML output
1.91 +#---------------------------------------------------------------------------
1.92 +
1.93 +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
1.94 +# generate HTML output.
1.95 +
1.96 +GENERATE_HTML = YES
1.97 +
1.98 +#---------------------------------------------------------------------------
1.99 +# configuration options related to the LaTeX output
1.100 +#---------------------------------------------------------------------------
1.101 +
1.102 +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
1.103 +# generate Latex output.
1.104 +
1.105 +GENERATE_LATEX = YES
1.106 +
1.107 +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
1.108 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be
1.109 +# put in front of it. If left blank `latex' will be used as the default path.
1.110 +
1.111 +LATEX_OUTPUT = latex
1.112 +
1.113 +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
1.114 +# invoked. If left blank `latex' will be used as the default command name.
1.115 +
1.116 +LATEX_CMD_NAME = latex
1.117 +
1.118 +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
1.119 +# generate index for LaTeX. If left blank `makeindex' will be used as the
1.120 +# default command name.
1.121 +
1.122 +MAKEINDEX_CMD_NAME = makeindex
1.123 +
1.124 +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
1.125 +# LaTeX documents. This may be useful for small projects and may help to
1.126 +# save some trees in general.
1.127 +
1.128 +COMPACT_LATEX = NO
1.129 +
1.130 +# The PAPER_TYPE tag can be used to set the paper type that is used
1.131 +# by the printer. Possible values are: a4, a4wide, letter, legal and
1.132 +# executive. If left blank a4wide will be used.
1.133 +
1.134 +PAPER_TYPE = a4wide
1.135 +
1.136 +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
1.137 +# packages that should be included in the LaTeX output.
1.138 +
1.139 +EXTRA_PACKAGES =
1.140 +
1.141 +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1.142 +# the generated latex document. The header should contain everything until
1.143 +# the first chapter. If it is left blank doxygen will generate a
1.144 +# standard header. Notice: only use this tag if you know what you are doing!
1.145 +
1.146 +LATEX_HEADER =
1.147 +
1.148 +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
1.149 +# is prepared for conversion to pdf (using ps2pdf). The pdf file will
1.150 +# contain links (just like the HTML output) instead of page references
1.151 +# This makes the output suitable for online browsing using a pdf viewer.
1.152 +
1.153 +PDF_HYPERLINKS = NO
1.154 +
1.155 +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
1.156 +# plain latex in the generated Makefile. Set this option to YES to get a
1.157 +# higher quality PDF documentation.
1.158 +
1.159 +USE_PDFLATEX = YES
1.160 +
1.161 +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
1.162 +# command to the generated LaTeX files. This will instruct LaTeX to keep
1.163 +# running if errors occur, instead of asking the user for help.
1.164 +# This option is also used when generating formulas in HTML.
1.165 +
1.166 +LATEX_BATCHMODE = NO
1.167 +
1.168 +# If LATEX_HIDE_INDICES is set to YES then doxygen will not
1.169 +# include the index chapters (such as File Index, Compound Index, etc.)
1.170 +# in the output.
1.171 +
1.172 +LATEX_HIDE_INDICES = NO
1.173 +
1.174 +#---------------------------------------------------------------------------
1.175 +# configuration options related to the man page output
1.176 +#---------------------------------------------------------------------------
1.177 +
1.178 +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
1.179 +# generate man pages
1.180 +
1.181 +GENERATE_MAN = NO
1.182 +
1.183 +# The MAN_EXTENSION tag determines the extension that is added to
1.184 +# the generated man pages (default is the subroutine's section .3)
1.185 +
1.186 +MAN_EXTENSION = .3
1.187 +
1.188 +# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
1.189 +# then it will generate one additional man file for each entity
1.190 +# documented in the real man page(s). These additional files
1.191 +# only source the real man page, but without them the man command
1.192 +# would be unable to find the correct page. The default is NO.
1.193 +
1.194 +MAN_LINKS = YES
1.195 +
1.196 +#---------------------------------------------------------------------------
1.197 +# Configuration options related to the preprocessor
1.198 +#---------------------------------------------------------------------------
1.199 +
1.200 +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
1.201 +# evaluate all C-preprocessor directives found in the sources and include
1.202 +# files.
1.203 +
1.204 +ENABLE_PREPROCESSING = YES
1.205 +
1.206 +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
1.207 +# names in the source code. If set to NO (the default) only conditional
1.208 +# compilation will be performed. Macro expansion can be done in a controlled
1.209 +# way by setting EXPAND_ONLY_PREDEF to YES.
1.210 +
1.211 +MACRO_EXPANSION = NO
1.212 +
1.213 +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
1.214 +# then the macro expansion is limited to the macros specified with the
1.215 +# PREDEFINED and EXPAND_AS_DEFINED tags.
1.216 +
1.217 +EXPAND_ONLY_PREDEF = NO
1.218 +
1.219 +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
1.220 +# in the INCLUDE_PATH (see below) will be search if a #include is found.
1.221 +
1.222 +SEARCH_INCLUDES = YES
1.223 +
1.224 +# The INCLUDE_PATH tag can be used to specify one or more directories that
1.225 +# contain include files that are not input files but should be processed by
1.226 +# the preprocessor.
1.227 +
1.228 +INCLUDE_PATH =
1.229 +
1.230 +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
1.231 +# patterns (like *.h and *.hpp) to filter out the header-files in the
1.232 +# directories. If left blank, the patterns specified with FILE_PATTERNS will
1.233 +# be used.
1.234 +
1.235 +INCLUDE_FILE_PATTERNS =
1.236 +
1.237 +# The PREDEFINED tag can be used to specify one or more macro names that
1.238 +# are defined before the preprocessor is started (similar to the -D option of
1.239 +# gcc). The argument of the tag is a list of macros of the form: name
1.240 +# or name=definition (no spaces). If the definition and the = are
1.241 +# omitted =1 is assumed. To prevent a macro definition from being
1.242 +# undefined via #undef or recursively expanded use the := operator
1.243 +# instead of the = operator.
1.244 +
1.245 +PREDEFINED = TAILQ_ENTRY RB_ENTRY _EVENT_DEFINED_TQENTRY _EVENT_IN_DOXYGEN
1.246 +
1.247 +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
1.248 +# this tag can be used to specify a list of macro names that should be expanded.
1.249 +# The macro definition that is found in the sources will be used.
1.250 +# Use the PREDEFINED tag if you want to use a different macro definition.
1.251 +
1.252 +EXPAND_AS_DEFINED =
1.253 +
1.254 +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then
1.255 +# doxygen's preprocessor will remove all function-like macros that are alone
1.256 +# on a line, have an all uppercase name, and do not end with a semicolon. Such
1.257 +# function macros are typically used for boiler-plate code, and will confuse
1.258 +# the parser if not removed.
1.259 +
1.260 +SKIP_FUNCTION_MACROS = YES
