On Sep 29, 2009, at 18:53:28, Bill Bumgarner wrote:
If it were tuned for the worst case scenario that only a few
projects encounter, then a boatload more people would complain that
build times are super long and why the heck is Xcode only compiling
1 or 2 files at a time?!?!?
Xcode 2.5 on 10.5 handled 16 threads with ease and never caused this
same project to grind to a halt. It was slicker 'n snot.
Some questions:
1) Have you tried compiling your current source with 2.5 on Leopard?
Yes, just a couple weeks ago before I installed 10.6.
I.e. did you change something in your source that caused gcc to
start consuming a boatload more memory than it did before?
Nope. Nada.
2) When compiling on Leopard, how many simultaneously compilation
jobs did you see?
16. 3.2 was only compiling 15 at a time - assumedly 1 was saved for
object code housekeeping or for the user's sanity.
3) Has the # of simultaneous compilations default been changed/
customized?
_______________________________________________
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
