Skip to content

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

Merged
merged 1 commit into from
Mar 17, 2019
Merged

Conversation

dev4dev
Copy link
Contributor

@dev4dev dev4dev commented Jan 9, 2019

No description provided.

@leavez
Copy link
Owner

leavez commented Jan 11, 2019

Hi @dev4dev

It seems BITCODE_GENERATION_MODE=bitcode and OTHER_CFLAGS="-fembed-bitcode" is doing the same thing. There should be only one flag here.

https://stackoverflow.com/questions/34959767/whats-the-difference-between-fembed-bitcode-and-bitcode-generation-mode

@dev4dev
Copy link
Contributor Author

dev4dev commented Jan 11, 2019

@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 BITCODE_GENERATION_MODE=bitcode without OTHER_CFLAGS="-fembed-bitcode", but OTHER_CFLAGS="-fembed-bitcode" only doesn't add bitcode into binary, because of that my builds failed. After adding BITCODE_GENERATION_MODE=bitcode now everything is ok. So these changes gave me working result

@dev4dev
Copy link
Contributor Author

dev4dev commented Jan 11, 2019

and by the way, thanks for the plugin, it saved a lot of build time, just packing Realm into a framework

@leavez
Copy link
Owner

leavez commented Jan 16, 2019

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?

@X140Yu
Copy link
Collaborator

X140Yu commented Jan 16, 2019

Hi @dev4dev ,

When I try to archive some target with pod Realm inside with OTHER_CFLAGS="-fembed-bitcode" setting, I got an error message like this,

image

But after changing the build option to BITCODE_GENERATION_MODE=bitcode, the error above has gone.

Also according to this SO link, it seems like only using BITCODE_GENERATION_MODE setting can do the work.

So could you change the setting to BITCODE_GENERATION_MODE=bitcode and remove the old cflags staff in your PR?

@X140Yu X140Yu added the bug Something isn't working label Jan 16, 2019
@X140Yu X140Yu self-requested a review January 16, 2019 16:16
@dev4dev
Copy link
Contributor Author

dev4dev commented Jan 17, 2019

@X140Yu I'll try to test this on our CI soon, and will let you know the result

@X140Yu X140Yu closed this in 2b683a5 Jan 18, 2019
@X140Yu X140Yu reopened this Jan 18, 2019
@grigorye
Copy link

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.

@ghost
Copy link

ghost commented Mar 11, 2019

can we merge this and release? I'm available to help if needed because I use this in my project ☺️ @X140Yu @leavez

@leavez leavez merged commit b4d1492 into leavez:master Mar 17, 2019
@leavez leavez added this to the 0.4.2 milestone Mar 17, 2019
@leavez
Copy link
Owner

leavez commented Mar 17, 2019

'OTHER_CFLAGS="-fembed-bitcode"' is removed in commit 30cbf7f1

leavez added a commit that referenced this pull request Mar 17, 2019
Added missing flag for enabling bitcode
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants