Sep 17, 2015, 8:36 AM
Post #22 of 27
No, the module did not install.
Re: [mohan] Automating cmd prompt command execution
[In reply to]
'windres' is not recognized as an internal or external command, operable program or batch file.Do you have windres.exe on your system and is it within your path environment?
You have 2 things working against you (1) Activestate perl and (2) Activestate 64 bit perl, which boils down to 1 problem, that being Activestate.
Activestate perl is broken in a number of ways, primarily with its module support and installation. Activestate doesn't come with the proper tools (i.e. compiler) to build modules, which is part of the reason they have the PPM utility to download/install precompiled modules instead of using CPAN. Some people download nmake.exe or dmake.exe (it appears that's what you have done) which works ok on Windows 32bit systems, but not quite as well with 64bit systems. The next step up would be to install MinGW which provides the compiler and other helper tools. There is both a 32bit and 64bit version.
The best solution to this problem is to drop Activestate and switch over to using Strawberry perl, which is what I and many many others have done. Strawberry perl comes with the required compiler tools to build modules. That doesn't mean that you'll never have build problems like this, but it does mean that they will be few and far between.
I'm currently on a Win7 32bit system using Strawberry perl and PAR::Packer installed without any problems. Later today when I get home I can verify the installation on my Win7 64bit system.
(This post was edited by FishMonger on Sep 17, 2015, 8:43 AM)