Whether you use our pre-built PPM packages or choose to compile modules yourself, ActivePerl makes installing CPAN modules easier than ever. Installing Xcode from the Mac App Store or the Apple Developer site will install all the necessary tools and allow you to build most modules. Once GCC is installed, the cpan command will be able to build most modules. Consult your Linux distribution’s documentation for details. If not, the necessary tools are usually grouped into a package called build-essential or similar. On Linux, GCC and associated build tools are typically already installed. Using other make tools such as GNU make or nmake will not work. Make sure this directory is on your PATH (done by default by the ActivePerl installer). MinGW and dmake will be installed into C:\Perl\site\bin.To manually compile or test a module outside of the cpan shell, use dmake in the directory where the downloaded module code resides: perl Makefile.PL The CPAN shell will automatically download and install MinGW and dmake on first use, and then attempt to build the requested module: These days, ActivePerl on Windows is built using MinGW (a Windows port of GCC) and can automatically install the tools needed. Windowsīuilding binary Perl modules on Windows used to be a bit of a black art, requiring Microsoft Visual Studio and a lot of trial-and-error. If you run into trouble with a particular module that needs a custom build configuration, and we may be able to add it to PPM in the future. Building these types of modules will not be covered here. Some modules, particularly those which require other C libraries, will require additional steps. For most modules, this is a simple process, even on Windows. If a precompiled version of the module you are looking for does not exist in the PPM repository, you can attempt to compile it yourself. The ppm log command is a handy debugging tool to display the last couple of minutes from the PPM log file in case the connection to the repo still fails after setting the http_proxy variable: ppm log 5įor more information about firewalls and proxies, visit this FAQ. Only the standard http_proxy variable is used. This information was true for the old PPM3 client and is no longer correct. Many places on the net explain that the environment variables http_proxy_user and http_proxy_pass need to be set. If Internet access must go through a proxy server, then the http_proxy environment variable must be set to tell LWP how to get a connection.įor Windows, use: set in bash on Linux/Mac, use: export common error is to leave out the protocol prefix (" or " from the variable setting, in which case it will not work at all. PPM uses the LWP module to access the ActiveState package repository.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |