note tsee <p> So you've had your opportunity to vent your frustration with this post. I had mine with another reply. Let's get back to work and analyze how we can improve things for the next guy. I'll just address some parts of your post and refer to the PAR toolkit only: </p> <ul> <li><i>The "use lib" bug":</i> You reported it and it's fixed in the Module::ScanDeps trunk. It'll be gone after the next release.</li> </ul> <ul> <li><i>The slowness of Module::ScanDeps:</i> The bulk of the time taken to package an application with PAR::Packer (== pp) is taken up by Module::ScanDeps. It scans your code for potential dependencies. Then recurses into them and does the same. This results in a lot of IO *and* in a lot of CPU churn. This is partly alleviated for multiple repeated builds by using the <a href="">caching</A> feature. But not entirely. It turns out that there's an underlying problem. Just recently, Chia-liang Kao reported this to me. I'm paraphrasing: <blockquote>The expanded DateTime::Locale modules all use utf8 and create a n-by-m dependency matrix with add_info <i>&#91;a Module::ScanDeps method for adding a dependency link&#93;</i>. They all get pushed into the return value which gets constantly iterated over. The duplicated calls only get skipped in the next level. </blockquote> This shows that there's clearly room for improvement. Neither Chia-Liang nor I have had the time to investigate a fix and it's not likely to happen any time soon. Volunteers and discussion on the PAR mailing list would be most welcome! </li> </ul> <ul> <li> <i>Couldn't package Wx application:</i> Others have pointed out that the external wxWidgets libraries need manual treatment. This isn't really a flaw in PAR (or other packagers). The only way to find out about what shared libraries would be needed by an XS module would be to ask the run-time linker. But that would be so utterly platform dependent and probably prone to breakage that nobody has bothered to attempt it. Instead, there are things like <a href="">Wx::Perl::Packager</a> that have the special cases for common libraries built-in. </li> </ul> <ul> <li> <i>The --gui option hides errors:</i> Well. It is documented as: <blockquote> Build an executable that does not have a console window. This option is ignored on non-MSWin32 platforms or when -p is specified.</blockquote> I <i>think</i> that this is quite clear about the effect of the option. </li> </ul> <ul> <li><i>Executable size:</i> Unfortunately, PAR packaged executables tend to be very large. It's because your Perl installation (which is packaged in the exe, mostly gzip'd) is very large, too. Add some shared libs... and you easily arrive at a couple of MB or even over ten. An alternative is something like Cava, which instead creates a "portable" library tree next to the slim executable loader. Choose your poison. There's one avenue to gain a bit in the case of PAR. The components that are required to bootstrap the application at run-time so far can't be compressed. Nowadays, that makes up for quite some overhead. Roderich Schupp and I have been experimenting with statically linking the executables to libz and decompressing the bootstrap-components on the fly. Roderich's code is available as a branch in the PAR repository. I'm sure he'd be open to contributions. </li> </ul> <p> I hope this constitutes a start in the direction of rational discussion (and action) with the goal of making our tools better. </p> 858805 858805