in reply to PC Problems with pp

I second JamesNC's advice -- get a developer's license from Active State, and use perlapp! (That's the program which produces a standalone Perl application).

I was the main Perl programmer at my last company, so they actually bought me a license, but if I had to get one again, I now know its benefits.  Perlapp has the nice features of running on Linux and Windows both (and one or two other OS's I never used), and any modules which you're using when you build the executable are automatically included, so you don't have to worry about it running on a "non-Perl" machine.  There's a lot more to the developer's package as well, but perlapp alone makes it worth the price.


@ARGV=split//,"/:L"; map{print substr crypt($_,ord pop),2,3}qw"PerlyouC READPIPE provides"

Replies are listed 'Best First'.
Re^2: PC Problems with pp
by Cody Pendant (Prior) on Feb 04, 2006 at 21:38 UTC
    Interesting point. My client is very patient, but that sounds like the professional way to go.

    Call me stingy, but, does an app created with the 30-day trial last after the 30 days?



    ($_='kkvvttuu bbooppuuiiffss qqffssmm iibbddllffss')
    =~y~b-v~a-z~s; print
      Oh, I'm sure it does.  I haven't used it in awhile (my current company is a Linux shop, so I'm blissfully removed from Windows now), but my experiences with Active State all indicate that they are above doing that sort of thing.

      For example, when I got the license for the developer's kit, I was happy to see that it permits the user to run it on multiple computers, as long as it's just one at a time. This, in contrast with the software licenses of many other places, which forbid installing on other than a single computer.


      @ARGV=split//,"/:L"; map{print substr crypt($_,ord pop),2,3}qw"PerlyouC READPIPE provides"
      If I remember rightly, the AS perlapp creates a fully functional .exe, but it has like a 5-second pause and shows a "You're using a trial version" banner before it exectutes. You can send it to your client and if it works, buy the full Dev Kit and get him the non-pause program.

      Something I thought of: To test for dependencies, go find perl58.dll in your Windows directory and rename it. Then rename c:\perl to c:\Notperl or something. If you can't run your packaged script with all dependent paths cut off, then the problem is likely in what you're packaging. See above messages for where to look.

      --marmot

        Two very useful suggestions, thank you.


        ($_='kkvvttuu bbooppuuiiffss qqffssmm iibbddllffss')
        =~y~b-v~a-z~s; print
Re^2: PC Problems with pp
by Anonymous Monk on Feb 05, 2006 at 12:23 UTC
    PAR and perlapp are equivalent in features and platforms they'll run on. If anything, PAR will run on some platforms perlapp doesn't.