>----Messaggio originale---- >Da: [EMAIL PROTECTED] Hi,
>I was able to get Christian Renz's PerlWrapper package working >(mostly) on MacOS X 10.4. I can get it to run pure Perl programs, but >DynaLoader was giving me errors (undefined symbols; seems to be a lib >or header mismatch somewhere in what I did) so I had to comment out >the DynaLoader code from PerlWrapper to get it to work. In any case, >I'd like to 1: Fix that problem, and 2: Get PerlWrapper to work with >wxPerl. Might it just be that you are not linking with the dynaloader static library? I can't remember the details, and if it applies for Perl 5.8/Mac, but I remember that in the past I had to explicitly link a libdynaloader.a (or something). >I found an old post on this list from from Dan Sugalski ( >http://www.nntp.perl.org/group/perl.wxperl. users/2007/06/msg3990.html >) which referenced some steps and patches that need to be applied to >get wxPerl to work with PerlWrapper, but I couldn't find the original >information to which that post refers. Any pointers appreciated. I use PerlWrapper on Tiger (both PPC and Intel), but the only changes I remember making were in include paths. >I'm a little out of my league with all this XCode stuff -- I'm an >Emacs and make guy and these days the only times I usually have to >touch a compiler are when I install an XS module from CPAN. I >understand that regular wxPerl scripts require the wxPerl binary >because it's linked against wx (right?). No, it's because OS X does not allow a plain binary to interact with the GUI; the wxPerl binary just exec()s a copy of the Perl interpreter wrapped inside a bundle. It's years I want to submit patches to remove the Xcode stuff from PerlWrapper and make it easier to create new projects, but I never got the tuits for it. Regards, Mattia
