cocoapods-static-swift-framework - GitLite

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #typescript #go #machine-learning #macos #java #windows #awesome #cli #vue #mcp

cocoapods-static-swift-framework

(★ 253)

A cocoapods plugin enables static framework for all pods

파일 탐색기

최종 버전 다운로드 (.zip)

- - gem_version.rb
  - main.rb
- cocoapods-static-swift-framework.rb
- cocoapods_plugin.rb
- - framework_spec.rb
- spec_helper.rb
.gitignore
cocoapods-static-swift-framework.gemspec
Gemfile
Gemfile.lock
LICENSE.txt
Rakefile
README.md

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/leavez/cocoapods-static-swift-framework

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd cocoapods-static-swift-framework

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. Ruby

쉬움 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
Ruby bundle 명령어를 쓰려면 Ruby가 필요합니다.

bundle install

Gemfile에 명시된 루비 라이브러리를 설치합니다.

✅ bundle install이 에러 없이 끝나면 README에 안내된 실행 명령어(예: rails server)로 마저 실행해보세요.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# 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:

```ruby
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](https://github.com/Ruenzuo/cocoapods-amimono#why-would-you-want-this-plugin-in-your-podfile)) 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](https://github.com/leavez/cocoapods-binary)