Check out the--scan, --shared, --use and -runlib options.
I thought I posted a sample for this to the PDK list, but the best I can find
right now is this:
http://aspn.activestate.com/ASPN/Mail/Message/pdk-beta/3355275
Note that you don't need to have a separate shared lib; you could try to bundle
as much as you can into one of your applications and
just use that one. Conceptually I prefer a separate lib though.
Cheers,
-Jan
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edward Peschko
Sent: June 18, 2008 10:41 AM
To: [email protected]
Subject: shared components in 'compiled' executables.
hey all,
I've been using perlapp/perltray/etc. to 'compile' executables, and was
wondering whether the following was possible:
I would like to be able to share components between executables of the same
overarching 'application'. As it stands right now, I
have several apps that are all related together, and hence could reuse each
others' components. But since they are all compiled
separately, they all bundle (repeatedly) the same perl executable, shared
libraries, etc.
How do you make it so that each library in one app is viewable/usable by the
others, and hence does not need to be archived
separately?
Thanks much,
Ed
_______________________________________________
ActivePerl mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
