So my current project is complete (my build system is working except for the automatic part - need a new nic so it can upload without me repairing the connection...and a new libssh2 that doesn't crash on disconnect) next on my list is the "GREAT PECL WINDOWS FUN HAPPY"...err I'll stop now.
So what is my PECL Windows nut project? Pretty simple, get every PECL extension imaginable compiling for windows. Now there will be some that are just frankly impossible (but there are some extensions that are impossible on *nix as well - you're not going to see me messing with xmms) What does this mean? Playing with lots of open source libraries, fixing simple errors, creating config.w32 files for extensions. Basically just looking at what is broken and fixing it. Since Wez has so kindly given me cvs access to PECL (don't hurt me, I'm just fixing build errors) I've already started on the project. And boy does PECL need the love. My first order of business? Fixing the amf extension's config.w32 file, took me all of five minutes. I'm hoping to continue to fix between 1 and 5 extensions a day. Some will take lots of work (uuid and xmlprci come to mind) where some will be very simple (find the library, roll a config.w32 file, we're done) however there are over 200 extensions, plus the "core" ones that haven't been booted to PECL, so this will take me awhile.
I'm making sure my fixes get put back into cvs, and I'm sending any libraries I beg, borrow, steal or compile to get put on the PECL4WIN box so you can get "official" builds, as well as getting builds at Perisama
What do I get out of this? Lots of cool php extensions I bet you've never even heard of, that are dead easy to install on windows. And brain exercise (too much code monkeyness makes me unhappy). If you have an extension NOT in PECL that you'd like to see on perisama, give me a URL and I'll hook it up. I'm currently tackling a php ffmpeg extension, so if you have more out there, please shout!