Re: Indexer takes wrong locations for C++ headers
Re: Indexer takes wrong locations for C++ headers
- Subject: Re: Indexer takes wrong locations for C++ headers
- From: Allan Odgaard <email@hidden>
- Date: Mon, 22 Mar 2004 04:05:11 +0100
On 22. Mar 2004, at 1:42, Geoff Leyland wrote:
I've found a header bug that might be related - the *compiler* ends up
including the wrong header files. I think it has something to do with
the way the .hmap file is used, but I haven't investigated much.
I once tried to look into this, because I wanted to compile a project
manually -- it seems that the hmap file is a map (i.e. hash) of all
headers in the project with the filename as key and path as value.
This means two things: all headers in your project, irrelevant of path,
will be found while compiling, when included w/o a path and, as you
notice, if you have two headers with the same name, problems will
arise.
I was not able to find any justification for this "feature" -- it is a
apple-only extension to gcc and it is not documented. Does anybody know
why one might want this feature? Perhaps it speeds up finding headers
on slow disks, but then, a cache could still be made w/o disregarding
path info...
On a slightly related note, I have a really frustrating problem: most
of the time when I recompile a changed source or header, Xcode will
compile the *old* version, often causing compiler errors which are
solved simply be selecting build again.
The problem is *not* that I do not save the files. I have auto save
enabled, and I have also tried to e.g. save the file, change it, save
it again and then compile, only to have Xcode show up errors even
quoting lines from the old source.
I think it is related to predictive compilation. Is there anyway I can
turn this off? and does other have the same problem?
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.