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

Comparing EV/Makefile.PL (file contents):
Revision 1.12 by root, Thu Nov 1 15:46:43 2007 UTC vs.
Revision 1.31 by root, Thu Jan 31 19:59:23 2008 UTC

1use 5.006; 1use 5.006;
2 2
3use Config; 3use Config;
4use ExtUtils::MakeMaker; 4use ExtUtils::MakeMaker;
5
6 5
7unless (-e "libev/ev_epoll.c") { 6unless (-e "libev/ev_epoll.c") {
8 print <<EOF; 7 print <<EOF;
9 8
10*** 9***
17 exit 1; 16 exit 1;
18} 17}
19 18
20print <<EOF; 19print <<EOF;
21 20
22
23*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 21*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
22
24 23
25Welcome to EV configuration. If you are in a hurry, just press return here 24Welcome to EV configuration. If you are in a hurry, just press return here
26and hope for the best. The defaults should usually do. 25and hope for the best. The defaults should usually do.
27 26
28EOF 27EOF
31 $ENV{PERL_MM_USE_DEFAULT} = 1; 30 $ENV{PERL_MM_USE_DEFAULT} = 1;
32} 31}
33 32
34print <<EOF; 33print <<EOF;
35 34
36
37*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 35*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
38 36
37
39POSIX optionally offers support for a monotonic clock source. EV can 38POSIX optionally offers support for a monotonic clock source. EV
40take advantage of this clock source to detect time jumps reliably. This 39can take advantage of this clock source to detect time jumps
41will usually slow down EV a tiny amount, but this is usually
42well-invested. Unfortunately, some systems are bound to be broken, so 40reliably. Unfortunately, some systems are bound to be broken, so you can
43you can disable this here. Whatever your reasons, you can completely 41disable this here: you can completely disable the detection and use of
44disable the detection and use of this monotonic clock by answering 'n' 42the monotonic clock by answering 'n' here. Support for this clock type
45here. Support for this clock type will otherwise be autodetected at both 43will otherwise be autodetected at both compile- and runtime. (this setting
46compile- and runtime. 44currently affects the use of nanosleep over select as well).
47 45
48EOF 46EOF
49 47
50if (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/) { 48$DEFINE .= " -DEV_USE_MONOTONIC=" . (0 + (prompt ("Enable optional support for CLOCK_MONOTONIC (y/n)?", "y") =~ /[yY]/));
51 $DEFINE .= " -DEV_USE_MONOTONIC";
52}
53 49
54print <<EOF; 50print <<EOF;
55 51
56
57*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 52*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
53
58 54
59POSIX optionally offers support for a (potentially) high-resolution 55POSIX optionally offers support for a (potentially) high-resolution
60realtime clock interface. In a good implementation, using it is faster 56realtime clock interface. In a good implementation, using it is faster
61than the normal method of using gettimeofday. Unfortunately, this option 57than the normal method of using gettimeofday. Unfortunately, this option
62is also bound to be broken on some systems, so you can disable use and 58is also bound to be broken on some systems, so you can disable use and
63probing of this feature altogether here. Otherwise support for this clock 59probing of this feature altogether here. Otherwise support for this clock
64type will be autodetected at compiletime. 60type will be autodetected at compiletime.
65 61
66EOF 62EOF
67 63
68if (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)?", "y") =~ /[yY]/));
65
66print <<EOF;
67
68*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
69
70
71EV can use various backends with various portability issue. The select
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
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
76OS, via the next question. I highly recommend keeping it in.
77
78EOF
79
80if (prompt ("Enable select backend (y/n)?", "y") =~ /[yY]/) {
69 $DEFINE .= " -DEV_USE_REALTIME=0"; 81 $DEFINE .= " -DEV_USE_SELECT=1";
70}
71 82
72print <<EOF; 83 print <<EOF;
73 84
74
75*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 85*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
86
87
88The select backend can operate in two modes. One uses the system-provided
89fd_set and is usually limited to 1024 file descriptors (64 on windows),
90the other requires your header files to define NFDBITS and declare a
91suitable fd_mask type. If you run into problems compiling ev_select.c, you
92can try forcing the use of the system fd_set here.
93
94EOF
95
96 if (prompt ("Force use of system fd_set for select backend (y/n)?", "n") =~ /[yY]/) {
97 $DEFINE .= " -DEV_SELECT_USE_FD_SET";
98 }
99} else {
100 $DEFINE .= " -DEV_USE_SELECT=0";
101}
102
103print <<EOF;
104
105*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
106
107
108The second very portable backend is poll(2). It does not exist on windows
109and various versions of Mac OS X (and on the other versions it simply
110doesn't work), but works basically everywhere else. It is recommended to use
111the default here unless you run into compile problems in ev_poll.c.
112
113EOF
114
115$DEFINE .= " -DEV_USE_POLL=" . (0 + (prompt ("Enable poll backend (y/n)?", (-e "/usr/include/poll.h") ? "y" : "n") =~ /[yY]/));
116
117print <<EOF;
118
119*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
120
121
122Select and poll make it hard to write efficient servers, especially if the
123number of active connections is much lower than the watched ones. GNU/Linux
124systems have a more scalable method called "epoll", which EV can use. For
125this to work, both your kernel and glibc have to support epoll, but if you
126can compile it, the detection will be done at runtime, and EV will safely
127fall back to using select when epoll isn't available. If unsure, accept
128the default.
129
130EOF
131
132$DEFINE .= " -DEV_USE_EPOLL=" . (0 + (prompt ("Enable epoll backend (y/n)?", (-e "/usr/include/sys/epoll.h") ? "y" : "n") =~ /[yY]/));
133
134print <<EOF;
135
136*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
137
138
139Similarly to the epoll backend above, EV can take advantage of kqueue on
140many BSD systems. Support for kqueue will be detected at runtime, with a
141safe fallback to other methods when it cannot be used.
142
143Note 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
145loop with qkueue backend.
146
147Here is what we know:
148
149NetBSD: partially working in at least 3.1. Yeah! :)
150FreeBSD: broken on at least 6.2-STABLE,
151 sockets *likely* work, ptys definitely don't.
152OpenBSD: reports indicate that it likely doesn't work
153 (similar problems as on FreeBSD).
154OS X: completely, utterly broken on at least < 10.5.
155
156EOF
157
158my $can_kqueue = -e "/usr/include/sys/event.h";
159
160$DEFINE .= " -DEV_USE_KQUEUE=" . (0 + (prompt ("Enable kqueue backend (y/n)?", $can_kqueue ? "y" : "n") =~ /[yY]/));
161
162print <<EOF;
163
164*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
165
166
167Similarly to the kqueue backend above, EV can take advantage of the
168solaris 10 event port interface. Support for event ports will be detected
169at runtime, with a safe fallback to other methods when it cannot be used.
170
171EOF
172
173$DEFINE .= " -DEV_USE_PORT=" . (0 + (prompt ("Enable event port backend (y/n)?", (-e "/usr/include/sys/port.h") ? "y" : "n") =~ /[yY]/));
174
175print <<EOF;
176
177*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
178
76 179
77EV needs the functions pthread_atfork and clock_gettime. On most systems 180EV needs the functions pthread_atfork and clock_gettime. On most systems
78you need some special libraries for this (such as -lrt and -lpthread). You can 181you need some special libraries for this (such as -lrt and -lpthread). You
79specify additional libraries to provide these calls now, or accept the default. 182can specify additional libraries to provide these calls (and any other
183required by EV) now, or accept the default.
80 184
81EOF 185EOF
82 186
187$SOLARIS_LIBS = $^O =~ /solaris/ ? " -lsocket -lnsl" : "";
188
83$LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", "-lpthread -lrt"; 189$LIBS = prompt "Extra libraries for pthread_atfork and clock_gettime?", "-lpthread -lrt$SOLARIS_LIBS";
84 190
85 191
86print <<EOF; 192print <<EOF;
87 193
88
89*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 194*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
90 195
91EV needs the functions pthread_atfork and clock_gettime. On most systems
92you need some special libraries for this (such as -lrt and -lpthread). You can
93specify additional libraries to provide these calls now, or accept the default.
94 196
95EOF 197A 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
199you have it, it is usually a good idea to enable it.
96 200
97if (prompt ("Enable epoll backend (y/n)?", (-e "/usr/include/sys/epoll.h") ? "y" : "n") =~ /[yY]/) {
98 $DEFINE .= " -DEV_USE_EPOLL";
99}
100
101print <<EOF;
102
103
104*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
105
106EOF 201EOF
107 202
108#$ENV{CC} = $Config{cc}; 203my $can_inotify = -e "/usr/include/sys/inotify.h";
109#$ENV{CFLAGS} = join " ", map $Config{$_}, qw(inc optimize ccflags cccdlflags);
110#system "cd libevent && ./configure --disable-shared --enable-static --disable-maintainer-mode"
111# and die "configure failed.";
112 204
113#$LIBS = qx<cd libevent && make printlibs>; 205$DEFINE .= " -DEV_USE_INOTIFY=" . (0 + (prompt ("Enable inotify support (y/n)?", $can_inotify ? "y" : "n") =~ /[yY]/));
206
207print <<EOF;
208
209*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
210
211
212EOF
213
214my @anyevent = eval { require AnyEvent; $AnyEvent::VERSION < 2.6 } ? (AnyEvent => 2.6) : ();
114 215
115WriteMakefile( 216WriteMakefile(
116 dist => { 217 dist => {
117 PREOP => 'pod2text EV.pm | tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;', 218 PREOP => 'pod2text EV.pm | tee README >$(DISTVNAME)/README; chmod -R u=rwX,go=rX . ;',
118 COMPRESS => 'gzip -9v', 219 COMPRESS => 'gzip -9v',
119 SUFFIX => '.gz', 220 SUFFIX => '.gz',
120 }, 221 },
121 depend => { 222 depend => {
122 "EV.c" => "EV/EVAPI.h libev/ev.c libev/ev.h libev/ev_epoll.c libev/ev_select.c", 223 "EV.c" => "EV/EVAPI.h "
224 . "libev/ev.c libev/ev.h libev/ev_epoll.c libev/ev_select.c libev/ev_kqueue.c libev/ev_poll.c "
225 . "libev/ev_vars.h libev/ev_wrap.h",
123 }, 226 },
124 INC => "-Ilibev", 227 INC => "-Ilibev",
125 DEFINE => "$DEFINE", 228 DEFINE => "$DEFINE",
126 NAME => "EV", 229 NAME => "EV",
127 LIBS => [$LIBS], 230 LIBS => [$LIBS],
231 PREREQ_PM => {
232 @anyevent,
233 },
128 VERSION_FROM => "EV.pm", 234 VERSION_FROM => "EV.pm",
129 PM => { 235 PM => {
130 'EV.pm' => '$(INST_LIBDIR)/EV.pm', 236 'EV.pm' => '$(INST_LIBDIR)/EV.pm',
131 'EV/AnyEvent.pm' => '$(INST_LIBDIR)/EV/AnyEvent.pm',
132 'EV/DNS.pm' => '$(INST_LIBDIR)/EV/DNS.pm',
133 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h', 237 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h',
134 'EV/MakeMaker.pm' => '$(INST_LIBDIR)/EV/MakeMaker.pm', 238 'EV/MakeMaker.pm' => '$(INST_LIBDIR)/EV/MakeMaker.pm',
135 'libev/ev.h' => '$(INST_LIBDIR)/EV/ev.h', 239 'libev/ev.h' => '$(INST_LIBDIR)/EV/ev.h',
136 }, 240 },
137); 241);

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines