go ahead... be a heretic | |
PerlMonks |
Re^5: On the road again with Gtk2 and PAR::Packerby syphilis (Archbishop) |
on Feb 14, 2019 at 14:08 UTC ( [id://1229911]=note: print w/replies, xml ) | Need Help?? |
Rob, how can you say it proves anything ? AIUI, Roderick was saying that you were experiencing the failures you're seeing because the perl-generated dlls (such as Pango.dll) are dependent upon various other perl-generated dlls (such as Cairo.dll and Glib.dll). But you've just shown that an earlier build was fine, even though those same dependencies existed. So the cause of the problem must be something else. Perhaps I've misread what he said, or have missed something else, but I'm starting to wonder whether your problem would disappear if you were to change the '.xs.dll' extensions to '.dll'. I'd first change the existing setting of $Config{dlext} from 'xs.dll' to 'dll' - by making that change in both lib/Config_heavy.pl and lib/Config.pm. (You can run perl -V:dlext to verify that your edits have worked. Note that it would need to report 'dll', not '.dll') Then I'd rebuild those Gtk2 modules I find that renaming Strawberry dlls from 'xs.dll' doesn't break anything - at least it didn't for me when I just tried it. Unfortunately you can't simply do that - because the Pango dll will still be looking for Cairo.xs.dll and Glib.xs.dll. So I think you'd have to rebuild the modules if you want to give that a try. At least, that's what I would be doing. Having said that, FAIK it may be possible to get things to work without having to change the extension back to 'dll'. Cheers, Rob
In Section
Seekers of Perl Wisdom
|
|