Why does Xcode always recompile all files the second time after a full build but not after that?

Question

Created Oct ’21

Replies 1

Boosts 0

Views 1k

Participants 1

This issue has bugged me for some time. Whenever I do a full build whether it's for debugging or profiling, Xcode always insists on recompiling all files the second time I build (regardless of whether there are changes or not), but then behaves normally after that and only recompiles changed files when I build.

FWIW, I use a precompiled header. My project also contains other Xcode projects that consists of static libraries and frameworks that are built as dependencies. Those other Xcode projects are not rebuilt after the first build, just the source files included in my project.

This has been an ongoing problem for years and continues with Xcode 13.1. I'm sure it's something within my Xcode project that I've been maintaining since at least Xcode 3 (I don't remember which version of Xcode I started with) because new projects don't exhibit this behavior.

Again, building doesn't unnecessarily recompile all files, only the second time I build.

Boost

Answer 1

chinhster1 OP

Nov ’23

To answer my own question, the problem was because a long time ago, I had specified a custom location for my build folder for reasons I won't get into but it was necessary in old version of Xcode and its legacy build system. In addition, some of the third party frameworks I use also had custom build folder locations. Once I changed all the projects to just let Xcode handle maintaining the build folder and ensuring that my Xcode project settings was showing that it was using the Xcode Default build location and not Legacy, the rebuild problem went away.

0