Perl.Executeable History

Hide minor edits - Show changes to markup - Cancel

December 09, 2009, at 03:01 PM by OtherMichael -
Added lines 1-23:

General Notes


(:source lang=text:)
Using PPM install the modules into your development environment.


Create your own modules, when you need them, in a directory under the execution directory. I use /lib. Then at the top of my root executable Perl file you will find:


use strict; use warnings ‘all’; use Find Bin?; use lib “$FindBin::Bin/lib”;


Then I use Active States? Perl App? from the Perl Dev Kit (you could possibly use PAR to do the same thing) to create an exe - making sure I tell it where to find my /lib directory so it can load my modules as well. Generally speaking this will create a bundled file which has all the modules and dependencies in it. This way you need not have Perl installed on the target machines and yet you will have everything you need, including the exact version of Perl you are developing with.


I currently service 1500 users this way with one product. The original version which relied on locally installed Perl and modules was a nightmare - using PAR (which I did for a time ) but more recently Perl App? has been an absolute godsend as far as distribution of executable code is concerned.



See Also




Category tags

Perl Programming