in reply to Perl script to EXE to Windows Service

you have to supply every .dll (loadable object) that a module uses (put it into the same path the .exe resides, i think).
  • Comment on Re: Perl script to EXE to Windows Service

Replies are listed 'Best First'.
Re^2: Perl script to EXE to Windows Service
by punkish (Priest) on Dec 30, 2004 at 21:31 UTC
    I thought that was the idea behind pp. That it took all the requirements of the script and wrapped them up along with a perl interpreter into a .exe.
[reply]
      all the perl-code. c-parts (dlls in windows) are different (because the are already compiled).
      you will have to supply them. (as you would have to if you deploy you program in perl-sourcecode)
[reply]
        Not really. If you have the latest PAR and Moudule::Scandeps (a dependency), you shouldn't have to (at least with a regular module like Win32::Daemon). Try these to see that its true :) 
        perl -e "use Win32::Daemon;print $/,$Win32::Daemon::VERSION,$/;"
scandeps -V -e "use Win32::Daemon;print $/,$Win32::Daemon::VERSION,$/;
+"
pp -e "use Win32::Daemon;print $/,$Win32::Daemon::VERSION,$/;"
a.exe

        [download]
        If it doesn't work for you (and you're on win32:), you're not using the latest and the greatest PAR (and its dependencies).

        As a general rule, if `pp' isn't packing up everything it should be, chances are you need to learn How to use PAR.

        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.

[reply]
[d/l]

In Section Seekers of Perl Wisdom