Re^3: New Perl on server

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

Comment on Re^3: New Perl on server

Replies are listed 'Best First'.
Re^4: New Perl on server by jdtoronto (Prior) on Jul 27, 2006 at 00:40 UTC
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]
Re^5: New Perl on server by Asim (Hermit) on Jul 27, 2006 at 15:25 UTC
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. Which was, indeed, the point of what I posted. I've also done the VS compiles for a few XS-based modules, and have similar opinions. Thank you. :) ----Asim, known to some as Woodrow.	[reply]