diff options
| author | Norwegian Rock Cat <qt-info@nokia.com> | 2009-07-20 08:08:52 (GMT) |
|---|---|---|
| committer | Norwegian Rock Cat <qt-info@nokia.com> | 2009-07-20 08:08:52 (GMT) |
| commit | f900b675047c2e595a270b2a65edf8a9731b252a (patch) | |
| tree | d1e31f1bb7552218be920a5ccd7bf29e4817b99c /src/xmlpatterns | |
| parent | 27a07955d796a9c2b52302ad7f5ce0cd9d6179e1 (diff) | |
| download | Qt-f900b675047c2e595a270b2a65edf8a9731b252a.zip Qt-f900b675047c2e595a270b2a65edf8a9731b252a.tar.gz Qt-f900b675047c2e595a270b2a65edf8a9731b252a.tar.bz2 | |
Get monotonic time working on Mac OS X for corelib programs.
Mac OS X does not provide POSIX monotonic timers. Instead it does
provide a Mach call to get the absolute time (a.k.a., number of CPU
ticks) for the next timer event. This gets us around the bug in
select(2) on Mac, that it doesn't wakeup when the times been changed.
Of course, if you used the GUI event dispatcher, which is based on
CFRunLoopTimers, this is not an issue, but if you really just need
corelib, it's a bear to bring in the other stuff.
Thanks to the nice guys at Parallels for the basics of the patch!
Task-number: 237384
Reviewed-by: Bradley T. Hughes
Diffstat (limited to 'src/xmlpatterns')
0 files changed, 0 insertions, 0 deletions