On Tue, 15 Feb 2005, Reini Urban wrote: > I have a huge cygwin patch pending, based on rafael kitover's cygwin > work, simplifying the hints (one central hints file for all), some > missing functions centrally defined, and one huge central headerfile. > (no MODULE/pports.h et al., => ../win32perl.h, ..) > Also lots of needed casts. > > I can be reviewed at > <http://xarch.tu-graz.ac.at/publ/cygwin/release/perl-libwin32/perl-libwin32-0.191-3.patch>
Doesn't seem to exist, but I see a source tarball in the parent directory, so I guess I can create my own diff. :) I'll take a look at the differences later this week. I remember that I saw a huge cygwin patch that reworked the structure of all modules significantly (that was probably 2 years ago, and I think had been rejected by Sarathy as needing more work). If this is still the case, then I would want to work through the pending per-module patches first, as they will be much harder to apply after modifying all modules globally. > This is the current cygwin patch, works fine for cygwin, and > reportedly should work on mingw, MSVC and Borland also. But on my own > tests (MSVC-6SP2) I found some minor problems with missing MSVC > includes. I'll try to clean that up in the next weeks. Could you (or anyone else) point me to the current setup instructions for using Perl on cygwin and mingw? I haven't used it in a long while, and back then you really had to use various development snapshots or all manner of stuff didn't work. I hope things are much improved now, but would prefer not to figure it all out by myself. I do want to have a test setup for all environments though, so that I can test patches for all of them before committing them. Cheers, -Jan
