Sparrow 2 and CocoaPods

Acnnair

Hi there!
Is there any chance to add Sparrow 2 to cocoapods? I'm already using pods to manage dependencies, including Sparrow 1 framework. In very near future I'm starting new project and would like to build it on Sparrow 2 and it would be awesome, if I could do that with pods.

tomekcejner

Hi!
I just pushed Sparrow 2 to CocoaPods specs repository, and it should work (tested on my project).

Acnnair

I looked yesterday on podspecs documentation and I try to create it myself too. I copied 1.4 podspec and everything looks good. But after I try to turn on SPViewController.showStats = YES;, it always crashed. I found that SPPoolObject has ARC disabled. So after some tweaking (GLKit.framework was missing too), this podspec works like a charm. Could you check it out? You can push it to specs repository if you want.

tomekcejner

Thanks for pointing this out - I was not using ARC in my project. I can push version with your changes to repository given the fact you are sure that it works correctly 🙂

I have hard time converting my project to ARC to verify, so I have to rely on you to tell if it works correctly 🙂

Acnnair

I'm not 100% sure, but it works for my ARC enabled project. I think, that you can push it to repo and if someone has problems, he probably find this thread on forum and we can sort it out.

tomekcejner

Your changes enabled ARC settings and added missing GLKit. However, it forces project to be ARC-enabled.

Was the 'no-arc' subspec supposed to give optional non ARC configuration? If yes, it probably does not work now, as it puts only single SPPoolObject into source list. Strange, I thought file list should be "inherited". I'll look into it. And there is need to define minimum deployment target in case of ARC.

P.S.
So normally (when not using pods) users are supposed to not include SPPoolObject in compiled sources when project is ARC enabled?

Acnnair

Are you sure that this forces your main project to be ARC enabled? Pods are compiled into one libPods.a static library, which you include in your main project. So it is up to you, if you are using ARC in your project or not.

Sparrow 2.0 is ARC enabled, except for SPPoolObject file. If you download sparrow archive from homepage, there is flag to disable ARC (-fno-objc-arc) only on SPPoolObject.m.

To podspec - Main root spec enables ARC for all files without SPPoolObject (exclude_files directive). The subspec 'no-arc' adds this file again to spec and disables ARC on it, so it is compiled properly. I added minimum deployment target, which is according to source files 5.0 (see Sparrow.h). Updated podspec is here.

When using Sparrow 2 without pods, you have to disable ARC on SPPoolObject with -fno-objc-arc flag in Build Phases -> Compile Sources.

It would be great if Daniel drops word or two here, so we will be sure 🙂

tomekcejner

Done.

I changed pod version to correct value (2.0rc), and added deployment platform requirement.
Example Podfile will look like below:

platform :ios, '5.0'
pod 'Sparrow-Framework', '~> 2.0rc'

Acnnair

Great!

I tested it out and everything looks good. Thanks for your help. 🙂

Daniel

Sorry for my late reply, I couldn't do any work this weekend!

I think you figured out everything correctly already:

Sparrow 2.0 uses ARC internally, except for "SPPoolObject", which *requires* ARC to be disabled
You can still use Sparrow with a non-ARC projects.

Thanks a lot for creating that CocoaPods spec! This makes working with Sparrow much easier, I definitely should add that information to the Wiki instructions!

noamgat

Sorry to bump this, but the current CocoaPods points to Sparrow v.2.0.1, while there is a v2.1rc.
I tried updating this myself, but I don't think I have permissions.

Daniel

Actually, the pod is not maintained by myself — perhaps one of the others could chime in?

In any case, I hope to make 2.1 final really soon, that would be a good moment to update the pod.

jdraymon

Pod specs don't really have maintainers, per se. I think I was the last one to update the spec before the great JSON migration, but I've been holding off doing so until the next revision is finalized. If you'd like, though, I can still put the RC out there

EDIT: It would appear cocoapods has transitioned the way they maintain Pod ownership. Looks like they're trying to have a single maintainer for each project. Daniel I don't know if you want to take that on or delegate to one of the little feathers, just let us know 🙂

jdraymon

@Daniel if I do go about updating this, are there now more files not using ARC than just

SPPoolObject

Daniel

Thanks a lot for the info, Jonathan! I plan to finally publish that blog post about the new version next week, so we can probably just wait for that.

I'd be very happy with some help with the Pod spec! I'm not using CocoaPods much, so I'm sure I'd make some stupid mistake. 😉

However, I'll definitely add the information about how to use it to the official documentation!

As for you last question: right now, Sparrow does not use ARC at all internally. Performance dictated to move back to MRC altogether.

Daniel

I just created a PodSpec for Sparrow 2.1, and I think it would make sense to add it directly to the main Sparrow repository.

Here it is:
https://gist.github.com/PrimaryFeather/b4276132a2023583627f

I ran into one problem: I had to name the project "Sparrow" instead of "Sparrow-Framework", because otherwise it would not find the header files when compiling. That's probably because in the latest version they are all referenced as

#import <Sparrow/SPWhatever.h>

instead of "Sparrow-Framework/SPWhatever.h", which is apparently what it would expect.

What do you guys think? Is that a problem?
And maybe someone with more experience with CocoaPods could look over it in general. I took the existing PodSpec as a blueprint.

Thanks in advance!

Shilo

SPWhatever! Can't wait to try it. Whatever the improvements are, i'm sure i'll love it!

membersheep

Thanks! Finally I can convert my current projects to 2.1!

Daniel

Hehe, so you discovered the secret new feature of Sparrow 2.1! ;-P

@jdraymon, I'd be happy about any input about the Podfile!

jdraymon

@Daniel Looks fine to me, though I don't understand your issues with imports - is it just a problem with existing projects/examples? When I use sparrow with cocoapods I use quoted imports e.g. "SPWhatever.h" instead of bracketed ones, Otherwise it does come up as <Sparrow-Framework/SPWhatever.h>. Might be a bad practice but it hasn't bitten me yet 😃 . I don't honestly know what cocoapods will do if you switch the name, though. It might add a new project to the repository. If you want to do the rename you might want to contact them directly, they probably have a better idea than I do.

As for putting it in the main repository, no reason that I know of not to.