ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/EV/Makefile.PL
Revision: 1.57
Committed: Sat Jun 20 11:11:01 2015 UTC (8 years, 10 months ago) by root
Content type: text/plain
Branch: MAIN
CVS Tags: EV-rel-4_25, EV-rel-4_22, EV-rel-4_20, EV-rel-4_21
Changes since 1.56: +2 -2 lines
Log Message:
4.20

File Contents

# Content
1 use strict qw(vars subs);
2 use Canary::Stability EV => 1, 5.008002;
3 use Config;
4 use ExtUtils::MakeMaker;
5
6 sub have_inc($) {
7 scalar grep -r "$_/$_[0]", $Config{usrinc}, split / /, $Config{incpth}
8 }
9
10 my $DEFINE;
11
12 unless (-e "libev/ev_epoll.c") {
13 print <<EOF;
14
15 ***
16 *** ERROR: libev is missing or damaged. If you used a CVS check-out of EV,
17 *** you also have to check-out the "libev" module from the same CVS
18 *** repository into the EV dir (i.e. EV/libev from outside).
19 ***
20
21 EOF
22 exit 1;
23 }
24
25 print <<EOF;
26
27 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
28
29
30 Welcome to EV configuration. If you are in a hurry, just press return here
31 and hope for the best. The defaults should usually do.
32
33 EOF
34
35 if (prompt ("Skip further questions and use defaults (y/n)?", "y") =~ /[yY]/) {
36 $ENV{PERL_MM_USE_DEFAULT} = 1;
37 }
38
39 print <<EOF;
40
41 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
42
43
44 POSIX optionally offers support for a monotonic clock source. EV
45 can take advantage of this clock source to detect time jumps more
46 reliably. Unfortunately, some systems are bound to be broken, so you can
47 disable this here: you can completely disable the detection and use of
48 the monotonic clock by answering 'n' here. Support for this clock type
49 will otherwise be autodetected at both compile- and runtime. (this setting
50 currently affects the use of nanosleep over select as well).
51
52 EOF
53
54 unless (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/) {
55 $DEFINE .= " -DEV_USE_MONOTONIC=0";
56 }
57
58 print <<EOF;
59
60 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
61
62
63 POSIX optionally offers support for a (potentially) high-resolution
64 realtime clock interface. In a good implementation, using it is faster
65 than the normal method of using gettimeofday. Unfortunately, this option
66 is also bound to be broken on some systems, and current EV versions do not
67 actually call gettimeofday very often, so it defaults to no.
68
69 EOF
70
71 $DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/));
72
73 print <<EOF;
74
75 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
76
77
78 EV can use various backends with various portability issues. The select
79 backend is the most portable and makes for a good fallback, but it can be
80 limited to a low number of file descriptors and/or might not compile. If
81 you have problems with compiling ev_select.c, you might try to play around
82 with disabling it here, or forcing it to use the fd_set provided by your
83 OS, via the next question. I highly recommend keeping it in.
84
85 EOF
86
87 if (prompt ("Enable select backend (y/n)?", "y") =~ /[yY]/) {
88 $DEFINE .= " -DEV_USE_SELECT=1";
89
90 print <<EOF;
91
92 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
93
94
95 The select backend can operate in two modes. One uses the system-provided
96 fd_set and is usually limited to 1024 file descriptors (64 on windows),
97 the other requires your header files to define NFDBITS and declare a
98 suitable fd_mask type. If you run into problems compiling ev_select.c, you
99 can try forcing the use of the system fd_set here.
100
101 EOF
102
103 if (prompt ("Force use of system fd_set for select backend (y/n)?", "n") =~ /[yY]/) {
104 $DEFINE .= " -DEV_SELECT_USE_FD_SET";
105 }
106 } else {
107 $DEFINE .= " -DEV_USE_SELECT=0";
108 }
109
110 print <<EOF;
111
112 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
113
114
115 The second very portable backend is poll(2). It does not exist on windows
116 and various versions of Mac OS X (and on the other versions it simply
117 doesn't work), but works basically everywhere else. It is recommended to use
118 the default here unless you run into compile problems in ev_poll.c.
119
120 EOF
121
122 $DEFINE .= " -DEV_USE_POLL=" . (0 + (prompt ("Enable poll backend (y/n)?", (have_inc "poll.h") ? "y" : "n") =~ /[yY]/));
123
124 print <<EOF;
125
126 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
127
128
129 Select and poll make it hard to write efficient servers, especially if the
130 number of active connections is much lower than the watched ones. GNU/Linux
131 systems have a more scalable method called "epoll", which EV can use. For
132 this to work, both your kernel and glibc have to support epoll, but if you
133 can compile it, the detection will be done at runtime, and EV will safely
134 fall back to using select when epoll isn't available. If unsure, accept
135 the default.
136
137 EOF
138
139 my $can_epoll = have_inc "sys/epoll.h";
140 $can_epoll = $ENV{EV_EPOLL} if exists $ENV{EV_EPOLL};
141 $DEFINE .= " -DEV_USE_EPOLL=" . (0 + (prompt ("Enable epoll backend (y/n)?", $can_epoll ? "y" : "n") =~ /[yY]/));
142
143 print <<EOF;
144
145 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
146
147
148 Similarly to the epoll backend above, EV can take advantage of kqueue on
149 many BSD systems. Support for kqueue will be detected at runtime, with a
150 safe fallback to other methods when it cannot be used.
151
152 Note that kqueue is broken on most operating systems, so by default it
153 won't be used on many platforms, but you can still create your own event
154 loop with kqueue backend if you ask specifically for it.
155
156 Here is what we know:
157
158 NetBSD: partially working in at least 3.1 and later. Yeah! :)
159 FreeBSD: broken on at least 6.2-STABLE, spotty in later versions,
160 sockets *likely* work, ptys definitely don't.
161 OpenBSD: reports indicate that it likely doesn't work
162 (similar problems as on FreeBSD).
163 OS X: completely, utterly broken on at least <= 10.6.
164
165 EOF
166
167 my $can_kqueue = have_inc "sys/event.h";
168 $can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE};
169 $DEFINE .= " -DEV_USE_KQUEUE=" . (0 + (prompt ("Enable kqueue backend (y/n)?", $can_kqueue ? "y" : "n") =~ /[yY]/));
170
171 print <<EOF;
172
173 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
174
175
176 Similarly to the kqueue backend above, EV can take advantage of the
177 solaris 10 event port interface. Support for event ports will be detected
178 at runtime, with a safe fallback to other methods when it cannot be used.
179
180 EOF
181
182 $DEFINE .= " -DEV_USE_PORT=" . (0 + (prompt ("Enable event port backend (y/n)?", (have_inc "sys/port.h") ? "y" : "n") =~ /[yY]/));
183
184 print <<EOF;
185
186 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
187
188
189 EV needs the functions pthread_atfork and clock_gettime. On most systems
190 you need some special libraries for this (such as -lrt and -lpthread). You
191 can specify additional libraries to provide these calls (and any other
192 required by EV) now, or accept the default.
193
194 On GNU/Linux systems, EV uses the LSB 3.1 __register_atfork function
195 to avoid the dependency on libpthread, and directly uses the clock_gettime
196 syscall to avoid a dependency on librt.
197
198 EOF
199
200 my $solaris_libs = $^O =~ /solaris/i ? "-lsocket -lnsl" : "";
201 my $librt = $^O =~ /linux/i ? "" : "-lpthread -lrt";
202 my $LIBS = exists $ENV{EV_LIBS} ? $ENV{EV_LIBS} : "$librt $solaris_libs";
203 $LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", $LIBS;
204
205
206 print <<EOF;
207
208 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
209
210
211 A backend of a different kind is the Linux inotify(7) interface, which can
212 be used to speed up (and reduce resource consumption) of stat watchers. If
213 you have the include file and libc support for it, it is usually a good
214 idea to enable it, as kernel availability is detected at runtime.
215
216 EOF
217
218 my $can_inotify = have_inc "sys/inotify.h";
219 $can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY};
220 $DEFINE .= " -DEV_USE_INOTIFY=" . (0 + (prompt ("Enable inotify support (y/n)?", $can_inotify ? "y" : "n") =~ /[yY]/));
221
222 print <<EOF;
223
224 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
225
226
227 Another useful bit of functionality is the Linux eventfd, which is useful
228 for faster signal handling (don't care) and intra-thread communications
229 (more relevant). Kernel support for this will be probed at runtime, but
230 your libc must contain the necessary wrapper. Glibc 2.7 and later should
231 have this wrapper.
232
233 EOF
234
235 my $can_eventfd = have_inc "sys/eventfd.h";
236 $can_eventfd = $ENV{EV_EVENTFD} if exists $ENV{EV_EVENTFD};
237 $DEFINE .= " -DEV_USE_EVENTFD=" . (0 + (prompt ("Enable linux eventfd support (y/n)?", $can_eventfd ? "y" : "n") =~ /[yY]/));
238
239 print <<EOF;
240
241 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
242
243
244 Another sometimes useful bit of functionality is the Linux signalfd, which
245 is useful for faster signal handling (don't care). Kernel support for
246 this will be probed at runtime, but your libc must contain the necessary
247 wrapper. Glibc 2.7 and later should have this wrapper.
248
249 EOF
250
251 my $can_signalfd = have_inc "sys/signalfd.h";
252 $can_signalfd = $ENV{EV_SIGNALFD} if exists $ENV{EV_SIGNALFD};
253 $DEFINE .= " -DEV_USE_SIGNALFD=" . (0 + (prompt ("Enable linux signalfd support (y/n)?", $can_signalfd ? "y" : "n") =~ /[yY]/));
254
255 print <<EOF;
256
257 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
258
259
260 Very rarely, people want to tweak EV even more, e.g. to exclude
261 or include certain watcher types or backends. This can be done by adding
262 extra -D options here, or via the EV_EXTRA_DEFS environment variable.
263
264 For example, if you run into compile problems because of missing memory
265 fences (or you just want extra performance), you can tell EV to not support
266 smp and threads via -DEV_NO_THREADS.
267
268 Normal persons just press enter.
269
270 EOF
271
272 $DEFINE .= " " . prompt "Any extra -D options?", "$ENV{EV_EXTRA_DEFS}";
273
274 print <<EOF;
275
276 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
277
278
279 EOF
280
281 my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 5.29 } ? (AnyEvent => 5.29) : ();
282
283 WriteMakefile(
284 dist => {
285 PREOP => 'pod2text EV.pm | tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;',
286 COMPRESS => 'gzip -9v',
287 SUFFIX => '.gz',
288 },
289 depend => {
290 "EV.c" => "EV/EVAPI.h "
291 . "libev/ev.c libev/ev.h libev/ev_epoll.c libev/ev_select.c libev/ev_kqueue.c libev/ev_poll.c "
292 . "libev/ev_vars.h libev/ev_wrap.h",
293 },
294 INC => "-Ilibev",
295 DEFINE => "$DEFINE",
296 NAME => "EV",
297 LIBS => [$LIBS],
298 PREREQ_PM => {
299 @anyevent,
300 "common::sense" => 0,
301 },
302 CONFIGURE_REQUIRES => { "ExtUtils::MakeMaker" => 6.52, "Canary::Stability" => 0 },
303 VERSION_FROM => "EV.pm",
304 PM => {
305 'EV.pm' => '$(INST_LIB)/EV.pm',
306 'EV/EVAPI.h' => '$(INST_LIB)/EV/EVAPI.h',
307 'EV/MakeMaker.pm' => '$(INST_LIB)/EV/MakeMaker.pm',
308 'libev/ev.h' => '$(INST_LIB)/EV/ev.h',
309 'libev/ev.pod' => '$(INST_LIB)/EV/libev.pod',
310 },
311 MAN3PODS => {
312 'EV.pm' => '$(INST_MAN3DIR)/EV.$(MAN3EXT)',
313 'EV/MakeMaker.pm' => '$(INST_MAN3DIR)/EV::MakeMaker.$(MAN3EXT)',
314 'libev/ev.pod' => '$(INST_MAN3DIR)/EV::libev.$(MAN3EXT)',
315 },
316 );
317
318