Gvr-unity-sdk: Add iOS Simulator support.

[dgoodine]

It should be a trivial task to add i386 and x86_64 slices in the static libraries. It's a significant burden on developers to not be able to run an app using the simulator if it links your code.

[miraleung]

We'll look into adding this for a future release. Thanks for the heads up!

[dgoodine]

Is there going to be any update on this?

[nathanmartz]

Those additional binaries add a lot of size to the plugin which is problematic for some users. We're looking into other options, so I've re-opened this issue.

[dgoodine]

First, post WWDC 2015, having unused architectures doesn't increase the downloaded binary side – those get stripped out on Apple's side when the app is prepared for distribution. So your users that have problems with the size being an issue are ill-informed. There was an issue where apps were getting rejected last year for having those slices in place (it false-triggered use of a non-public API), and, as is typical of Apple, there's been no confirmation that has been fixed.

The only other option would be to supply _two_ binaries, one with he ARM architectures, and another with the Intel architectures. That would be fine, as it's easy to combine them into the fat binary that people tend to typically use. (We're using 18 third party frameworks/libraries in our app, and yours is the _only_ one that doesn't include the Intel slices, or alternative .a files.)

When I dowloaded and checked out the native iOS Cardboard library, it did indeed include the Intel architectures. It shouldn't be too hard to implement either choice in your build process. As more and more Unity experiences move to a native iOS app container, this is going to be more and more important. Developing while needing to be tethered to a device is a very significant drag on productivity compared to working in the simulator.

[nathanmartz]

Sorry, I meant that for some developers the extra size hit was difficult. Cardboard is used around the world, including places where 100MB extra download is meaningful. Still, I agree with you that supporting the simulator is important and something we'll be looking at w/ the native integrations in Unity.

[dgoodine]

Ah, I see. Yeah, if that's a significant burden on some users, you could conceivably make two versions of each release, one for the device, one for the simulator. Or you could just open-source Cardboard and we could do the build. ;)

[alimoeeny]

Yeah, honestly, opensource the damn thing and avoid all the troubles and people can fix all the pesky little bugs,

[rusmaxham]

The x86_64 simulator binary of the native audio libs will be included in the next release of the SDK to enable simulator builds. If you don't need GVR Audio, you can remove those components from the SDK and build and run in the simulator with native Cardboard integration in Unity v5.6.