No release in over 3 years
Low commit activity in last 3 years
There's a lot of open issues
use static framework for Swift
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.3
>= 0

Runtime

>= 1.5.0, < 2.0
 Project Readme

cocoapods-static-swift-framework

A cocoapods plugin that enables static frameworks for all pods.

Cocoapods only supports static framework at pod level, which means an option in podspec and just valid for that pod. By using this plugin, we can make all pod to static framework with only one word!

(There's 'swift' in the plugin name as it's originally built for swift. You can also use it for pure objc project too.)

Usage

Install via gem:

$ gem install cocoapods-static-swift-framework

Add the following to your podfile:

plugin 'cocoapods-static-swift-framework'

NOTE: Static frameworks is still using framework, not static library. So don't forget to add use_frameworks!

NOTE: From cocoapods 1.7, the generated resource bundle specified with s.resource_bundle in podspec, will not be copied to the .framework folder. It's a default behavior of cocoapods.

About Static framework

Why

Too many dynamic frameworks will increase app boot time dramatically, also the Copy framework build phase will expend unendurable time in the code-build-run loop. (There is also a dyld crash) Static framework have no these problems.

What is a static framework

First of all, what is a framework? Framework is just a bundle with specifications to organize files, for whom xcode provides convenient methods to link bianry and copy resources.

Static framework, or precisely static-linking framework, has no official defination. There's only (dynamic) framework. "When linking, it found that the binary in the framework is static-linking, then it will link the binary staticaly. There's no special handling." an Apple engineer answered me at WWDC.

Resources in static framework can't be copied to app's main bundle automatically. If you use cocoapods, it will handle it automatically, but not for the manual integration.

The binary in the framework will be linked statically, as its name, to the main binary. There's no framework file in the Framework folder of the app bundle. Resources will copied to app bundle's root path. So there's a potential bug of conflict of resource file names.

requirement

  • Xcode 9+
  • cocoapods 1.5+ (v1.7 tested)

License

MIT

Appreciate a 🌟 if you like it. Another cocoapods plugin made by me to improve pod compile time: cocoapods-binary