Add section around why we can only support all Frameworks or all Libraries about guides.cocoapods.org

[segiddins]

@mrackwitz / @neonichu could either of you please do this?

[neonichu]

I have to pass, because I am also not sure anymore about the reasons.

[AliSoftware]

According to @mrackwitz in Slack just now:

[It was] to avoid complexity, because there are situations, where you wouldn't be able to ensure that you can build it in that way, and we don't have the tooling in place to check if e.g. a vendored framework is static or dynamic

[AliSoftware]

I think we should also explain somewhere in the guides why a pod containing Swift must be compiled as a framework and can't be a static library. The reason being because of ABI compatibility issues, as the runtime is evolving (this can simply be a simple link to this Apple's blog post but it needs to be mentioned somewhere in CP guides anyway IMHO)

[drewcrawford]

So essentially the rant that originally inspired this issue's filing was correct on the facts. It's not impossible to support both, it's just a question of effort.

I think this isn’t done for a few reasons. One, it’s hard. It’s harder to write a tool that can [mix frameworks/libraries/etc.] then it is to do one.... This is all fair. The thing is, either it’s worth doing it to share code with each other or it’s not.

[scionwest]

Does this mean that you can not use a library like SSKeychain/AFNetworking with a framework like Alamofire on the same project via cocoapods?

[segiddins]

@scionwest no, since those libraries would be built as Frameworks :)

[scionwest]

Hmm, it's weird then why as soon as I add use_frameworks! the SSKeychain & LiveSDK (only two non-frameworks I have) can no longer have their types found. I get an 'identifier not found' compiler error. While AlamoFire works fire due to being a Swift framework. I remove use_frameworks! and AlamoFire can't be found but LiveSDK & SSKeychain can be.

[orta]

Probably worth making a stack overflow issue for this. As alamofire is a swift library it has to have use_frameworks.

[scionwest]

I actually do already have an issue on Stackoverflow for this. http://stackoverflow.com/q/31103831/1815321

[segiddins]

You should be using modular import statements with frameworks, that will probably solve your issue.

[neonichu]

Yep, only module imports work in the bridging header when using frameworks. Also, you might want to get rid of the bridging header entirely, as it is unnecessary when using frameworks, they can be imported directly in Swift.

[scionwest]

That solved my issue perfectly. Thanks for the help!