Hi, using both of your processors can be done from within makefiles too.
the option is “-j2” for a two procc. machine. It might even be better to write a -j4. (experiment)
Another thing:
It is not needed to add the paths to frameworks in your LIBDIR.
the -framework settings do this for you.
Also: there is no reason to manually add -lstdc++.
this is done for when you are using the g++ compiler.
And as someone said erlier, gcc for ppc is not as fast as for x86 yet. But apple has done great strides in this compartment (they actually has the largest developement team on gcc Ive heard), and I think we have great things to come!.
If you want to keep your makefile platform independent, use “uname” (look at man page in terminal)
a “uname” call in the termnal yields “Darwin” on os x and “Linux” on linux and “IRIX64” on sgi.
I usually define my uname result into my app.
see example below.
<inMakefile>
PLATFORM_OSTYPE = $(shell uname)
oki silly stuff here… but…
ifeq ($(PLATFORM_OSTYPE) , Darwin)
CPP := c++
STATIC_CCFLAGS := -D$(PLATFORM_OSTYPE) -Wall
#…
#…
endif
#and whatever comes
</inMakefile>
the nice thing with defining the uname result during the compilation is that you can use this settings for
#ifdef checks in your code.
ex)
#ifdef Darwin
do Darwin specific stuff here…
#endif
Dont polute your code though!
I typically hide the usage:
like in my DataTypes.h
#ifndef __DATA_TYPE_H__
#define __DATA_TYPE_H__
#ifdef Darwin
#include "DarwinDataTypes.h"
#endif
#ifdef Linux
#include "LinuxDataTypes.h"
#endif
// etc..
#endif /* __DATA_TYPE_H__ */
oki hope this helpes. (got a bit carried away