On Jan 4, 2016, at 14:10 , Doug Hill <email@hidden> wrote:
In any case, I don’t totally understand why checking in extra Xcode info would result in out of date PCHs, particularly for system frameworks. It looks to me that Xcode is looking for a version of the cache that doesn’t exist or was rebuilt with a different ID. I’m not sure how I can do anything about this for Xcode.
The question is whether the reference to the non-existing ModuleCache subdirectory is in the git repository or not. If it is, for whatever reason, it seems like it shouldn’t be there.
If not, the one other thing you can try is deleting the entire ModuleCache directory. It’s possible that there’s an out-of-date file in there that Xcode trips over when it’s *scanning* that directory the first time you build the project, and cleaning the project probably won’t help with that. I seem to recall there were a couple of versions of Xcode that complained about incompatible precompiled header files, rather than just re-precompiling them, so a bug report about this might be in order.
It wasn’t 100% clear from your original post, but it sounds like anyone checking out the project has the problem — or is it just you? If it’s happening on multiple Macs but complaining about the *same* ID, then that certainly points in the direction of something being checked in.
Finally, in the straw-clutching department, take a look at your header and framework includes, to see if a funny path has found its way in there at some point.
|