Re: Any supported way to build a static lib with both ARM and x86 (simulator) binaries?
Re: Any supported way to build a static lib with both ARM and x86 (simulator) binaries?
- Subject: Re: Any supported way to build a static lib with both ARM and x86 (simulator) binaries?
- From: Nick Blievers <email@hidden>
- Date: Wed, 16 Jul 2014 20:27:49 -0500
- Acceptlanguage: en-US
- Thread-topic: Any supported way to build a static lib with both ARM and x86 (simulator) binaries?
On 17 Jul 2014, at 10:59 am, Dave Camp < email@hidden> wrote: On Jul 16, 2014, at 4:35 PM, Jens Alfke < email@hidden> wrote: On Jul 16, 2014, at 2:18 PM, Nick Blievers < email@hidden> wrote: I use a post build step on my CI that runs lipo to join the simulator (i386/x86_64) and device (armv7/armv7s/arm64) objects, which is effectively your #2.
How do you get both of those libraries to build, though? As I said, it seems you have to either switch the scheme destination in the GUI or invoke xcodebuild.
I use an Aggregate target with a Run Script phase that executes two xcodebuild commands (one for sim, one for device) and then lipo them together. Build that to generate the final shippable framework/library.
I do pretty much exactly the same thing, but I call xcodebuild twice in my jenkins config. An aggregate target is probably a nicer idea, I should look into that.
Nick
|
_______________________________________________
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