X-Git-Url: https://git.llucax.com/software/libev.git/blobdiff_plain/f4f2094b6a36eac7778c5091ee4160a2f403e808..2fa1c9cb48b3bbf9d5e305dbf3d4269abcce0ec2:/README.embed diff --git a/README.embed b/README.embed index b6322d9..28bbe07 100644 --- a/README.embed +++ b/README.embed @@ -1,6 +1,6 @@ EMBEDDING THE LIBEV CODE INTO YOUR OWN PROGRAMS - Instead of building the libev library you cna also include the code + Instead of building the libev library you can also include the code as-is into your programs. To update, you only have to copy a few files into your source tree. @@ -8,6 +8,8 @@ EMBEDDING THE LIBEV CODE INTO YOUR OWN PROGRAMS FILESETS + CORE EVENT LOOP + To include only the libev core (all the ev_* functions): #define EV_STANDALONE 1 @@ -27,6 +29,16 @@ FILESETS ev.c ev_vars.h ev_wrap.h + ev_win32.c + + ev_select.c only when select backend is enabled (which is by default) + ev_poll.c only when poll backend is enabled (disabled by default) + ev_epoll.c only when the epoll backend is enabled (disabled by default) + ev_kqueue.c only when the kqueue backend is enabled (disabled by default) + + "ev.c" includes the backend files directly when enabled. + + LIBEVENT COMPATIBILITY API To include the libevent compatibility API, also include: @@ -80,6 +92,15 @@ PREPROCESSOR SYMBOLS done: if no other method takes over, select will be it. Otherwise the select backend will not be compiled in. + EV_SELECT_USE_WIN32_HANDLES + + When defined to 1, the select backend will assume that select + doesn't understand file descriptors but wants osf handles on + win32 (this is the case when the select to be used is the winsock + select). This means that it will call _get_osfhandle on the fd to + convert it to an OS handle. Should not be defined on non-win32 + platforms. + EV_USE_POLL If defined to be "1", libev will compile in support for the poll(2) @@ -114,7 +135,7 @@ PREPROCESSOR SYMBOLS #define EV_COMMON \ SV *self; /* contains this struct */ \ - SV *cb_sv, *fh; + SV *cb_sv, *fh /* note no trailing ";" */ EV_PROTOTYPES @@ -136,7 +157,7 @@ EXAMPLES For a real-world example of a program the includes libev verbatim, you can have a look at the EV perl module (http://software.schmorp.de/pkg/EV.html). It has the libev files in - the liev/ subdirectory and includes them in the EV/EVAPI.h (public - interface) and EV.xs (implementation) files. Only EV.xs file will be - compiled. + the libev/ subdirectory and includes them in the EV/EVAPI.h (public + interface) and EV.xs (implementation) files. Only the EV.xs file will + be compiled.