This is the mail archive of the
mailing list for the GCC project.
Re: Apple's implementation of precompiled headers
- To: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- Subject: Re: Apple's implementation of precompiled headers
- From: Devang Patel <dpatel at apple dot com>
- Date: Wed, 3 Oct 2001 10:31:29 -0700
- Cc: Stan Shebs <shebs at apple dot com>, gcc at gcc dot gnu dot org
On Tuesday, October 2, 2001, at 02:34 PM, Neil Booth wrote:
> Devang Patel wrote:-
>> Yes and No, because how/when to decide if it is 'changed' ?
>> - content is changed
>> - content is same but different compiler options
>> - content is same but different macro settings
>> - content is same but different time stamp
>> - content is same but different file system location
>> - ...
>> Any suggestions ?
> IMO, an implementation of precompiled headers that is deemed worthy
> for inclusion must handle all the above, but I don't understand what
> you are referring to by file system location, unless you're talking
> about (sym)link games.
Yes. links plus relative paths.
I am interested to know, how other precompiled headers implementations
"content is same but different ..." issues.
I recently read about the RedHat precompiled headers branch being
created in gcc
source. How does it handles/plant to handle these issues ?