in reply to Re^2: Included scripts did not encrypt using pp (libs aren't scripts)
in thread Included scripts did not encrypt using pp

Let me add one remark:

All additional pl-files (foo1.pl and foo2.pl) are subroutines from other applications. That's why there are separate files.

  • Comment on Re^3: Included scripts did not encrypt using pp (libs aren't scripts)

Replies are listed 'Best First'.
Re^4: Included scripts did not encrypt using pp (libs aren't scripts)
by Anonymous Monk on Dec 03, 2015 at 00:44 UTC

    pp will try to generate multiple executables and will fail.

    I'm sure that it will not do that :)

    I was under the impression that the '-f'-option will decrypt ALL scripts automatically.

    You mean encrypt. Why should -f option encrypt something that is not considered a script and ends up in inc/lib instead of inc/scripts?

    OTOH, the -F option probably ought to encrypt any .pl files that end up in inc/lib -- you probably found a bug

    All additional pl-files (foo1.pl and foo2.pl) are subroutines from other applications. That's why there are separate files.

    Smart! Writing perl like its 1994 :)

      I tried it with the -F option:
      pp .. -f Crypto -F Crypto ... pp .. -f Crypto -F Crypto=foo1.pl ... pp .. -f Crypto -F Crypto=foo*\.pl ...
      None of it worked for me. Any suggestions?