in reply to Runtime only Perl for Win32

The two approaches already mentioned:

  1. use PAR::Packer, Win32::Packer and then pp to create stand-alone perl executables (PEX) for a single perl script (like jars for java so to speak). These PEX carry all the modules you will ever need for that particular script you are distributing. So, duplicate modules exist in each PEX. In addition, it takes some time to run because of initial setup costs (unpacking). But that decreases by activating the cache switch. I consider this a good solution, the minus is the duplicate modules in each PEX.
  2. Install some minimal perl distribution.

I will suggest add to the list a solution based on containers (e.g. docker): create such container to include perl and all your scripts. Right now I can not even make docker run on my Linux to try this approache and that reminds me why I never use them nor caught their band-wagon when first came to town. But I am sure it's child's play to sell that idea to any snake charmer, any day.

bw, bliako

Replies are listed 'Best First'.
Re^2: Runtime only Perl for Win32
by fdesar (Beadle) on Feb 02, 2019 at 16:17 UTC

    This is not at all what I'm looking for: I don't have any script to run, but want to have a Perl runtime to be able to run any script written as an Inkscape extension, which calls directly wperl.exe with the name of the extension script which get its parameters from Inkscape through STDIN, including a temporary XML file name which is the current document, and output its messages , if any, to Inkscape through STDERR and finally returns the modified document through STDOUT). As I said earlier, it smells like Strawberry but without all the stuff needed for Perl development, like gcc, cpan, pods etc. Only a wperl.exe excecutable, some XS modules and the DLL needed to run them, nothing more.