extutils::makemaker.3

视频监控网络部分的协议ddns,的模块的实现代码,请大家大胆指正.

Defaults to \f(CW$Config\fR{installprefixexp} falling back to
\&\f(CW$Config\fR{installprefix}, \f(CW$Config\fR{prefixexp} or \f(CW$Config\fR{prefix} should
\&\f(CW$Config\fR{installprefixexp} not exist.
.Sp
Overridden by \s-1PREFIX\s0.
.IP "\s-1PERLRUN\s0" 2
.IX Item "PERLRUN"
Use this instead of $(\s-1PERL\s0) when you wish to run perl.  It will set up
extra necessary flags for you.
.IP "\s-1PERLRUNINST\s0" 2
.IX Item "PERLRUNINST"
Use this instead of $(\s-1PERL\s0) when you wish to run perl to work with
modules.  It will add things like \-I$(\s-1INST_ARCH\s0) and other necessary
flags so perl can see the modules you're about to install.
.IP "\s-1PERL_SRC\s0" 2
.IX Item "PERL_SRC"
Directory containing the Perl source code (use of this should be
avoided, it may be undefined)
.IP "\s-1PERM_RW\s0" 2
.IX Item "PERM_RW"
Desired permission for read/writable files. Defaults to \f(CW644\fR.
See also \*(L"perm_rw\*(R" in MM_Unix.
.IP "\s-1PERM_RWX\s0" 2
.IX Item "PERM_RWX"
Desired permission for executable files. Defaults to \f(CW755\fR.
See also \*(L"perm_rwx\*(R" in MM_Unix.
.IP "\s-1PL_FILES\s0" 2
.IX Item "PL_FILES"
MakeMaker can run programs to generate files for you at build time.
By default any file named *.PL (except Makefile.PL and Build.PL) in
the top level directory will be assumed to be a Perl program and run
passing its own basename in as an argument.  For example...
.Sp
.Vb 1
\&    perl foo.PL foo
.Ve
.Sp
This behavior can be overridden by supplying your own set of files to
search.  \s-1PL_FILES\s0 accepts a hash ref, the key being the file to run
and the value is passed in as the first argument when the \s-1PL\s0 file is run.
.Sp
.Vb 1
\&    PL_FILES => {\*(Aqbin/foobar.PL\*(Aq => \*(Aqbin/foobar\*(Aq}
.Ve
.Sp
Would run bin/foobar.PL like this:
.Sp
.Vb 1
\&    perl bin/foobar.PL bin/foobar
.Ve
.Sp
If multiple files from one program are desired an array ref can be used.
.Sp
.Vb 1
\&    PL_FILES => {\*(Aqbin/foobar.PL\*(Aq => [qw(bin/foobar1 bin/foobar2)]}
.Ve
.Sp
In this case the program will be run multiple times using each target file.
.Sp
.Vb 2
\&    perl bin/foobar.PL bin/foobar1
\&    perl bin/foobar.PL bin/foobar2
.Ve
.Sp
\&\s-1PL\s0 files are normally run \fBafter\fR pm_to_blib and include \s-1INST_LIB\s0 and
\&\s-1INST_ARCH\s0 in its \f(CW@INC\fR so the just built modules can be
accessed... unless the \s-1PL\s0 file is making a module (or anything else in
\&\s-1PM\s0) in which case it is run \fBbefore\fR pm_to_blib and does not include
\&\s-1INST_LIB\s0 and \s-1INST_ARCH\s0 in its \f(CW@INC\fR.  This apparently odd behavior
is there for backwards compatibility (and its somewhat \s-1DWIM\s0).
.IP "\s-1PM\s0" 2
.IX Item "PM"
Hashref of .pm files and *.pl files to be installed.  e.g.
.Sp
.Vb 1
\&  {\*(Aqname_of_file.pm\*(Aq => \*(Aq$(INST_LIBDIR)/install_as.pm\*(Aq}
.Ve
.Sp
By default this will include *.pm and *.pl and the files found in
the \s-1PMLIBDIRS\s0 directories.  Defining \s-1PM\s0 in the
Makefile.PL will override \s-1PMLIBDIRS\s0.
.IP "\s-1PMLIBDIRS\s0" 2
.IX Item "PMLIBDIRS"
Ref to array of subdirectories containing library files.  Defaults to
[ 'lib', $(\s-1BASEEXT\s0) ]. The directories will be scanned and \fIany\fR files
they contain will be installed in the corresponding location in the
library.  A \fIlibscan()\fR method can be used to alter the behaviour.
Defining \s-1PM\s0 in the Makefile.PL will override \s-1PMLIBDIRS\s0.
.Sp
(Where \s-1BASEEXT\s0 is the last component of \s-1NAME\s0.)
.IP "\s-1PM_FILTER\s0" 2
.IX Item "PM_FILTER"
A filter program, in the traditional Unix sense (input from stdin, output
to stdout) that is passed on each .pm file during the build (in the
\&\fIpm_to_blib()\fR phase).  It is empty by default, meaning no filtering is done.
.Sp
Great care is necessary when defining the command if quoting needs to be
done.  For instance, you would need to say:
.Sp
.Vb 1
\&  {\*(AqPM_FILTER\*(Aq => \*(Aqgrep \-v \e\e"^\e\e#\e\e"\*(Aq}
.Ve
.Sp
to remove all the leading comments on the fly during the build.  The
extra \e\e are necessary, unfortunately, because this variable is interpolated
within the context of a Perl program built on the command line, and double
quotes are what is used with the \-e switch to build that command line.  The
# is escaped for the Makefile, since what is going to be generated will then
be:
.Sp
.Vb 1
\&  PM_FILTER = grep \-v \e"^\e#\e"
.Ve
.Sp
Without the \e\e before the #, we'd have the start of a Makefile comment,
and the macro would be incorrectly defined.
.IP "\s-1POLLUTE\s0" 2
.IX Item "POLLUTE"
Release 5.005 grandfathered old global symbol names by providing preprocessor
macros for extension source compatibility.  As of release 5.6, these
preprocessor definitions are not available by default.  The \s-1POLLUTE\s0 flag
specifies that the old names should still be defined:
.Sp
.Vb 1
\&  perl Makefile.PL POLLUTE=1
.Ve
.Sp
Please inform the module author if this is necessary to successfully install
a module under 5.6 or later.
.IP "\s-1PPM_INSTALL_EXEC\s0" 2
.IX Item "PPM_INSTALL_EXEC"
Name of the executable used to run \f(CW\*(C`PPM_INSTALL_SCRIPT\*(C'\fR below. (e.g. perl)
.IP "\s-1PPM_INSTALL_SCRIPT\s0" 2
.IX Item "PPM_INSTALL_SCRIPT"
Name of the script that gets executed by the Perl Package Manager after
the installation of a package.
.IP "\s-1PREFIX\s0" 2
.IX Item "PREFIX"
This overrides all the default install locations.  Man pages,
libraries, scripts, etc...  MakeMaker will try to make an educated
guess about where to place things under the new \s-1PREFIX\s0 based on your
Config defaults.  Failing that, it will fall back to a structure
which should be sensible for your platform.
.Sp
If you specify \s-1LIB\s0 or any INSTALL* variables they will not be effected
by the \s-1PREFIX\s0.
.IP "\s-1PREREQ_FATAL\s0" 2
.IX Item "PREREQ_FATAL"
Bool. If this parameter is true, failing to have the required modules
(or the right versions thereof) will be fatal. \f(CW\*(C`perl Makefile.PL\*(C'\fR
will \f(CW\*(C`die\*(C'\fR instead of simply informing the user of the missing dependencies.
.Sp
It is \fIextremely\fR rare to have to use \f(CW\*(C`PREREQ_FATAL\*(C'\fR. Its use by module
authors is \fIstrongly discouraged\fR and should never be used lightly.
Module installation tools have ways of resolving umet dependencies but
to do that they need a \fIMakefile\fR.  Using \f(CW\*(C`PREREQ_FATAL\*(C'\fR breaks this.
That's bad.
.Sp
The only situation where it is appropriate is when you have
dependencies that are indispensible to actually \fIwrite\fR a
\&\fIMakefile\fR. For example, MakeMaker's \fIMakefile.PL\fR needs File::Spec.
If its not available it cannot write the \fIMakefile\fR.
.Sp
Note: see Test::Harness for a shortcut for stopping tests early
if you are missing dependencies and are afraid that users might
use your module with an incomplete environment.
.IP "\s-1PREREQ_PM\s0" 2
.IX Item "PREREQ_PM"
Hashref: Names of modules that need to be available to run this
extension (e.g. Fcntl for SDBM_File) are the keys of the hash and the
desired version is the value. If the required version number is 0, we
only check if any version is installed already.
.IP "\s-1PREREQ_PRINT\s0" 2
.IX Item "PREREQ_PRINT"
Bool.  If this parameter is true, the prerequisites will be printed to
stdout and MakeMaker will exit.  The output format is an evalable hash
ref.
.Sp
\&\f(CW$PREREQ_PM\fR = {
               'A::B' => Vers1,
               'C::D' => Vers2,
               ...
             };
.IP "\s-1PRINT_PREREQ\s0" 2
.IX Item "PRINT_PREREQ"
RedHatism for \f(CW\*(C`PREREQ_PRINT\*(C'\fR.  The output format is different, though:
.Sp
.Vb 1
\&    perl(A::B)>=Vers1 perl(C::D)>=Vers2 ...
.Ve
.IP "\s-1SITEPREFIX\s0" 2
.IX Item "SITEPREFIX"
Like \s-1PERLPREFIX\s0, but only for the site install locations.
.Sp
Defaults to \f(CW$Config\fR{siteprefixexp}.  Perls prior to 5.6.0 didn't have
an explicit siteprefix in the Config.  In those cases
\&\f(CW$Config\fR{installprefix} will be used.
.Sp
Overridable by \s-1PREFIX\s0
.IP "\s-1SIGN\s0" 2
.IX Item "SIGN"
When true, perform the generation and addition to the \s-1MANIFEST\s0 of the
\&\s-1SIGNATURE\s0 file in the distdir during 'make distdir', via 'cpansign
\&\-s'.
.Sp
Note that you need to install the Module::Signature module to
perform this operation.
.Sp
Defaults to false.
.IP "\s-1SKIP\s0" 2
.IX Item "SKIP"
Arrayref. E.g. [qw(name1 name2)] skip (do not write) sections of the
Makefile. Caution! Do not use the \s-1SKIP\s0 attribute for the negligible
speedup. It may seriously damage the resulting Makefile. Only use it
if you really need it.
.IP "\s-1TYPEMAPS\s0" 2
.IX Item "TYPEMAPS"
Ref to array of typemap file names.  Use this when the typemaps are
in some directory other than the current directory or when they are
not named \fBtypemap\fR.  The last typemap in the list takes
precedence.  A typemap in the current directory has highest
precedence, even if it isn't listed in \s-1TYPEMAPS\s0.  The default system
typemap has lowest precedence.
.IP "\s-1VENDORPREFIX\s0" 2
.IX Item "VENDORPREFIX"
Like \s-1PERLPREFIX\s0, but only for the vendor install locations.
.Sp
Defaults to \f(CW$Config\fR{vendorprefixexp}.
.Sp
Overridable by \s-1PREFIX\s0
.IP "\s-1VERBINST\s0" 2
.IX Item "VERBINST"
If true, make install will be verbose
.IP "\s-1VERSION\s0" 2
.IX Item "VERSION"
Your version number for distributing the package.  This defaults to
0.1.
.IP "\s-1VERSION_FROM\s0" 2
.IX Item "VERSION_FROM"
Instead of specifying the \s-1VERSION\s0 in the Makefile.PL you can let
MakeMaker parse a file to determine the version number. The parsing
routine requires that the file named by \s-1VERSION_FROM\s0 contains one
single line to compute the version number. The first line in the file
that contains the regular expression
.Sp
.Vb 1
\&    /([\e$*])(([\ew\e:\e\*(Aq]*)\ebVERSION)\eb.*\e=/
.Ve
.Sp
will be evaluated with \fIeval()\fR and the value of the named variable
\&\fBafter\fR the \fIeval()\fR will be assigned to the \s-1VERSION\s0 attribute of the
MakeMaker object. The following lines will be parsed o.k.:
.Sp
.Vb 6
\&    $VERSION = \*(Aq1.00\*(Aq;
\&    *VERSION = \e\*(Aq1.01\*(Aq;
\&    ($VERSION) = q$Revision: 41145 $ =~ /(\ed+)/g;
\&    $FOO::VERSION = \*(Aq1.10\*(Aq;
\&    *FOO::VERSION = \e\*(Aq1.11\*(Aq;
\&    our $VERSION = 1.2.3;       # new for perl5.6.0
.Ve
.Sp
but these will fail:
.Sp
.Vb 3
\&    my $VERSION = \*(Aq1.01\*(Aq;
\&    local $VERSION = \*(Aq1.02\*(Aq;
\&    local $FOO::VERSION = \*(Aq1.30\*(Aq;
.Ve
.Sp
version will be loaded, if available, so this will work.
.Sp
.Vb 1
\&    our $VERSION = qv(1.2.3);   # version.pm will be loaded if available
.Ve
.Sp
Its up to you to declare a dependency on \f(CW\*(C`version\*(C'\fR.  Also note that this
feature was introduced in MakeMaker 6.35.  Earlier versions of MakeMaker
require this:
.Sp
.Vb 2
\&    # All on one line
\&    use version; our $VERSION = qv(1.2.3);
.Ve
.Sp
(Putting \f(CW\*(C`my\*(C'\fR or \f(CW\*(C`local\*(C'\fR on the preceding line will work o.k.)
.Sp
The file named in \s-1VERSION_FROM\s0 is not added as a dependency to
Makefile. This is not really correct, but it would be a major pain
during development to have to rewrite the Makefile for any smallish
change in that file. If you want to make sure that the Makefile
contains the correct \s-1VERSION\s0 macro after any change of the file, you
would have to do something like
.Sp
.Vb 1
\&    depend => { Makefile => \*(Aq$(VERSION_FROM)\*(Aq }
.Ve
.Sp
See attribute \f(CW\*(C`depend\*(C'\fR below.
.IP "\s-1VERSION_SYM\s0" 2
.IX Item "VERSION_SYM"
A sanitized \s-1VERSION\s0 with . replaced by _.  For places where . has
special meaning (some filesystems, \s-1RCS\s0 labels, etc...)
.IP "\s-1XS\s0" 2
.IX Item "XS"
Hashref of .xs files. MakeMaker will default this.  e.g.
.Sp
.Vb 1
\&  {\*(Aqname_of_file.xs\*(Aq => \*(Aqname_of_file.c\*(Aq}
.Ve
.Sp
The .c files will automatically be included in the list of files
deleted by a make clean.
.IP "\s-1XSOPT\s0" 2
.IX Item "XSOPT"
String of options to pass to xsubpp.  This might include \f(CW\*(C`\-C++\*(C'\fR or
\&\f(CW\*(C`\-extern\*(C'\fR.  Do not include typemaps here; the \s-1TYPEMAP\s0 parameter exists for
that purpose.
.IP "\s-1XSPROTOARG\s0" 2
.IX Item "XSPROTOARG"
May be set to an empty string, which is identical to \f(CW\*(C`\-prototypes\*(C'\fR, or
\&\f(CW\*(C`\-noprototypes\*(C'\fR. See the xsubpp documentation for details. MakeMaker
defaults to the empty string.
.IP "\s-1XS_VERSION\s0" 2
.IX Item "XS_VERSION"
Your version number for the .xs file of this package.  This defaults
to the value of the \s-1VERSION\s0 attribute.
.Sh "Additional lowercase attributes"
.IX Subsection "Additional lowercase attributes"
can be used to pass parameters to the methods which implement that
part of the Makefile.  Parameters are specified as a hash ref but are
passed to the method as a hash.
.IP "clean" 2
.IX Item "clean"
.Vb 1
\&  {FILES => "*.xyz foo"}
.Ve
.IP "depend" 2
.IX Item "depend"
.Vb 1