Roderich Schupp <roderich.sch...@googlemail.com> writes:
> On Mon, Apr 20, 2015 at 11:05 PM, Harald Jörg <harald.jo...@arcor.de>
> wrote:
>
> So I thought that I could just
>
> use lib 'foo';
>
> in my source, and then drop the plugins to directory 'foo'. To my
> disappointment, this fails, the modules aren't found. Drats.
> [...]
> * is that intended / accidental behaviour?
>
> That's definitely a bug, please submit a bug report to rt.cpan.org (in
> queue PAR::Packer).
Thanks for the clarification! I've submitted a bug report.
> [...]
> I've managed to overcome some pitfalls (missing DLLs, dynamic
> loading of modules which Scandeps can't find), but there's still
> one thing I don't understand, and Google didn't point me into an
> explanation so far.
>
> If these are public modules (ie. they are on CPAN), please consider
> submitting bugs for these as well (queue Module::ScanDeps).
The DLLs are the notorious libeay32_.dll and ssleay32_.dll. I seem to
recall having found an article of yours saying this can't be solved, but
am unable to find the article right now. I guess zlib1_.dll, as used by
Archive::Tar, is of the same sort. Hmmm... I can --link them to the
executable, but after unpacking to tempdir they end up in a directory
where apparently Windows doesn't look for them. Would adding that
directory to $ENV{PATH} solve the issue? This would be a job of the
unpacker, right?
I can provide a list of CPAN module dependencies which Module::ScanDeps
doesn't find to its queue. However, these dependencies are only
required if certain conditions are met. For applications where these
conditions don't apply, the PAR gets bloated without need.
Actually, this problem is rather easy to workaround: I added a module
which just uses the undetected dependencies. I need this anyway, for
dynamic loading by the application itself. So if I submit a bug report
and it gets rejected, I'm fine with it - at least we leave a trace for
Googlers who encounter the same issues.
Thanks again for your support!
--
Cheers,
haj
BTW: There are references to http://par.perl.org/ on CPAN, but that
website is more PARrot than PARish.
