There are two widely available environmental flavors: -. Perl is a modern programming language and mostly being used in scripting and writing applications. It's environment setup in MS Windows for 32 as well as 64 bit can be done by choosing your suited environment like ActiveState and Strawberry. Strawberry is the open source, and facilitate an easy install of modules from CPAN. August Anil Kumar General Comments 0.
If there are no binhtml or libhtml installation targets defined no action is taken for HTML documents. This is just like the install action, but it won't actually do anything, it will just report what it would have done if you had actually run the install action.
This action will simply print out a message that is meant to help you use the build process. It will show you a list of available build actions too. With an optional argument specifying an action name e. Build help test , the 'help' action will show you any POD documentation it can find for that action. The HTML documentation will only be installed if the install paths can be determined from values in Config.
If you want the installation process to look around in INC for other versions of the stuff you're installing and try to delete it, you can use the uninst parameter, which tells ExtUtils::Install to do so:. This can be a good idea, as it helps prevent multiple versions of a module from being present on your system, which can be a confusing situation indeed.
You will be prompted whether to install optional dependencies. It must be a shell command that takes a list of modules to install as arguments e. If the program part is a relative path e. This is an action intended for use by module authors, not people installing modules. SKIP should contain a bunch of regular expressions, one per line. SKIP starting point, you can add your own stuff to it:.
See the "distcheck" and "skipcheck" actions if you want to find out what the manifest action would do, without actually doing anything. SKIP file if one does not already exist. The man pages will only be installed if the install paths can be determined from values in Config.
You can also supply or override install paths by specifying there values on the command line with the bindoc and libdoc installation targets. This action takes an optional argument codebase which is used in the generated PPD file to specify the usually relative URL of the distribution. By default, this value is the distribution name without any path information. This action also invokes the ppd action, so it can accept the same codebase argument described under that action.
This action prints out a Perl data structure of all prerequisites and the versions required. The output can be loaded again using eval. This can be useful for external tools that wish to query a Build script for prerequisites. This action prints out a list of all prerequisites, the versions required, and the versions actually installed.
This can be useful for reviewing the configuration of your system prior to a build, or when compiling data to send for a bug report. This action is identical to the install action. If you run the realclean action, you are essentially starting over, so you will have to re-create the Build script again. This can be used to verify that a certain installed distribution still works, or to see whether newer versions of a distribution still pass the old regression tests, and so on.
SKIP file See "manifest" for details. Tests can be defined in the standard places: a file called test. If you want tests to be 'verbose', i. In addition, if a file called visual. This is a good place to put speed tests or other tests that don't use the Test::Harness format for output. This is especially useful in development, when you only want to run a single test to see whether you've squashed a certain bug yet:.
Runs the test action using Devel::Cover , generating a code-coverage report showing which parts of the code were actually exercised during the tests. This checks all the files described in the docs action and produces Test::Harness -style output. If you are a module author, this is useful to run before creating a new release. This checks the pod coverage of the distribution and produces Test::Harness -style output. If you have the only. This means that you can have several versions of the same module installed and use a specific one like this:.
To override the default installation libraries in only::config , specify the versionlib parameter when you run the Build. PL script:. To override which version the module is installed as, specify the version parameter when you run the Build.
The following options can be used during any invocation of Build. PL or the Build script, during any action. For information on other options specific to an action, see the documentation for the respective action. NOTE: There is some preliminary support for options to use the more familiar long option style.
Most options can be preceded with the -- long option prefix, and the underscores changed to dashes e. Additionally, the argument to boolean options is optional, and boolean options can be negated by prefixing them with no or no- e. Display extra information about the Build on output.
See installdeps for more details. This option can be set to false to prevent the custom resource file from being loaded. Suppresses the check upon startup that the version of Module::Build we're now running under is the same version that was initially invoked when building the distribution i.
PL script was first run. As of 0. If it's not found there, it will look in the. If the file exists, the options specified there will be used as defaults, as if they were typed on the command line. The defaults can be overridden by specifying new values on the command line. The action name must come at the beginning of the line, followed by any amount of whitespace and then the options.
Options are given the same as they would be on the command line. Also , many times you may not be able to use PPM tool to install modules , because of you being under - privileged user in Windows machine. In all such cases , if you need to install a module , you should be able to install it manually , as discussed below. If there is zip or tar file inside , then unzip it. This needs to be maintained when placing the.
This file is a help file describing the functions available in corresponding. Please note that every package may not have autosplit. In other words , autosplit. If it is not available there , then there is no need to put it. For example , the entry will be like this in. This is useful, especially when one is not able to install Perl module using PPM tool. Required Modules none specified.
0コメント