|
Re: strawberry vs activestate perl
by syphilis (Archbishop) on May 25, 2009 at 08:20 UTC
|
Strawberry uses CPAN and activestate uses ppm
Nope - both CPAN and PPM are available on both StrawberryPerl and ActivePerl.
The main difference is that StrawberryPerl comes with the MinGW compiler and dmake, whereas ActivePerl comes with no compiler and make utility at all. However, installing MinGW and dmake for use with ActivePerl is very easy - it's just a matter of running ppm install MinGW.
As to which is better ... they're both very good.
Cheers,
Rob | [reply]
[d/l] |
|
|
As an alternative:
I used nmake. Depending on your IDE/platform you might have to download nmake from M$. I recall it used to be included in Visual Studio.
You also need a C-compiler of course, see free compilers for some options. I used the bloodshed IDE (the Mingw compiler goes with that if I recall correctly).
| [reply] |
|
|
Hmmm,
I recall spending long, arduous hours attempting to use nmake ... but could never get the perl Makefile.PL step to generate a make script that nmake didn't baulk at!!
You'd never imagine the pleasure and indeed relief, I felt when some kind soul on this here site pointed me in the direction of Strawberry - an act for which I shall be eternally grateful :-D
A user level that continues to overstate my experience :-))
| [reply]
[d/l] |
Re: strawberry vs activestate perl
by Corion (Patriarch) on May 25, 2009 at 07:52 UTC
|
Strawberry Perl also includes a preconfigured C compiler and make tool, so you can build XS components directly. Both distributions come with various precompiled modules, and you can even install PPMs into Strawberry Perl or compile PPMs with Strawberry Perl for ActiveState Perl. If you need commercial support, ActiveState Perl is better, because there is an office that will send you an invoice.
| [reply]
[d/l] |
|
|
If you need commercial support, ActiveState Perl is better
You wish;-)
Fair enough, I worked a few years with ActiveState Perl on Windows and it has served me well. Meaning as long as there is a ppm that installs correctly... In my experience ActiveState is not too responsive in case of problems, e.g. if you issue a bug report you're likely to hear nothing ever after.
| [reply] |
|
|
Ah - but commercial support is important for a different reason (you're aware of this, but others might not be). In certain places, you are not allowed to introduced "unsupported" software. And support necessarily means getting an invoice, and budgeting for that invoice. That's the advantage ActiveState has over Strawberry. How responsive AS are with their support I don't know, but I'm not the one paying our AS contract or opening tickets with them :).
| [reply] |
Re: strawberry vs activestate perl
by grinder (Bishop) on May 25, 2009 at 08:56 UTC
|
I had trouble getting GD to install on Strawberry. As in "I gave up". Other than that I am very fond of Strawberry.
I realise that it should be fairly easy to download the GD C library source and compile it, and then use it to build the XS component of GD. I fiddled around for a while and since I was pressed for time, I just installed the GD.ppm module for Activestate and generated the graphs I needed to generate.
In other words, AS and Strawberry coexist peacefully on the same machine, so you can always use both. Executing a particular perl binary by specifying its full path is sufficient for it to locate the libraries that belong to it. The question comes down to which one you wish to use by default when you run 'perl' from a DOS box. That just depends on your PATH setting.
• another intruder with the mooring in the heart of the Perl
| [reply] |
|
|
I just installed the GD.ppm module for Activestate
You didn't say whether you 'ppm install'ed it into Strawberry Perl or ActivePerl - you should be able to do either.
Cheers,
Rob
| [reply] |
Re: strawberry vs activestate perl
by Burak (Chaplain) on May 26, 2009 at 21:13 UTC
|
Strawberry also misses all the ActiveState binaries:
- PerlIS - ISAPI extension for IIS
- PerlEx - Although no longer supported/developed, this the persistent environment under IIS
- PerlScript - ActiveX Engine that runs on wherever VBS & JScript runs like the (Classic) ASP, WSH, etc
| [reply] |
Re: strawberry vs activestate perl
by ikegami (Patriarch) on May 25, 2009 at 17:02 UTC
|
Strawberry Perl's installation directory is hardcoded (so you can only have one version installed), but you can install to any directory with ActivePerl.
| [reply] |
|
|
Strawberry Perl's installation directory is hardcoded
They've recently made available alternative distro's that include a zip package which can, I believe, be unpacked to any location.
Cheers,
Rob
| [reply] |
