-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Cocoapods support #190
Comments
It's not, at least insofar as I could figure out: CocoaPods compiles the libraries into a single .a file, which won't work for Sparkle because it needs to additionally compile an external helper executable to actually perform the copy and relaunch steps (an app can't overwrite itself while running).
|
hi @andymatuschak, cocoaPods supports frameworks. You may consider to generate the Sparkle.framework file. Then submit it to cocoapods like this: |
It's not enough to just make a framework: Sparkle is a framework which contains a .app that is also itself compiled as part of the project. |
@andymatuschak I think @ohsc means you should consider publishing a new framework binary (i.e. newer than 1.5b6). CocoaPods can easily integrate these, no matter what they contain. I have already created a working pod spec for 1.5b6, but I'm hesitant to push it, because that version is so old (and Debug builds don't work because of an old bug). |
Ah. Now that is indeed something I should do. I guess I'm hesitant to do it without sandboxing support, but I'm also not really making any progress on that, so maybe I should just do it. On Jan 16, 2013, at 2:36 PM, Nikolaj Schumacher notifications@github.com wrote:
|
@nschum do you still have the podspec for 1.5b6 handy? I'd love to integrate sparkle using cocoapods and would appreciate a starting point. |
There's really not much "integrating" in the spec. It's just an automated way of downloading the framework and adding it. Without an official version number and binary, there's so much manual work involved (compiling the binary, maintaining versions) that there's really no point in using CocoaPods just to copy it. Look at this pod to get an idea how it works: |
I just released a RubyMotion gem to make it even easier to integrate with Sparkle (motion-sparkle). The solution I've used to distribute Sparkle.framework is dubious. I'd love to use a CocoaPod, even if it is just to download and copy the framework. Maintaining a repository with just that code could be worth it at scale, even though the ideal would be to have a podspec. So I write to express my support for this issue and to ask for more pointers on how to tackle it. @andymatuschak, big thanks for Sparkle! |
👍 |
1 similar comment
+1 |
A pod would be appreciated :) |
Is Sparkle compatible with Cocoapods? I'm surprised to find that there's no pod spec for sparkle yet.
The text was updated successfully, but these errors were encountered: