Re: Building sqlite universal [was:Re: .a under version control]
Re: Building sqlite universal [was:Re: .a under version control]
- Subject: Re: Building sqlite universal [was:Re: .a under version control]
- From: Bill Bumgarner <email@hidden>
- Date: Thu, 18 May 2006 19:50:23 -0700
On May 18, 2006, at 7:19 PM, Peter O'Gorman wrote:
I installed the latest GNU tools, did `env LIBTOOLIZE=glibtoolize
autoreconf -fvi; ./configure
CFLAGS="-isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch ppc -arch
i386";
make' and got a fat sqlite.
Maybe so, maybe not.
The problem with autoconf is that it has absolutely no notion that
the compiler might produce binaries for more than one architecture at
a time. If there are any endian related bits in the SQLite source
tree (I honestly don't remember if there are), then they will likely
be set to the endian configuration of the architecture of your local
machine, even when compiling for the opposite architecture.
If the autoconf stuff is configured correctly, it will support cross
compilation. That tends to be a rarity, though.
More comments here:
http://www.friday.com/bbum/2006/04/10/universal-python-build/
b.bum
_______________________________________________
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