Re: Xcode 2.4 and shared workgroup build
Re: Xcode 2.4 and shared workgroup build
- Subject: Re: Xcode 2.4 and shared workgroup build
- From: "William H. Schultz" <email@hidden>
- Date: Tue, 19 Sep 2006 14:31:29 -0700
I was actually really excited about us getting a MacBook Pro, as I expected this to cut down on build times even more. This was a rather frustrating change. I tried all kinds of things to get Xcode to compile to both machines, including setting both machines as dedicated build machines. This didn't even work, as it's too flakey to be useful. I've successfully gotten command line builds to work with distcc, but Xcode overrides my manual attempts at telling distcc which machines to use. It's rather annoying. This was one of the major benefits of Xcode over Visual Studio, but now that's gone, or rather not cost effective.
------------------------------- Hank Schultz Cedrus Corporation On Sep 15, 2006, at 11:25 PM, Dix Lorenz wrote: On Sep 15, 2006, at 12:17 AM, Ondrej Valik wrote:
Hello. Switching from Xcode 2.2.1 to Xcode 2.4 I realized that shared workgroup builds are behaving differently. We have two intel iMacs which are both shared for distributed compilation. One of them is used by developer who builds our software in Xcode. In 2.2.1 Xcode was using both iMacs for compilation (six simultaneous compilation processes), but Xcode 2.4 is using only remote iMac and local machine does not compile anything (no overhead in Activity Monitor and only four simultaneous compilation processes). We assured several times that everything is properly configured, both macs are sharing for shared workgroup build and both are visible in Bonjour set. We even tried Trusted set with both mac manually added.
So my question: is there anything that I am missing or is this correct behaviour (maybe it was introduced already in Xcode 2.3 but we skipped this version because of Debugger step over issues)? And if so is there any expert option which could enable old 2.2.1 behaviour?
Using both computers in the 2.2.1 way means for us huge time saving so this new change makes distributed builds for us completely unusable.
Apple changed the behaviour at some point (I think 2.3 although traces of it showed up earlier) and since then I can't use distributed compiling anymore. My main machine is a lot faster than the other machines and to have 4 cores just sitting idle makes no sense. I filed a bug in January (#4402261) and this one actually got answered: "Engineering has determined this issue behaves as intended". Well, so much for using dc until I buy a few more Quad Cores...
Dix
|
_______________________________________________
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