Re: Problem when using NMAKE to build Perl on Windows




"treble54" <treble54@xxxxxxxxx> wrote in message news:1180560992.248641.213220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am trying to run Perl in a Windows environment.

Here is my setup:
I have installed Visual Studio C++ Express 2005 as well as the latest
SDK (non 64-bit version). I am currently running Windows XP SP2.

Others have reported problems with miniperl when attempting to use that compiler to build perl. I don't think anyone has managed to build perl using that compiler - I haven't checked for a while, so please let me know if you discover that's not so.

Building perl is a fairly straightforward procedure using Visual Studio 6.0, 7.0, or 7.1. (Do you have either of them ?)
It's also fairly straightforward using the (freely available) MinGW port of the gcc compiler and dmake.

For MinGW and dmake:
http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=82721&release_id=158801
and
http://search.cpan.org/dist/dmake/

I know activestate uses the freely available Windows Server 2003 R2 Platform SDK compiler for their 64-bit build of ActivePerl (as Visual Studio 6.0 won't work in a 64-bit environment). I think there's a good chance that the 32-bit version of Windows Server 2003 R2 Platform SDK compiler would also build perl on a 32-bit platform (but I don't really know). You can get it from:
http://www.microsoft.com/downloads/details.aspx?FamilyId=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en

if you want to give it a try.

One other option worth investigating is Strawberry Perl: http://vanillaperl.com/ .

It's a precompiled perl but it comes packaged with it's own compiler (MinGW's gcc) and make (dmake) - so there's nothing else that needs to be installed if you want to build perl extensions. (For that matter, you could use the MinGW and dmake that comes with Strawberry perl to build your own perl if you wanted.)

Then, of course, there's ActivePerl (as Dean mentioned). It doesn't give you a compiler, but there's a good PPM utility for installing pre-built modules. And I think you might even have a fair degree of success using Visual Studio C++ Express 2005 to build perl extensions - though I'm loathe to recommend using that compiler with ActivePerl.

Cheers,
Rob

.



Relevant Pages

  • Re: Difference between VC++ and UNIX
    ... It uses whatever compiler you have, in whatever language you like. ... like edit Lisp or integrate 3rd party compilers into Visual Studio. ... Windows, HP-UX, and Linux. ...
    (comp.programming)
  • Re: hmm..interesting
    ... work out at more power per Watt than x86. ... mainstream (many netbooks and smartphones run Linux instead of Windows ... the fact that Visual Studio allows you to get away with fairly sloppy ... difficult to find a C compiler that *doesn't* have vendor-specific ...
    (comp.sys.acorn.hardware)
  • Re: Redefinition of target errors
    ... compiler instead of the Borland compiler. ... I can't remember if you said your Perl was activestate. ... to find a link or a way to get dmake for Borland. ... The last time I tried to compile a perl module written in C for Windows it was a real PITA. ...
    (perl.dbi.users)
  • Re: Difference between VC++ and UNIX
    ... It uses whatever compiler you have, in whatever language you like. ... like edit Lisp or integrate 3rd party compilers into Visual Studio. ... Windows, HP-UX, and Linux. ...
    (comp.programming)
  • Re: hmm..interesting
    ... I used to be a professional software developer on both Unix/Linux (all ... flavours) and Windows (writing CFD and Valve-train dynamics software, ... the fact that Visual Studio allows you to get away with fairly sloppy ... difficult to find a C compiler that *doesn't* have vendor-specific ...
    (comp.sys.acorn.hardware)