biovijay89 has asked for the wisdom of the Perl Monks concerning the following question:

Dear monks, I have written a piece of perl script and i packed it as a .exe using perl dev kit. I have used the 21 day trial version of PDK. Can someone please let me know if the exe would work after the trial period also?? This has been puzzling em for quite sometime!!! Thanks.

Replies are listed 'Best First'.
Re: Creating .exe using PERL dev kit
by stevieb (Canon) on Jun 15, 2016 at 11:04 UTC

    You could also use the Open Source Par::Packer module and its related pp utility to create packaged binaries for Windows.

[reply]
Re: Creating .exe using PERL dev kit
by $h4X4_|=73}{ (Monk) on Jun 15, 2016 at 10:27 UTC

    Perl Dev Kit 5.3.0.530 Release: November 2003 >>> When used with an evaluation license, all tools display a warning that the generated executables will stop working once the evaluation license expires.

    Yes it looks like it will.Perl Dev Kit 9.3 -- Release Notes

[reply]
Re: Creating .exe using PERL dev kit
by dasgar (Priest) on Jun 15, 2016 at 16:55 UTC

    The trial period licensing applies only to using the PDK - not the executables that are created by using the PDK.

    It's been a long time since I have used PDK, but if the PDK licensing (even for the trial version) includes some restrictions/requirements regarding use/distribution of executables created by PDK, then those licensing restrictions/requirements would still apply to the executables you created even after the trial period expires.

    As stevieb suggested, using the pp utility from PAR::Packer is a good free alternative.

    I'm assuming that if you're using PDK, then you're probably using ActiveState's ActivePerl. If so, I'd recommend using the PPM utility to install dmake and MinGW from ActiveState's PPM repository. With 32-bit ActivePerl, this will let you install modules directly from CPAN, which will let you install PAR::Packer. (For 64-bit ActivePerl, there might be additional steps needed in order to install modules directly from CPAN.) Alternatively, you can move to using Strawberry Perl, which comes with all of the compiler tools needed to install modules directly from CPAN.

    Another alternative to using PDK is Cava Packager from the Citrus Perl folks. I personally have not used Cava Packager so I can't really comment on it.

[reply]
      Thanks for our suggestion. I have now got the 32 bit version of activestate perl and have set the paths for dmake and MinGW. However I am encountering the below error messae while installing perl packages.

      C:\Perl\bin\perl.exe Makefile.PL INSTALLDIRS=site -- OK Running make for M/MD/MDOOTSON/Win32-Exe-0.17.tar.gz The filename, directory name, or volume label syntax is incorrect.

      dmake.exe: Error code 1, while making 'pm_to_blib' MDOOTSON/Win32-Exe-0.17.tar.gz C:\Perl\bin\dmake.exe -- NOT OK RSCHUPP/PAR-Packer-1.033.tar.gz Has already been unwrapped into directory C:\Perl\cpan\build\PAR-Packer-1.033- wO194G

      RSCHUPP/PAR-Packer-1.033.tar.gz Has already been prepared Running make for R/RS/RSCHUPP/PAR-Packer-1.033.tar.gz Warning: Prerequisite 'Win32::Exe => 0.17' for 'RSCHUPP/PAR-Packer-1.033.tar.gz' failed when processing 'MDOOTSON/Win32-Exe-0.17.tar.gz' with 'make => NO'. Cont inuing, but chances to succeed are limited. CPAN: Time::HiRes loaded ok (v1.9733)

      'C:\Perl\bin\perl.exe" "-Iinc' is not recognized as an internal or external comm and, operable program or batch file. dmake.exe: Error code 1, while making 'blib\lib\PAR\.exists' RSCHUPP/PAR-Packer-1.033.tar.gz C:\Perl\bin\dmake.exe -- NOT OK

      I am trying to resolve this for a long time but no luck. Any suggestions to fix this ??

[reply]
[reply]

Back to Seekers of Perl Wisdom