Inicio Explorar Axuda
Iniciar sesión
andy
/
rust-on-ios
Seguir 1
Destacar 0
Fork 0
Código Incidencias 0 Pull Requests 0 Achegas 4 Lanzamentos 0 Wiki

Sen descrición

Rama: master
Ramas Etiquetas
rust-on-ios
ZIP TAR.GZ
Andy Dill e1f297214c Document the madness %!s(int64=5) %!d(string=hai) anos
librusty f7f33d7d06 It works! %!s(int64=5) %!d(string=hai) anos
unity f7f33d7d06 It works! %!s(int64=5) %!d(string=hai) anos
.gitignore 5336c23c68 Add librusty %!s(int64=5) %!d(string=hai) anos
README.md e1f297214c Document the madness %!s(int64=5) %!d(string=hai) anos

README.md

rust-on-ios

This is a quick proof-of-concept for a bitcode-enabled library built from Rust intended for consumption in an iOS app built in Unity (2018.4.11f1)

Unity defaults to embedding bitcode meaning all static dependencies must do likewise. Rust, by default, does not embed bitcode for static library targets. We can use -C lto -Z embed-bitcode to ask Rust to embed bitcode (afaict -C lto is required because the shipped iOS rust-std libs also need to embed bitcode.)

Naturally both Rust and Apple have forked LLVM and they are not always in-sync which is the current major problem outlined here. For Xcode 11.1 the latest Rust version we can use is nightly-2019-07-17.

Building

  • cd librusty
  • cargo install cargo-lipo
  • rustup target add aarch64-apple-ios
  • cargo lipo --targets aarch64-apple-ios --release
  • cp target/universal/release/librusty.a ../unity/Assets/Plugins/iOS/librusty.a

So, what?

Until Rust officially decides to support bitcode we have to jump through hoops in order to do so:

  • We must use a specific (nightly) compiler version
  • Xcode betas/updates may break linkability of our static library
  • Downstream developers may not all be on the same (latest) version of Xcode