Yes, I know this tool, is very good! Perhaps in the next release I publish it with a installer! ;-p
For the 2.0 version I want to test more LibZip, maybe cut off the small ./lib directory using some Perl magics. And I will enable the end user to append their script in the executable, to delivery their applications using TinyPerl, since I already do that (take a look in the end of the file tinyperl.exe).
Graciliano M. P.
"The creativity is the expression of the liberty". | [reply] |
Also, if you use NSIS and its built-in compression, you can probably distribute the lib/ directory as a set of files instead of a zip. This will save loading time for modules, allow easier installation of modules, and will obviate LibZip (and the 111K it uses when uncompressed). Also, the tinyperl you're shipping doesn't seem to be UPX'd. Your version is 16KB; the UPX'd version is 3.5KB. Finally, UPX'ing all the files in the auto directory of lib.zip will save you a good amount of space.
Good luck!
Bill
| [reply] |
I only UPX the DLLs, the executable can't be UPX'ed because it has some appended data in the end, it has a script that automatically loads LibZip!
About the ./auto files, I forgot to UPX them in the release! Thanks for the alert!
Graciliano M. P.
"The creativity is the expression of the liberty".
| [reply] |