Re: Universal build of cranky open source lib with a configure script
Re: Universal build of cranky open source lib with a configure script
- Subject: Re: Universal build of cranky open source lib with a configure script
- From: John Daniel <email@hidden>
- Date: Fri, 26 Jan 2007 10:40:26 -0600
On Jan 26, 2007, at 10:12 AM, John Daniel wrote:
It seems like the only viable solution is to configure for 10.2 PPC
and make, then configure for 10.4 intel and make, then lipo
together. I'll probably also need --prefix=/tmp/ppc and --prefix=/
tmp/i386. That's probably not the answer you wanted to hear :) It
may be ugly, but it is the most reasonable solution for me. Plus, I
can have 10.2 compatibility if I need it.
I just remembered! You don't want to do that either. Your binaries
could very likely have hard-coded paths to /tmp/i386 or /tmp/ppc
because the --prefix line says that is where they'll be installed.
What a mess!
Here is a another idea:
Avoid open-source code, if possible. Apple has given us quite a bit
already. Learn to use it and write cross-platform wrappers if required.
If you must use an open-source library, configure it to a non-native
platform. For example, if you have an Intel machine, do the following:
env CFLAGS="-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch ppc" ./
configure
Then hack up the makefile and add "-arch i386" right after the "-arch
ppc".
Build and test hoping that, if it is going to beak, it will break on
your primary test machine.
I apologize in advance if this idea is hopelessly dangerous and
stupid. At this point, I'm just confused. I've already wasted too
much time on it. Building the "official Apple way" has worked for me
so far.
John
_______________________________________________
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