Re:iOS Static Libraries Are, Like, Really Bad
by seivan on Sunday January 12, 2014 @04:35PM
(#7047549)
+1, cocoapods is really great and solves 99% of the issues.
EDIT: Issues I had with integrating third party libs into projects as dependencies in the past, not issues in regards to the blog post.
Re:iOS Static Libraries Are, Like, Really Bad
by therealkerni on Sunday January 12, 2014 @06:00PM
(#7047871)
You might want to read the blog post again: CocoaPods does NOT solve the mentioned issues or provides the system that should be made available for developers as it exists on OS X.
Re:iOS Static Libraries Are, Like, Really Bad
by seivan on Sunday January 12, 2014 @06:22PM
(#7047934)
Sorry, you're right, but still mean my own issues with dealing with third party libraries, it does help out quickly adding something so I could get to use it.
Re:iOS Static Libraries Are, Like, Really Bad
by teacup50 on Sunday January 12, 2014 @04:41PM
(#7047567)
Except for all the issues that the article goes into great detail describing, and not without cost. CocoaPods is even mentioned in there, at the very end.
Apple needs to fix this before they've shamelessly let it sit for an entire decade. CocoaPods is just a partial band-aid.
Re:iOS Static Libraries Are, Like, Really Bad
by LinaLauneBaer on Sunday January 12, 2014 @06:56PM
(#7048033)
In my experience you spend more time fixing strange Cocoapods issues than you save using it.
This is true for both, people using existing pods and for people creating new pods. The whole process is just frustrating IMO.
In addition Cocoapods does not solve the problems described in the article.
And if you have to distribute static libs Cocapods again makes it much easier.