Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: How do I build universal binaries for libraries with endian-specific code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How do I build universal binaries for libraries with endian-specific code

Subject: Re: How do I build universal binaries for libraries with endian-specific code
From: Gerben Wierda <email@hidden>
Date: Tue, 4 Oct 2005 08:38:36 +0200

I build an app which is compiled on 10.3.9 with XCode 1 (foo.pbproj) for PPC with Mac OS X 10.2.8 as target. The same code base is used to compile it under XCode 2 (foo.xcodeproj) on 10.4.2 with ppc and i386 as architecture and 10.4 as target because there are no i386 libraries for 10.2 available. Both Xcode's write results in different locations.

In a shell script phase at the end of my XCode 2 build, I replace the ppc binary parts of the fat files with the ppc binaries from the XCode 1 build using the lipo tool. That gives me an app compiled for i386 and ppc, but the ppc is compiled with 10.2 as target. This is Apple's own preferred procedure for this nasty situation (I got this from dev support when I asked if there would be 10.2 libraries for i386 architectureso I can build my app universal *and* backwards compatible).

Unix level libraries like libpng may or may not handle double arch flags during compile (some do, some don't because they use other compiler flags which conflict with "-arch ppc -arch i386"). If they do not handle them, I compile separately for both architectures and then use lipo gain to glue them together afterwards.

PS. As I wrote off list, a universal compile is in fact multiple compiles, each with its correct defined value for BIG_ENDIAN etc. You do not need to worry about this and it will work fine. You do not need to change your code. _______________________________________________ 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 Prev by Date: Arguments are not being passed correctly -- Please help Next by Date: Re: Arguments are not being passed correctly -- Please help Previous by thread: Re: How do I build universal binaries for libraries with endian-specific code Next by thread: GetAliasSize vs. sliasSize Index(es): Date Thread