![]() ![]() The official repository is hosted by ActiveState. I think Strawberry Perl also comes with a few modules that let you install PPMs (Perl Package Manager files).ĪctivePerl installs modules using its own format called PPM (Perl Package Manager). The MinGW distribution comes with gcc, make, ld and other tools to help you build modules. Strawberry Perl also comes with MinGW which means that Strawberry Perl can use quite a few XS modules directly from CPAN without any modification. When things are added to CPAN, you have immediate access to them. Strawberry Perl uses CPAN, which means that you are up to date as far as modules are concerned. This would solve one important (IMHO) disadvantage of Strawberry Perl (compared to ActivePerl). And maybe one can choose the directory where Strawberry Perl gets installed (I couldn't).īTW: for compiling your own Inline or XS stuff, just install the MinGW compiler by ppm (I didn't do that, but it looks interesting).Īddendum: after reading the comment below, I checked Strawberry Perl again and it's now possible to change the installation directory, which is a denoted feature of the 5.12.0 release (which is the actual version). I think I dropped Strawberry Perl after trying to install DBI + DBD::mysql on Windows 7 (which is a no brainer in ActivePerl just click on the ppms and choose install).īut maybe that's solved by now. Even for the Windows version of the Apache HTTP server, there is a precompiled mod_perl (2.0.4) ppm available which will (did for me) work out of the box with ActivePerl 5. This was for me, in the long run, a much better (and more robust) choice. The PPM installer included in ActivePerl allows you to add alternative PPM repositories which will give you access to almost all useful Perl modules available on CPAN - but prepared and tested for Windows. If you do not have the required privileges you should contact your Administrator.After having used both for years, I'd say, for me at least, ActivePerl is a much more convenient choice. In order to perform all of the above steps, you will need to have Administrative privileges on the target machine. Once the installation has completed successfully, the above actions may be undone although restoring the environment variables or the registry values may interfere with the proper operation of your new ActivePerl installation. This can be accomplished from the command prompt using the following command: Realizing that this is not always possible, you can follow these steps to ensure the other installations will not interfere. The sure-fire solution is to make absolutely certain that no other installations of Perl are on the target machine. We have determined that some of these problems are due to other installations of Perl that may be pointed at by something in the environment. The first thing to note is that you CANNOT install ActivePerl 5.16 over an older version of ActivePerl based on 5.14, 5.12, 5.10, 5.8, 5.6 or 5.005, such as build 1204 or any other 1200, 1000, 800, 600 or 500 series build. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |