Mark Could you elaborate:
"But it does have functions that will translate your 'perl' time calls to execute scripts into 'packaged' time calls to run executables." What do you mean by 'time calls'? Jeff On Mon, 2011-02-14 at 22:51 +0000, Mark Dootson wrote: > Hi, > > Cava does what you want automatically. (I was bound to say that). But it > does have functions that will translate your 'perl' time calls to > execute scripts into 'packaged' time calls to run executables. > > With PAR::Packer I guess you could ship one large .par file with > everything shared in and 'use' it from slim pp executables. > > PerlApp allows you to share modules - so you would put almost everything > in one executable - then other executables could share the modules > packed in that. > > H.T.H. > > Mark > > On 14/02/2011 22:43, Johan Vromans wrote: > > Currently, I know of three packagers that can handle wxPerl > > applications: Cava, PAR and PerlApp. Each have pros and cons. > > > > I have some biggish applications that share a collection of modules. In > > fact, each application only differs in the Main module. The applications > > call each other when necessary. > > > > I can, of course, pack each application individually but that would > > result in a big waste of resources (and probably performance). So I > > guess this can be done much smarter. > > > > The question is: how? > > To eliminate one possibility: switching to threads instead of calling > > the other applications is currently not feasible. > > > > -- Johan > > > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________
