I should have added that the pseudo-fork and condition vars on cygwin would actually be better preserved by using the unix port. In fact, if the cygwin build simply used the win32 apr_file_io code I'd be quite happy with it relying on the other (unambiguous) features of the cygwin API.
Using the win32 apr file_io code on cygwin is impossible.
Cygwin provides a mapping of posix-like paths to windows paths. If you use the win32 API, you essentially cut cygwin out of the loop, breaking the translation of those pathnames.
Max.
