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

Comparing EV/Makefile.PL (file contents):
Revision 1.38 by root, Thu Nov 20 00:35:16 2008 UTC vs.
Revision 1.41 by root, Tue Jul 14 00:09:59 2009 UTC

… …
54 54
55 55
56POSIX optionally offers support for a (potentially) high-resolution 56POSIX optionally offers support for a (potentially) high-resolution
57realtime clock interface. In a good implementation, using it is faster 57realtime clock interface. In a good implementation, using it is faster
58than the normal method of using gettimeofday. Unfortunately, this option 58than the normal method of using gettimeofday. Unfortunately, this option
59is 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
60probing of this feature altogether here. Otherwise support for this clock 60actually call C<gettimeofday> very often, so ti defaults to no.
61type will be autodetected at compiletime.
62 61
63EOF 62EOF
64 63
65$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]/));
66 65
67print <<EOF; 66print <<EOF;
68 67
69*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 68*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
70 69
… …
143many 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
144safe fallback to other methods when it cannot be used. 143safe fallback to other methods when it cannot be used.
145 144
146Note 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
147won'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
148loop with kqueue backend. 147loop with kqueue backend if you ask specifically for it.
149 148
150Here is what we know: 149Here is what we know:
151 150
152NetBSD: partially working in at least 3.1. Yeah! :) 151NetBSD: partially working in at least 3.1. Yeah! :)
153FreeBSD: broken on at least 6.2-STABLE, 152FreeBSD: broken on at least 6.2-STABLE,
… …
197*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 196*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
198 197
199 198
200A 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
201be 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
202you 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.
203 203
204EOF 204EOF
205 205
206my $can_inotify = -e "/usr/include/sys/inotify.h"; 206my $can_inotify = -e "/usr/include/sys/inotify.h";
207$can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY}; 207$can_inotify = $ENV{EV_INOTIFY} if exists $ENV{EV_INOTIFY};
… …
248 DEFINE => "$DEFINE", 248 DEFINE => "$DEFINE",
249 NAME => "EV", 249 NAME => "EV",
250 LIBS => [$LIBS], 250 LIBS => [$LIBS],
251 PREREQ_PM => { 251 PREREQ_PM => {
252 @anyevent, 252 @anyevent,
253 "common::sense" => 0,
253 }, 254 },
254 VERSION_FROM => "EV.pm", 255 VERSION_FROM => "EV.pm",
255 PM => { 256 PM => {
256 'EV.pm' => '$(INST_LIBDIR)/EV.pm', 257 'EV.pm' => '$(INST_LIBDIR)/EV.pm',
257 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h', 258 'EV/EVAPI.h' => '$(INST_LIBDIR)/EV/EVAPI.h',

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines