So using PAR, normally you can type pp -o runme.exe myscript.pl
and it will create a standalone executable. Finds dependent modules, binds in Perl, everything. EXE starts up slow, but that's OK for my use case. But if myscript.pl has any Inline::C code, it doesn't work without a C compiler configured on the target machine. Now, I know I can repackage my Inline::C code as a CPAN module, or generate XS code, but it would be really useful to have an IJW solution that allows me to easily continue to use Inline::C (all my scripts are continually being developed) yet deliver EXEs that do not. I also saw a suggestion to zip up _Inline directory and unpack it next to the PAR executable. But that's an extra step for my users. I'm currently working in SQA, and I like end users to be able to repro my bug reports using as few steps as possible. A single executable that packages up a set of regression test cases is the ultimate goal. Any ideas on starting points to add this feature to Inline::C? What I'd really like is to be able to have PAR build the Inline::C module during the process of making runme.exe, and automatically bind. Or is this more of a PAR question? -- John.
