in reply to New Perl on server

As said by duc, ActiveState's port works well. It also has a reasonable set of modules for Windows. I've not used Indigo Perl, PXPerl, or any of the other Windows ports of Perl listed in http://www.cpan.org/ports/#win32.

Do not base the decision of which version of Perl to installed based on the number of modules. Modules can always be added later, using CPAN.

You could, of course, compile from source. Nonetheless, I think your best choice would be to use ActiveState's port. Just don't install a beta version.

emc

Login incorrect.
Only perfect spellers may
enter this system.

Jason Axley

Replies are listed 'Best First'.
Re^2: New Perl on server
by Asim (Hermit) on Jul 26, 2006 at 18:17 UTC
    Do not base the decision of which version of Perl to installed based on the number of modules. Modules can always be added later, using CPAN.

    Save that modules that need a C compiler cannot always be added via the CPAN module/program in Windows, due to the lack of said compiler.

    ----Asim, known to some as Woodrow.

[reply]
      Sheesh!

      Whadda you want for free! Everything? Of course, it is all free!

      Activestate's distribution is usually compiled with VC++6 which can be had for the simple cost of just a little bandwidth from Microsoft.

      jdtoronto

[reply]

      I realize that not all Windows boxes have C compilers. Conversely, one could reasonably expect a developer to be able to find and install one of Microsoft's command-line C++ compilers (as jdtoronto mentioned, they're free), gcc (also free), or spend a few dollars (less than $100 USD) to install Visual Studio C++.

      emc

      Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read.

      Groucho Marx
[reply]
        Bearing in mind, of course, that the compiler used for building modules must be the same as the one used to build the Perl. So if you are using ACtiveStae you would need (V)C++ 6, or if you use Vanilla/Strawberry Perl you would need gcc.

        I have one application which runs on its own Windows box that uses a couple of big ugly XS modules, we build the Perl locally and then modules build easilly and we have no issues. However, it is also fair to say (for the OP's benefit) that if a module isn't available as a binary build from any of the main PPM respositories, then it is a brave man who embarks on building it without serious malice of forethought, and commitment of time and effort.

        jdtoronto

[reply]

In Section Seekers of Perl Wisdom