CocoaPods manages library dependencies for your Xcode project.
You specify the dependencies for your project in one easy text file. CocoaPods resolves dependencies between libraries, fetches source code for the dependencies, and creates and maintains an Xcode workspace to build your project.
Ultimately, the goal is to improve discoverability of, and engagement in, third party open-source libraries, by creating a more centralized ecosystem.
Or, if you’re already using CocoaPods, you can find the changelog here, which contains an overview of the changes in recent versions.
Downloading and installing CocoaPods only takes a few minutes.
CocoaPods runs on Ruby. To install it run the following commands:
$ [sudo] gem install cocoapods
If you want to have CocoaPods generate documentation for each library, then install the appledoc tool:
$ brew install appledoc --HEAD $ ln -sf "`brew --prefix`/Cellar/appledoc/HEAD/Templates" ~/Library/Application\ Support/appledoc
Now that you've got CocoaPods installed you can easily add it to your project.
If you're using a fresh out of the box Mac with Lion using Xcode from the Mac App Store, you will need to install the Command Line Tools for Xcode first: here
CocoaPods re-uses some of the RubyGems classes. If you have a version older than 1.4.0, you will have to update RubyGems:
$ gem update --system.
Search for Pods by name or description.
$ pod search json --> JSONKit (1.4, 1.5pre) A Very High Performance Objective-C JSON Library. - Homepage: https://github.com/johnezang/JSONKit - Source: https://github.com/johnezang/JSONKit.git --> SBJson (2.2.3, 3.0.4, 3.1) This library implements strict JSON parsing and generation in Objective-C. - Homepage: http://stig.github.com/json-framework/ - Source: https://github.com/stig/json-framework.git
After you've found your favorite dependencies you add them to your Podfile.
$ edit Podfile
platform :ios pod 'JSONKit', '~> 1.4' pod 'Reachability', '~> 2.0.4'
And then you install the dependencies in your project.
$ pod install
Remember to always open the Xcode workspace instead of the project file when you're building.
$ open App.xcworkspace
Sometimes CocoaPods doesn't have a Pod for one of your dependencies yet. Fortunately creating a Pod is really easy.
$ pod spec create Peanuts $ edit Peanuts.podspec $ pod spec lint Peanuts.podspec
There are several other ways to start using any library without a Pod specification, which can be seen in the SSCatalog example.
All CocoaPods development happens on GitHub, there is a repository for CocoaPods and one for the CocoaPods specs. Contributing patches or Pods is really easy and gratifying. You even get push access when one of your specs or patches is accepted.
Follow @CocoaPodsOrg to get up to date information about what's going on in the CocoaPods world.
- @fngtps is donating time to work on the design of the forthcoming cocoapods.org website and donated the money to hire Max Steenbergen to design an icon for it.
- @sauspiel uses CocoaPods for their games and have hired me to add features and specs they needed. These are Nimbus, QuincyKit, and HockeyKit. For the Nimbus spec, the ‘subspecs’ feature was added.
- “I am crazy excited about this. With the growing number of Objective-C libraries, this will make things so much better.” –– Sam Soffes
- “Are you doing open source iOS components? You really should support @CocoaPodsOrg!” –– Matthias Tretter
- “So glad someone has finally done this...” –– Tom Wilson
- “Anybody who has tasted the coolness of RubyGems (and @gembundler) understands how cool CocoaPods might be.” –– StuFF mc
- “I will be working on getting several of my Objective-C libraries ready for CocoaPods this week!” –– Luke Redpath
- “Really digg how @alloy is building a potential game changer” –– Klaas Speller
- “@alloy's making an Objective-C package manager. This is fantastic news kids!” –– Josh Abernathy
- “A package manager for Cocoa/Objective-C, built with @MacRuby. Awesomeness!” –– Johannes Fahrenkrug
- “This is awesome, I love endorsements!” –– Appie Durán