The media contains the sub-directories:
FAQ Frequently Asked Questions about G5G products
For more details you can find a FAQ file in
demos/GPHIGS
demos/GPHIGS_GUI
demos/PHIGURE
DIFF Contains informations between OPGS minor releases.
DIFF_2.1_3.0 Contains different between OPGS version 2.1 and 3.0.
run_time Contains the files used at execution time as well as font file description, drivers description files and Phigs Input Manager (PIM).The environment variable OPGS_RUN_TIME will need to be set to the pathname of this directory.
For compatibility GPHIGS_FILE works too
NB : Instead of OPGS_RUN_TIME, another environment variable can be set to the top of the sub-tree OPGS : OPGS_HOME
For example :
in C-shell, if the product is installed in the directory /usr/g5g:
setenv OPGS_RUN_TIME /usr/g5g/OPGS/run_time
or setenv OPGS_HOME /usr/g5g/OPGS
or in K-Shell
export OPGS_RUN_TIME=/usr/g5g/OPGS/run_time
or export OPGS_HOME=/usr/g5g/OPGS
demos Sub-directories tree :
GPHIGS, GPHIGS_GUI and PHIGURE.
All contains C, FORTRAN, DIFF_XXX, FAQ, datafile sub-directories and a README file.
C : C demonstration programs
FORTRAN : Fortran demonstration programs
DIFF_XXX : Differences between old version and new version of G5G products.
FAQ : Frequently Asked Questions file about G5G products
datafile : Files needed for demonstrations
README : A readme file
Each directory C and FORTRAN contains a Makefile.
This Makefile read 2 files :
OPGS/include/Make.inc
OPGS/config/Make.conf
To use GPHIGS_GUI set the environment variable OPGS_USE_GUI to yes, otherwise unset this variable. You can also generate a specified Makefile for GPHIGS_GUI using make gui command ( or make nogui to unset )
NB : make help give a help for demonstration's Makefile.
For more details see the README file in each directory
include This directory contains all include files needed for compiling G5G products.
lib This directory contains library needed for linking G5G product
Depending of your purchase it contains:
libgphigsc.a GPHIGS C library
libgphigsf2c.a FORTRAN interface for GPHIGS
libgphigsf_c.a FORTRAN interface with '_' for GPHIGS (option)
libgphigsgui.a GPHIGS C library and GPHIGS_GUI functionalities
This library contains the GPHIGS library (libgphigsc.a)
libphigure.a PHIGURE functionalities
libphiguref.a FORTRAN interface for PHIGURE
libphiguref_.a FORTRAN interface with '_' for PHIGURE (option)
Depending on your computer you can find shared libraries.
To generate those shared libraries you can use mkshlib utility in config directory.
Because some FORTRAN compilers generate object code with function names having a "_" appended to them, while other compilers do not, the directory lib can also contain the library libgphigsf_c.a and libphiguref_.a (for example an HP9000/700 or an IBM/RS6000 workstation). Note, however, that only one of these two libraries is needed for linking.
For linking a GPHIGS C program you need :
libgphigsc.a
For linking a GPHIGS FORTRAN program you need :
libgphigsf2c.a (or libgphigsf_c.a)
libgphigsc.a
For linking a GPHIGS_GUI C program or GPHIGS C program you need :
libgphigsgui.a
For linking a GPHIGS_GUI FORTRAN program you need :
libgphigsf2c.a
libgphigsgui.a
For linking a PHIGURE C program you need :
libphigure.a
libgphigsc.a
For linking a PHIGURE FORTRAN program you need :
libphiguref.a (or libphiguref_.a)
libphigure.a
libgphigsf2c.a (or libgphigsf_c.a)
libgphigsc.a
For linking a PHIGURE C program and access to GPHIGS_GUI you need :
libphigure.a
libgphigsgui.a
For linking a PHIGURE FORTRAN program and access to GPHIGS_GUI you need :
libphiguref.a (or libphiguref_.a)
libphigure.a
libgphigsf2c.a (or libgphigsf_c.a)
libgphigsgui.a
config You find a configuration file and (depending on your computer) a shell script mkshlib.
mkshlib is used to generate shared libraries.
Example :
Silicon :
mkshlib libgphigsc.a libgphigsc.so
HP :
mkshlib libgphigsc.a libgphigsc.sl
Contains a script shell named conf which can be used to configure the list of linked drivers for an application.
GPHIGS can access simultaneously several type of workstation. Each type is associated to a driver. GPHIGS allows programmers to select the list of drivers to link with an application. This can reduce the size of an executable.
This selects the list of workstation types an application may access with GPHIGS by OPEN WORKSTATION. E.g., an application may use PostScript for paper outputs and X11 for drawing on the screen. The other OPGS drivers are not being used so it is not necessary to link them with the application.
Conf may be used to disable all unnecessary drivers.
Conf creates a file PHGDVR.c, and compiles and archives it in the GPHIGS library.
Note: Conf lists all the drivers available with GPHIGS on all platforms even if they are not installed on a specific machine. This may produce link errors. E.g. Xgl must not be selected on platforms other then SUN.
The list of drivers delivered with GPHIGS is listed on the delivery form.
To configure OPGS's drivers just type conf. A panel appears with information for each driver and the link status (yes/no). Just enter the driver number and the status for the required driver changes. When the modifications are made just type a to apply changes. In this case the GPHIGS library is modified. If the changes concern only a specific application, the c option should be used to generate the PHGDVR.o file. This file may then be linked with the application without modifying the library. In this case the object is not archived.
contrib Some sources (X-contrib) with G5G products.
obj Contains pim.a library necessary if the Phigs Input Manager (PIM) executable must be relinked. On some systems, it contains also specified objets files. A README file describe the content of those objets files.