Time machine backing up temporary binary files.
Time machine backing up temporary binary files.
- Subject: Time machine backing up temporary binary files.
- From: John Lunt <email@hidden>
- Date: Thu, 15 Nov 2007 22:08:05 +0000
I've just realized that Time Machine (TM) seems to be backing up the
temporary binary files from my Xcode projects. I'm particularly
thinking about the .o files, but I'm sure there are others. If checked
for a simple "Hello World" program that main.o appears in my TM backup.
It seems to me that the compiler generated temporaries take up 2 to 10
times the space of the source, and are completely regenerated every
time I do a clean build. This is going to fill up my backup drive
quite fast.
- excluding the files manually doesn't seem feasible. I've got dozens
of projects each creating .o files in several sub-directories
- excluding my whole Xcode project seems like a bad idea, as I
actively want my source to be backed up.
- Apple have thought about the issue in general (e.g. as a developer I
can call CSBackupSetItemExcluded(.)from my own app) but as far as I
can tell, there is no option in Xcode to stop .o files from being
archived automatically.
Example: At work I on a (non Xcode) project which is about 200M of
source, 100M of deliverable end-user code, and a fully built project
takes up about 4.6 GB. I do a clean build at least twice a week, so I
make that about 8G of new compiler generated temporaries every week
that I would have no interest in backing up. If I was to do this at
home, my back-up would fill up very rapidly with temporary files.
Am I missing something here, or should I just file a bug against this?
John.
_______________________________________________
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