Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- Question about building modules on W2K
September 24, 2004, 11:09 am
rate this thread
I have two environments here -- development and production. The
software architecture of the boxes are strictly controlled by the
security administrators. The Perl I have is 5.8 but it's pretty
stripped down (no additional modules, ppm, etc.). We have the need
for and I have the go-ahead to load Win32. I got Win32 built but it
didn't go exactly according to CPAN's HOWTO.
While on the development suite, I did 'perl Makefile.PL' and the
package looked good but when I ran 'nmake' next, it failed with, "'cl'
is not recognized as a internal or external command yada yada yada".
So I went to a box which has MS Visual C++ on it and 'nmake' worked
great (none of this is in CPAN's HOWTO). I did 'nmake install' and
was able to run some test scripts which used Win32.
So now that this is working on dev, I took the compiled files (and
nmake 1.5, which is supposed to be stand alone) over to the production
suite. 'nmake install' failed there. I decided just to copy the
files over to \...\site\lib and when I ran the test scripts I got a
system error bitchin that mscvr71.dll couldn't be found. MSVC++ put
its dirty little hands all over my perl module and without loading the
IDE on the boxes, I cannot use the Win32 module. And obviously I'm
not going to put an IDE on a production suite.
So, is there a way to build Win32 so that it can be deployed on a box
that doesn't have cl or any of the MSVC++ *.dlls?
- Brian McCauley
September 25, 2004, 12:11 am
Re: Question about building modules on W2K
corn29@ no_spam excite.com wrote:
> Subject: Question about building modules on W2K
I don't think your question is really about Perl or W2K.
Your quesion is mostly about Microsoft VC++.
> ... error bitchin that mscvr71.dll couldn't be found. MSVC++ put
> its dirty little hands all over my perl module and without loading the
> IDE on the boxes, I cannot use the Win32 module.
Er, no you only need mscvr71.dll. (which is freely redistributable).
As far as I know you'll get this if you install any windows application
that has been built with M$ C compiler version 7.1.
I don't think you are bein very fair on M$ - you'd have hit exactly the
same problem on Linux if you'd built a module using a later version of
glibc than that on the target platform.
> So, is there a way to build Win32 so that it can be deployed on a box
> that doesn't have cl or any of the MSVC++ *.dlls?
Maybe there's a static version of the mscv71 library.