.\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
.\" ========================================================================
.de Sh \" Subsection heading
.de Sp \" Vertical space (when we can't use .PP)
.de Vb \" Begin verbatim text
.de Ve \" End verbatim text
.\" Set up some character translations and predefined strings. \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote. | will give a
.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
. tm Index:\\$1\t\\n%\t"\\$2"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. \" simple accents for nroff and troff
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
. \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
. \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
. \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
.\" ========================================================================
.IX Title "ExtUtils::MakeMaker::FAQ 3"
.TH ExtUtils::MakeMaker::FAQ 3 "2003-08-18" "perl v5.8.0" "User Contributed Perl Documentation"
ExtUtils::MakeMaker::FAQ \- Frequently Asked Questions About MakeMaker
FAQs, tricks and tips for \f(CW\*(C`ExtUtils::MakeMaker\*(C'\fR.
.Sh "Module Installation"
.IX Subsection "Module Installation"
.IP "How do I keep from installing man pages?" 4
.IX Item "How do I keep from installing man pages?"
Recent versions of MakeMaker will only install man pages on Unix like
For an individual module:
\& perl Makefile.PL INSTALLMAN1DIR=none INSTALLMAN3DIR=none
If you want to suppress man page installation for all modules you have
to reconfigure Perl and tell it 'none' when it asks where to install
.IP "How do I use a module without installing it?" 4
.IX Item "How do I use a module without installing it?"
Two ways. One is to build the module normally...
\&...and then set the \s-1PERL5LIB\s0 environment variable to point at the
blib/lib and blib/arch directories.
The other is to install the module in a temporary location.
\& perl Makefile.PL PREFIX=/tmp LIB=/tmp/lib/perl
And then set \s-1PERL5LIB\s0 to /tmp/lib/perl. This works well when you have
multiple modules to work with. It also ensures that the module goes
through its full installation process which may modify it.
.Sh "Philosophy and History"
.IX Subsection "Philosophy and History"
.IP "Why not just use <insert other build config tool here>?" 4
.IX Item "Why not just use <insert other build config tool here>?"
Why did MakeMaker reinvent the build configuration wheel? Why not
just use autoconf or automake or ppm or Ant or ...
There are many reasons, but the major one is cross-platform
Perl is one of the most ported pieces of software ever. It works on
operating systems I've never even heard of (see perlport for details).
It needs a build tool that can work on all those platforms and with
any wacky C compilers and linkers they might have.
No such build tool exists. Even make itself has wildly different
dialects. So we have to build our own.
.IP "What is Module::Build and how does it relate to MakeMaker?" 4
.IX Item "What is Module::Build and how does it relate to MakeMaker?"
Module::Build is a project by Ken Williams to supplant MakeMaker.
Its primary advantages are:
.IP "\(bu pure perl. no make, no shell commands" 8
.IX Item "pure perl. no make, no shell commands"
.IP "\(bu easier to customize" 8
.IX Item "easier to customize"
.IP "\(bu cleaner internals" 8
.IX Item "cleaner internals"
Module::Build is the official heir apparent to MakeMaker and we
encourage people to work on M::B rather than spending time adding features
.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.
Simplest way to do it automatically is to use your version control
system's revision number (you are using version control, right?).
In \s-1CVS\s0 and \s-1RCS\s0 you use $\&Revision$ writing it like so:
\& $VERSION = sprintf "%d.%03d", q$Revision: 1.10 $ =~ /(\ed+)/g;
Every time the file is checked in the $\&Revision$ will be updated,
updating your \f(CW$VERSION\fR.
In \s-1CVS\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.
If branches are involved (ie. $\&Revision: 1.5.3.4) its a little more
\& # must be all on one line or MakeMaker will get confused.
\& $VERSION = do { my @r = (q$Revision: 1.10 $ =~ /\ed+/g); sprintf "%d."."%03d" x $#r, @r };
.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.
To shut off its generation, pass the \f(CW\*(C`NO_META\*(C'\fR flag to \f(CW\*(C`WriteMakefile()\*(C'\fR.
.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 reruning Makefile.PL the old
version number will remain in the Makefile causing the \s-1XS\s0 code to be built
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.
\& depend => { '$(FIRST_MAKEFILE)' => '$(VERSION_FROM)' }
.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.
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:
\& use ExtUtils::MakeMaker;
\& VERSION_FROM => 'Foo.pm',
\& OBJECT => q/$(O_FILES)/,
Notice the \f(CW\*(C`OBJECT\*(C'\fR attribute. MakeMaker generates the following
variables in \fIMakefile\fR:
\& # Handy lists of source code files:
Therefore we can use the \f(CW\*(C`O_FILES\*(C'\fR variable to tell MakeMaker to use
these objects into the shared library.
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.
The only issue left is to how to bootstrap \fIBar.xs\fR. This is done
\& MODULE = Cool::Foo PACKAGE = Cool::Foo
\& # boot the second XS file
\& boot_Cool__Bar(aTHX_ cv);
If you have more than two files, this is the place where you should
boot extra \s-1XS\s0 files from.
The following four files sum up all the details discussed so far.
\& our @ISA = qw(DynaLoader);
\& our $VERSION = '0.01';
\& bootstrap Cool::Foo $VERSION;
\& use Cool::Foo; # bootstraps Bar.xs
\& MODULE = Cool::Foo PACKAGE = Cool::Foo
\& # boot the second XS file
\& boot_Cool__Bar(aTHX_ cv);
\& MODULE = Cool::Foo PACKAGE = Cool::Foo PREFIX = cool_foo_
\& fprintf(stderr, "Cool::Foo says: Perl Rules\en");
\& MODULE = Cool::Bar PACKAGE = Cool::Bar PREFIX = cool_bar_
\& fprintf(stderr, "Cool::Bar says: Perl Rules\en");
And of course a very basic test:
\& BEGIN { plan tests => 1 };
\& Cool::Foo::perl_rules();
\& Cool::Bar::perl_rules();
This tip has been brought to you by Nick Ing-Simmons and Stas Bekman.
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 makemaker@perl.org.
The denizens of makemaker@perl.org.
projects / OpenSPARC-T2-DV / blob