Using a Single Build Directory in Xcode
Here’s an old screencast which I never got around to uploading.
It makes sense to set up a single directory in Xcode where built products and intermediate files are kept. You can blitz all the files at once if you don’t need them, you don’t have to set up manual exclusions for your version control and you can set up the files to be excluded from Time Machine backups.
This was recorded with an earlier version of Xcode, but the steps still apply. Please excuse the sound quality.
Comments
Just a minor note. Xcode build directories (and all subdirectories thereof, I believe) are automatically excluded from Time Machine backups. Xcode sets the com.apple.XcodeGenerated extended attribute on the build folders which tells Time Machine to exclude them.
There are still plenty of other benefits to a single build directory, as mentioned.
Comment by Jesse Read on
Thanks Jesse, I didn’t know that about Time Machine exclusion.
I forgot to add that when building and linking to external libraries there is no need to set a common build directory for the project because by default they will all go to the same place.
Comment by Abizer on
Add a Comment.