Re^3: citrus perl generated .exe and Perlapp

Replies are listed 'Best First'.
Re^4: citrus perl generated .exe and Perlapp by james28909 (Deacon) on May 28, 2014 at 05:29 UTC
lol, you got a point there, but i think ill just figure out why i cannot get the gui working with wxperl and active state perl. cz i like for my exe's to be independent. I want it to "look" professional, even tho im /not/ a professional. Actually... installing citrus perl made me realize actually that i didnt have the correct modules installed anyway lol. i will cross refence my citrus perl and download the same modules thru cpan or ppm for active state and see what happens, cause if it works in citrus perl, there should be no reason it doesnt work in Active State with WxPerl ^^	[reply]
Re^5: citrus perl generated .exe and Perlapp by dasgar (Priest) on May 28, 2014 at 05:55 UTC
Since you're using Citrus Perl, you could try using Cava Packager (from the makers of Citrus Perl) to create your stand-alone executables. I personally haven't used Cava Packager, so I can't offer insight on the tool. If you're wanting to move to ActivePerl, you might find it easier to install Wx from the Bribes respository. I think that ActiveState may have configured PPM with the needed information to add the Bribes repository. If not, you can go to http://www.bribes.org/perl/ to get more details about using the repository. If you plan to install Wx and related modules in ActivePerl directly from CPAN, keep in mind that ActiveState does not include compiler and related tools by default in ActivePerl installation. For 32-bit ActivePerl, you can use PPM and install MinGW and dmake from ActiveState's repository, which will then allow you to install modules from CPAN that need to be compiled (like Wx). Another alternative is that you can use the pp utility from the PAR::Packer module.	[reply]