Comments on: Using a Single Build Directory in Xcode http://abizern.org/2010/03/18/using-a-single-build-directory-in-xcode/ The personal and developer blog of a Mac developer in London. Fri, 20 Jan 2012 17:55:48 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Abizer http://abizern.org/2010/03/18/using-a-single-build-directory-in-xcode/#comment-64 Abizer Thu, 18 Mar 2010 22:38:36 +0000 http://abizern.org/?p=325#comment-64 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. 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.

]]> By: Jesse Read http://abizern.org/2010/03/18/using-a-single-build-directory-in-xcode/#comment-63 Jesse Read Thu, 18 Mar 2010 22:12:15 +0000 http://abizern.org/?p=325#comment-63 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. 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.

]]>