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

Comparing libev/README.embed (file contents):
Revision 1.6 by root, Tue Nov 6 19:46:15 2007 UTC vs.
Revision 1.16 by root, Fri Nov 9 21:06:23 2007 UTC

1EMBEDDING THE LIBEV CODE INTO YOUR OWN PROGRAMS 1EMBEDDING THE LIBEV CODE INTO YOUR OWN PROGRAMS
2 2
3 Instead of building the libev library you cna also include the code 3 Instead of building the libev library you can also include the code
4 as-is into your programs. To update, you only have to copy a few files 4 as-is into your programs. To update, you only have to copy a few files
5 into your source tree. 5 into your source tree.
6 6
7 This is how it works: 7 This is how it works:
8 8
… …
15 #define EV_STANDALONE 1 15 #define EV_STANDALONE 1
16 #include "ev.c" 16 #include "ev.c"
17 17
18 This will automatically include ev.h, too, and should be done in a 18 This will automatically include ev.h, too, and should be done in a
19 single C source file only to provide the function implementations. To 19 single C source file only to provide the function implementations. To
20 use it, do the same for ev.h in all users: 20 use it, do the same for ev.h in all files wishing to use this API
21 (best done by writing a wrapper around ev.h that you can include
22 instead and where you can put other configuration options):
21 23
22 #define EV_STANDALONE 1 24 #define EV_STANDALONE 1
23 #include "ev.h" 25 #include "ev.h"
26
27 Both header files and implementation files can be compiled with a C++
28 compiler (at least, thats a stated goal, and breakage will be treated
29 as a bug).
24 30
25 You need the following files in your source tree, or in a directory 31 You need the following files in your source tree, or in a directory
26 in your include path (e.g. in libev/ when using -Ilibev): 32 in your include path (e.g. in libev/ when using -Ilibev):
27 33
28 ev.h 34 ev.h
29 ev.c 35 ev.c
30 ev_vars.h 36 ev_vars.h
31 ev_wrap.h 37 ev_wrap.h
32 ev_win32.c 38 ev_win32.c
33 39
34 ev_select.c only when select backend is enabled (which is by default) 40 ev_select.c only when select backend is enabled (which is is by default)
35 ev_poll.c only when poll backend is enabled (disabled by default) 41 ev_poll.c only when poll backend is enabled (disabled by default)
36 ev_epoll.c only when the epoll backend is enabled (disabled by default) 42 ev_epoll.c only when the epoll backend is enabled (disabled by default)
37 ev_kqueue.c only when the kqueue backend is enabled (disabled by default) 43 ev_kqueue.c only when the kqueue backend is enabled (disabled by default)
38 44
39 "ev.c" includes the backend files directly when enabled. 45 "ev.c" includes the backend files directly when enabled.
… …
90 If undefined or defined to be "1", libev will compile in support 96 If undefined or defined to be "1", libev will compile in support
91 for the select(2) backend. No attempt at autodetection will be 97 for the select(2) backend. No attempt at autodetection will be
92 done: if no other method takes over, select will be it. Otherwise 98 done: if no other method takes over, select will be it. Otherwise
93 the select backend will not be compiled in. 99 the select backend will not be compiled in.
94 100
101 EV_SELECT_USE_WIN32_HANDLES
102
103 When defined to 1, the select backend will assume that select
104 doesn't understand file descriptors but wants osf handles on
105 win32 (this is the case when the select to be used is the winsock
106 select). This means that it will call _get_osfhandle on the fd to
107 convert it to an OS handle. Should not be defined on non-win32
108 platforms.
109
95 EV_USE_POLL 110 EV_USE_POLL
96 111
97 If defined to be "1", libev will compile in support for the poll(2) 112 If defined to be "1", libev will compile in support for the poll(2)
98 backend. No attempt at autodetection will be done. poll usually 113 backend. No attempt at autodetection will be done. poll usually
99 performs worse than select, so its not enabled by default (it is 114 performs worse than select, so its not enabled by default (it is
… …
112 style kqueue backend. Its availability will be detected at runtime, 127 style kqueue backend. Its availability will be detected at runtime,
113 otherwise another method will be used as fallback. This is the 128 otherwise another method will be used as fallback. This is the
114 preferred backend for BSD and BSd-like systems. Darwin brokenness 129 preferred backend for BSD and BSd-like systems. Darwin brokenness
115 will be detected at runtime and routed around by disabling this 130 will be detected at runtime and routed around by disabling this
116 backend. 131 backend.
132
133 EV_H
134
135 The name of the ev.h header file used to include it. The default
136 if undefined is <ev.h> in event.h and "ev.h" in ev.c. This can
137 be used to virtually rename the ev.h header file in case of
138 conflicts.
139
140 EV_EVENT_H
141
142 Similarly to EV_H, this macro cna be used to override event.c's idea
143 of how the event.h header can be found.
117 144
118 EV_COMMON 145 EV_COMMON
119 146
120 By default, all watchers have a "void *data" member. By redefining 147 By default, all watchers have a "void *data" member. By redefining
121 this macro to a something else you can include more and other types 148 this macro to a something else you can include more and other types
… …
141 you can create additional independent event loops. Otherwise there 168 you can create additional independent event loops. Otherwise there
142 will be no support for multiple event loops and there is no first 169 will be no support for multiple event loops and there is no first
143 event loop pointer argument. Instead, all functions act on the 170 event loop pointer argument. Instead, all functions act on the
144 single default loop. 171 single default loop.
145 172
173 EV_CB_DECLARE(type)
174 EV_CB_INVOKE(watcher,revents)
175
176 Can be used to change the callback member declaration in each
177 watcher, and the way callbacks are invoked. Must expand to a struct
178 member definition and a statement, respectively. See the ev.v
179 header file for their default definitions. One possible use for overriding
180 these is to avoid the ev_loop pointer as first argument in all cases, or
181 to use method calls instead of plain function calls in C++.
182
146EXAMPLES 183EXAMPLES
147 184
148 For a real-world example of a program the includes libev 185 For a real-world example of a program the includes libev
149 verbatim, you can have a look at the EV perl module 186 verbatim, you can have a look at the EV perl module
150 (http://software.schmorp.de/pkg/EV.html). It has the libev files in 187 (http://software.schmorp.de/pkg/EV.html). It has the libev files in

Diff Legend

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