CocoaPods Dependency Management #4
Comments
|
Hi Rob, Your project looks intriguing. Do you have many users? I've noticed that Does CocoaPod have the ability to run arbitrary commands? If you look Can this be easily accomplished by CocoaPod or would iOS Ports need to be --David M. Syzdek On Thu, Jul 5, 2012 at 10:17 AM, Rob W <
|
|
Sorry for any confusion, but I'm actually just a dev that has recently converted to CocoaPods in our team. We are going through our dependencies and saw that iOSPorts hasn't been added to the CocoaPods repo, so I was beginning to write a new Pod for your project and wanted to check with you. From the looks of usage, CocoaPods looks like its taking off in the Obj-C community just like Maven or Ivy did for the Java community. To comment on your concerns, I think having this as a Pod might make things easier for new iOS developers to use your ports. I'm fairly new to CocoaPods and am going through the process of adding a new Pod to the repo, so I will find out how it manages the makefiles. Since each individual framework can be opened and built on it's own, I don't think there will be a compatibility problem, but I will find out. |
|
If you haven't already written the new pod, let me know and I'll start chipping away at integrating iOS Ports with CocoaPod. |
|
I started with OpenSSL but ran into a bug with the CocoaPods gem. My podspec for it is included in the bug report. Once they push a fix, I will try again and see if I can get it working. |
|
Ok, now that they have updated the gem over the weekend, I gave it another go. Here is the podspec so far: Here is the output for when I build the project. So my guess is we need to figure out how to tell the podspec to use the make file as the target? |
|
A pre install hook can be used to run the make file. Pod::Spec.new do |s|
def pre_install(pod, target_definition)
Dir.chdir(pod.root){ `sh make.sh` }
end
end |
|
Has there been any progress on this? |
I'm working on adding your ports to the CocoPods repository to enable dependency management of your frameworks and wanted to check in with you to make sure I'm doing this right.
http://cocoapods.org/
I'm going to split up iOSPorts into 5 separate CocoaPods as you have listed in your readme and then include the inner dependencies as needed. Something I noticed is that each dependency has a different license which can be accounted for in each CocoaPod.
Also, I am going to add a CocoaPod for iOSPorts project that includes all 5 of the inner dependencies to allow devs just just include everything. This will have your license on it.
Does this sound correct? Did you want to help out with the process?
Thanks
The text was updated successfully, but these errors were encountered: