> On Jan 4, 2016, at 2:25 PM, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > On Jan 4, 2016, at 14:10 , Doug Hill <xcodeus...@breaqz.com > <mailto:xcodeus...@breaqz.com>> 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.
I don’t see any references to the ModuleCache directory in our git repository. > 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. This sounds more likely and would seem to be an Xcode bug. Difficulty: happens randomly so hard to reproduce for a bug report. > 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. Again, this happens to multiple team members more or less randomly. They have the same behavior that I see; that sometimes after switching branches and doing ‘pod install’ would show these warnings. I never checked the IDs but my guess is that they’re not the same as I don’t check in ModuleCache files. Also, it can happen after I’ve been building this project many times. Then I’ll switch git branches and sometimes get warnings. > 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. Good tip! But I don’t see any funny paths either. Doug Hill
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
