Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site atux01.UUCP
Path: utzoo!linus!decvax!ucbvax!ucdavis!lll-crg!caip!atux01!perry
From: perry@atux01.UUCP (P. Kivolowitz)
Newsgroups: net.micro.amiga
Subject: Re: Disk organization for developing
Message-ID: <137@atux01.UUCP>
Date: Tue, 31-Dec-85 00:48:52 EST
Article-I.D.: atux01.137
Posted: Tue Dec 31 00:48:52 1985
Date-Received: Wed, 1-Jan-86 04:28:41 EST
References: <861@caip.RUTGERS.EDU>
Organization: CSEd, AT&T Communications, Piscataway, N.J.
Lines: 31
Summary: my development disk layout

As people have been asking about how to layout disk contents for C
development I thought I'd share the way I've gravitated towards. I
place everything on df0 except the  c  load time libraries. Df0 is
(of course) a cli only disk. Get rid of libraries, fonts, and pro-
grams in c: that you don't absolutely need.

I include in c: only programs like  run, date, copy, delete, type,
format and other essentials in  addition to the lattice  c compiler
as well as alink.

My rational for putting the include files on df0 went like this:

The include files are around 500 blocks.
The libraries are around 250 blocks.

I'd rather have more room keep source, object, and executables
around on the development disk.

As it is (while trying to port a *very* popular unix game) I ran
out of disk space and had to create a source disk distinct from an
object/executable disk.

Hope this helped


					Perry S. Kivolowitz
---------------------------------
Next JAUG* Meeting is Jan 24th - the first was hampered by snow but
the 80 people who trudged through the mini-storm had a blast.

*Jaug is non-profit and is not associated with C-A, Inc.