|No such thing as a small change|
Sorry y'all. I've been working on other things for a bit ($work/2, A fence, a LAN party, and a busted Lada Niva mostly).
Hahaha, Nivas are cool as hell. You ever seen where they took a Niva and totally submerged it, ran it around the bottom of a shallow lake in Russia wearing scuba gear, with nothing but snorkels for intake/exhaust.
I've noticed that a lot of you also seem to have the Perl source available (which I don't) and I'm wondering if getting that set up to compile makes a difference. OTOH it's a bit out of the scope of this project which is specifically about using Strawberry Perl 5.10 and what it provides (which seems to be enough).
I don't want to knock Strawberry/Vanilla Perl, I just find that if I do it myself, I understand the whole setup better, and have a somewhat better chance of figuring out what goes wrong when things do go wrong. After I get a Windows Installer built for my Perl/GTK build, I'd like to try to see if the same instructions work on Strawberry/Vanilla Perl as well as my own build. You can watch my Gtk2-Perl installer package progress here:
My final conclusion is that Strawberry Perl does provide everything you need to compile modules, provided that they don't need more libraries. Almost everything I've done is telling the compiler where these external libraries are. I haven't yet figured out if this is a deficiency in the Makefiles, or in the way that minGW is set up in Strawberry Perl. Both seem equally likely.
From the way it was explained to me in a set of posts on the gtk2-perl mailing lists (my original post, a reply later on in the same thread), the ExtUtils::Maker module could not find the right libraries on Windows for whatever reason, hence the need to do the hand-hackery. ExtUtils::Maker is what generates the Makefile that the Gtk2-Perl modules are built from.