🚀 go-pugleaf

[Note: if this is getting to any 8bit groups it isn't my fault.
I am mailing this to info-atari16@su-score on the ARPA net]

Here is a batch file which I use for running the compiler and linker
using a 285K RAM disk installed as drive C:, with source on drive B:
and the compiler, assembler and linker on drive A:.

C:rm C:%1.prg
cp68 -i B: B:%1.c C:%1.i
c068 C:%1.i C:%1.1 C:%1.2 C:%1.3 -f
C:rm C:%1.i
c168 C:%1.1 C:%1.2 C:%1.s
C:rm C:%1.1
C:rm C:%1.2
as68 -l -u -f C: -s C: C:%1.s
link68 [temp [C:],u] C:%1.68k = C:gemstart,C:osbind,C:%1,C:vdibind,C:gemlib
relmod C:%1
C:rm C:%1.68K
C:wait

The argument %1 is the name of the single program to be compiled and linked.
Additional required libraries can be added beyond 80 columns in the link68
line, or you might want to use the com option as described in the
documentation.

The philosophy behind this setup is to put all files that will be *written*
into RAM disk, since writing a file takes longer than reading (probably
because there is verification going on). Also, the biggest bottleneck
seems to be the linker.  Try replacing C:gemlib by B:gemlib, for instance,
and watch that drive spin for an additional 30 seconds or so.

Oh, by the way.  The batch file, and all files without a C: should sit
on the same drive (I use A:).  Also you need the file C:as68sym.dat (I
think that's the name) to initialize the assembler.  I have all my
source code, .h's and the editor on drive B:.

Please let me know of your experiences with this, or any improvements, or
comments.

	Franz Lanzinger (fxl@aids-unix)
	415 941 3912
	Advanced Information Systems