Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site 3comvax.UUCP
Path: utzoo!linus!decvax!decwrl!sun!idi!oliveb!3comvax!mykes
From: mykes@3comvax.UUCP (Mike Schwartz)
Newsgroups: net.micro.amiga
Subject: Re: AmigaTerm & Lattice_C
Message-ID: <304@3comvax.UUCP>
Date: Fri, 27-Dec-85 14:36:02 EST
Article-I.D.: 3comvax.304
Posted: Fri Dec 27 14:36:02 1985
Date-Received: Sat, 28-Dec-85 13:18:31 EST
References: <1889@hao.UUCP> <1893@hao.UUCP>
Distribution: net
Organization: 3Com Corp; Mountain View, CA
Lines: 48

This is how I set up my system for compiling lattice 'C' stuff native
on the Amiga.  

1.	I formatted a disk and used the install command to make it
into a bootable disk.  Then I copied most of the commands from my
workbench disk's :c directory.  I also copied the fonts, devices, etc.
I then deleted a lot of the workbench :c commands from my new disk.
I then created a directory to hold the 'C' compiler and linker as :lc.
I also copyied the include files (in the standard tree structured format)
subdirectories to this disk.  This disk I call my lattice 'C' workbench
disk.  You can edit the file :s/startup-sequence to assign any devices
that you might want, set your default working directory, etc.

2.	My second disk I call my work disk.  All my work disks must
have a special subdirectory on them called :clib, which contains
lstartup.obj and the 'C' libraries.  For convenience's sake, I concatonated
these three files to make clib.lib - lc.lib+amiga.lib+debug.lib.  The rest
of the work disks are used to hold (flame on) a few source files along with
the MONSTROUS output of the sad lattice 'C' compiler (flame off).  I find
that the 880K floppies are enough to hold about 3 to 4 fair size projects
at a time.  

3.	Using this configuration, the following commands compile hello.c: 
	df0:lc/lc1 -idf0:include/ -oram: hello
	df0:lc/lc2 -odf1:hello.o ram:hello
	df0:lc/alink df1:clib/lstartup.obj+hello.o library=df1:clib/clib.lib
					to hello

	These commands can be simplified by putting the following assigns
	in your startup-sequence file on df0:
	assign cc: df0:lc
	assign ci: df0:include
	assign clib: df1:clib/clib.lib
	assign cmain: df1:clib/lstartup.obj


	This makes the compilation commands:
	cc:lc1 -ici: -oram: hello
	cc:lc2 -odf1:hello.o ram:hello
	cc:alink cmain:+hello.o library=clib: to hello

I hope that this helps some of you out there.  I have played around with
system configurations for native development, and have found that using
the RAM disk too much (too much == not much) that the linker and compiler
have a hard time.  Also, Lattice 'C' doesn't handle lots of if ... else if...
in a row too well (you need gobs of stack).

/mykes