Cocoa tip for Cocoaheads Shanghai February 2016
0 likes228 views
This document summarizes the changes between CocoaPods version 0.39.0 and the upcoming 1.0.0 release. It outlines breaking changes to the Podfile format and new features like root options and deduplication. The document also previews an explanation of deduplication but notes it will not be fully explained until subsequent slides.
![What else is new?
(many things, but I will only list two)
(full list at https://github.com/CocoaPods/CocoaPods/
releases)
• Root Options let you use install! in your Podfile
to configure how you integrate your pods. Example:
install! 'cocoapods', :clean => false
• "Allow deduplication to take effect even when the
same pod is used with different sets of subspecs
across different platforms." --Marius Rackwitz
[what is that? next slides will explain it]](https://image.slidesharecdn.com/cocoatipforcocoaheadsshanghaifebruary2016-160226085152/85/Cocoa-tip-for-Cocoaheads-Shanghai-February-2016-7-320.jpg)
Cocoa tip for Cocoaheads Shanghai February 2016
- 1. a 5 minutes CocoaTip by ♥ February 2016 CocoaPods 1.0.0 beta 4
- 2. Transitioning to new CocoaPods • Latest stable version is 0.39.0 You install it with `gem install cocoapods` You use it with `pod _0.39.0_ <command>` • Latest beta version is 1.0.0 beta 4 You install it with `gem install cocoapods --pre` You use it with `pod <command>`
- 3. • .podspec stays the same • Podfile introduces breaking changes: • No more implicit target • No more link_with • No more :exclusive => true • No more :head • etc. With Cocoapods 1.0.0
- 4. • This is an example of Podfile for 0.39.0 • It will not work for1.0.0 • This is the equivalent Podfile for 1.0.0, using abstract_target • It will not work for 0.39.0
- 5. • This is an example of Podfile for 0.39.0 • It will not work for1.0.0 • This is the equivalent Podfile for 1.0.0, using a Ruby def • It will work for 0.39.0 as well :)
- 6. • You will have to replace :exclusive => true with inherit! :search_paths Sadly, you can't have a Podfile compatible for both versions for this feature. • You will have to replace :head with an explicit repository path using :git => '...' This solution is compatible with both versions, but requires that the repository has a .podspec inside. -> so, please, if you have your own pod, always include your .podspec inside your git repository :)
- 7. What else is new? (many things, but I will only list two) (full list at https://github.com/CocoaPods/CocoaPods/ releases) • Root Options let you use install! in your Podfile to configure how you integrate your pods. Example: install! 'cocoapods', :clean => false • "Allow deduplication to take effect even when the same pod is used with different sets of subspecs across different platforms." --Marius Rackwitz [what is that? next slides will explain it]
- 8. To understand deduplication xcworkspace... • Well, it was lie, you will not get the explanation on deduplication on this slide... • First, lets review a typical .xcworkspace structure: • 1 Workspace • multiple Projects for the Workspace • multiple Targets for each Project • multiple Configurations for each Project • many Schemes to link 1 Target with 1 Configuration (well, it's more complicated, but I'm simplifying)
- 9. The debug issue • If the classic setup is usually to have Debug & Release configurations, I found it more convenient to have DEV, QA, STAGE and LIVE configurations. • And I find it more convenient to have Debug, Release and Automation targets. • Previously, with Cocoapods 0.39.0 and multiple targets in your Podfile, all your pods would be, by default, configured in a unique state: "release" • Which means you were not easily able to properly debug something happening in a pod
- 10. The deduplication solution with 1.0.0 beta 4 released 24th February 2016 • The solution is very new!