|No such thing as a small change|
Using Proc::Background and Win32by mmartin (Monk)
|on Oct 18, 2013 at 17:12 UTC||Need Help??|
mmartin has asked for the
wisdom of the Perl Monks concerning the following question:
OS: Win32 (XP)
Does anyone know why if I execute a Perl script using Proc::Background I get an error about 'absolute path' if
I don't include the "perl" keyword before the script name?
Both the calling script and the Background Script reside in the same directory. If I run the EXACT same command
using something like backticks or the 'system()' command it runs just fine, but when Proc:Background does it I get
an error. Any ideas?
I ran both the ASSOC and FTYPE commands in the cmd prompt and they are good. I can run the Perl script from the CLI
without any errors, and without needing to add "perl" before the script name, but for some reason Proc::Background
complains when I don't include that...
I assume those are correct since it works from the Command Prompt without needing to add the "perl" keyword...?
Now here are some of the things I've tried:
Does anyone know why the Proc::Background command will not run the Perl script without the "perl" keyword before
the script name...?
These other methods seem to work without any errors:
Is there something with the Proc::Background command I'm missing?
I don't want to include the "perl" keyword because I'm packaging my Perl Scripts using the CavaPackager Program to
make them into exe's...
I also want to keep them as relative paths since this won't be the final location of the program when I'm completed
everything. And both of those script will ALWAYS be in the same directory.
If anyone has ANY hints or suggestions for me, PLEASE feel free, this is getting very frustrating...
Thanks in Advance,