|Think about Loose Coupling|
many exe files rely on one libraryby xiaoyafeng (Chaplain)
|on Oct 13, 2012 at 07:36 UTC||Need Help??|
xiaoyafeng has asked for the
wisdom of the Perl Monks concerning the following question:
I package perl script with pp when I need to publish it to windows clients. Life is peace until one day clients complain temp directory was full. 20+ 50M-size exe files created almost 7G files in C drive!
the straightforward way I can think is install perl on client machines and replace exe with scripts. yes, it's a way, but, I prefer exe, which can be view as a protection to prevent user modify it easily.
So my question is: how to make all exe built with pp shared libraries other than contain all modules into one executable file? Just like .NET, install one and all exe file can make use of it.Thanks in advance!
Sorry for the long time to reply this. After dig monks' reply below, I realize the better way to deal with this request is packing my own perl distribution, not local lib, not pp. just whole perl distribuiton: perl executable, libraries etc. And use pl2bat, bat2exe to wrap around script, or even make this by hand personally as thomas895 suggest.
Thanks monks, your generous help always makes me less headache. ;)
I am trying to improve my English skills, if you see a mistake please feel free to reply or /msg me a correction