| [reply] |
I hear you're a prominent figure in the Perl community, and I would enjoy hearing what your pro's and con's are of both products which lead to your recommendation.
-Nitrox
| [reply] |
If you check out a recent thread (namely perl2exe - no more secrets), I think you will understand merlyn's point of view. :)
If the above content is missing any vital points or you feel that any of the information is misleading, incorrect or irrelevant, please feel free to downvote the post. At the same time, reply to this node or /msg me to tell me what is wrong with the post, so that I may update the node to the best of my ability. If you do not inform me as to why the post deserved a downvote, your vote does not have any significance and will be disregarded.
| [reply] |
PAR is very cool, but I've had problems using it with more complex dependency chains -- i.e., modules using PerlTk, or if the perl on the compiling box uses shared libraries and the target box doesn't have the shared libraries. That's perhaps not surprising.
Would suggest that the monk first try PAR, yes, but if he really needs an executable and PAR doesn't work, ActiveState does make a fine product...
| [reply] |
Go to Start Menu\Programs\ActiveState Perl Dev Kit and select "Documentation". If something is not clear from the docs tell us what and we will try to help.
Usualy the whole thing you have to do is to run
perlapp yourScript.pl
on the Command Prompt
and you get a freestanding yourScript.exe.
Jenda | [reply]
[d/l] |
| [reply] |