From: root
ev.c includes the backend files directly when enabled, so you only need -to compile a single file.
+to compile this single file.Instead of using EV_STANDALONE=1
and providing your config in
whatever way you want, you can also m4_include([libev.m4])
in your
-configure.ac and leave EV_STANDALONE
off. ev.c will then include
-config.h and configure itself accordingly.
EV_STANDALONE
undefined. ev.c will then
+include config.h and configure itself accordingly.
For this of course you need the m4 file:
libev.m4 diff --git a/ev.pod b/ev.pod index 1a9af3f..d1c5d63 100644 --- a/ev.pod +++ b/ev.pod @@ -1471,14 +1471,14 @@ in your include path (e.g. in libev/ when using -Ilibev): ev_win32.c required on win32 platforms only - ev_select.c only when select backend is enabled (which is is by default) + 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_port.c only when the solaris port backend is enabled (disabled by default) Fincludes the backend files directly when enabled, so you only need -to compile a single file. +to compile this single file. =head3 LIBEVENT COMPATIBILITY API @@ -1501,8 +1501,8 @@ You need the following additional files for this: Instead of using C and providing your config in whatever way you want, you can also C in your -F and leave C off. F will then include -F and configure itself accordingly. +F and leave C undefined. F will then +include F and configure itself accordingly. For this of course you need the m4 file: