Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!spool.mu.edu!cs.umn.edu!thelake!steve
From: steve@thelake.mn.org (Steve Yelvington)
Newsgroups: comp.sys.atari.st
Subject: Re: Re: Sozobon C help.
Message-ID: <A2305627801@thelake.mn.org>
Date: 25 Apr 91 22:11:26 GMT
References: <1991Apr24.094735.19857@dcs.glasgow.ac.uk>
Organization: St. Croix Valley C and Ski
Lines: 40

[In article <1991Apr24.094735.19857@dcs.glasgow.ac.uk>,
     waddella@dcs.glasgow.ac.uk (Alexander Waddell) writes ... ]

> I am converting all my C listings from Laser C to Sozobon C, and I have
> encountered a major problem - I can't make GEM programs any more!
> 
> The problem is this - I have changed the INCLUDE statement to include the
> GEMFAST.H header file, compiling the source produces errors. The compiler
> says it does not know about statements such as :
> 
> 	appl_init
> 	v_clswrk...etc...

The GEMFAST.H file doesn't provide the library functions; it merely
replaces GEMDEFS.H and OBDEFS.H, which define various useful
constants, structures, etc.

You need to explicitly include the aesfast and vdifast libraries as
command-line arguments to CC.TTP. (You can add a -GEM feature to CC
if you want, since you have the sources.)

I use MAKE instead. Here is a generic makefile that can be modified
for any GEM program under Sozobon C and GEMFAST. Note that there is
no rule in this makefile for turning .C files into .O -- MAKE knows
how to do that without any special training.

PROGRAM = my.prg
MODULES = my.o
CFLAGS = -O
LIBS = aesfast.a vdifast.a

$(PROGRAM):	$(MODULES)
	cc -o $(PROGRAM) $(MODULES) $(LIBS)

I keep my aesfast.a and vdifast.a files in the same folder as
dlibs.a, dstart.o, libm.a, etc. The LIB environment variable points
there.

 ----
 Steve Yelvington, Marine on St. Croix, Minnesota, USA / steve@thelake.mn.org