Xcode2Rust makes 2D apps and games written in Rust accessible and deployable in Xcode.

Xcode2Rust is currently under development and functionality is not yet complete.

It opens a Metal based window or screen on macOS, iOS or tvOS (using Xcode) and passes the content of the BGRA8 surface texture to a Rust library for drawing. Xcode2Rust also passes user events and gestures to the Rust library.

Xcode2Rust has similar functionality as the pixels crate which I use heavily for my applications (like Eldiron). You can prototype your app in pixels and once you want to deploy it to the Apple AppStore you can do that via Xcode2Rust with no headache. Window setup, deployment and AppStore settings are a breeze because you use Xcode directly for upload.

Xcode2Rust has a minimal Rust API, located in the rustapi folder of this repository. The current API looks like this:

#[no_mangle]
/// Draw into the pixel buffer
pub extern "C" fn rust_draw(pixels: *mut u8, width: u32, height: u32) {
}

#[no_mangle]
/// The target framerate, if 0, only update on demand, i.e. when one of the user event functions below return true.
pub extern "C" fn rust_target_fps() -> u32 {
}

#[no_mangle]
/// Mouse down or touch down event
pub extern "C" fn rust_touch_down(x: f32, y: f32) -> bool {
}

#[no_mangle]
/// Mouse dragged or touch dragged event
pub extern "C" fn rust_touch_dragged(x: f32, y: f32) -> bool {
}

#[no_mangle]
/// Mouse up or touch up event
pub extern "C" fn rust_touch_up(x: f32, y: f32) -> bool {
}

The example library in the the rustapi folder defines a global DISC class which draws a white circle (multitthreaded via rayon). You can drag the circle with the mouse.

Change the example library to fit your need, compile the library and copy the target/release/librustapi.a file into rustapi/libs.

Thats it, after this re-compile the Xcode project for the given platform, copy the resulting .a file into the rustapi/libs folder and your app or game will start inside Xcode.

You can specifiy the target framerate with the rust_target_fps() function. A game would just specify something like 30 or 60. An app can also set the framerate to 0, this means that the view is only updated on demand. In this case a refresh happens when one of the user event functions (like rust_touch_down) returns true. The boolean return value indicates to Swift that the view needs to be refreshed, for example when a button has been clicked in the app.

Additionally, each time a user event function returns true and the fps is 0, rust_target_fps() will be called again to see if the framerate needs to be changed. Imagine the user clicks a button to play a small animation, you would want to set the fps to 60, and when he presses stop you can set it to 0 again.

The example library sets the target framerate to 0 and returns true for rust_touch_dragged() when the disc has been dragged, and this way only updates the view when needed.

But again, for a game you would just set the target fps to a specific value and be done with it.

When you change the example library you will need to recompile it.

For a macOS build, you can just compile the rustapi library with cargo build --release and copy the resulting target/release/librustapi.a to the rustapi/libs folder.

For iOS builds I currently use cargo lipo --release --targets aarch64-apple-ios (you can install lipo with cargo install cargo-lipo). Copy the resulting target/aarch64-apple-ios/universal/librustapi.a file to rustapi/libs/librustapiios.a. Note that this library works only on devices, not in the simulator. Normally cargo lipo --release should create a binary for both the simulator and devices, however for me the build fails right now for some reason.

• Provide all user events and gestures to the Rust API (mouse and keyboard events, gestures).
• Although the overall goal for Xcode2Rust is to draw via the CPU, some 2D Metal based hardware accelerated blit operations (for example for tiles and sprites) should be possible.

• Hardware accelerated 3D operations.