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

Comparing EV/Makefile.PL (file contents):
Revision 1.36 by root, Wed Oct 29 17:41:11 2008 UTC vs.
Revision 1.49 by root, Thu Dec 30 07:37:38 2010 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. (this setting 44will otherwise be autodetected at both compile- and runtime. (this setting
44currently affects the use of nanosleep over select as well). 45currently affects the use of nanosleep over select as well).
45 46
46EOF 47EOF
47 48
48$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]/));
49 50
50print <<EOF; 51print <<EOF;
51 52
52*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 53*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
53 54
54 55
55POSIX optionally offers support for a (potentially) high-resolution 56POSIX optionally offers support for a (potentially) high-resolution
56realtime clock interface. In a good implementation, using it is faster 57realtime clock interface. In a good implementation, using it is faster
57than the normal method of using gettimeofday. Unfortunately, this option 58than the normal method of using gettimeofday. Unfortunately, this option
58is 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
59probing of this feature altogether here. Otherwise support for this clock 60actually call gettimeofday very often, so it defaults to no.
60type will be autodetected at compiletime.
61 61
62EOF 62EOF
63 63
64$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]/));
65 65
66print <<EOF; 66print <<EOF;
67 67
68*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 68*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
69 69
70 70
71EV can use various backends with various portability issue. The select 71EV can use various backends with various portability issues. The select
72backend 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
73limited 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
74you 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
75with 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
76OS, via the next question. I highly recommend keeping it in. 76OS, via the next question. I highly recommend keeping it in.
127fall 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
128the default. 128the default.
129 129
130EOF 130EOF
131 131
132my $can_epoll = -e "/usr/include/sys/epoll.h";
133$can_epoll = $ENV{EV_EPOLL} if exists $ENV{EV_EPOLL};
132$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]/));
133 135
134print <<EOF; 136print <<EOF;
135 137
136*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 138*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
137 139
140many 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
141safe fallback to other methods when it cannot be used. 143safe fallback to other methods when it cannot be used.
142 144
143Note that kqueue is broken on most operating systems, so by default it 145Note that kqueue is broken on most operating systems, so by default it
144won't be used on many platforms, but you can still create your own event 146won't be used on many platforms, but you can still create your own event
145loop with qkueue backend. 147loop with kqueue backend if you ask specifically for it.
146 148
147Here is what we know: 149Here is what we know:
148 150
149NetBSD: partially working in at least 3.1. Yeah! :) 151NetBSD: partially working in at least 3.1 and later. Yeah! :)
150FreeBSD: broken on at least 6.2-STABLE, 152FreeBSD: broken on at least 6.2-STABLE, spotty in later versions,
151 sockets *likely* work, ptys definitely don't. 153 sockets *likely* work, ptys definitely don't.
152OpenBSD: reports indicate that it likely doesn't work 154OpenBSD: reports indicate that it likely doesn't work
153 (similar problems as on FreeBSD). 155 (similar problems as on FreeBSD).
154OS X: completely, utterly broken on at least < 10.5. 156OS X: completely, utterly broken on at least <= 10.6.
155 157
156EOF 158EOF
157 159
158my $can_kqueue = -e "/usr/include/sys/event.h"; 160my $can_kqueue = -e "/usr/include/sys/event.h";
159 161$can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE};
160$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]/));
161 163
162print <<EOF; 164print <<EOF;
163 165
164*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 166*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
182can specify additional libraries to provide these calls (and any other 184can specify additional libraries to provide these calls (and any other
183required by EV) now, or accept the default. 185required by EV) now, or accept the default.
184 186
185EOF 187EOF
186 188
187$SOLARIS_LIBS = $^O =~ /solaris/ ? " -lsocket -lnsl" : ""; 189my $solaris_libs = $^O =~ /solaris/i ? "-lsocket -lnsl" : "";
188 190my $librt = $^O =~ /linux/i ? "-lpthread" : "-lpthread -lrt";
189$LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", "-lpthread -lrt$SOLARIS_LIBS"; 191my $LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", "$librt $solaris_libs";
190 192
191 193
192print <<EOF; 194print <<EOF;
193 195
194*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 196*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
195 197
196 198
197A backend of a different kind is the Linux inotify(7) interface, which can 199A backend of a different kind is the Linux inotify(7) interface, which can
198be used to speed up (and reduce resource consumption) of stat watchers. If 200be used to speed up (and reduce resource consumption) of stat watchers. If
199you have it, it is usually a good idea to enable it. 201you have the include file and libc support for it, it is usually a good
202idea to enable it, as kernel availability is detected at runtime.
200 203
201EOF 204EOF
202 205
203my $can_inotify = -e "/usr/include/sys/inotify.h"; 206my $can_inotify = -e "/usr/include/sys/inotify.h";
204 207$can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY};
205$DEFINE .= " -DEV_USE_INOTIFY=" . (0 + (prompt ("Enable inotify support (y/n)?", $can_inotify ? "y" : "n") =~ /[yY]/)); 208$DEFINE .= " -DEV_USE_INOTIFY=" . (0 + (prompt ("Enable inotify support (y/n)?", $can_inotify ? "y" : "n") =~ /[yY]/));
206 209
207print <<EOF; 210print <<EOF;
208 211
209*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 212*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
215your libc must contain the necessary wrapper. Glibc 2.7 and later should 218your libc must contain the necessary wrapper. Glibc 2.7 and later should
216have this wrapper. 219have this wrapper.
217 220
218EOF 221EOF
219 222
223my $can_eventfd = -e "/usr/include/sys/eventfd.h";
224$can_eventfd = $ENV{EV_EVENTFD} if exists $ENV{EV_EVENTFD};
220$DEFINE .= " -DEV_USE_EVENTFD=" . (0 + (prompt ("Enable linux eventfd support (y/n)?", (-e "/usr/include/sys/eventfd.h") || $ENV{EV_EVENTFD} ? "y" : "n") =~ /[yY]/)); 225$DEFINE .= " -DEV_USE_EVENTFD=" . (0 + (prompt ("Enable linux eventfd support (y/n)?", $can_eventfd ? "y" : "n") =~ /[yY]/));
221 226
222print <<EOF; 227print <<EOF;
223 228
224*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 229*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
225 230
226 231
227EOF 232Another sometimes useful bit of functionality is the Linux signalfd, which
233is useful for faster signal handling (don't care). Kernel support for
234this will be probed at runtime, but your libc must contain the necessary
235wrapper. Glibc 2.7 and later should have this wrapper.
228 236
237EOF
238
239my $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
243print <<EOF;
244
245*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
246
247
248Very rarely, people want to tweak EV even more, e.g. to exclude
249or incldue certain watcher types or backends. Thisc na be done by adding
250extra -D options here, or via the EV_EXTRA_DEFS environment variable.
251Normal persons just press enter.
252
253EOF
254
255$DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}";
256
257print <<EOF;
258
259*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
260
261
262EOF
263
229my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 2.6 } ? (AnyEvent => 2.6) : (); 264my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 5.29 } ? (AnyEvent => 5.29) : ();
230 265
231WriteMakefile( 266WriteMakefile(
232 dist => { 267 dist => {
233 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 . ;',
234 COMPRESS => 'gzip -9v', 269 COMPRESS => 'gzip -9v',
243 DEFINE => "$DEFINE", 278 DEFINE => "$DEFINE",
244 NAME => "EV", 279 NAME => "EV",
245 LIBS => [$LIBS], 280 LIBS => [$LIBS],
246 PREREQ_PM => { 281 PREREQ_PM => {
247 @anyevent, 282 @anyevent,
283 "common::sense" => 0,
248 }, 284 },
249 VERSION_FROM => "EV.pm", 285 VERSION_FROM => "EV.pm",
250 PM => { 286 PM => {
251 'EV.pm' => '$(INST_LIBDIR)/EV.pm', 287 'EV.pm' => '$(INST_LIBDIR)/EV.pm',
252 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h', 288 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h',

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines