If compiled libraries are already available,
then the distribution is made via a tar file called unix_lib.tar.
As this file contains binary libraries
it must be compatible with the target machine.
It may also be distributed by an institute affiliated to CERN,
rather than by the CERN Program Library, if the target machine
is not available on the CERN site.
The first thing to do is to create a root directory, for example, /user/gts-root, and set this as current. The tar file should then be copied to this root from tape or via a network, and then be unpacked:
mkdir /user/gts-root (cp-or-ftp-or-mv unix_lib.tar /user/gts-root/unix_lib.tar) cd /user/gts-root tar -xf unix_lib.tar .
If the driver library contains the required drivers, then the only
thing that remains to be done is to define the environment variables
gkshome, gkslib, gksdriv, gks3dlib, GKS_FONTS, etc.
This is best done by modifying the file startgks, as described above.
If there is a requirement to use a driver which is not included
in the the driver library, then the mechanism to add a driver
is described below.
The tar file contains the same directory structure described
in section on Page 
, but the contents are modified slightly:
To add drivers to the driver library one follows a procedure
similar to that given in section on Page
which describes how to build the libraries from a source distribution.
$gksdrivlist to specify the drivers you wish to include.
The file has one line per driver, with the format 'dn name'.
The first character is a literal 'd' and is followed by an integer
which numbers the lines. The second argument is the name of the
sub-directory below $gkshome/gks/drivers containing the driver which
is to be added.
$gkstools/c_gksdriv_create, which will compile the whole
driver library. Alternatively, one can simply add the driver
to the existing library via the commands:
cd $gkshome/gks/drivers/new_driver $compile $gksdriv $ccompile $gksdriv
$gkshome/gks/kernel/gkddlk.f and
$gkshome/gks3d/kernel/gkddlk.f (they are not identical) to ensure
that the drivers compiled above are known to GKS and GKS-3D.
The routines must then be compiled and replaced in their
respective libraries using the tool $gkstools/c_gks_comp_single:
c_gks_comp_single $gkshome/gks/kernel/gkddlk.f $gkslib c_gks_comp_single $gkshome/gks3d/kernel/gkddlk.f $gks3dlib
Those people who wish to write new drivers are basically on their own.
They are advised to start from the source of an existing driver
with features similar to the one they wish to write. However,
a few points of interest are to be found in the file 'help.drivers'.