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 gitpyr.UUCP
Path: utzoo!watmath!clyde!cbosgd!gatech!gitpyr!lbg
From: lbg@gitpyr.UUCP (Lee B Grey)
Newsgroups: net.micro.amiga
Subject: Re: Disk organization for developing
Message-ID: <1221@gitpyr.UUCP>
Date: Thu, 2-Jan-86 16:59:44 EST
Article-I.D.: gitpyr.1221
Posted: Thu Jan  2 16:59:44 1986
Date-Received: Fri, 3-Jan-86 08:03:02 EST
References: <861@caip.RUTGERS.EDU>
Organization: Georgia Institute of Technology
Lines: 27

In article <861@caip.RUTGERS.EDU>, cosell@BBN-PROPHET.ARPA writes:
> From: Bernie Cosell <cosell@BBN-PROPHET.ARPA>
> 
>                      ...  I'm a developer and I've started to puzzle
> through where the "include" hierarchy will live and junk like that
> and I really can't come up with a satisfactory layout.  Any advice
> or tricks would be appreciated.  Thanks
> 
>   /Bernie
>    cosell@bbn-prophet
>    USENET: bbncc5!bpc

This may be common knowledge, so I'll keep it short.  The first pass of the
compiler allows you to specify up to four paths to be searched for include
files.  I have found this to be a big help in organizing myself.  Not only
that, the Make script supplied allows you to specify up to three additional
options on the command line.  I changed my Make script so that it checks
the correct paths.  If I ever want to access a non-standard include file,
I can specify it on the command line, rather than editting the Make script or
moving the include file.

One note, the Make script came without disk specifiers;  I changed that so that 
I can compile from any current directory.  I hope this was clear.  I tried to be
so brief that I think I wasted everyone's time.  If so, let me know and I'll
do this again, only better.  Lots of luck.

Lee