Pod dependencies

[djbe]

How would you go about creating a pod with dependencies? Currently there is no use of CocoaPods in either the module project or the example app project.

[fulldecent]

In the example app project you can add a podfile and run pod install as usual. That approach is used in this project https://github.com/CocoaPods/pod-template/pull/187

Some use that approach to add UI testing to the example app.

[djbe]

Funnily enough, I saw your pull request there pointing to this repo, thus the question. Won't doing this break the existing (generated) workspace?

I don't ask it for UI testing reasons, more because I'm creating pods that depend on other pods.

[fulldecent]

Hmmm, I think it should work. Because the only special thing that workspace is doing is depending on the module.

I haven't thought about this issue yet. Mainly because my only goal so far is to steal what AlamoFire is doing so well and distilling it into a reusable template. The problem is that I don't know any projects that are organized as beautifully as AlamoFire and also have CocoaPods dependencies so that I can steal their ideas :-)

[djbe]

Allright, I did the following steps:

• Deleted existing workspace
• Removed "link with" old framework
• Added Podfile in example directory
• pod install

Seems to work. Only thing for now, using your sample project, is that the image doesn't load. The bundle it refers to is this:

.../iOS Example.app/Frameworks/TestLib.framework

Whereas the image's path is actually:

.../iOS Example.app/Frameworks/TestLib.framework/TestLib.bundle/wk.png

Podfile:

platform :ios, '9.0'
inhibit_all_warnings!
use_frameworks!
source 'https://github.com/CocoaPods/Specs.git'

target 'iOS Example' do
    pod 'TestLib', :path => '../'
end

[fulldecent]

Thank you, great help. This is very good progress.

[djbe]

The thing is, I don't know if there should be a step in the configure script asking if you want to have pod dependencies, or just document what steps are needed for people that want it.

[djbe]

Replacing

let bundle = Bundle(for: type(of: self))
let image = UIImage(named: "wk", in: resources, compatibleWith: nil)

with

let bundle = Bundle(for: type(of: self))
let resources = Bundle(path: bundle.path(forResource: "TestLib", ofType: "bundle")!)
let image = UIImage(named: "wk", in: resources, compatibleWith: nil)

fixes the image issue.

I imagine this is something that's needed when the module is installed via cocoapods. No idea about SPM or Carthage, never used those.

[fulldecent]

Thank you. In general I would like to provide extra instruction for people that would want this.

Personally I think CocoaPods as a dependency manager will go out of style immediately when SPM takes off. I think of CocoaPods as a publishing outlet but I prefer not to build it in as a dependency. That's why it will be "extra work" if people want to use it for their dependency manager. People might want to use Carthage or SPM and this should be compatible with that.

Sorry if all this sounds theoretical. I plan on replacing all my projects to be based off of this template so I am hoping to get it right :-)

[djbe]

Fair enough.

When do you think SPM will take off? Last I heard was that it's still in early stages.

[fulldecent]

Apple states is schedule for release as part of Swift 3.

Swift 4 is scheduled for Fall 2017, so I expect SPM before then.

[djbe]

Closing this.

[fulldecent]

Thanks for all the discussion here. I have added a note the the README.md referencing here.