Re: Time Machine backs up my Xcode 3.2 build folders
Re: Time Machine backs up my Xcode 3.2 build folders
- Subject: Re: Time Machine backs up my Xcode 3.2 build folders
- From: Chris Espinosa <email@hidden>
- Date: Thu, 8 Oct 2009 11:17:48 -0700
On Oct 8, 2009, at 10:14 AM, David Gimeno Gost wrote: I created a new test Cocoa Application project, left it at its default settings, and Time Machine didn't back up the build folder.
Then, I changed the "Project Info > General > Place Build Products In" setting to "../build" (which is how the other project was configured), told Time Machine to "Back Up Now", and the build folder was backed up like any other folder.
The extended attributes of the build folders are exactly the same in both cases:
[iMac-Core2Duo:~]$ ls -ld@ /Users/David/Test/build
drwxr-xr-x@ 4 David David 136 Oct 8 17:55 /Users/David/Test/build/
com.apple.XcodeGenerated 3
[iMac-Core2Duo:~]$ ls -ld@ /Users/David/build
drwxr-xr-x@ 4 David David 136 Oct 8 18:36 /Users/David/build/
com.apple.XcodeGenerated 3
Looks like an easily reproducible bug, at least on my system. Does it make sense?
rdar://problem/7287003
That makes sense. Xcode does two separate things here; it tells Time Machine not to back up the folder using the CoreServices API, and it tags the folder itself so it doesn't copy it for Snapshots, etc. The Xcode process seems to resolve the ../ in the Unix path correctly, but the Core Services API may not be able to.
Thanks for filing the bug.
Chris |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden