Re: Caching compiled files
Re: Caching compiled files
- Subject: Re: Caching compiled files
- From: Steve Checkoway <email@hidden>
- Date: Thu, 20 Jul 2006 14:12:59 -0700
Subject really repaired.
On Jul 20, 2006, at 5:27 AM, Ulf Dunkel wrote:
I use to compile and build a Cocoa project (iCalamus) every now and
then with the actual XCode version. In fact I don't write much of
the iCalamus source code, but get the stuff written by our
developers, from our SVN server. Everything's fine so far.
But - I really wonder why XCode so often compiles the whole stuff
(about 1.800 files in Deployment mode, still half of them in
Development Native mode) when only one or two files have been
changed. And I am aware of relations of base source files which are
included in almost everything. The changed files are rather kind of
branch source files, thus they should not effect many other files.
Are there no cashing options for XCode in order to check which
files really need to be re-compiled? Or do I have to set a checkbox
I could have forgotten to check?
Please help - for me and our developers this is the most time-
wasting part on working with XCode.
I've had this happen quite frequently (as in several times in a
week). Sometimes (but not always), checking a file into CVS is enough
for Xcode to think it needs to be recompiled. There are exactly two
files in my project that affect my precompiled headers and yet
seemingly at random, Xcode will recompile those and then everything
else.
I've never been able to reproduce this reliably, so I've never filed
a bug since I don't have any more info to offer than "It doesn't work
at times." That's not exactly a helpful bug report.
--
Steve Checkoway
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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