Skip to content
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

Fix bitcode generation for Release builds #2567

Merged
merged 1 commit into from
Sep 24, 2015
Merged

Fix bitcode generation for Release builds #2567

merged 1 commit into from
Sep 24, 2015

Conversation

conradev
Copy link
Contributor

The current binary release of Realm for watchOS is unsuitable for submitting to the App Store.

It was compiled with -fembed-bitcode-marker and not -fembed-bitcode, meaning the bitcode section is size 1, or empty:

$ otool -l ./realm-objc-0.95.1/watchos/Realm.framework/Realm | grep -A 5 __bundle
  sectname __bundle
   segname __LLVM
      addr 0x00184000
      size 0x00000001
    offset 1589248
     align 2^0 (1)

This is because BITCODE_GENERATION_MODE is normally set to marker when building, and only set to bitcode when archiving. I assume this is for performance reasons.

This pull request embeds bitcode in all Release builds.

@realm-ci
Copy link
Contributor

Thanks for the PR, @conradev! We'll need you to accept our Contributor License Agreement before we can merge your contributions.

Cheers,
The robots and humans at Realm

@jpsim
Copy link
Contributor

jpsim commented Sep 24, 2015

Thanks a lot for this, and for explaining what was wrong. Your thoroughness is appreciated.

If this fix is indeed correct (and it sure looks like it is), I imagine the same should be done for the iOS Dynamic scheme as well as the RealmSwift.xcodeproj xcconfig.

tgoyne added a commit that referenced this pull request Sep 24, 2015
Fix bitcode generation for Release builds
@tgoyne tgoyne merged commit b0f51a8 into realm:master Sep 24, 2015
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants