ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/README.embed
(Generate patch)

Comparing libev/README.embed (file contents):
Revision 1.13 by root, Fri Nov 9 19:14:37 2007 UTC vs.
Revision 1.26 by root, Fri Nov 16 10:37:28 2007 UTC

… …
33 33
34 ev.h 34 ev.h
35 ev.c 35 ev.c
36 ev_vars.h 36 ev_vars.h
37 ev_wrap.h 37 ev_wrap.h
38 ev_win32.c 38
39 ev_win32.c required on win32 platforms only
39 40
40 ev_select.c only when select backend is enabled (which is is by default) 41 ev_select.c only when select backend is enabled (which is is by default)
41 ev_poll.c only when poll backend is enabled (disabled by default) 42 ev_poll.c only when poll backend is enabled (disabled by default)
42 ev_epoll.c only when the epoll backend is enabled (disabled by default) 43 ev_epoll.c only when the epoll backend is enabled (disabled by default)
43 ev_kqueue.c only when the kqueue backend is enabled (disabled by default) 44 ev_kqueue.c only when the kqueue backend is enabled (disabled by default)
45 ev_port.c only when the solaris port backend is enabled (disabled by default)
44 46
45 "ev.c" includes the backend files directly when enabled. 47 "ev.c" includes the backend files directly when enabled.
46 48
47 LIBEVENT COMPATIBILITY API 49 LIBEVENT COMPATIBILITY API
48 50
… …
59 You need the following additional files for this: 61 You need the following additional files for this:
60 62
61 event.h 63 event.h
62 event.c 64 event.c
63 65
66AUTOCONF SUPPORT
67
68 Instead of using EV_STANDALONE=1 and providing your config in whatever
69 way you want, you can also m4_include([libev.m4]) in your configure.ac
70 and leave EV_STANDALONE off. ev.c will then include "config.h" and
71 configure itself accordingly.
72
64PREPROCESSOR SYMBOLS 73PREPROCESSOR SYMBOLS
65 74
66 Libev can be configured via a variety of preprocessor symbols you have to define 75 Libev can be configured via a variety of preprocessor symbols you have to define
67 before including any of its files. The default is not to build for mulciplicity 76 before including any of its files. The default is not to build for multiplicity
68 and only include the select backend. 77 and only include the select backend.
69 78
70 EV_STANDALONE 79 EV_STANDALONE
71 80
72 Must always be "1", which keeps libev from including config.h or 81 Must always be "1", which keeps libev from including config.h or
73 other files, and it also defines dummy implementations for some 82 other files, and it also defines dummy implementations for some
74 libevent functions (such as logging, which is not supported). It 83 libevent functions (such as logging, which is not supported). It
75 will also not define any of the structs usually found in "event.h" 84 will also not define any of the structs usually found in "event.h"
76 that are not directly supported by libev code alone. 85 that are not directly supported by libev code alone.
77 86
78 EV_H
79
80 The name of the ev.h header file used to include it. The default
81 if undefined is <ev.h> in event.h and "ev.h" in ev.c. This can
82 be used to virtually rename the ev.h header file in case of
83 conflicts.
84
85 EV_EVENT_H
86
87 Similarly to EV_H, this macro cna be used to override event.c's idea
88 of where the event.h header can be found.
89
90 EV_USE_MONOTONIC 87 EV_USE_MONOTONIC
91 88
92 If undefined or defined to be "1", libev will try to detect the 89 If defined to be "1", libev will try to detect the availability
93 availability of the monotonic clock option at both compiletime and 90 of the monotonic clock option at both compiletime and
94 runtime. Otherwise no use of the monotonic clock option will be 91 runtime. Otherwise no use of the monotonic clock option will be
95 attempted. 92 attempted. If you enable this, you usually have to link against
93 librt or something similar. Enabling it when the functionality
94 isn't available is safe, though.
96 95
97 EV_USE_REALTIME 96 EV_USE_REALTIME
98 97
99 If defined to be "1", libev will try to detect the availability 98 If defined to be "1", libev will try to detect the availability
100 of the realtime clock option at compiletime (and assume its 99 of the realtime clock option at compiletime (and assume its
… …
108 If undefined or defined to be "1", libev will compile in support 107 If undefined or defined to be "1", libev will compile in support
109 for the select(2) backend. No attempt at autodetection will be 108 for the select(2) backend. No attempt at autodetection will be
110 done: if no other method takes over, select will be it. Otherwise 109 done: if no other method takes over, select will be it. Otherwise
111 the select backend will not be compiled in. 110 the select backend will not be compiled in.
112 111
113 EV_SELECT_USE_WIN32_HANDLES 112 EV_SELECT_USE_FD_SET
113
114 If defined to 1, then the select backend will use the system fd_set
115 structure. This is useful if libev doesn't compile due to a missing
116 NFDBITS or fd_mask definition or it misguesses the bitset layout on
117 exotic systems. This usually limits the range of file descriptors
118 to some low limit such as 1024 or might have other limitations
119 (winsocket only allows 64 sockets). The FD_SETSIZE macro, set
120 before compilation, might influence the size of the fd_set used.
121
122 EV_SELECT_IS_WINSOCKET
114 123
115 When defined to 1, the select backend will assume that select 124 When defined to 1, the select backend will assume that select
116 doesn't understand file descriptors but wants osf handles on 125 doesn't understand file descriptors but wants osf handles on
117 win32 (this is the case when the select to be used is the winsock 126 win32 (this is the case when the select to be used is the winsock
118 select). This means that it will call _get_osfhandle on the fd to 127 select). This means that it will call _get_osfhandle on the fd to
… …
120 platforms. 129 platforms.
121 130
122 EV_USE_POLL 131 EV_USE_POLL
123 132
124 If defined to be "1", libev will compile in support for the poll(2) 133 If defined to be "1", libev will compile in support for the poll(2)
125 backend. No attempt at autodetection will be done. poll usually 134 backend. Otherwise it will be enabled on non-win32 platforms. It
126 performs worse than select, so its not enabled by default (it is 135 takes precedence over select.
127 also slightly less portable).
128 136
129 EV_USE_EPOLL 137 EV_USE_EPOLL
130 138
131 If defined to be "1", libev will compile in support for the Linux 139 If defined to be "1", libev will compile in support for the Linux
132 epoll backend. Its availability will be detected at runtime, 140 epoll backend. Its availability will be detected at runtime,
… …
136 EV_USE_KQUEUE 144 EV_USE_KQUEUE
137 145
138 If defined to be "1", libev will compile in support for the BSD 146 If defined to be "1", libev will compile in support for the BSD
139 style kqueue backend. Its availability will be detected at runtime, 147 style kqueue backend. Its availability will be detected at runtime,
140 otherwise another method will be used as fallback. This is the 148 otherwise another method will be used as fallback. This is the
141 preferred backend for BSD and BSd-like systems. Darwin brokenness 149 preferred backend for BSD and BSD-like systems. Darwin brokenness
142 will be detected at runtime and routed around by disabling this 150 will be detected at runtime and routed around by disabling this
143 backend. 151 backend.
152
153 EV_USE_PORT
154
155 If defined to be "1", libev will compile in support for the Solaris
156 10 port style backend. Its availability will be detected at runtime,
157 otherwise another method will be used as fallback. This is the
158 preferred backend for Solaris 10 systems.
159
160 EV_USE_DEVPOLL
161
162 reserved for future expansion, works like the USE symbols above.
163
164 EV_H
165
166 The name of the ev.h header file used to include it. The default
167 if undefined is <ev.h> in event.h and "ev.h" in ev.c. This can
168 be used to virtually rename the ev.h header file in case of
169 conflicts.
170
171 EV_EVENT_H
172
173 Similarly to EV_H, this macro cna be used to override event.c's idea
174 of how the event.h header can be found.
175
176 EV_PROTOTYPES
177
178 If defined to be "0", then "ev.h" will not define any function
179 prototypes, but still define all the structs and other
180 symbols. This is occasionally useful.
181
182 EV_MULTIPLICITY
183
184 If undefined or defined to "1", then all event-loop-specific
185 functions will have the "struct ev_loop *" as first argument, and
186 you can create additional independent event loops. Otherwise there
187 will be no support for multiple event loops and there is no first
188 event loop pointer argument. Instead, all functions act on the
189 single default loop.
190
191 EV_PERIODICS
192
193 If undefined or defined to be "1", then periodic timers are
194 supported, otherwise not. This saves a few kb of code.
144 195
145 EV_COMMON 196 EV_COMMON
146 197
147 By default, all watchers have a "void *data" member. By redefining 198 By default, all watchers have a "void *data" member. By redefining
148 this macro to a something else you can include more and other types 199 this macro to a something else you can include more and other types
… …
153 204
154 #define EV_COMMON \ 205 #define EV_COMMON \
155 SV *self; /* contains this struct */ \ 206 SV *self; /* contains this struct */ \
156 SV *cb_sv, *fh /* note no trailing ";" */ 207 SV *cb_sv, *fh /* note no trailing ";" */
157 208
158 EV_PROTOTYPES 209 EV_CB_DECLARE(type)
210 EV_CB_INVOKE(watcher,revents)
211 ev_set_cb(ev,cb)
159 212
160 If defined to be "0", then "ev.h" will not define any function 213 Can be used to change the callback member declaration in each
161 prototypes, but still define all the structs and other 214 watcher, and the way callbacks are invoked and set. Must expand
162 symbols. This is occasionally useful. 215 to a struct member definition and a statement, respectively. See
163 216 the ev.v header file for their default definitions. One possible
164 EV_MULTIPLICITY 217 use for overriding these is to avoid the ev_loop pointer as first
165 218 argument in all cases, or to use method calls instead of plain
166 If undefined or defined to "1", then all event-loop-specific 219 function calls in C++.
167 functions will have the "struct ev_loop *" as first argument, and
168 you can create additional independent event loops. Otherwise there
169 will be no support for multiple event loops and there is no first
170 event loop pointer argument. Instead, all functions act on the
171 single default loop.
172 220
173EXAMPLES 221EXAMPLES
174 222
175 For a real-world example of a program the includes libev 223 For a real-world example of a program the includes libev
176 verbatim, you can have a look at the EV perl module 224 verbatim, you can have a look at the EV perl module

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines