Skip to content
A cocoapods plugin enables static framework for all pods
Ruby
Branch: master
Clone or download
Latest commit 7d8b91d Jul 2, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
lib
spec Initial commit Jan 3, 2018
.gitignore Initial commit Jan 3, 2018
Gemfile Initial commit Jan 3, 2018
Gemfile.lock simply files Jul 3, 2018
LICENSE.txt update file Jan 4, 2018
README.md Update README.md Jul 1, 2019
Rakefile Initial commit Jan 3, 2018
cocoapods-static-swift-framework.gemspec simply files Jul 3, 2018

README.md

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

You can’t perform that action at this time.