Click on FTP to download from the FTP archives.
![[FTP]](http://www2.encompassus.org/hidedecus/graphics/i_ftp.gif)
------------------------------------------
Requirements:
-------------
The build procedure utilizes DEC/MMS and DEC/CMS. The VDS sources are included
in both a CMS library format, and in a normal text-file format. At present,
the build procedure does not use the text-file format source directory.
However, the need for CMS could be eliminated by replacing all CMS 'Fetch'
operations with a copy command from the non-CMS source directory.
The following languages are also required:
o BLISS-32
o VAX PASCAL
In addition to the storage required by the files included in the Encompass release
tape, approximately 50,000 blocks of disk space is required to build the VDS
software.
Organization:
-------------
The Encompass release tape contains the following directories:
[VS100] - Contains this file ('BUILD.DOC')
[VS100.EXAMPLES] - Contains the example programs described in the
VaxStation Display Services manual.
[VS100.FONT] - Contains binary images of the fonts.
[VS100.HELP] - Contains the help library available at the VMS DCL
'HELP' level.
[VS100.MICRO] - Contains the downloadable microcode for the
VAXstation 100 hardware.
[VS100.UETP] - Contains the sources and executables for the VS100
User Environment Test Package.
[VS100.HILIB] - Contains files needed by the Human Interface portion
of VDS.
[VS100.LIBRARY] - Contains the libraries needed to build the VDS
software.
[VS100.Encompass_CMSCODE] - Contains the sources released to Encompass, in
CMS form, including build command procedures.
[VS100.Encompass_SOURCES] - Contains the sources in text-file format.
All of these directories, with the exception of [VS100.Encompass_SOURCES] are
needed in order to build the VDS software. The build procedures use these
directories to obtain the needed source and library files; however, the build
itself takes place in a separate area on a different disk. Thus, these
directories are referred to as the source area (or SOURCE:), whereas the
directories used for building are referred to as the build area (or
BUILD_DEVICE:). Any references to SOURCE: or BUILD_DEVICE: should be renamed
to devices appropriate to your system.
Overview of Build Process:
--------------------------
The following steps describe the VDS software and installation kit build
process. The steps will each be described in greater detail in following
sections. Note that the command procedures referenced here are included in the
CMS library (SOURCE:[VS100.Encompass_CMSCODE]), and in the directory
SOURCE:[VS100.Encompass_SOURCES].
1. INIT_BUILD_DEVICE.COM is used to initialize the build disk and copy
the library files from the [VS100.LIBRARY] source area. WARNING: If you
are not going to use a separate disk for the build area, then this procedure
MUST be modified so that the disk is not initialized accidentally.
2. COMBINE.COM is used to build the VDS software. This procedure utilizes
MMS and CMS to fetch and build the sources in the [VS100.Encompass_CMSCODE]
library. You MUST make sure that all logicals are set up correctly as
described below in the section on COMBINE.COM.
3. GET_KIT_FILES.COM is used to collect all the built images and other
files needed to build an installation kit. All the needed files will be
copied to a single directory.
4. MAKEKIT.COM is used to put all the files collected by the last step into
a VMSINSTALable kit. NOTE: This step requires system privileges whereas
none of the previous steps require any privileges other than those possessed by
a normal user.
5. The kit built by MAKEKIT can than be installed on any VMS system using
VMSINSTAL.
The following sections will describe these steps in further detail.
Step 1: Initializing the build area.
-------------------------------------
INIT_BUILD_DEVICE.COM assumes that the build is occurring on a disk dedicated to
this task, so it erases all previous scratch information with a VMS DCL
'INITIALIZE' command, and then it creates new directories. If you wish to
build on a disk that has other useful information, then this procedure should
be modified to DELETE all data from the build directory, and than copy the
necessary libraries from SOURCE:[VS100.LIBRARY] to the build area.
The build area is structured as follows:
BUILD_DEVICE:[VS100.BL.SOURCE]
BUILD_DEVICE:[VS100.BL.BUILD]
BUILD_DEVICE:[VS100.BL.LIBRARY] - contains library files copied from
[VS100.LIBRARY] source directory.
BUILD_DEVICE:[VS100.BL.EXE]
BUILD_DEVICE:[VS100.BL.HILIB]
BUILD_DEVICE:[VS100.BL.SCAFF]
The initialize step should create this directory structure, and leave it
completely empty except for the library directory.
Step 2: Build the VDS software using COMBINE.COM
-------------------------------------------------
COMBINE.COM begins execution by defining logicals in the form 'VSTA$*' to point
to each of the directories listed above. Thus, it must be edited to make sure
that each logical points to the proper directory (on the proper device). It
also establishes the CMS library via the CMS SET LIBRARY command; the library
should be set to the SOURCE:[VS100.Encompass_CMSCODE] directory. Once the logicals
are defined, COMBINE.COM passes control to DEC/MMS, which uses the file
COMBINE.MMS to build everything. Assuming that all logicals are set up
correctly, the result of the MMS build with be the all the image and library
files needed for the installation kit.
The logicals are defined as follows:
VSTA$COM - > BUILD_DEVICE:[VS100.BL.SOURCE]
VSTA$SOURCE - > BUILD_DEVICE:[VS100.BL.SOURCE],
BUILD_DEVICE:[VS100.BL.BUILD]
VSTA$BUILD - > BUILD_DEVICE:[VS100.BL.BUILD],
BUILD_DEVICE:[VS100.BL.SOURCE]
VSTA$LIBRARY - > BUILD_DEVICE:[VS100.BL.LIBRARY]
VSTA$EXE - > BUILD_DEVICE:[VS100.BL.EXE]
VSTA$HILIB - > BUILD_DEVICE:[VS100.BL.HILIB]
VSTA$SCAFF - > BUILD_DEVICE:[VS100.BL.SCAFF]
Note that COMBINE.COM hard codes BUILD_DEVICE to a specific device; you
MUST edit this to point to a drive appropriate for your installation.
Step 3: GET_KIT_FILES.COM
--------------------------
GET_KIT_FILES.COM will also need to be modified so that the logicals point
to the proper directories. In this case, some of the logicals point to
the build area, and some point to the source area as follows:
BL$EXAMPLES - > SOURCE:[VS100.EXAMPLES]
BL$FONT - > SOURCE:[VS100.FONT]
BL$HELP - > SOURCE:[VS100.HELP]
BL$MICRO - > SOURCE:[VS100.MICRO]
BL$UETP - > SOURCE:[VS100.UETP]
BL$HILIB - > SOURCE:[VS100.HILIB]
BL$BUILD -> BUILD_DEVICE:[VS100.BL.BUILD]
BL$EXE - > BUILD_DEVICE:[VS100.BL.EXE]
BL$LIBRARY - > BUILD_DEVICE:[VS100.BL.LIBRARY]
BL$SOURCE - > BUILD_DEVICE:[VS100.BL.SOURCE]
Note that SOURCE: and BUILD_DEVICE: are hard coded to point to specific devices
in the command procedure; they must be edited to fit your installation. The
CMS library must also be set to the SOURCE:[VS100.Encompass_CMSCODE] directory. The
output is directed to the directory pointed to by the BL$KIT_FILES logical.
Step 4: Making the installation kit.
-------------------------------------
The MAKEKIT.COM procedure will take the files collected in the previous step
and build an installation kit. Again it must be edited to make sure that the
logical definitions point to the correct devices and directories. Input
and output is controlled by the following logicals:
BL$KIT_FILES - points to directory containing kit files collected
by GET_KIT_FILES.COM.
BL$SAVESET - points to directory in which the installation kit saveset
will be created.
Edit the file MAKEKIT.COM to make sure that these logicals are defined to
the desired devices and directories. Note that several system privileges are
required to build the saveset; the procedure will inform you if you do not have
the needed privileges.
Step 5:
-------
If the preceding steps were carried out correctly, then the resultant saveset
should be a VMSINSTALable kit.
Click on FTP to download from the FTP archives.