From: Mattia B. <mb...@ds...> - 2001-11-21 21:17:16
|
> U:\Perls\Wx\VNC>perlapp -f -g -c vncadmin.pl -exe testwx.exe > "EVT_MENU" is not exported by the Wx::Event module at VA_Frame.pm line 5 > "EVT_SIZE" is not exported by the Wx::Event module at VA_Frame.pm line 5 > > FreeStanding Builder failed to compile the script : Can't continue after > import errors at > VA_Frame.pm line 5 > BEGIN failed--compilation aborted at VA_Frame.pm line 5. > BEGIN failed--compilation aborted at (eval 30) line 5. > > ...whenever I tried building with PerlApp. So...I opened up the Event.pm in > the Wx directory in my site\lib dir and added all of the events that I'm > using in my program to the @EXPORT_OK array. Now building and running > works. > > My question is...Would adding all of the Events in the Event.pm file into > the @EXPORT_OK array screw anything up, (I don't see why it would)? If not, No, it wont, but see below > could this be added in the next release of wxPerl? :) Heck, I'll do it and > send in if the developer doesn't want the hassle. :) Oh, and you'll send me an updated list everytime I add a new event? ;-) Seriously: I once had the @EXPORT_OK list in Wx::Event, but when I wrote the code to automatically generate the export list for constants ( at the moment they are avove 1000 ... ), I figured it'd be easier to autogenerate exports for events too. You should look at Wx::_Exp.pm, that lists them all, and it use()d by Wx.pm . In short: there is something wrong with perl2exe :-) Regards Mattia |