Allow static library usage from Cocoapods

[bridger]

Version 1.4.0 of Cocoapods allows a pod to be used as a static library, even in a Swift app. It requires the library's podspec to contain s.static_framework = true.

I believe this will help apps launch faster. Here's a blog post that explains why too many dynamic frameworks slows down launch: https://blog.automatic.com/how-we-cut-our-ios-apps-launch-time-in-half-with-this-one-cool-trick-7aca2011e2ea

[thomasvl]

I couldn't find much in the way on details for this on the Cocoapods site.

What does this do from the POV of Swift Modules? Does the library remain a module on its own, or does it lump all the pods into a single static library that shares a module? For Swift's visibility, it would seem like an important detail as it could mean apis are exposed that aren't meant to be (anything internal and what code counts as getting access to those).

[mackoj]

This might help CocoaPods/CocoaPods#6966 to answer your questions.

[bridger]

It looks like CocoaPods v1.5 lets the app decide if the dependencies are static or dynamic. http://blog.cocoapods.org/CocoaPods-1.5.0/ This issue can be closed now. Thank you!