So you want to build an iOS Framework with a static library - which isn’t supported
And you want that static library to be in Swift, which isn’t supported either, explicitly I thought, especially given that Swift apps embed copies of runtime libraries because they change between even minor versions let-alone major ones And then you want to hope that even though you used Swift 2 the library code is sufficiently similar that it allows linking with Swift 1.x on Xcode 6 And you want to build that code with a compiler which, although very good for a beta, is preview 1, most definitely has quite a lot of bugs in it and is most definitely not designed for building shipping code And you want to do that for a paying client to ship apps to paying customer I don’t think I would do this any more than I’d try learning to juggle lighted torches at a gas station. I’d build it in Swift 1.<latest shipping>, deal with the things which are harder in that version but save time trying to work around 2-3 unsupported things. And then I’d also get some sleep at night. > On 18 Jun 2015, at 00:47, Rick Mann <[email protected]> wrote: > > Of course! And this is complicated enough that I should probably do just > that; I'm sure to screw it up more than once. > >> On Jun 17, 2015, at 06:04 , Alex Zavatone <[email protected]> wrote: >> >> Any way for you to try a short proof of concept? >> >> Like one that displays an alert message? >> >> Back in ye olde Macromedia days, I was always reminded to switch to a simple >> case to get past issues like these. >> >> On Jun 15, 2015, at 7:36 PM, Rick Mann wrote: >> >>> I've been tasked with developing a Framework to allow third parties to >>> embed our content in their apps. I'm hoping to do this with an embeddable >>> iOS Framework that contains a compiled .a file. This may require some >>> shenanigans around Xcode for distribution. >>> >>> Assuming that works, if I compile this with Xcode 7 and write it in Swift >>> 2, but set the deployment target to iOS 8.0, will a user of Xcode 6 (and >>> Obj-C) be able to embed this Framework in their app? Will they be able to >>> publish to the App Store with Xcode 6 (assuming my Framework doesn't use >>> any new APIs, etc.)? >>> >>> I'd like to do this project in Swift 2, but our clients absolutely must be >>> able to submit to the store and use Xcode 6, at least until Apple requires >>> Xcode 7. >>> >>> Thoughts? Thanks, >>> >>> -- >>> Rick Mann >>> [email protected] >>> >>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Xcode-users mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/xcode-users/zav%40mac.com >>> >>> This email sent to [email protected] >> > > > -- > Rick Mann > [email protected] <mailto:[email protected]> > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Xcode-users mailing list ([email protected] > <mailto:[email protected]>) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/xcode-users/rols%40rols.org > <https://lists.apple.com/mailman/options/xcode-users/rols%40rols.org> > > This email sent to [email protected] <mailto:[email protected]>
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
