-
Notifications
You must be signed in to change notification settings - Fork 420
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cocoapods Support? #111
Comments
We have that in the list. gRPC and BoringSSL are in Cocoapods already. |
@muxi why does the podspec say it’s incomplete? |
@AttilaTheFun I started the podspec and ran into problems, so I renamed it to avoid over-promising (since it didn't work). I'm not a Cocoapods user, so am hoping @muxi can help from his experience with Objective-C gRPC. |
@muxi @timburks I tried forking the library and linting the podspec. I got an error about a double-import from the boringSSL module map. I googled around about the error and I think it has since been fixed, but the version of gRPC-Core depended on by this library is significantly out of date. (1.0.1 vs 1.9.1 which is current). When I tried to bump the gRPC-Core version to 1.9.1, I got a bunch of compile errors because I think this library used some non-backwards compatible APIs. Is it possible to get grpc-swift to be compatible with the latest version of grpc-core? |
Btw here is the discussion about the issue I see currently: |
I have created a Podspec depending on the latest
Not sure if this is production ready yet (I might have missed something and it generates a lot of warnings because Note that generated code currently refers to the For now, I'm solving this by running
after running the codegen (assuming the generated code is in the |
@MrMage I tried adding your branches as dependencies in my pod file but was unable to install them because I don't believe they're published to the master specs repo. I then attempted to clone your forks and push your pod specs to my private repo, and the gRPC-Core spec didn't validate. This was the output of the failed validation:
|
@AttilaTheFun Sorry, the
Could you try using those Also, what happens if you just try using them, regardless of what the linter says? I did not touch the gRPC Podspec at all (my only change in that repo is MrMage/grpc@21897a6), yet it works for me. |
Hey @MrMage - getting closer! This time I was able to successfully pod install, but I got a build error for grpc: |
Could you just try the official gRPC-Core pod then? |
Also, not sure why not including inttypes.h should make memcpy unavailable. |
@MrMage I tried the official pod and still got the same error. After some googling I found out I could fix it by replacing |
Feel free to send a PR over to the gRPC team already :-) Note, though, that that patch might go into the v1.10-dev branch, which isn't yet working with my CocoaPod (or the SwiftGRPC library itself, I've forgotten). |
@MrMage, is this expected to be working at this time?
However, compiling fails with this error:
Am I missing any steps? |
This issue blames to aa746f8. Going beyond that though, looks like the For anybody else, this should work:
|
Thanks for figuring this out. We are still moving a lot of things around, but once the dust has settled I plan to fix the podspec. I have just filed grpc/grpc#14640 to get the |
@dhavalcue FYI, I updated the Podspec: #180 |
I added the pod:
There are compile errors: Is the |
s.dependency 'gRPC-Core', '~> 1.11.0-pre2'
s.dependency 'BoringSSL', '~> 10.0'
s.dependency 'SwiftProtobuf', '~> 1.0.3' I updated |
I'm interested in using this library for a prototype Swift iOS application. It's nice that https://github.com/apple/swift-protobuf allows for installation. I was wondering if it would be possible to offer the SwiftGRPC.xcodeproj through Cocoapods, though I suppose it would require BoringSSL, CgRPC, gRPC, and CzLib all be available through Cocoapods as well.
The text was updated successfully, but these errors were encountered: