-
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
iOS bitcode compilation error (via Carthage) #377
Comments
@JonasVautherin @byuarus have you guys seen this before? |
@JonasVautherin I'm using CocoaPods, and I'm only compiling for macOS (i.e. without Bitcode). |
It was fine on 0.7.0 with CocoaPods – haven’t tried with master. So yes, only happens with Carthage for me.
…On 25 Feb 2019, 21:37 +1300, Jonas Vautherin , wrote:
Haven't, but I disable bitcode on my end.
@dekpient: does it only happen with Carthage?
@MrMage: do you compile with bitcode enabled on your side (using SwiftPM or CocoaPods)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Oh right, that probably means that SwiftPM doesn't enable bitcode when generating the xcodeproj, since SwiftPM doesn't know about iOS 😅. Should we add that in one of the patch scripts, e.g. fix-project-settings, because it already sets the iPhoneOS target? @dekpient: would enabling bitcode fix your |
@JonasVautherin I believe bitcode is already enabled by default. I could see Still, setting By the way, master is failing for Carthage since this commit. Could you guys run |
Yes that's an issue coming from the fact that the xcodeproj needs to be versioned. We don't want to update the xcodeproj for each commit, so the tradeoff is to generate it for each release. Meaning that Carthage only works with release tags (the rest is "undefined behavior").
I'd like to understand the root cause of this problem. Does SwiftPM set |
FYI, I'm updating the |
Ahh, so SwiftPM only supports macOS at the moment. I came across this Overture issue while researching this problem. Looks like they have switched to XcodeGen to generate their project – see PR#32. Their project.yml looks simple enough. It might worth a try. |
The CgRPC implementation is now officially deprecated; closing this for now. |
New Issue Checklist
Issue Description
Bitcode compilation error when exporting an iOS app that depends on Swift gPRC via Carthage (with default build config).
The issue seems to be around
LD_RUNPATH_SEARCH_PATHS = "$(inherited) $(TOOLCHAIN_DIR)/usr/lib/swift/macosx";
for SwiftProtobuf. Overriding the build config when running Carthage withLD_RUNPATH_SEARCH_PATHS = "$(inherited) @executable_path/Frameworks"
works around this issue, but it still sounds like bug to me – unless overriding build config is expected? Is there any documentation around this?Complete output when running grpc-swift, including the stack trace and command used
N/A
Environment
The text was updated successfully, but these errors were encountered: