Tweaks to project to support Framework Project #3062
Conversation
cc @kcharwood and @kylef |
@kcharwood I also changed the release version from |
@@ -1,6 +1,6 @@ | |||
Pod::Spec.new do |s| | |||
s.name = 'AFNetworking' | |||
s.version = '3.0.0' | |||
s.version = '3.0.0-beta.1' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm confused with this change, isn't 3.0.0 already out? https://github.com/CocoaPods/Specs/blob/master/Specs/Alamofire/3.0.0/Alamofire.podspec.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops sorry, too late in the day. Mistaken AFNetworking for Alamofire.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sleep my man...sleep! 💤😉
I'm having trouble building using Carthage on 122f1b2, using Xcode 7.0.1.
|
Ignore this - I've realised that it's trying to build the tvOS target, but the SDK isn't provided on Xcode 7.0. Building with |
Thanks @cnoon. These all look good to me! 🍻 I'm also cool with the version name change. |
…e_tweaks Project - Framework Structure Tweaks
Dug through the new 3.0.0 structure and found a few things that could be condensed or unified. I tried to split each change out into a separate commit to make it easier to see what changes I actually made.
The only callout I have is that I changed the deployment target in the project on iOS to 8.0 to help the compiler out to generate non-compatible changes. However, the podspec is still supporting iOS 7.0 as a deployment target. Does CocoaPods handle the difference between 7 and 8 support for frameworks properly? I'm assuming it does, but wanted to ask. I've spent so much time in Swift over the last year, I'm not even sure how this works for Obj-C libraries.