On Sat, Jun 23, 2018, 12:26 PM Mats Wichmann <m...@wichmann.us> wrote:
> On 06/23/2018 11:19 AM, Gregg Reynolds wrote: > > On Fri, Jun 22, 2018, 5:13 AM < > sabaripriya.rangasamy_...@lnttechservices.com> > > wrote: > > > > ... > > > >> > >> "Pods/iotivity/iotivity.framework/iotivity(ocprovisioningmanager.o)' > does > >> not contain bitcode. > >> > > Check the verbose output of the build to see if this module was compiled > > with -fembed-bitcode. My guess is not. You may need to go thru all the > > Scons files to make sure they do the right thing for iOS. > > and indeed, if places _other_ than the ios-specific script > (build_common/ios/SConscript or possibly build_common/darwin/SConscript > due to the shared nature of those two) seem to need changing, do let me > know. I'm trying to continue the transition to as much as possible of > "needed for given platform" flags to the platform-specific setup! (I > know there are still exceptions to that) > 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. G > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9733): https://lists.iotivity.org/g/iotivity-dev/message/9733 Mute This Topic: https://lists.iotivity.org/mt/22499995/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
