When I do a "Clean Build Folder" I always get:
<unknown>:0: error: module file '…/…/….pcm' is out of date and needs to be rebuilt: signature mismatch
If Xcode knows that it is out of date, why doesn't it recompile? This just doesn't make any sense.
Roddi
I’ve used a local variation of this script when Xcode has gotten very tangled:
… https://gist.github.com/maciekish/66b6deaa7bc979d0a16c50784e16d697
#!/bin/bash
killall Xcode
xcrun -k
xcodebuild -alltargets clean
rm -rf "$(getconf DARWIN_USER_CACHE_DIR)/org.llvm.clang/ModuleCache"
rm -rf "$(getconf DARWIN_USER_CACHE_DIR)/org.llvm.clang.$(whoami)/ModuleCache"
rm -rf ~/Library/Developer/Xcode/DerivedData/*
rm -rf ~/Library/Caches/com.apple.dt.Xcode/*
open /Applications/Xcode.app
I haven’t met the clang paths in recent years, and there’s a build data path that might need to be targeted in the same place as that com.apple.dt.Xcode cache path.
No warranties, have solid backups beforehand, YMMV, etc.
I’ve used a local variation of this script when Xcode has gotten very tangled:
… https://gist.github.com/maciekish/66b6deaa7bc979d0a16c50784e16d697
#!/bin/bash
killall Xcode
xcrun -k
xcodebuild -alltargets clean
rm -rf "$(getconf DARWIN_USER_CACHE_DIR)/org.llvm.clang/ModuleCache"
rm -rf "$(getconf DARWIN_USER_CACHE_DIR)/org.llvm.clang.$(whoami)/ModuleCache"
rm -rf ~/Library/Developer/Xcode/DerivedData/*
rm -rf ~/Library/Caches/com.apple.dt.Xcode/*
open /Applications/Xcode.app
I haven’t met the clang paths in recent years, and there’s a build data path that might need to be targeted in the same place as that com.apple.dt.Xcode cache path.
No warranties, have solid backups beforehand, YMMV, etc.
I’m guessing this probably isn’t your code, but something you’re building from elsewhere from source? If so, is that code current?
Which version of macOS, and which Xcode? Monterey, and Xcode 14.0.1?
What’s cleaning and what’s building that pcm module? Xcode itself, or a makefile or build script?
Yes, Monterey and Xcode 13.4.1. We still use 13.4.1 because we wait Xcode 14 to stabilise well enough to install it into our CI pipeline.
Apple has this tendency to create more problems in Xcode than fixing old ones, especially in fresh major versions of it. So we tend to be pretty conservative with updating.
The cleaning and building is done by Xcode itself. The project has a (probably unhealthy) mix of remote swift packages, local swift packages and cocoa pods. Also still 20% of Objc code left in the project (not counting external dependencies).
Xcode: "is out of date and needs to be rebuilt"