On Mar 8, 2006, at 8:25 AM, William Turner wrote: I came across this in the archives:
http://lists.apple.com/archives/xcode-users/2004/Jan/msg00540.html
According to the thread, it was entered as bug #3536366 around Jan, 2004. We recently ran into a very closely related issue with xcodebuild. According to the man page for xcodebuild, there's no way of indicating that a "clean" build should, or should not, remove precompiled headers. So, they (apparently) are not removed. This can, in turn, lead to occasional confusing build errors.
My question - what's the status of the bug, has anyone run into this problem, is there a good workaround, etc., etc.
The bug indicated was marked as fixed in Xcode 1.5. A lot has happened to precompiled header management since then, in 2.0, 2.1, and 2.2. But generally:
- xcodebuild clean should delete the precompiled headers in use for that target - There's no option not to do so for xcodebuild clean - Precomps used by other projects (or by this target in previous configurations) won't be cleaned, but shouldn't be used, either.
If you see "occasional confusing build errors" that you think are caused by stale precomps, please file a bug. That's a different and more important problem.
Chris |