Bloehdian has asked for the wisdom of the Perl Monks concerning the following question:
Hello,
a client of mine wants a Perl script for system surveillance be programmed, the target operating systems ranging from Windows 2012 to 2019. But he wants to avoid third party installations, i e., would not allow the installation of the Perl interpreter under a privileged account.
Hence, I have the task to devise a solution which is not dependent on a "normally" installed Perl interpreter and which (ideally) does not require individual development environments for each operating system (Windows 2012, Windows 2016,...).
So, is this possible w/o relying on modules like App-Staticperl? Can one compile a Perl script on ONE Windows version which include all libraries statically and which can be deployed on all three target versions?
And, IF I am forced to deploy systems like App-Staticperl, are they passably uncomplicated to use?.
I would like to avoid introducing unnecessary trouble into a project which itself is quite ambitious already.
Any thoughts?
Greetz
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Running compiled Perl script on different Windows Server versions
by marto (Cardinal) on Sep 24, 2019 at 19:23 UTC | |
by Anonymous Monk on Sep 24, 2019 at 22:21 UTC | |
| A reply falls below the community's threshold of quality. You may see it by logging in. |