See ExtUtils::MM_Unix for a documentation of the methods provided there.
This package overrides the implementation of these methods, not the
semantics.
Expands MM[KS]/Make macros in a text string, using the contents of
identically named elements of %$self, and returns the result as a file specification in Unix syntax.
Catchall routine to clean up problem MM[SK]/Make macros. Expands macros in any directory specification, in order to avoid juxtaposing two VMS-syntax directories when
MM[SK] is run. Also expands expressions which are all macro, so that we can tell how long the expansion is, and avoid overrunning DCL's command buffer when
MM[KS] is running.
If optional second argument has a
TRUE value, then the return string is a VMS-syntax directory specification, if it is
FALSE, the return string is a VMS-syntax file specification, and if it is not specified,
fixpath() checks to see whether it matches the name of a directory in the current default directory, and returns a directory or file specification accordingly.
Those methods which override default MM_Unix methods are marked ``(override)'', while methods unique to
MM_VMS are marked ``(specific)''. For overridden methods, documentation is limited to an explanation of why this method overrides the MM_Unix method; see the ExtUtils::MM_Unix documentation for more details.
Try to determine name of extension being built. We begin with the name of the current directory. Since
VMS filenames are case-insensitive, however, we look for a
.pm file whose name matches that of the current directory (presumably the
'main' .pm file for this extension), and try to find a package statement from which to obtain the Mixed::Case package name.
Follows
VMS naming conventions for executable files. If the
name passed in doesn't exactly match an executable file, appends .Exe (or equivalent) to check for executable image, and .Com
to check for
DCL procedure. If this fails, checks directories in
DCL$PATH and finally
Sys$System: for an executable file having the name specified, with or without the .Exe-equivalent suffix.
If name passed in doesn't specify a readable file, appends .com or
.pl and tries again, since it's customary to have file types on all files under
VMS.
Fixes up numerous file and directory macros to insure
VMS syntax regardless of input syntax. Also adds a few
VMS-specific macros and makes lists of files comma-separated.
Bypass shell script and produce qualifiers for
CC directly (but warn user if a shell script for this extension exists). Fold multiple /Defines into one, since some
C compilers pay attention to only one instance of this qualifier on the command line.
Adds directives to point
C preprocessor to the right place when handling #include <sys/foo.h> directives. Also constructs
CC command line a bit differently than MM_Unix method.
DCL still accepts a maximum of 255 characters on a command line, so we write the
(potentially) long list of file names to a temp file, then persuade Perl to
read it instead of the command line to find args.
Adds a few
MM[SK] macros, and shortens some the installatin commands, in order to stay under DCL's 255-character limit. Also changes
EQUALIZE_TIMESTAMP to set revision date of target file to one second later than source file, since
MMK interprets precisely equal revision dates for a source and target file as a sign that the target needs to be updated.
Create
VMS linker options files specifying universal symbols
for this extension's shareable image, and listing other shareable images or
libraries to which it should be linked.
Split potentially long list of files across multiple commands (in order to stay under the magic command line limit). Also use
MM[SK] commands for handling subdirectories.
Use VMS-style syntax for files; it's cheaper to just do it directly here
than to have the MM_Unix method call catfile repeatedly. Also, if we have to rebuild Config.pm, use
MM[SK] to do it.
Undertake to build a new set of Perl images using
VMS commands. Since
VMS does dynamic loading, it's not necessary to statically link each extension into the Perl image, so this isn't the normal build path. Consequently, it hasn't really been tested, and may well be incomplete.
Insure that colons marking targets are preceded by space, in order to
distinguish the target delimiter from a colon appearing as part of a
filespec.
DISCLAIMER
We are painfully aware that these documents may contain incorrect links and
misformatted HTML. Such bugs lie in the automatic translation process
that automatically created the hundreds and hundreds of separate documents that you find here. Please do
not report link or formatting bugs, because we cannot fix
per-document problems. The only bug reports that will help us are those
that supply working patches to the installhtml or pod2html
programs, or to the Pod::HTML module itself, for which I and the entire
Perl community will shower you with thanks and praises.
If rather than formatting bugs, you encounter substantive content errors in these documents, such as mistakes in
the explanations or code, please use the perlbug utility included
with the Perl distribution.
--Tom Christiansen, Perl Documentation Compiler and Editor