-
Notifications
You must be signed in to change notification settings - Fork 204
Added missing flag for enabling bitcode #32
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
Conversation
Hi @dev4dev It seems |
@leavez I don't see where in that SO post stated that they are the same. At other posts I googled, it was mentioned that both of them are required, to include bitcode. To be honest, I haven't tested only |
and by the way, thanks for the plugin, it saved a lot of build time, just packing Realm into a framework |
Very glad to hear that. And sorry about the slow response as I'm too busy these days. @X140Yu Could you take care of this? |
Hi @dev4dev , When I try to archive some target with pod Realm inside with But after changing the build option to Also according to this SO link, it seems like only using So could you change the setting to |
@X140Yu I'll try to test this on our CI soon, and will let you know the result |
Just in case, I can confirm that "BITCODE_GENERATION_MODE=bitcode" is a necessary change in our project. Without it "archive" action failed trying to link some app code (apparently bitcode enabled, verified it through the logs) with the framework generated by this plugin. |
'OTHER_CFLAGS="-fembed-bitcode"' is removed in commit |
Added missing flag for enabling bitcode
No description provided.