Silicon Graphics IRIS Workstation, User Manual

Page: 156 / 170

150 IRIS WORKSTATION GUIDE
Version 1.0
Appendix K:
% ls $BOOT
...
2. Create a sub-directory to test IRIS terminal programs generated with
the IRIS Terminal programming environment.
% mkdir $BOOT/test
The IRIS Terminal programming environment makefile ’s install IRIS
terminal programs in $BOOT/test . After testing these IRIS terminal
programs, they should be moved to $BOOT .
3. The following csh commands define the environment variables for
the IRIS Terminal programming environment:
% setenv BASE /usr/progenv/engr
% setenv DESTDIR /usr/progenv/engr
% setenv MACHINE MC68000
% setenv SYSTEM SYSTEM5
4. Next, source the file env . csh (if you are using csh — the C shell) or
env . sh (if you use sh — the Bourne shell).
% source env.csh
K.4 Adding Commands to the IRIS Graphics Library
To add a new command to the IRIS Graphics Library, you need to:
• Write and test (on the IRIS Workstation, if possible), the routine to
be added.
• Add this routine to the $IRIS/srclterm/local.c file.
• Make an appropriate entry into the command table
( $IRIS/lib/lib.prim ). Section W.5 describes the entry format of the
$IRIS/lib/lib.prim file.
• Run makefile ’s that automatically generate a new version of the IRIS
terminal program and of the remote graphics library.
As an example, suppose you wish to make an IRIS Graphics Library command
that clears the screen to a given color, and then returns the number of bitplanes
on the system. The following routine on the IRIS Workstation does this:
short funnycolor(col)
Colorindex col;
{
color(col);
clear 0 ;
return getplanes();
}
If you call
x = funnycolor(BLACK)
on the remote host, the screen will clear to
BLACK , and the number of available bitplanes will be returned in x .