On Sat, Jun 23, 2018, 12:34 PM Gregg Reynolds <[email protected]> wrote: ...
> > Also (from > https://www.google.com/amp/s/jonasdevlieghere.com/embedded-bitcode/amp/): > > "Xcode 7.0 introduced the ENABLE_BITCODE option. When enabled, this > passes -fembed-bitcode to clang when making an archive build, i.e. the > one you submit to the App Store" > > Which leaves open the possibility that you may need additional flags, > depending on what "making an archive build" means. > > Suggestion: build one of Apple's sample apps with ENABLE_BITCODE and > examine the resulting compile commands. That should tell what's needed. > Sigh. Then there's this: "For all other build types, -fembed-bitcode-marker is passed, which results in an empty __LLVMsegment, without any real content. This speeds up compilation while maintaining enough information to validate if all the files contain a bitcode section." So: 1. -fembed-bitcode-marker might do the trick here 2. For non-release builds, is -fembed-bitcode-marker required? Not clear to me. G > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9735): https://lists.iotivity.org/g/iotivity-dev/message/9735 Mute This Topic: https://lists.iotivity.org/mt/22499995/21656 Group Owner: [email protected] Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
