in reply to Re^2: Converting to exe
in thread Converting to exe

Well I am a bit confused. PerlApp is part of Active State's development kit and will cost you about $300 - check their website for current pricing. This thing works better and is smarter than the free tools, but you have to buy it!

I must say that I am no salesman for Active State. I started using this thing a long time ago, Win NT, Perl 5.6. They've come a long way and the tool has definitely progressed. I am a satisfied user and I have found that this thing works.

Basically if you are getting paid money to write the Perl program that you want to make into an exe, then paying some money to make that process easier and better is not that much of a stretch.

You can use pp with ActiveState Perl. But you cannot use PerlApp with Strawberry Perl. Again, after a decade+ use, I would recommend PerlApp for professional environments.

Replies are listed 'Best First'.
Re^4: Converting to exe
by Anonymous Monk on Oct 13, 2011 at 08:56 UTC
    Thx, i will try the ActiveState distribution. It is funny that Perl App actually builds the exe in exact same way as the pp application(or package packer). So in other words i can build with PerlApp a script with a Strawberry Perl installation. It recognizes the paths to the modules(but not all how it seems).It builds but i get the same error as with the pp application

    I must say i'm a C++ programmer and i'm very new to the Perl world(3 separated weeks at max) so if i say something stupid ... that's also a explanation.

    Anyway i'll try the ActiveState solution and see further.

      This is a situation where I am telling you from my experience that if you do steps: x,y,z it will work. If you want to do step c instead of step y, then you are "on your own".

      If you have the ActiveState license, build an "clean" ActiveState installation and then run the tool. I think that I have been very, very clear about what to do and how to do it.