extutils::mkbootstrap(3perl) [debian man page]

ExtUtils::Mkbootstrap(3perl)				 Perl Programmers Reference Guide			      ExtUtils::Mkbootstrap(3perl)

NAME

       ExtUtils::Mkbootstrap - make a bootstrap file for use by DynaLoader

SYNOPSIS

       "Mkbootstrap"

DESCRIPTION

       Mkbootstrap typically gets called from an extension Makefile.

       There is no "*.bs" file supplied with the extension. Instead, there may be a *_BS file which has code for the special cases, like posix for
       berkeley db on the NeXT.

       This file will get parsed, and produce a maybe empty @DynaLoader::dl_resolve_using array for the current architecture.  That will be
       extended by $BSLOADLIBS, which was computed by ExtUtils::Liblist::ext(). If this array still is empty, we do nothing, else we write a .bs
       file with an @DynaLoader::dl_resolve_using array.

       The *_BS file can put some code into the generated "*.bs" file by placing it in $bscode. This is a handy 'escape' mechanism that may prove
       useful in complex situations.

       If @DynaLoader::dl_resolve_using contains "-L*" or "-l*" entries then Mkbootstrap will automatically add a dl_findfile() call to the
       generated "*.bs" file.

perl v5.14.2							    2011-09-26					      ExtUtils::Mkbootstrap(3perl)

ExtUtils::Command::MM(3perl)				 Perl Programmers Reference Guide			      ExtUtils::Command::MM(3perl)

NAME

       ExtUtils::Command::MM - Commands for the MM's to use in Makefiles

SYNOPSIS

	 perl "-MExtUtils::Command::MM" -e "function" "--" arguments...

DESCRIPTION

       FOR INTERNAL USE ONLY!  The interface is not stable.

       ExtUtils::Command::MM encapsulates code which would otherwise have to be done with large "one" liners.

       Any $(FOO) used in the examples are make variables, not Perl.

       test_harness
	     test_harness($verbose, @test_libs);

	   Runs the tests on @ARGV via Test::Harness passing through the $verbose flag.  Any @test_libs will be unshifted onto the test's @INC.

	   @test_libs are run in alphabetical order.

       pod2man
	     pod2man( '--option=value',
		      $podfile1 => $manpage1,
		      $podfile2 => $manpage2,
		      ...
		    );

	     # or args on @ARGV

	   pod2man() is a function performing most of the duties of the pod2man program.  Its arguments are exactly the same as pod2man as of
	   5.8.0 with the addition of:

	       --perm_rw   octal permission to set the resulting manpage to

	   And the removal of:

	       --verbose/-v
	       --help/-h

	   If no arguments are given to pod2man it will read from @ARGV.

	   If Pod::Man is unavailable, this function will warn and return undef.

       warn_if_old_packlist
	     perl "-MExtUtils::Command::MM" -e warn_if_old_packlist <somefile>

	   Displays a warning that an old packlist file was found.  Reads the filename from @ARGV.

       perllocal_install
	       perl "-MExtUtils::Command::MM" -e perllocal_install
		   <type> <module name> <key> <value> ...

	       # VMS only, key|value pairs come on STDIN
	       perl "-MExtUtils::Command::MM" -e perllocal_install
		   <type> <module name> < <key>|<value> ...

	   Prints a fragment of POD suitable for appending to perllocal.pod.  Arguments are read from @ARGV.

	   'type' is the type of what you're installing.  Usually 'Module'.

	   'module name' is simply the name of your module.  (Foo::Bar)

	   Key/value pairs are extra information about the module.  Fields include:

	       installed into	   which directory your module was out into
	       LINKTYPE 	   dynamic or static linking
	       VERSION		   module version number
	       EXE_FILES	   any executables installed in a space seperated
				   list

       uninstall
	       perl "-MExtUtils::Command::MM" -e uninstall <packlist>

	   A wrapper around ExtUtils::Install::uninstall().  Warns that uninstallation is deprecated and doesn't actually perform the
	   uninstallation.

perl v5.14.2							    2011-09-26					      ExtUtils::Command::MM(3perl)