Creating your own CocoaPod is fairly straight forward. If you already have a separate component, you're most of the way there. This guide is an overview to the entire process, with the other guides in this section serving as more of a deep-dive for more advanced users.
We recommend letting CocoaPods do the hard work here. Running
pod lib create [pod name] will set you up with a well thought out library structure allowing you to easily include your files and get started quickly, we have a guide for this. If you'd like an up-to-date walkthrough of the whole process through to pushing to trunk, check out this 3rd party tutorial from tutsplus.
<The Pod Files
There are only a few differences between a CocoaPod and a generic open source library. The most important ones, aside from the actual source, are the
LICENSE. We do not accept libraries into the trunk without a code license. For information on what license to choose, we suggest reading this article on CodingHorror or tl;dr Legal.
You can work on the library from its folder on your system.
Alternatively you can work from an application project using the