| You will probably find that it's the attributes in the file system on the build directory which disabled Time Machine:
com.apple.XcodeGenerated: Yes
Not that you should go changing those!
I use subversion locally, with a file:/// repository on my local disk and check out a working area to my home area that uses the repository, then check in and out from my home area which Xcode understands. I've added to my subversion config file the following, it exclude the build directory and per user settings files, which seems to work correctly.
global-ignores = <whatever is there currently> build *.mode1v3 *.pbxuser
I was pleasantly surprised that Time Machine skips the build directory. With big projects they can get quite large and change very often. You don't really want to fill your disk with a different build every hour :-)
If your using your build area for packaged releases, then you will want to tar them up or otherwise package them up and store them elsewhere when you do a formal release. It's all well and good being able to go back to an older version of code, but Xcode may have moved on and you may have applied patches to the compile or SDKs. If you really have to have a copy of what you released in the past, you need to keep it separate. Years of supporting customers who don't like to move on gets you into the habit of keeping copies of all released packages :-)
Regards, Darren
On 5 Nov 2008, at 17:42, Sherm Pendley wrote: 100% agreed. The build folder is little more than a special-purpose /tmp. The fact that it doesn't get backed up isn't the problem; the problem is that you're putting stuff in there that you care about backing up.
sherm--
On Wed, Nov 5, 2008 at 12:30 PM, Steven W Riggins <email@hidden> wrote: You should not rely on build folders for storing private resources. Anything that is part of a build should be code managed.
I keep all of my resources outside of the build folder, and then use copy files build phases to copy the resources into the build.
On Nov 5, 2008, at 9:11 AM, turbo3d wrote:
1) the build folder also contains the linked and built applications in subfolders ( according to the various build configurations ) Applications are certainly derived from source code, but they also contains various ( and sometimes lot of) private resources that have nothing to do with code management. 2) Obviously , XCode 3.1.1 prevents me from saving what I want. The build folder is just a folder... And Time Machine has functionnalities to let me exclude what I dont want to backup.. I just dont like something that pretends to play with my data and decide for me what is worth saving... The question remains : is there a mean to have the build folder included in Time Machine backups ? JP Le 5 nov. 08 à 17:35, Greg Hulands a écrit : The build folder is something that is derived. eg. from the source code.
Sounds like you should be using versioning control of some sort.
On Nov 5, 2008, at 8:03 AM, turbo3d wrote:
Since I use Xcode 3.1.1 , Time Machine no longer saves the "build" folder in backups. This is documented in the XCode release note.
I dont unserstand why and this causes me some trouble, and because of this, I have lost previous builds which where important to me....
Is there any mean to have the XCode build folder included in the time machine backups ?
Thanks
JP
|