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

That won't work because the module has a compiled component. You'll get the following error message: 
Can't locate loadable object for module Win32::OLE in @INC

[download]

Replies are listed 'Best First'.
Re^3: "Lag" of modules in ActiveState ?
by pobocks (Chaplain) on Nov 05, 2008 at 23:25 UTC
    Huh. Is there any way to get around that? What process does the CPAN shell do when installing the module?
    for(split(" ","tsuJ rehtonA lreP rekcaH")){print reverse . " "}print "\b.\n";
[reply]
[d/l]

      The procedure to install most modules is 

      perl Makefile.PL
make
make test
make install

      [download]

      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.

[reply]
[d/l]
[select]
        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
[reply]

In Section Seekers of Perl Wisdom