VMS Help  —  MMS  Generating Description Files
    MMS/GENERATE [/qualifier[/...]] source_filespec[,...]

    Controls whether MMS automatically generates a description file.
    The source_filespec specifies the source files to inspect for
    dependencies and from which the target will be built. The first
    file specified must contain the main module from which the target
    will be built. Otherwise, the source files can be specified in
    any order and wildcard characters can be used. Unless the /CMS
    qualifier has been specified, the description-file generator
    scans all the specified files for dependencies and generates an
    MMS description file for the target defined by the main module.

    For example, if the target is built from C files in the current
    default directory and from Bliss files in the subdirectory
    [.BLISS], and the file MAIN.C contains the main module, the
    following command generates the description file in DESCRIP.MMS:

    $ MMS/GENERATE MAIN.C,*.C,[.BLISS]*.BLI

1  –  Qualifiers

1.1    /BUILTIN_RULES_APPLY

    /BUILTIN_RULES_APPLY
    /NOBUILTIN_RULES_APPLY (D)

    Controls whether MMS generates compilation actions lines. When
    /BUILTIN_RULES_APPLY is selected, no compilation action lines are
    included in the generated description file; the MMS built-in rules
    will be used to perform the compilations.

1.2    /CMS

    /CMS
    /NOCMS (D)

    Controls whether MMS looks for source files and include files in
    the current default CMS library. CMS must be installed on your
    system. If a directory-spec is associated with a file, that is the
    directory into which MMS fetches the file when building the target.

1.3    /DESCRIPTION

    /DESCRIPTION[=filespec]

    Specifies the file to which the generated description is written.
    When not specified, the description is written to the file
    DESCRIP.MMS in the current default directory.

1.4    /FMS_LIBRARY

    /FMS_LIBRARY=forms-library-name

    Specifies an FMS library. This qualifier defaults to MMS$FLB.FLB.

1.5    /INCLUDES

    /INCLUDES (D)
    /NOINCLUDES

    Indicates whether C include files are scanned for dependencies.
    This qualifier gives the same functionality as the Scan Include
    Files toggle button.

1.6    /LINK_LIBRARY

    /LINK_LIBRARY=filespec[,...]

    Specifies additional object libraries to be included in the LINK
    command in the description file.

1.7    /MAIN_MODULE

    /MAIN_MODULE=module-name

    Specifies the main module to be included from the object library
    during the Link process. The main module is that defined in the
    first source file specified and, by default, the module name is
    the same name as the file. This qualifier lets you specify a
    module name that is different from the file name. Note that if an
    appropriate language-dependent module name directive is detected
    within the first source file, the value specified by this
    qualifier is ignored.

1.8    /OBJECT_LIBRARY

    /OBJECT_LIBRARY=filespec

    Specifies the object library to be included in the LINK command in
    the description file. Object files from the compilations are
    inserted into this object library.

1.9    /OPTIONS_FILE

    /OPTIONS_FILE=filespec[,...]

    Specifies user-written options files to be included in the LINK
    command in the description file.

1.10    /SWITCHES

    /SWITCHES=COMPILE="/qualifier..."
    /SWITCHES=LINK="/qualifier..."
    /SWITCHES=(COMPILE="/qualifier...",LINK="/qualifier...")

    Specifies additional command line qualifiers to be included in the
    generated description file for all compilation and/or link commands.
    Additional compilation switches can not be specified when
    /BUILTIN_RULES_APPLY has been specified.

1.11    /TARGET

    /TARGET=name

    Specifies a name for the build target. If this qualifier is not
    specified, the target defaults to the first file specified. This
    lets you specify an executable name that is different from the file
    name.
Close Help