1) It's recalculating the dependency tree to mark dependent files
and targets as dirty and needing a rebuild. We know this process is
unoptimized and are working on it.
Can you elaborate on this one? What would be a large dependency tree?
2) It's reindexing that file. This happens on a lower-priority
background thread and shouldn't take too long or be noticeable.
It's stalling the main thread.
3) It's actually compiling the file in the background for you, in
case that's the next thing you'll be doing. Again, this happens on
a low-priority background thread. If you have a low-memory machine
this may cause swapping and result in a spin, but if you have more
RAM this is not noticeable
I have 2.5gigs of RAM and it is a legacy target.
4) It's unfortunately doing a full text layout of the entire file.
This is only noticeable in very large files, but is an optimization
opportunity for us.
I think this is what I am running into. It is a very large text file.
My guess is that you have a large dependency tree, and that you're
running into 1).
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
