ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/EV/Makefile.PL
(Generate patch)

Comparing EV/Makefile.PL (file contents):
Revision 1.24 by root, Fri Nov 23 03:39:15 2007 UTC vs.
Revision 1.54 by root, Tue Oct 22 10:43:05 2013 UTC

1use 5.006; 1use 5.008002;
2 2
3use strict qw(vars subs);
3use Config; 4use Config;
4use ExtUtils::MakeMaker; 5use ExtUtils::MakeMaker;
5 6
6unless (-e "libev/ev_epoll.c") { 7unless (-e "libev/ev_epoll.c") {
7 print <<EOF; 8 print <<EOF;
34 35
35*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 36*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
36 37
37 38
38POSIX optionally offers support for a monotonic clock source. EV 39POSIX optionally offers support for a monotonic clock source. EV
39can take advantage of this clock source to detect time jumps 40can take advantage of this clock source to detect time jumps more
40reliably. Unfortunately, some systems are bound to be broken, so you can 41reliably. Unfortunately, some systems are bound to be broken, so you can
41disable this here: you can completely disable the detection and use of 42disable this here: you can completely disable the detection and use of
42the monotonic clock by answering 'n' here. Support for this clock type 43the monotonic clock by answering 'n' here. Support for this clock type
43will otherwise be autodetected at both compile- and runtime. 44will otherwise be autodetected at both compile- and runtime. (this setting
45currently affects the use of nanosleep over select as well).
44 46
45EOF 47EOF
46 48
47$DEFINE .= " -DEV_USE_MONOTONIC=" . (0 + (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/)); 49my $DEFINE .= " -DEV_USE_MONOTONIC=" . (0 + (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/));
48 50
49print <<EOF; 51print <<EOF;
50 52
51*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 53*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
52 54
53 55
54POSIX optionally offers support for a (potentially) high-resolution 56POSIX optionally offers support for a (potentially) high-resolution
55realtime clock interface. In a good implementation, using it is faster 57realtime clock interface. In a good implementation, using it is faster
56than the normal method of using gettimeofday. Unfortunately, this option 58than the normal method of using gettimeofday. Unfortunately, this option
57is also bound to be broken on some systems, so you can disable use and 59is also bound to be broken on some systems, and current EV versions do not
58probing of this feature altogether here. Otherwise support for this clock 60actually call gettimeofday very often, so it defaults to no.
59type will be autodetected at compiletime.
60 61
61EOF 62EOF
62 63
63$DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "y") =~ /[yY]/)); 64$DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/));
64 65
65print <<EOF; 66print <<EOF;
66 67
67*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 68*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
68 69
69 70
70EV can use various backends with various portability issue. The select 71EV can use various backends with various portability issues. The select
71backend is the most portable and makes for a good fallback, but it can be 72backend is the most portable and makes for a good fallback, but it can be
72limited to a low number of file descriptors and/or might not compile. If 73limited to a low number of file descriptors and/or might not compile. If
73you have problems with compiling ev_select.c, you might try to play around 74you have problems with compiling ev_select.c, you might try to play around
74with disabling it here, or forcing it to use the fd_set provided by your 75with disabling it here, or forcing it to use the fd_set provided by your
75OS, via the next question. I highly recommend keeping it in. 76OS, via the next question. I highly recommend keeping it in.
126fall back to using select when epoll isn't available. If unsure, accept 127fall back to using select when epoll isn't available. If unsure, accept
127the default. 128the default.
128 129
129EOF 130EOF
130 131
132my $can_epoll = -e "/usr/include/sys/epoll.h";
133$can_epoll = $ENV{EV_EPOLL} if exists $ENV{EV_EPOLL};
131$DEFINE .= " -DEV_USE_EPOLL=" . (0 + (prompt ("Enable epoll backend (y/n)?", (-e "/usr/include/sys/epoll.h") ? "y" : "n") =~ /[yY]/)); 134$DEFINE .= " -DEV_USE_EPOLL=" . (0 + (prompt ("Enable epoll backend (y/n)?", $can_epoll ? "y" : "n") =~ /[yY]/));
132 135
133print <<EOF; 136print <<EOF;
134 137
135*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 138*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
136 139
137 140
138Similarly to the epoll backend above, EV can take advantage of kqueue on 141Similarly to the epoll backend above, EV can take advantage of kqueue on
139many BSD systems. Support for kqueue will be detected at runtime, with a 142many BSD systems. Support for kqueue will be detected at runtime, with a
140safe fallback to other methods when it cannot be used. 143safe fallback to other methods when it cannot be used.
141 144
142Note that kqueue is broken on most operating systems, so it defaults to 145Note that kqueue is broken on most operating systems, so by default it
143'n' on everything but netbsd. Here is what we know: 146won't be used on many platforms, but you can still create your own event
147loop with kqueue backend if you ask specifically for it.
144 148
149Here is what we know:
150
145NetBSD: working in at least 3.1. Yeah! :) 151NetBSD: partially working in at least 3.1 and later. Yeah! :)
146FreeBSD: broken on at least 6.2-STABLE, 152FreeBSD: broken on at least 6.2-STABLE, spotty in later versions,
147 sockets and pipes *might* work, ptys definitely don't. 153 sockets *likely* work, ptys definitely don't.
148OpenBSD: reports indicate that it likely doesn't work 154OpenBSD: reports indicate that it likely doesn't work
149 (similar problems as on FreeBSD). 155 (similar problems as on FreeBSD).
150OS X: completely, utterly broken on at least <= 10.5. 156OS X: completely, utterly broken on at least <= 10.6.
151 157
152EOF 158EOF
153 159
154my $can_kqueue = $^O =~ /netbsd/i && -e "/usr/include/sys/event.h"; 160my $can_kqueue = -e "/usr/include/sys/event.h";
155 161$can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE};
156$DEFINE .= " -DEV_USE_KQUEUE=" . (0 + (prompt ("Enable kqueue backend (y/n)?", $can_kqueue ? "y" : "n") =~ /[yY]/)); 162$DEFINE .= " -DEV_USE_KQUEUE=" . (0 + (prompt ("Enable kqueue backend (y/n)?", $can_kqueue ? "y" : "n") =~ /[yY]/));
157 163
158print <<EOF; 164print <<EOF;
159 165
160*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 166*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
161 167
162 168
163Similarly to the kqueue backend above, EV can take advantage of the 169Similarly to the kqueue backend above, EV can take advantage of the
164solaris 10 port interface. Support for port will be detected at runtime, 170solaris 10 event port interface. Support for event ports will be detected
165with a safe fallback to other methods when it cannot be used. 171at runtime, with a safe fallback to other methods when it cannot be used.
166 172
167EOF 173EOF
168 174
169$DEFINE .= " -DEV_USE_PORT=" . (0 + (prompt ("Enable port backend (y/n)?", (-e "/usr/include/sys/port.h") ? "y" : "n") =~ /[yY]/)); 175$DEFINE .= " -DEV_USE_PORT=" . (0 + (prompt ("Enable event port backend (y/n)?", (-e "/usr/include/sys/port.h") ? "y" : "n") =~ /[yY]/));
170 176
171print <<EOF; 177print <<EOF;
172 178
173*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 179*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
174 180
176EV needs the functions pthread_atfork and clock_gettime. On most systems 182EV needs the functions pthread_atfork and clock_gettime. On most systems
177you need some special libraries for this (such as -lrt and -lpthread). You 183you need some special libraries for this (such as -lrt and -lpthread). You
178can specify additional libraries to provide these calls (and any other 184can specify additional libraries to provide these calls (and any other
179required by EV) now, or accept the default. 185required by EV) now, or accept the default.
180 186
181EOF 187On GNU/Linux systems, EV uses the LSB 3.1 __register_atfork function
188to avoid the dependency on libpthread, and directly uses the clock_gettime
189syscall to avoid a dependency on librt.
182 190
191EOF
192
183$SOLARIS_LIBS = $^O =~ /solaris/ ? " -lsocket -lnsl" : ""; 193my $solaris_libs = $^O =~ /solaris/i ? "-lsocket -lnsl" : "";
184 194my $librt = $^O =~ /linux/i ? "" : "-lpthread -lrt";
195my $LIBS = exists $ENV{EV_LIBS} ? $ENV{EV_LIBS} : "$librt $solaris_libs";
185$LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", "-lpthread -lrt$SOLARIS_LIBS"; 196$LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", $LIBS;
186 197
187 198
188print <<EOF; 199print <<EOF;
189 200
190*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 201*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
191 202
192 203
193EOF 204A backend of a different kind is the Linux inotify(7) interface, which can
205be used to speed up (and reduce resource consumption) of stat watchers. If
206you have the include file and libc support for it, it is usually a good
207idea to enable it, as kernel availability is detected at runtime.
194 208
209EOF
210
211my $can_inotify = -e "/usr/include/sys/inotify.h";
212$can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY};
213$DEFINE .= " -DEV_USE_INOTIFY=" . (0 + (prompt ("Enable inotify support (y/n)?", $can_inotify ? "y" : "n") =~ /[yY]/));
214
215print <<EOF;
216
217*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
218
219
220Another useful bit of functionality is the Linux eventfd, which is useful
221for faster signal handling (don't care) and intra-thread communications
222(more relevant). Kernel support for this will be probed at runtime, but
223your libc must contain the necessary wrapper. Glibc 2.7 and later should
224have this wrapper.
225
226EOF
227
228my $can_eventfd = -e "/usr/include/sys/eventfd.h";
229$can_eventfd = $ENV{EV_EVENTFD} if exists $ENV{EV_EVENTFD};
230$DEFINE .= " -DEV_USE_EVENTFD=" . (0 + (prompt ("Enable linux eventfd support (y/n)?", $can_eventfd ? "y" : "n") =~ /[yY]/));
231
232print <<EOF;
233
234*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
235
236
237Another sometimes useful bit of functionality is the Linux signalfd, which
238is useful for faster signal handling (don't care). Kernel support for
239this will be probed at runtime, but your libc must contain the necessary
240wrapper. Glibc 2.7 and later should have this wrapper.
241
242EOF
243
244my $can_signalfd = -e "/usr/include/sys/signalfd.h";
245$can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD};
246$DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/));
247
248print <<EOF;
249
250*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
251
252
253Very rarely, people want to tweak EV even more, e.g. to exclude
254or include certain watcher types or backends. This can be done by adding
255extra -D options here, or via the EV_EXTRA_DEFS environment variable.
256
257For example, if you run into compile problems because of missing memory
258fences (or you just want extra performance), you can tell EV to not support
259smp and threads via -DEV_NO_THREADS.
260
261Normal persons just press enter.
262
263EOF
264
265$DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}";
266
267print <<EOF;
268
269*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
270
271
272EOF
273
195my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 2.6 } ? (AnyEvent => 2.6) : (); 274my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 5.29 } ? (AnyEvent => 5.29) : ();
196 275
197WriteMakefile( 276WriteMakefile(
198 dist => { 277 dist => {
199 PREOP => 'pod2text EV.pm | tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;', 278 PREOP => 'pod2text EV.pm | tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;',
200 COMPRESS => 'gzip -9v', 279 COMPRESS => 'gzip -9v',
201 SUFFIX => '.gz', 280 SUFFIX => '.gz',
202 }, 281 },
203 depend => { 282 depend => {
204 "EV.c" => "EV/EVAPI.h " 283 "EV.c" => "EV/EVAPI.h "
205 . "libev/ev.c libev/ev.h libev/ev_epoll.c libev/ev_select.c libev/ev_kqueue.c libev/ev_poll.c " 284 . "libev/ev.c libev/ev.h libev/ev_epoll.c libev/ev_select.c libev/ev_kqueue.c libev/ev_poll.c "
206 . "libev/event.h libev/event.c evdns.h evdns.c libev/ev_vars.h libev/ev_wrap.h", 285 . "libev/ev_vars.h libev/ev_wrap.h",
207 }, 286 },
208 INC => "-Ilibev", 287 INC => "-Ilibev",
209 DEFINE => "$DEFINE", 288 DEFINE => "$DEFINE",
210 NAME => "EV", 289 NAME => "EV",
211 LIBS => [$LIBS], 290 LIBS => [$LIBS],
212 PREREQ_PM => { 291 PREREQ_PM => {
213 @anyevent, 292 @anyevent,
293 "common::sense" => 0,
214 }, 294 },
215 VERSION_FROM => "EV.pm", 295 VERSION_FROM => "EV.pm",
216 PM => { 296 PM => {
217 'EV.pm' => '$(INST_LIBDIR)/EV.pm', 297 'EV.pm' => '$(INST_LIB)/EV.pm',
218 'EV/DNS.pm' => '$(INST_LIBDIR)/EV/DNS.pm',
219 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h', 298 'EV/EVAPI.h' => '$(INST_LIB)/EV/EVAPI.h',
220 'EV/MakeMaker.pm' => '$(INST_LIBDIR)/EV/MakeMaker.pm', 299 'EV/MakeMaker.pm' => '$(INST_LIB)/EV/MakeMaker.pm',
221 'libev/ev.h' => '$(INST_LIBDIR)/EV/ev.h', 300 'libev/ev.h' => '$(INST_LIB)/EV/ev.h',
301 'libev/ev.pod' => '$(INST_LIB)/EV/libev.pod',
222 }, 302 },
303 MAN3PODS => {
304 'EV.pm' => '$(INST_MAN3DIR)/EV.$(MAN3EXT)',
305 'EV/MakeMaker.pm' => '$(INST_MAN3DIR)/EV::MakeMaker.$(MAN3EXT)',
306 'libev/ev.pod' => '$(INST_MAN3DIR)/EV::libev.$(MAN3EXT)',
307 },
223); 308);
224 309
225 310

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines