1 | use 5.006; |
1 | use 5.008002; |
2 | |
2 | |
3 | use strict qw(vars subs); |
3 | use strict qw(vars subs); |
4 | use Config; |
4 | use Config; |
5 | use ExtUtils::MakeMaker; |
5 | use ExtUtils::MakeMaker; |
6 | |
6 | |
… | |
… | |
35 | |
35 | |
36 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
36 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
37 | |
37 | |
38 | |
38 | |
39 | POSIX optionally offers support for a monotonic clock source. EV |
39 | POSIX optionally offers support for a monotonic clock source. EV |
40 | can take advantage of this clock source to detect time jumps |
40 | can take advantage of this clock source to detect time jumps more |
41 | reliably. Unfortunately, some systems are bound to be broken, so you can |
41 | reliably. Unfortunately, some systems are bound to be broken, so you can |
42 | disable this here: you can completely disable the detection and use of |
42 | disable this here: you can completely disable the detection and use of |
43 | the monotonic clock by answering 'n' here. Support for this clock type |
43 | the monotonic clock by answering 'n' here. Support for this clock type |
44 | will otherwise be autodetected at both compile- and runtime. (this setting |
44 | will otherwise be autodetected at both compile- and runtime. (this setting |
45 | currently affects the use of nanosleep over select as well). |
45 | currently affects the use of nanosleep over select as well). |
… | |
… | |
55 | |
55 | |
56 | POSIX optionally offers support for a (potentially) high-resolution |
56 | POSIX optionally offers support for a (potentially) high-resolution |
57 | realtime clock interface. In a good implementation, using it is faster |
57 | realtime clock interface. In a good implementation, using it is faster |
58 | than the normal method of using gettimeofday. Unfortunately, this option |
58 | than the normal method of using gettimeofday. Unfortunately, this option |
59 | is also bound to be broken on some systems, and current EV versions do not |
59 | is also bound to be broken on some systems, and current EV versions do not |
60 | actually call C<gettimeofday> very often, so ti defaults to no. |
60 | actually call gettimeofday very often, so it defaults to no. |
61 | |
61 | |
62 | EOF |
62 | EOF |
63 | |
63 | |
64 | $DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/)); |
64 | $DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/)); |
65 | |
65 | |
66 | print <<EOF; |
66 | print <<EOF; |
67 | |
67 | |
68 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
68 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
69 | |
69 | |
70 | |
70 | |
71 | EV can use various backends with various portability issue. The select |
71 | EV can use various backends with various portability issues. The select |
72 | backend is the most portable and makes for a good fallback, but it can be |
72 | backend is the most portable and makes for a good fallback, but it can be |
73 | limited to a low number of file descriptors and/or might not compile. If |
73 | limited to a low number of file descriptors and/or might not compile. If |
74 | you have problems with compiling ev_select.c, you might try to play around |
74 | you have problems with compiling ev_select.c, you might try to play around |
75 | with disabling it here, or forcing it to use the fd_set provided by your |
75 | with disabling it here, or forcing it to use the fd_set provided by your |
76 | OS, via the next question. I highly recommend keeping it in. |
76 | OS, via the next question. I highly recommend keeping it in. |
… | |
… | |
146 | won't be used on many platforms, but you can still create your own event |
146 | won't be used on many platforms, but you can still create your own event |
147 | loop with kqueue backend if you ask specifically for it. |
147 | loop with kqueue backend if you ask specifically for it. |
148 | |
148 | |
149 | Here is what we know: |
149 | Here is what we know: |
150 | |
150 | |
151 | NetBSD: partially working in at least 3.1. Yeah! :) |
151 | NetBSD: partially working in at least 3.1 and later. Yeah! :) |
152 | FreeBSD: broken on at least 6.2-STABLE, |
152 | FreeBSD: broken on at least 6.2-STABLE, spotty in later versions, |
153 | sockets *likely* work, ptys definitely don't. |
153 | sockets *likely* work, ptys definitely don't. |
154 | OpenBSD: reports indicate that it likely doesn't work |
154 | OpenBSD: reports indicate that it likely doesn't work |
155 | (similar problems as on FreeBSD). |
155 | (similar problems as on FreeBSD). |
156 | OS X: completely, utterly broken on at least < 10.5. |
156 | OS X: completely, utterly broken on at least <= 10.6. |
157 | |
157 | |
158 | EOF |
158 | EOF |
159 | |
159 | |
160 | my $can_kqueue = -e "/usr/include/sys/event.h"; |
160 | my $can_kqueue = -e "/usr/include/sys/event.h"; |
161 | $can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE}; |
161 | $can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE}; |
… | |
… | |
227 | print <<EOF; |
227 | print <<EOF; |
228 | |
228 | |
229 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
229 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
230 | |
230 | |
231 | |
231 | |
232 | EOF |
232 | Another sometimes useful bit of functionality is the Linux signalfd, which |
|
|
233 | is useful for faster signal handling (don't care). Kernel support for |
|
|
234 | this will be probed at runtime, but your libc must contain the necessary |
|
|
235 | wrapper. Glibc 2.7 and later should have this wrapper. |
233 | |
236 | |
|
|
237 | EOF |
|
|
238 | |
|
|
239 | my $can_signalfd = -e "/usr/include/sys/signalfd.h"; |
|
|
240 | $can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD}; |
|
|
241 | $DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/)); |
|
|
242 | |
|
|
243 | print <<EOF; |
|
|
244 | |
|
|
245 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
|
|
246 | |
|
|
247 | |
|
|
248 | Very rarely, people want to tweak EV even more, e.g. to exclude |
|
|
249 | or incldue certain watcher types or backends. Thisc na be done by adding |
|
|
250 | extra -D options here, or via the EV_EXTRA_DEFS environment variable. |
|
|
251 | Normal persons just press enter. |
|
|
252 | |
|
|
253 | EOF |
|
|
254 | |
|
|
255 | $DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}"; |
|
|
256 | |
|
|
257 | print <<EOF; |
|
|
258 | |
|
|
259 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
|
|
260 | |
|
|
261 | |
|
|
262 | EOF |
|
|
263 | |
234 | my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 2.6 } ? (AnyEvent => 2.6) : (); |
264 | my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 5.29 } ? (AnyEvent => 5.29) : (); |
235 | |
265 | |
236 | WriteMakefile( |
266 | WriteMakefile( |
237 | dist => { |
267 | dist => { |
238 | PREOP => 'pod2text EV.pm | tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;', |
268 | PREOP => 'pod2text EV.pm | tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;', |
239 | COMPRESS => 'gzip -9v', |
269 | COMPRESS => 'gzip -9v', |
… | |
… | |
248 | DEFINE => "$DEFINE", |
278 | DEFINE => "$DEFINE", |
249 | NAME => "EV", |
279 | NAME => "EV", |
250 | LIBS => [$LIBS], |
280 | LIBS => [$LIBS], |
251 | PREREQ_PM => { |
281 | PREREQ_PM => { |
252 | @anyevent, |
282 | @anyevent, |
|
|
283 | "common::sense" => 0, |
253 | }, |
284 | }, |
254 | VERSION_FROM => "EV.pm", |
285 | VERSION_FROM => "EV.pm", |
255 | PM => { |
286 | PM => { |
256 | 'EV.pm' => '$(INST_LIBDIR)/EV.pm', |
287 | 'EV.pm' => '$(INST_LIBDIR)/EV.pm', |
257 | 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h', |
288 | 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h', |