Enhancements to Xcode building (incl. Mac static library support)#16
Enhancements to Xcode building (incl. Mac static library support)#16zwaldowski wants to merge 3 commits intolibffi:masterfrom zwaldowski:master
Conversation
Signed-off-by: Zachary Waldowski <[email protected]> Also support a Mac static library via Xcode. Signed-off-by: Zachary Waldowski <[email protected]>
Signed-off-by: Zachary Waldowski <[email protected]>
…. Don't always regenerate config files. Signed-off-by: Zachary Waldowski <[email protected]>
|
Thanks! 16 years old for real? In any case, I've merged your changes. Thanks again. AG |
|
zwaldowski - could you please look at this... |
|
Terribly sorry, man, the Xcode project was including dlmalloc.c separately Sincerely, On Fri, Apr 27, 2012 at 10:29 AM, Anthony Green <
|
|
Can you send me a pull request for the fix so I can put it in 3.0.12? AG On Fri, Apr 27, 2012 at 10:48 AM, Zachary Waldowski
|
|
Sure. I also have some fixes for the ARM assembly on some new-style assemblers, like the LLVM one. I don't know if you know anything about ARM assembly (because I know nothing), but I'll add those in as well? |
2 participants
I started working on an Xcode project today, and, oh look, somebody's already done it. Changes over the just-plain iOS library are nominal; the only things I really changed on that front are the name of the target (
ffitolibffi iOS, still producing alibffi.a) and the release target (iOS 4.0).The Mac version is an almost identical version of the setup, producing only x86_64 and i386 targets against the latest OS X SDK. A far more skilled Python developer than I could probably take a crack at unifying the two systems.
Some tiny adjustments are made to allow building iOS and OS X from the same tree. Also, the scripts are added to Xcode as build scripts so that one can simply open the libffi.xcodeproj and build for a fully functional static library in under 30 seconds, no terminal required. These adjustments also allow for iOS and OS X library production to be entirely automated for use in something like CocoaPods as a dependency. No specific hard-coded changes are made to the tree for that, however.