I do a uconfigure and then a umake. If it doesn't work perfectly, it
gets me really close.
You may need to update your config script using a recent version of
autoconf, automake, and libtool.
Don't do this.
Doing the above with autoconf based source will not yield a correctly
working universal binary.
There are two issues at hand; cross compilation and simultaneously
compiling for two architectures (as per the above recommendation).
Autoconf can support cross compilation, but most projects that use
autoconf do not support cross architecture compilation. Good
projects that don't will actually spew an error and refuse to
configure when targeting something other than the local host's
architecture. Bad projects will merrily configure "correctly" and
then suck up various architecture specific configuration parameters
from the local system's architecture.
The real problem is that passing "-arch i386 -arch ppc" completely
bypasses the per-architecture configuration features of autoconf.
Autoconf works by testing a bunch of crap on the system, often by
compiling little bits of test code to see if various functions,
features or bugs are present. The results of all these tests are
typically quantified in a bunch of variables and #ifdefs spread across
makefiles and header files.
By specifying '-arch i386 -arch ppc', you are effectively telling the
project to build for two different architectures where both should use
all the configuration from whatever architecture the files happened to
be compiled on!
The end result will be incorrect. The resulting problems may be
obvious or, more likely, they might be incredibly subtle. Depending
on how you are using the compiled product, you might get really lucky
and have something that seems like it works.
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