On Sun, Dec 14, 2014 at 6:30 PM, Juan José 'Peco' San Martín < [email protected]> wrote:
> I think PAR (Module-ScanDeps) detects "use XX" pushing the needed modules > into the EXE, but why this change the behaviour of the script? > Correct, so the executable should just contain some more modules which can't hurt, right? But stranger things have happened... Try to figure out the difference: create your excutable both with and without "use XX", run "unzip -l your.exe" on them (a pp'ed executable is also a zip file), sort the outputs and run diff on them. > It's not sane, but at this point my pp line includes all the DLLs/.a > libraries that exist (double checked with the list of Roderich). > Note that adding *.a libraries is useless in this context. And do NOT simply add "all DLLs that exist", esp. do NOT add perl520.dll, libgcc*.dll, libstdc++*.dll, libwinpthread*.dll. Cheers, Roderich
