search

googlesamples / ios-nearby

68 stars 30 forks source link

Unable to build a podSpec using NearbyMessages as a subSpec. #23

Open tstamm opened 7 years ago

tstamm commented 7 years ago

NearbyMessages does not have binary slices for x86_64 & i386. this makes it impossible to be used in a dependancy in a prodSpec. since "pod trunk push" and "pod lint" pre-flight in the simulator.

Does anyone know how to work around this?

dan-webb commented 7 years ago

Hello,

I'm able to build the NearbyMessagesExample app for the simulator, and when I run 'file Pods/NearbyMessages/Libraries/libGNSMessages.a', it lists i386, armv7, x86_64, and arm64.

But I'm not familiar with subspecs, so I wonder if something is going wrong there. Perhaps someone with knowledge of subspecs can help.

TomStammActv8 commented 7 years ago

Dan-webb:

I lipo'd all the binaries from google and you are correct then have the x86_64 & i386 binaries. It seems when CocoaPods builds the static library (I also tried dynamic frameworks) the interim build from the Pods project is obly building armv7 and arm64. then my binary errors out when invoking libtools (i386 & x86_36)

dan-webb commented 7 years ago

Tom,

Here's a discussion about a problem that looks similar. Is it helpful at all? https://github.com/CocoaPods/CocoaPods/issues/6309

I see that you've asked about the problem on StackOverflow. http://stackoverflow.com/questions/41992225/unable-to-create-a-cocoapod-subspec-with-a-3rd-party-dependancy-with-missing-i38 You may want to edit your question to say that the architectures are present in NearbyMessages, but missing in the build of your subspec library.

TomStammActv8 commented 7 years ago

Dan:

Thanks so much for your input. Currently we’ve been able to play-passed-it by doing two separate builds. Build to active Arch = YES. Then build to a simulated device to get the i386 & x86_64 slices. Do a separate build to “Generic iOS Device” to get the armv7 & arm64 slices the merge them together.

Best Regards, :Tom

From: Dan Webb notifications@github.com Reply-To: googlesamples/ios-nearby reply@reply.github.com Date: Friday, February 10, 2017 at 4:39 PM To: googlesamples/ios-nearby ios-nearby@noreply.github.com Cc: Tom Stamm tom.stamm@actv8me.com, Comment comment@noreply.github.com Subject: Re: [googlesamples/ios-nearby] Unable to build a podSpec using NearbyMessages as a subSpec. (#23)

Tom,

Here's a discussion about a problem that looks similar. Is it helpful at all? CocoaPods/CocoaPods#6309https://github.com/CocoaPods/CocoaPods/issues/6309

I see that you've asked about the problem on StackOverflow. http://stackoverflow.com/questions/41992225/unable-to-create-a-cocoapod-subspec-with-a-3rd-party-dependancy-with-missing-i38 You may want to edit your question to say that the architectures are present in NearbyMessages, but missing in the build of your subspec library.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/googlesamples/ios-nearby/issues/23#issuecomment-279104324, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AStGmeAudDxOGZWml0BZWpy56DE6bb3lks5rbQNHgaJpZM4L40u1.

This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. ACTV8me, Inc. is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.