Add framework support

[Rupert-RR]

Added a new project to provide targets for building AFNetworking as a dynamic framework.
Should facilitate using Carthage.

[mattt]

CocoaPods is the only supported means of integrating AFNetworking into projects. There are no current plans to integrate support for Carthage.

[Rupert-RR]

Fair enough, but Carthage is simply a use case. Surely having AFNetworking as a dynamic framework makes sense...

[mattt]

It's a question of support burden. CocoaPods guarantees that things work as expected. Dynamic Frameworks do not. Officially supporting them would increase the overall volume of issues and questions on Stack Overflow significantly.

[Rupert-RR]

I appreciate the overhead that would bring, and will use my fork for dynamic frameworks. But given where iOS development is headed (which would seem to be Swift and dynamic frameworks) and the fact that Cocoapods is currently building in support for dynamic frameworks I would have thought that this would be something that will be highly desirable in the long term.

[robb]

It would be really nice to have framework support, with or without Carthage support.

[kyledecot]

I agree with those above. +1 for carthage/dynamic support

[fsosa]

Framework support via Carthage or something similar would be greatly appreciated. +1 for this.

[krunk4ever]

👍 Would also love to see AFNetworking supported as a dynamic framework in the near future!

[robb]

Having a framework target wouldn't affect the CocoaPods integration at all, it could remain the official way to install AFNetworking while making life a little easier for people who use submodules.

[Igor-Khomich]

+1 for carthage

[andreyz]

I'd add a +1 vote for Carthage support

[csjones]

+1 for Carthage

[istx25]

+1 for Carthage

[istx25]

Oh, I just read the more long winded responses.

[istx25]

I feel like CocoaPods is starting to become outdated as new and better technologies are released. Carthage is an awesome alternative to CocoaPods and I don't really think there would be any reason not to support it. It won't get in the way of CocoaPods, just let the people who have adopted the new technology to embrace it in everything they use.

[bruceflowers]

+1 for Carthage and +1 for what he ^^^ says about CocoaPods.

[ekimia]

+1

[SilentChris]

+1 for Carthage support - I would be totally fine if the answer to any odd issue arising from using it as a dynamic framework was "install it using CocoaPods instead"

[danielphillips]

I would like to also put forward my +1 for framework support.

[lilyball]

+1. CocoaPods is a nightmare.

[andreyz]

For anyone who's tired (fruitlessly) banging their keys in this thread, point your Cartfiles to https://github.com/Automatic/AFNetworking. It's a Carthage supported fork.

[kcharwood]

We'll be looking into adding Carthage support in a future release. It's going to happen 🍻

[andreyz]

Thanks @kcharwood for good news :)

[istx25]

\o/ yay! 👍 🎊

[kcharwood]

It won't happen overnight, but its on the roadmap.

If anyone wants to start putting together a PR that makes it manageable, I'll be happy to dig into it.

[istx25]

@kcharwood If I remember correctly, It is very easy to support Carthage. Just share the target's scheme and voilà.

[redfearnk]

👍 Carthage

[kcharwood]

I remember it being slightly more complicated for this project, just don't have details off the top of my head

[jeryRazakarison]

+1 for Carthage ^^

[bluemarble]

+1 for Carthage! Thanks for putting it on the roadmap!

[kcharwood]

It is currently in the 3.0.0 branch.