In article <1169377525.348002@[EMAIL PROTECTED]
>,
Michael Ash <mike@[EMAIL PROTECTED]
> wrote:
> 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.
*THAT* is a good point, but then AFAIK gcc doesn't perform any
parallelization
-- one invocation of gcc equals one process, no parallel builds. Even if
gcc is
compiling for two archs from one invocation of gcc, I believe that still
happens
on a single processor.
Ben
--
If this message helped you, consider buying an item
from my wish list: <http://artins.org/ben/wishlist>
I changed my name: <http://periodic-kingdom.org/People/NameChange.php>
|
