PAR::Packer generates the following when I attempt to run the resulting .exe:#!/usr/bin/perl #perl2exe_include "attributes.pm"; use strict; use warnings; $|=1; use Symbol qw( gensym ); use IPC::Run qw( start ); use Tie::Handle; use IPC::Run::Win32IO; my %sp; $sp{'STDIN'} = gensym(); $sp{'STDOUT'} = gensym(); $sp{'STDERR'} = gensym(); my $h = start ['./cnc.exe'], '<pipe', $sp{'STDIN'}, '>pipe', $sp{'STDOUT'}, '2>pipe', $sp{'STDERR'} or die "returned $?"; sleep 20;
Inappropriate I/O control operation: Win32::Process::Create() at C:\Us +ers\Izomiac\AppData\Local\Temp\par-4a6f7368\cache-6146a0a42031e00189f +f49a355f90de7875866db\inc\lib/IPC/Run.pm line 2143. Inappropriate I/O control operation: Win32::Process::Create() at C:\Us +ers\Izomiac\AppData\Local\Temp\par-4a6f7368\cache-6146a0a42031e00189f +f49a355f90de7875866db\inc\lib/IPC/Run.pm line 2244. Inappropriate I/O control operation: Win32::Process::Create() at C:\Us +ers\Izomiac\AppData\Local\Temp\par-4a6f7368\cache-6146a0a42031e00189f +f49a355f90de7875866db\inc\lib/IPC/Run.pm line 2244.
And Perl2Exe runs the .exe version dozens of times simultaneously.
For context, this script launches a half-dozen other scripts and coordinates communication between them by piping things through STDIN/STDOUT. I adopted this approach since one subprocess is a Tk GUI, another loads gigabytes of data into memory, and another is a 32 thread genetic sorting algorithm, and combining them into one process caused all sorts of instability. This version is faster and much more stable, but it's a big ask to have end-users install perl.
Any suggestions or alternatives?
In reply to PAR-Packer and IPC-Run by izomiac
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |