Wed Dec 12 17:52:44 2018: Request 127971 was acted upon.
Transaction: Correspondence added by SLAFFAN
Queue: PAR
Subject: {Windows] PAR-Packer-1.047
Broken in: (no value)
Severity: (no value)
Owner: Nobody
Requestors: welleoz...@googlemail.com
Status: open
Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=127971 >
And just to add a few extra data points, I have a script that uses objdump to
find dependent DLLs on windows. It would need some edits to work on Linux, and
a different approach to work on Macs, but it does the job for my use case.
https://github.com/shawnlaffan/perl-pp-autolink
The logic has been adapted from the pp_simple.pl script at
https://www.perlmonks.org/?node_id=1148802
That script itself might work well enough for most use cases, I just did not
need to check for all the extra WX stuff.
There is also some similar logic in the build system that could perhaps be
adapted to the more general packing case.
https://github.com/rschupp/PAR-Packer/tree/master/myldr/find_files_to_embed
Shawn.
On Wed Dec 12 10:31:43 2018, LAMPRECHT wrote:
> Am Mi 12. Dez 2018, 07:03:49, welleoz...@googlemail.com schrieb:
> > Adding also --link zlib1_.dll it works.
> >
> > However, the same problem occurs with all other missing .dll
> > Unfortunately, the error message doesn't say the name of the dll
> > missing
> > (it has an arbitrary code), just the module referring to it, which
> > makes it
> > difficult to find the respective dlls
>
> My reply on the list did not show up, so I retry via rt.cpan.org:
>
> you can use
> https://docs.microsoft.com/en-us/sysinternals/downloads/process-
> explorer
> to see which dlls are opened by your packed executable on the packing
> machine.
> The DLLs referenced there should either be in your PAR-cache-
> directory or windows system libraries.
>
> Christoph
