extutils::makemaker::faq.3

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

pure perl.  no make, no shell commands
.IP "\(bu" 8
easier to customize
.IP "\(bu" 8
cleaner internals
.IP "\(bu" 8
less cruft
.RE
.RS 4
.Sp
Module::Build is the official heir apparent to MakeMaker and we
encourage people to work on M::B rather than spending time adding features
to MakeMaker.
.RE
.Sh "Module Writing"
.IX Subsection "Module Writing"
.ie n .IP "How do I keep my $VERSION up to date without resetting it manually?" 4
.el .IP "How do I keep my \f(CW$VERSION\fR up to date without resetting it manually?" 4
.IX Item "How do I keep my $VERSION up to date without resetting it manually?"
Often you want to manually set the \f(CW$VERSION\fR in the main module
distribution because this is the version that everybody sees on \s-1CPAN\s0
and maybe you want to customize it a bit.  But for all the other
modules in your dist, \f(CW$VERSION\fR is really just bookkeeping and all that's
important is it goes up every time the module is changed.  Doing this
by hand is a pain and you often forget.
.Sp
Simplest way to do it automatically is to use your version control
system's revision number (you are using version control, right?).
.Sp
In \s-1CVS\s0, \s-1RCS\s0 and \s-1SVN\s0 you use \f(CW$Revision\fR$ (see the documentation of your
version control system for details).  Every time the file is checked
in the \f(CW$Revision\fR$ will be updated, updating your \f(CW$VERSION\fR.
.Sp
\&\s-1SVN\s0 uses a simple integer for \f(CW$Revision\fR$ so you can adapt it for your
\&\f(CW$VERSION\fR like so:
.Sp
.Vb 1
\&    ($VERSION) = q$Revision$ =~ /(\ed+)/;
.Ve
.Sp
In \s-1CVS\s0 and \s-1RCS\s0 version 1.9 is followed by 1.10.  Since \s-1CPAN\s0 compares
version numbers numerically we use a \fIsprintf()\fR to convert 1.9 to 1.009
and 1.10 to 1.010 which compare properly.
.Sp
.Vb 1
\&    $VERSION = sprintf "%d.%03d", q$Revision$ =~ /(\ed+)\e.(\ed+)/g;
.Ve
.Sp
If branches are involved (ie. \f(CW$Revision:\fR 1.5.3.4$) its a little more
complicated.
.Sp
.Vb 2
\&    # must be all on one line or MakeMaker will get confused.
\&    $VERSION = do { my @r = (q$Revision$ =~ /\ed+/g); sprintf "%d."."%03d" x $#r, @r };
.Ve
.Sp
In \s-1SVN\s0, \f(CW$Revision\fR$ should be the same for every file in the project so
they would all have the same \f(CW$VERSION\fR.  \s-1CVS\s0 and \s-1RCS\s0 have a different
\&\f(CW$Revision\fR$ per file so each file will have a differnt \f(CW$VERSION\fR.
Distributed version control systems, such as \s-1SVK\s0, may have a different
\&\f(CW$Revision\fR$ based on who checks out the file leading to a different \f(CW$VERSION\fR
on each machine!  Finally, some distributed version control systems, such
as darcs, have no concept of revision number at all.
.IP "What's this \fI\s-1META\s0.yml\fR thing and how did it get in my \fI\s-1MANIFEST\s0\fR?!" 4
.IX Item "What's this META.yml thing and how did it get in my MANIFEST?!"
\&\fI\s-1META\s0.yml\fR is a module meta-data file pioneered by Module::Build and
automatically generated as part of the 'distdir' target (and thus
\&'dist').  See \*(L"Module Meta-Data\*(R" in ExtUtils::MakeMaker.
.Sp
To shut off its generation, pass the \f(CW\*(C`NO_META\*(C'\fR flag to \f(CW\*(C`WriteMakefile()\*(C'\fR.
.IP "How do I delete everything not in my \fI\s-1MANIFEST\s0\fR?" 4
.IX Item "How do I delete everything not in my MANIFEST?"
Some folks are surpried that \f(CW\*(C`make distclean\*(C'\fR does not delete
everything not listed in their \s-1MANIFEST\s0 (thus making a clean
distribution) but only tells them what they need to delete.  This is
done because it is considered too dangerous.  While developing your
module you might write a new file, not add it to the \s-1MANIFEST\s0, then
run a \f(CW\*(C`distclean\*(C'\fR and be sad because your new work was deleted.
.Sp
If you really want to do this, you can use
\&\f(CW\*(C`ExtUtils::Manifest::manifind()\*(C'\fR to read the \s-1MANIFEST\s0 and File::Find
to delete the files.  But you have to be careful.  Here's a script to
do that.  Use at your own risk.  Have fun blowing holes in your foot.
.Sp
.Vb 1
\&    #!/usr/bin/perl \-w
\&    
\&    use strict;
\&    
\&    use File::Spec;
\&    use File::Find;
\&    use ExtUtils::Manifest qw(maniread);
\&    
\&    my %manifest = map  {( $_ => 1 )}
\&                   grep { File::Spec\->canonpath($_) }
\&                        keys %{ maniread() };
\&
\&    if( !keys %manifest ) {
\&        print "No files found in MANIFEST.  Stopping.\en";
\&        exit;
\&    }
\&    
\&    find({
\&          wanted   => sub {
\&              my $path = File::Spec\->canonpath($_);
\&    
\&              return unless \-f $path;
\&              return if exists $manifest{ $path };
\&    
\&              print "unlink $path\en";
\&              unlink $path;
\&          },
\&          no_chdir => 1
\&         },
\&         "."
\&    );
.Ve
.Sh "\s-1XS\s0"
.IX Subsection "XS"
.ie n .IP "How to I prevent ""object version X.XX does not match bootstrap parameter Y.YY"" errors?" 4
.el .IP "How to I prevent ``object version X.XX does not match bootstrap parameter Y.YY'' errors?" 4
.IX Item "How to I prevent object version X.XX does not match bootstrap parameter Y.YY errors?"
\&\s-1XS\s0 code is very sensitive to the module version number and will
complain if the version number in your Perl module doesn't match.  If
you change your module's version # without rerunning Makefile.PL the old
version number will remain in the Makefile causing the \s-1XS\s0 code to be built
with the wrong number.
.Sp
To avoid this, you can force the Makefile to be rebuilt whenever you
change the module containing the version number by adding this to your
\&\fIWriteMakefile()\fR arguments.
.Sp
.Vb 1
\&    depend => { \*(Aq$(FIRST_MAKEFILE)\*(Aq => \*(Aq$(VERSION_FROM)\*(Aq }
.Ve
.IP "How do I make two or more \s-1XS\s0 files coexist in the same directory?" 4
.IX Item "How do I make two or more XS files coexist in the same directory?"
Sometimes you need to have two and more \s-1XS\s0 files in the same package.
One way to go is to put them into separate directories, but sometimes
this is not the most suitable solution. The following technique allows
you to put two (and more) \s-1XS\s0 files in the same directory.
.Sp
Let's assume that we have a package \f(CW\*(C`Cool::Foo\*(C'\fR, which includes
\&\f(CW\*(C`Cool::Foo\*(C'\fR and \f(CW\*(C`Cool::Bar\*(C'\fR modules each having a separate \s-1XS\s0
file. First we use the following \fIMakefile.PL\fR:
.Sp
.Vb 1
\&  use ExtUtils::MakeMaker;
\&
\&  WriteMakefile(
\&      NAME              => \*(AqCool::Foo\*(Aq,
\&      VERSION_FROM      => \*(AqFoo.pm\*(Aq,
\&      OBJECT              => q/$(O_FILES)/,
\&      # ... other attrs ...
\&  );
.Ve
.Sp
Notice the \f(CW\*(C`OBJECT\*(C'\fR attribute. MakeMaker generates the following
variables in \fIMakefile\fR:
.Sp
.Vb 7
\&  # Handy lists of source code files:
\&  XS_FILES= Bar.xs \e
\&        Foo.xs
\&  C_FILES = Bar.c \e
\&        Foo.c
\&  O_FILES = Bar.o \e
\&        Foo.o
.Ve
.Sp
Therefore we can use the \f(CW\*(C`O_FILES\*(C'\fR variable to tell MakeMaker to use
these objects into the shared library.
.Sp
That's pretty much it. Now write \fIFoo.pm\fR and \fIFoo.xs\fR, \fIBar.pm\fR
and \fIBar.xs\fR, where \fIFoo.pm\fR bootstraps the shared library and
\&\fIBar.pm\fR simply loading \fIFoo.pm\fR.
.Sp
The only issue left is to how to bootstrap \fIBar.xs\fR. This is done
from \fIFoo.xs\fR:
.Sp
.Vb 1
\&  MODULE = Cool::Foo PACKAGE = Cool::Foo
\&
\&  BOOT:
\&  # boot the second XS file
\&  boot_Cool_\|_Bar(aTHX_ cv);
.Ve
.Sp
If you have more than two files, this is the place where you should
boot extra \s-1XS\s0 files from.
.Sp
The following four files sum up all the details discussed so far.
.Sp
.Vb 3
\&  Foo.pm:
\&  \-\-\-\-\-\-\-
\&  package Cool::Foo;
\&
\&  require DynaLoader;
\&
\&  our @ISA = qw(DynaLoader);
\&  our $VERSION = \*(Aq0.01\*(Aq;
\&  bootstrap Cool::Foo $VERSION;
\&
\&  1;
\&
\&  Bar.pm:
\&  \-\-\-\-\-\-\-
\&  package Cool::Bar;
\&
\&  use Cool::Foo; # bootstraps Bar.xs
\&
\&  1;
\&
\&  Foo.xs:
\&  \-\-\-\-\-\-\-
\&  #include "EXTERN.h"
\&  #include "perl.h"
\&  #include "XSUB.h"
\&
\&  MODULE = Cool::Foo  PACKAGE = Cool::Foo
\&
\&  BOOT:
\&  # boot the second XS file
\&  boot_Cool_\|_Bar(aTHX_ cv);
\&
\&  MODULE = Cool::Foo  PACKAGE = Cool::Foo  PREFIX = cool_foo_
\&
\&  void
\&  cool_foo_perl_rules()
\&
\&      CODE:
\&      fprintf(stderr, "Cool::Foo says: Perl Rules\en");
\&
\&  Bar.xs:
\&  \-\-\-\-\-\-\-
\&  #include "EXTERN.h"
\&  #include "perl.h"
\&  #include "XSUB.h"
\&
\&  MODULE = Cool::Bar  PACKAGE = Cool::Bar PREFIX = cool_bar_
\&
\&  void
\&  cool_bar_perl_rules()
\&
\&      CODE:
\&      fprintf(stderr, "Cool::Bar says: Perl Rules\en");
.Ve
.Sp
And of course a very basic test:
.Sp
.Vb 9
\&  t/cool.t:
\&  \-\-\-\-\-\-\-\-
\&  use Test;
\&  BEGIN { plan tests => 1 };
\&  use Cool::Foo;
\&  use Cool::Bar;
\&  Cool::Foo::perl_rules();
\&  Cool::Bar::perl_rules();
\&  ok 1;
.Ve
.Sp
This tip has been brought to you by Nick Ing-Simmons and Stas Bekman.
.SH "PATCHING"
.IX Header "PATCHING"
If you have a question you'd like to see added to the \s-1FAQ\s0 (whether or
not you have the answer) please send it to [e-mail].
.SH "AUTHOR"
.IX Header "AUTHOR"
The denizens of [e-mail].
.SH "SEE ALSO"
.IX Header "SEE ALSO"
ExtUtils::MakeMaker