mirror of /home/gitosis/repositories/libev.git
*** empty log message ***
parent
1e54f9a230
commit
2c44baf6db
10
README.embed
10
README.embed
|
@ -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
|
||||
|
@ -36,6 +38,8 @@ FILESETS
|
|||
|
||||
"ev.c" includes the backend files directly when enabled.
|
||||
|
||||
LIBEVENT COMPATIBILITY API
|
||||
|
||||
To include the libevent compatibility API, also include:
|
||||
|
||||
#include "event.c"
|
||||
|
@ -144,7 +148,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.
|
||||
|
||||
|
|
Loading…
Reference in New Issue