Integrate `swift_version` DSL support into pod targets
7 files changed
tree: 271d12bb60613126753ac76a4f2b325eed269752
  1. .circle-scripts/
  2. .github/
  3. bin/
  4. examples/
  5. lib/
  6. spec/
  7. .gitattributes
  8. .gitignore
  9. .gitmodules
  10. .kick
  11. .rubocop.yml
  12. .rubocop_cocoapods.yml
  13. .rubocop_todo.yml
  14. .travis.yml
  15. .yardopts
  16. CHANGELOG.md
  17. circle.yml
  18. cocoapods.gemspec
  19. CODE_OF_CONDUCT.md
  20. CONTRIBUTING.md
  21. Dangerfile
  22. Gemfile
  23. Gemfile.lock
  24. LICENSE
  25. NOMENCLATURE.md
  26. Rakefile
  27. README.md
README.md

CocoaPods Logo

CocoaPods: The Cocoa dependency manager

Build Status Gem Version Code Climate

CocoaPods manages dependencies for your Xcode projects.

You specify the dependencies for your project in a simple text file: your Podfile. CocoaPods recursively resolves dependencies between libraries, fetches source code for all dependencies, and creates and maintains an Xcode workspace to build your project.

Installing and updating CocoaPods is very easy. Don't miss the Installation guide and the Getting Started guide.

Project Goals

CocoaPods aims to improve the engagement with, and discoverability of, third party open-source Cocoa libraries. These project goals influence and drive the design of CocoaPods:

  • Create and share libraries, and use them in your own projects, without creating extra work for library authors. Integrate non-CocoaPods libraries and hack on your own fork of any CocoaPods library with a simple transparent Podspec standard.
  • Allow library authors to structure their libraries however they like.
  • Save time for library authors by automating a lot of Xcode work not related to their libraries' functionality.
  • Support any source management system. (Currently supported are git, svn, mercurial, bazaar, and various types of archives downloaded over HTTP.)
  • Promote a culture of distributed collaboration on pods, but also provide features only possible with a centralised solution to foster a community.
  • Build tools on top of the core Cocoa development system, including those typically deployed to other operating systems, such as web-services.
  • Provide opinionated and automated integration, but make it completely optional. You may manually integrate your CocoaPods dependencies into your Xcode project as you see fit, with or without a workspace.
  • Solve everyday problems for Cocoa and Xcode developers.

Sponsors

Lovingly sponsored by a collection of companies, see the footer of CocoaPods.org for an up-to-date list.

Collaborate

All CocoaPods development happens on GitHub. Contributions make for good karma and we welcome new contributors with joy. We take contributors seriously, and thus have a contributor code of conduct.

Links

LinkDescription
CocoaPods.orgHomepage and search for Pods.
@CocoaPodsFollow CocoaPods on Twitter to stay up to date.
BlogThe CocoaPods blog.
Mailing ListFeel free to ask any kind of question.
GuidesEverything you want to know about CocoaPods.
ChangelogSee the changes introduced in each CocoaPods version.
New Pods RSSDon't miss any new Pods.
Code of ConductFind out the standards we hold ourselves to.

Projects

CocoaPods is composed of the following projects:

StatusProjectDescriptionInfo
Build StatusCocoaPodsThe CocoaPods command line tool.guides
Build StatusCocoaPods CoreSupport for working with specifications and podfiles.docs
Build StatusCocoaPods DownloaderDownloaders for various source types.docs
Build StatusXcodeprojCreate and modify Xcode projects from Ruby.docs
Build StatusCLAideA small command-line interface framework.docs
Build StatusMolinilloA powerful generic dependency resolver.docs
Build StatusCocoaPods.appA full-featured and standalone installation of CocoaPods.info
Master Repo Master repository of specifications.guides