Re: How to disable GCC parallel compilation of universal binaries?

In comp.sys.mac.programmer.help Ben Artin <macdev@[EMAIL PROTECTED]
> wrote:
> In article <1169124122.249350@[EMAIL PROTECTED]
>,
> Michael Ash <mike@[EMAIL PROTECTED]
> wrote:
> 
>> In comp.sys.mac.programmer.help Gabriele Greco 
>> <gabrielegreco@[EMAIL PROTECTED]
> wrote:
>> > I know it's a useful feature since I have a core duo processor, but
I'm 
>> > compiling quite heavy C++ sources and my machine has not enough
memory 
>> > to keep TWO instances of GCC compiling them in memory at once..
>> 
>> There is no reason to compile for both architectures during
development. 
>> Since your development machine is i386, kill the -arch ppc. You can put
it 
>> back when you're ready to build for deployment and, I suppose, just
suffer 
>> through the build times in that case.
> 
> That's irrelevant because Xcode will just spin off two i386 compiles
instead 
> when it sees 2 CPUs. The real question is how to tell Xcode how many
CPUs to 
> use, and I don't know the answer to that :-(

*That* is irrelevant because he's not using Xcode.

But as to the point you raise, a bit of searching turns up 
PBXNumberOfParallelBuildSubtasks. I have gobs of RAM and so I have never 
actually tried it, however. Parallel builds are Good For You.

-- 
Michael Ash
Rogue Amoeba Software