Re: perlXStut

From: Sisyphus (kalinaubears_at_iinet.net.au)
Date: 09/25/04 

Date: Sat, 25 Sep 2004 21:03:13 +1000

Ketema wrote:
> I am attempting to go through the perlXStut and I can't complete the
> make process. My system is WinXP. I have Visual Studio.Net 2003
> installed, so I am using nmake, as also confirmed by perl -V:make. My
> perl is Activestate v5.8.4.
> My perl -V:libc is msvcrt.lib.
>
> After having a buch of files missing I finally figured out to add
> "c:\Program Files\Microsoft Visual Studio .NET
> 2003\Vc7\bin","c:\Program Files\Microsoft Visual Studio .NET
> 2003\Vc7\include" and "c:\Program Files\Microsoft Visual Studio .NET
> 2003\Vc7\lib" in my perl inc path. The files I am trying to create is
> right out of perlXStut: Mytest. The error I am getting is:
>
> Microsoft (R) Program Maintenance Utility Version 7.10.3077
> Copyright (C) Microsoft Corporation. All rights reserved.
>

If you want to use Visual Studio .NET as your compiler you should build
your perl with that compiler. ActiveState perl was built with Visual
Studio 6 and that will lead to problems when you try to use Visual
Studio .NET with it (as you have just found out). You could download the
source to AS build 810 (perl 5.8.4) from the ActiveState site and build
with Visual Studio .NET. It's not difficult. Or you would probably find
that the latest source from CPAN (perl 5.8.5) also builds easily with
Visual Studio .NET.

Alternatively, if you want to stick with ActiveState-built perl, then
you should use Visual Studio 6 (MSVC++ 6.0) as your compiler.

There are possibly workarounds that enable you to use Visual Studio .NET
with ActiveState-built perl, but I don't know what they are (and have
little interest in learning of them :-)

Cheers,
Rob 

-- 
To reply by email u have to take out the u in kalinaubears.

Relevant Pages

  • Re: Converting From C to Perl
    ... >> generating C code and translating that into Perl sounds like too strange ... Inline::C just needs a C compiler. ... the bloat that is MS Visual Studio. ...
    (comp.lang.perl.misc)
  • Same problem building several modules on XP using Visual Studio .NET
    ... of this problem can be useful for several Windows Perl coders, ... I wanted to upgrade Tk (and install several new modules) on my system and I ... Typing mspdb71.dll from the command prompt (from another folder) invokes the ...
    (comp.lang.perl.misc)
  • Developing - a basic question
    ... I found a JRE available for java apps and stuff, which I know java a bit better now than other tools but I had a few basic questions so I can ... Can visual studio 2002 be used to develop on the pocket PC? ... I saw Java and Perl so far. ... I noticed there aren't any command line tools except some pretty expensive ones out there. ...
    (microsoft.public.pocketpc.developer)
  • Re: Problem when using NMAKE to build Perl on Windows
    ... 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, ... I know activestate uses the freely available Windows Server 2003 R2 Platform SDK compiler for their 64-bit build of ActivePerl. ...
    (comp.lang.perl.misc)
  • RE: [Info-ingres] Building DBD::Ingres for ActiveState Perl
    ... > It is possible to build the DBI using Active State's perl - however I ... > After testing and installing DBI I did the following within the ... > - nmake test ...
    (comp.databases.ingres)