Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!know!theep!wildcat!steve
From: steve@wildcat.UUCP (Steve Holland)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: PreCompiled SASC includes
Message-ID: <steve.3728@wildcat.UUCP>
Date: 8 Feb 91 02:47:02 GMT
References: <rshaw.0289@theborg.mlb.fl.us>
Reply-To: wildcat!steve@alphalpha.com
Lines: 17

>In article <rshaw.0289@theborg.mlb.fl.us> rshaw@theborg.mlb.fl.us (Ron) writes:
>Anyways, I have been trying to determine how to
>pre-compiler the includes under SASC to no avail. manx uses cc -ho (or
>something similar in the 5.0 series) how does SASC do it. I see the
>LC -ph flag, but don't fully understand how to set the damn thing up to
>precompile all the headers.

The way I do my precompiled headers is as follows:
	for each C program file, I make separate .c file which just has all
the required #includes. This is compiled with the -ph option.
Then the program (which may #include the headers file) is compiled with
the -Hfilename. 

----------->Steve Holland<-----------
Internet: wildcat!steve@alfalfa.com  | "To err is human, but to really foul
USENET: ..bu!alphalpha!wildcat!steve |  things up requires a computer."
<if alfalfa doesn't work, try alphalpha>