in reply to Re^3: "Lag" of modules in ActiveState ?
in thread "Lag" of modules in ActiveState ?

The procedure to install most modules is

perl Makefile.PL make make test make install

These or alternate instructions are usually present in the README file in the distribution. It's no exception here.

Note that if a compiler is required (as is the case for this distribution), it needs to be compatible with the one used to build Perl. Since the OP is using an ActiveState perl distribution, he'll need to use a compiler compatible with the one ActiveState used, namely Visual Studio 6. Note that Visual Studio's make tool is called nmake.

Replies are listed 'Best First'.
Re^5: "Lag" of modules in ActiveState ?
by syphilis (Archbishop) on Nov 06, 2008 at 08:28 UTC
    use a compiler compatible with the one ActiveState used, namely Visual Studio 6

    Hmmm ... not entirely sure that I understand the point correctly. You can use the MinGW compiler with ActivePerl to build Win32-OLE-0.1709. You might also be able to use Visual Studio 7, Visual Studio 8, and Visual Studio 9 - I haven't tested any of those, however.

    Note that Visual Studio's make tool is called nmake

    That's correct - but you can also use dmake with ActivePerl (and with Visual Studio, too, I think).

    There's an elaboration at Compiling C/C++ based Modules under ActiveState using MinGW for anyone interested

    Cheers,
    Rob
      MinGW is compatible, yes. I am under the impression that other versions of VS aren't. Correct me if I'm wrong. Confirmation if I'm right would also be appreciated.
        MinGW is compatible, yes

        Yes - that's what I was unsure about. On first reading I thought you were saying that Visual Studio 6 must be used (which would be incorrect). You weren't saying that (you were correct :-)

        As regards the other Visual Studio compilers, my hunch is that VC 7.0 (at least) would build Win32::OLE for ActivePerl, but I haven't checked.

        Cheers,
        Rob