in reply to pp generated exe can't find DLL when using OLE

It seems to me like you might need to explicitly include DynaLoader.pm in your archive. Check the pp manual for instructions on how to do that. If you envision yourself compiling Perl for Windows regularly, you might want to check out ActiveState's PDK; it contains a tool called 'PerlApp' that makes PAR-like packing incredibly convenient.

Back when I started using Perl, that's all I used. It actually helped me learn to use PAR, since it shows you the commmand line it's passing for the build.

radiantmatrix
require General::Disclaimer;
s//2fde04abe76c036c9074586c1/; while(m/(.)/g){print substr(' ,JPacehklnorstu',hex($1),1)}

  • Comment on Re: pp generated exe can't find DLL when using OLE

Replies are listed 'Best First'.
Re^2: pp generated exe can't find DLL when using OLE
by PodMaster (Abbot) on Feb 01, 2005 at 15:16 UTC
    No. That error message is generated by DynaLoader (specifically dl_load_file). It's saying that it can't load nDCEaSeL9M.dll for Win32::OLE due to a system error (ERROR_PROC_NOT_FOUND).

    DaleCooper needs to turn on the env var PERL_DL_DEBUG to see if he can get some debugging messages, and/or examine his system logs (in EventViewer).

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

      Thanks, guys.

      The set PERL_DL_DEBUG=true got me started. Strange thing was that the OLE.DLL is where things were going P*P.

      When I ran the pp command in verbose mode and with the PERL_DL_DEBUG, OLE.dll is never mentioned, even though I have explicitly refered to it in the pp command line?

      pp -v -B -l "C:\Perl\site\lib\auto\Win32\OLE\OLE.dll" -M Win32:OLE -o +PatchMeThese.exe PatchMeThese.pl
      I then ran PPM to query which version of OLE I had. PPM couldn't find Win32-OLE or OLE, so I simply installed, run the PP command the output was a working exe.

      Strange but fixed.

      Many Thanks,

      Dale