Skip to content

Commit

Permalink
Update 2014-12-25-Pod-Authors-Guide-to-CocoaPods-Frameworks.markdown
Browse files Browse the repository at this point in the history
Thanks to @neonacho & @getaroon.
  • Loading branch information
mrackwitz committed Jan 23, 2015
1 parent 2728965 commit 6933ae5
Showing 1 changed file with 19 additions and 0 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -197,6 +197,25 @@ We have seen this error a few times during development.
An error like above can appear, if you develop a framework in Xcode, and you alter header visibility to fix build problems like described previously and try to ensure a clean build state by executing the Clean action (**⌘+
⇧+K** in Xcode). In this situation, it can be helpful to nuke the products build directory (alas `DerivedData`) manually from the file system.


## Availability

CocoaPods only supports Swift on OS X 10.9 and newer, and iOS 8 and newer.

Here's why:

- Swift is supported on OS X 10.9 / iOS 7 and newer, as stated by Apple numerous times.
- There is [no support for building static archives with Swift](http://openradar.appspot.com/radar?id=5536341827780608).
- Dynamic frameworks are supported on all versions of OS X.
- Dynamic frameworks are unsupported on iOS versions prior to 8:

> ld: warning: embedded dylibs/frameworks only run on iOS 8 or later.
From this we can conclude that it is **not possible** to support Swift on any platforms earlier than OS X 10.9 and iOS 8.

To use Swift libraries on apps that support iOS 7, you must manually copy the files into your application project.


## Updating

To install the latest Beta of CocoaPods you can run:

This comment has been minimized.

Copy link
@lexuanquynh

lexuanquynh Sep 27, 2016

what is this?

This comment has been minimized.

Copy link
@mrackwitz

mrackwitz Sep 27, 2016

Author Member

Do you mean which was the latest beta at this point? This doesn't matter anymore. This is more than a year ago. Meanwhile CocoaPods has reached 1.0 and you should really always use the latest stable version.

Please refrain from commenting on merged commits. Thanks.

Expand Down

0 comments on commit 6933ae5

Please sign in to comment.