Re: PerlApp stopped working
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.exeXSLoader.pm line 45. Use of uninitialized value within %INC in pattern match (m//) at /Y:\path\to\prog.exeDynaLoader.pm line 163. I have a PerlApp 7.3.0. Any advice appreciated. Thank you, Jiri
Re: PerlApp stopped working
Hi, I have the same configuration (Windows 7) and the test script compiles and runs fine. Hm, maybe it is not a Wx problem? Till today I had no problem to compile and run my program. Today I suddenly could not run perl at all (side by side configuration error). I went to update my perl installation to the latest ActiveState build and the problems started. One more thing: I forgot to tell that with the ppm package from www.wxperl.co.uk I could not run my prog at all. Error was missing wxbase28u_vc_custom.dll (IIRC). That I resolved by replacing Alien-wxWidgets-gcc-0.50.4 with Alien-wxWidgets0.50. Thanks Dne 2.3.2010 18:14, Mark Dootson napsal(a): 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.exeXSLoader.pm line 45. Use of uninitialized value within %INC in pattern match (m//) at /Y:\path\to\prog.exeDynaLoader.pm line 163. I have a PerlApp 7.3.0. Any advice appreciated. Thank you, Jiri
Re: PerlApp stopped working
Hi, On 02/03/2010 17:54, Jiří Pavlovský wrote: One more thing: I forgot to tell that with the ppm package from www.wxperl.co.uk I could not run my prog at all. Error was missing wxbase28u_vc_custom.dll (IIRC). That I resolved by replacing Alien-wxWidgets-gcc-0.50.4 with Alien-wxWidgets0.50. That is because the Wx you installed was from the ActiveState repository. I think you must have manually selected both Wx and Alien-wxWidgets from different repositories. I have fixed the dependencies in www.wxperl.co.uk repository so that, if you choose say Wx or one of the xs compiled modules - Wx::TreeListCtrl, for example, the correct dependencies will be installed. It is an irritation, I know, but I don't want to revert to building with VC6 because some wxWidgets features I use cannot be compiled using VC6 (the last SDK that works with VC6 was released Feb 2003). This can only get worse as wxWidgets development continues. One thing I did notice - I only fixed the dependency issue last weekend - and I just tested it by uninstalling and reinstalling ActivePerl 1007. The ActivePerl PPM did not pick up the new package.xml from the repository (or at least decided it was unchanged). This, despite me reinstalling to a completely fresh location. Clearly, 'uninstall' leaves stuff hanging around. I had to disable the wxperl repository in PPM and then re-enable it for new information to be loaded properly. I fixed the dependencies in the repository by having Wx depend on the package Alien::wxWidgets::gcc and everything else with XS modules depend on Wx::gcc. The repository info for Alien-wxWidgets-gcc says that it provides Alien::wxWidgets::gcc and the repo info for Wx says that it provides Wx::gcc. So, provided the PPM manager has updated its info AND you don't manually add dependencies yourself, selecting Wx from ActiveState repo OR www.wxperl.co.uk repo should get you the right things installed. I went to the trouble of ensuring that Wx::TreeListCtrl and Wx::ActiveX compile with the ActiveState VC6 builds + Feb 2003 SDK to maintain choice - I've no idea why the ActiveState build system fails to build these modules. regards Mark
RE: PerlApp stopped working
On Tue, 02 Mar 2010, Mark Dootson wrote: The ActivePerl PPM did not pick up the new package.xml from the repository (or at least decided it was unchanged). This, despite me reinstalling to a completely fresh location. Clearly, 'uninstall' leaves stuff hanging around. I had to disable the wxperl repository in PPM and then re-enable it for new information to be loaded properly. You should be able to force a package.xml update with: ppm repo sync --force wxperl I went to the trouble of ensuring that Wx::TreeListCtrl and Wx::ActiveX compile with the ActiveState VC6 builds + Feb 2003 SDK to maintain choice - I've no idea why the ActiveState build system fails to build these modules. Neither do I. Every now and then I try to figure this out, but always run out of time before I get things working in a way that can be automated. :( Thanks a lot of putting in all the effort to manually get stuff working! Cheers, -Jan
Re: PerlApp stopped working
On 02/03/2010 18:52, Jan Dubois wrote: You should be able to force a package.xml update with: ppm repo sync --force wxperl Nice tip. I really ought to read the docs more often. Neither do I. Every now and then I try to figure this out, but always run out of time before I get things working in a way that can be automated. :( Something awry with my Makefile.PL / dist perhaps - I looked at the PPM failure reports and it appears a simple matter of not finding Wx Alien-wxWidgets installed. Thanks a lot of putting in all the effort to manually get stuff working! It is scripted across a number of VirtualBox vms + a physical mac mini and, since Wx 0.97 without patches being applied to the Alien-wxWidgets source or building wxWidgets separately. Woo hoo. Hmmm - well, I guess my ppd and package.xml build scripts are non-standard. I'm sure that's what you meant - but I wouldn't want anyone to think I sit typing makefile parameters for 4 architectures - or be left with the impression that there is any magic in the build process that goes beyond parameters to perl Makefile.PL and perl Build.PL. Evil things ARE scripted post-build to make everything work as a relocatable PPM on Linux / MacOSX. And as I have an interest in being able to distribute applications using a packager, the actions that make Wx/wxWidgets distributable as a PPM also make packaging an application reasonably straightforward. ( well, possible at least ) I do still manually set off the repository upload for fear of inflicting a broken build on everyone - but that's probably not necessary. Thanks for thanks and PPM tip. regards Mark
