Front page | perl.wxperl.users |
Postings from March 2010
BTW I think I realise why you added the symlinks. There is a bug/feature in PerlApp whereby bound files get added relative to the 'build' directory. If you change the build directory, the relative paths are not updated - you have to unbind, and rebind each bound file if PerlApp is to find it. Mark On 13/03/2010 23:05, Mark Dootson wrote: > Hi, > > Your original woes were down to a bug in Wx-Perl-Packager. Sorry! I > fixed it to work with PAR - then forgot to re-test PerlApp. > > To fix: > > Re-install Wx-Perl-Packager 0.21 from wxperl repository. (you may need > to refresh the repository in PPM for it to show up - > > ppm repo sync --force wxperl > > ) > > Get rid of all the symlinks you created - these are not needed - and > contribute to your segfault on exit. You might want to just delete the > Alien and Wx directories and install again. But be sure the symlinks are > gone. > > Start with a new .perlapp file. (This seems to be necessary). > > Bind wx dlls as described in Wx::Perl::Packager POD. > > Bind Wx.so as wxmain.so - as described in Wx::Perl::Packager POD. > > All should work. > > On MacOSX you should find everything works fine - but you'll have to > read the Wx::Perl::Packager POD as a few actions are necessary. > > Regards > > Mark > > > > On 13/03/2010 16:27, perltk wrote: >> Got it working. (Still get seg fault on exit.) >> >> I had created soft links to so.0 files - seemed neccessary for the first >> 3 libraries to get picked up. >> Anyway for the additional 3 (html,stc & net ) the links weren't good >> enough - had to copy >> to .so extension and bind to executable. >> >> Is this the wrong approach ? >> Comments appreciated ! >> >> By the way, been a while since I tried this. Is there still a problem on >> the Mac with wxperl creating its own executable that can't be picked up >> by perlapp ( wasn't it just called 'wxperl' in the bin directory ? ) >> >> perltk wrote: >>> Hi there, >>> >>> Just discovered yhe wxperl binary oasis - great idea ! >>> Looking forward to build some GUIs so I hope I can get some help. >>> >>> So decide to try it. >>> Straight forward, out-of-the-box install of Activesate 5.10, Wxperl >>> from wxperl.co.uk >>> and Perlapp 8.2.1 >>> >>> Tried out packtest.pl - modified nothing. Get a seg fault >>> >>> Any thoughts? >>> >>> >>> Perlapp Settings: >>> >>> perlapp --bind >>> "libwx_baseu-2.8.so[file=../perl510/site/lib/Alien/wxWidgets/gtk_2_8_10_uni/lib/libwx_baseu-2.8.so,extract,mode=755]" >>> >>> --bind >>> "libwx_gtk2u_core-2.8.so[file=../perl510/site/lib/Alien/wxWidgets/gtk_2_8_10_uni/lib/libwx_gtk2u_core-2.8.so,extract,mode=755]" >>> >>> --bind >>> "libwx_gtk2u_adv-2.8.so[file=../perl510/site/lib/Alien/wxWidgets/gtk_2_8_10_uni/lib/libwx_gtk2u_adv-2.8.so.0,extract,mode=755]" >>> >>> --norunlib --force --exe packtest.exe --perl >>> /home/jeff/Activestate/perl510/bin/perl packtest.pl >>> >>> (jeff) maine: /home/jeff > uname -a >>> Linux maine 2.6.18-128.2.1.el5 #1 SMP Tue Jul 14 06:39:56 EDT 2009 i686 >>> i686 i386 GNU/Linux >>> >>> >>> (jeff) maine: /home/jeff/Activestate/TESTwx> packtest.exe >>> DEBUG : Initial wx_path is : >>> DEBUG : preparing Wx for runtime PERLAPP >>> DEBUG : Runtime PERLAPP Preparation complete >>> DEBUG : Preparing Load Paths for Wx >>> DEBUG : Load Path set /tmp/pdk-jeff-8714 >>> DEBUG : Load Paths Complete >>> DEBUG : Relocating extracted modules for Wx >>> DEBUG : Relocate Path >>> is /tmp/wxppl-jeff/1284dca6865a26b07830e08b46b24aa7 >>> DEBUG : Extract Path is /tmp/pdk-jeff-8714 >>> DEBUG : Relocated base >>> DEBUG : Relocated core >>> DEBUG : Relocated adv >>> DEBUG : Relocation Complete >>> DEBUG : Preparing and Loading Wx >>> DEBUG : Core Load = 1 >>> DEBUG : Loading Core Module base >>> from /tmp/wxppl-jeff/1284dca6865a26b07830e08b46b24aa7/libwx_baseu-2.8.so >>> DEBUG : Loading Core Module core >>> from >>> /tmp/wxppl-jeff/1284dca6865a26b07830e08b46b24aa7/libwx_gtk2u_core-2.8.so >>> DEBUG : Loading Core Module adv >>> from >>> /tmp/wxppl-jeff/1284dca6865a26b07830e08b46b24aa7/libwx_gtk2u_adv-2.8.so >>> DEBUG : Load Method = packload >>> DEBUG : Wx Load Complete >>> DEBUG : Loading Plugin net >>> from /tmp/pdk-jeff-8714/libwx_baseu_net-2.8.so >>> >>> Segmentation fault >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> Mark Dootson wrote: >>>> Hi, >>>> >>>> The PDK "error: Can't locate Wx\Loader\Custom.pm" is fine and >>>> expected. You can ignore it. >>>> >>>> wxpdk is not needed anymore (since PerlApp 7.1) >>>> >>>> I have tested >>>> >>>> ActivePerl 5.10 build 1007 >>>> Wx 0.9701 >>>> Wx::Perl::Packager 0.20 >>>> PerlApp 7.3 >>>> >>>> And all seems to work OK ? >>>> >>>> What is your version of ActivePerl? >>>> There is a test script at >>>> >>>> <perl>/site/lib/Wx/Perl/Packager/resource/packtest.pl >>>> >>>> could you try packaging that and check if it works? >>>> >>>> >>>> regards >>>> >>>> Mark >>>> >>>> >>>> >>>> On 02/03/2010 14:35, Jiří Pavlovský wrote: >>>>> Hello, >>>>> >>>>> till today I was using PerlApp to compile my wxPerl application >>>>> without >>>>> a problem. >>>>> >>>>> I had to reinstall perl (ActiveState latest build) and cannot get it >>>>> going since then. >>>>> I installed all the latest modules from www.wxperl.co.uk. >>>>> >>>>> First I noticed that Wx::Perl::Packager no longer contains wxpdk - >>>>> is it >>>>> not needed anymore? >>>>> >>>>> During "compile " I can see the following error (but it creates the >>>>> executable): >>>>> Wx\Loader\Custom.pm: >>>>> error: Can't locate Wx\Loader\Custom.pm >>>>> refby: C:\Perl\site\lib\Wx\Mini.pm line 82 >>>>> >>>>> When I try to run the excutable it terminates with the following >>>>> error: >>>>> >>>>> Use of uninitialized value within %INC in pattern match (m//) at >>>>> /<Y:\path\to\prog.exe>XSLoader.pm line 45. >>>>> Use of uninitialized value within %INC in pattern match (m//) at >>>>> /<Y:\path\to\prog.exe>DynaLoader.pm line 163. >>>>> >>>>> I have a PerlApp 7.3.0. >>>>> >>>>> Any advice appreciated. >>>>> >>>>> Thank you, >>>>> Jiri >>>>> >>>>> >>>> >>>> >>> >>> >> >Thread Previous | Thread Next