• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode-way of using lipo to obtain universal binaries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode-way of using lipo to obtain universal binaries


  • Subject: Re: Xcode-way of using lipo to obtain universal binaries
  • From: Chris Espinosa <email@hidden>
  • Date: Thu, 16 Feb 2006 08:44:34 -0800


On Feb 16, 2006, at 8:29 AM, Kaspar Fischer wrote:

My project uses a library, which itself is configured using

autoconf (./configure blabla). In order to build a universal

library, I generated, once on a PowerPC box, once on a Intel

box, the config.h file for the respective build.


(In other words, I went for the approach where you build the

library twice; doing all in one step using "-arch ppc -arch i386"

did not work for me as some files need not even be compiled

in one build...)


What is the best way to implement something like this in Xcode?

I have the following in mind:


- add two subprojects, one generating the ppc library,

  one the intel library

- add a shell script phase that calls lipo to unify them


Is this the way to go?


You could just add the -arch ppc -arch i386 flags to your ./configure files.  But you'd really need to make sure that the built product ends up in a common directory where the application target can find it.

Is there some info somewhere on

the web illustrating how best to do this? (I could not find

anything.)


I have an example of building the PPC and Intel sides of an app separately then lipoing them together at http://idisk.mac.com/cdespinosa/Public/SDKExample

You might get some clues from the Run Script build phase in the aggregate target.

Can Xcode do the lipo step directly for me?


It does, but only if you build with an Xcode native targets, and eliminate the ./configure step.

Chris
 _______________________________________________
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

References: 
 >Xcode-way of using lipo to obtain universal binaries (From: Kaspar Fischer <email@hidden>)

  • Prev by Date: Xcode-way of using lipo to obtain universal binaries
  • Next by Date: Re: Beginner Questions (was no subject)
  • Previous by thread: Xcode-way of using lipo to obtain universal binaries
  • Next by thread: PPC and x86 target but build only one version
  • Index(es):
    • Date
    • Thread