Skip to content
This repository has been archived by the owner on Sep 27, 2024. It is now read-only.

Latest commit

 

History

History
164 lines (117 loc) · 5.74 KB

README.md

File metadata and controls

164 lines (117 loc) · 5.74 KB
Raw

wysiwyg-ffi

Rust code that can be used to generate Kotlin and Swift bindings for wysiwyg-rust.

Setting up Rust

1. Install Rust

See the installation guide.

2. Configure cross compilation

Configure Rust for cross compilation to any target platforms you'll need.

# Android targets
rustup target add aarch64-linux-android # for most physical Android devices
rustup target add x86_64-linux-android # for Android emulator on PC
rustup target add i686-linux-android # for 32-bit Android emulators
rustup target add armv7-linux-androideabi # for older devices

# iOS targets
rustup target add aarch64-apple-ios
rustup target add aarch64-apple-ios-sim
rustup target add x86_64-apple-ios

Building for Android

Ensure you have first completed the steps to install and configure Rust.

1. Install the Android SDK

The simplest way to do this is by installing Android Studio.

2. Install the Android NDK

Find the required NDK version by searching for ndkVersion in platforms/android/library/build.gradle.

Now install the NDK, the simplest way being to use the Android SDK manager from within Android Studio.

Note: If you decide to install the NDK manually, you must still use the "side-by-side" structure (i.e. the NDK must be inside the Android SDK directory, in a path like ~/Android/Sdk/ndk/22.1.7171670).

Note: at time of writing (2022-06-28) you needed to use android-ndk-r22b or earlier, because later versions fail with an error like ld: error: unable to find library -lgcc. See rust-lang #85806 for more.

3. Point Cargo to the NDK

Create a Cargo config at bindings/wysiwyg-ffi/.cargo/config.toml to tell Cargo where to look for the NDK during cross compilation (more details in the Cargo reference).

Add any platforms that you need to target to this file, replacing instances of NDK_HOME with the location of your NDK (for example/home/andy/Android/Sdk/ndk/22.1.7171670).

# bindings/wysiwyg-ffi/.cargo/config.toml

[target.aarch64-linux-android]
ar = "NDK_HOME/toolchains/llvm/prebuilt/linux-x86_64/bin/ar"
linker = "NDK_HOME/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android30-clang"

[target.x86_64-linux-android]
ar = "NDK_HOME/toolchains/llvm/prebuilt/linux-x86_64/bin/ar"
linker = "NDK_HOME/toolchains/llvm/prebuilt/linux-x86_64/bin/x86_64-linux-android30-clang"

Note: You may need to add additional targets, for example i686 if you use a 32-bit emulator.

Note: this file is ignored in the top-level .gitignore file, so it won't be checked in to Git.

4. Building

Building the Android library

The following command builds the whole library and deploys it to Maven local for local development.

# Ensure ANDROID_HOME is set correctly!
make android

Building the shared object

cd bindings/wysiwyg-ffi
cargo build --target x86_64-linux-android --release

This will create:

../../target/x86_64-linux-android/release/libuniffi_wysiwyg_composer.so

To strip the libraries and make them smaller:

NDK_HOME/toolchains/x86_64-4.9/prebuilt/linux-x86_64/bin/x86_64-linux-android-strip \
    ../../target/x86_64-linux-android/debug/libuniffi_wysiwyg_composer.so

Building for iOS

Ensure you have first completed the steps to install and configure Rust.

  • Build shared object:
cd bindings/ffi
cargo build --release --target aarch64-apple-ios
cargo build --release --target aarch64-apple-ios-sim
cargo build --release --target x86_64-apple-ios

mkdir -p ../../target/ios-simulator
lipo -create \
  ../../target/x86_64-apple-ios/release/libuniffi_wysiwyg_composer.a \
  ../../target/aarch64-apple-ios-sim/release/libuniffi_wysiwyg_composer.a \
  -output ../../target/ios-simulator/libuniffi_wysiwyg_composer.a
  • This will create static libraries for both iOS devices and simulators:
../../target/x86_64-apple-ios/debug/libuniffi_wysiwyg_composer.a
../../target/ios-simulator/libuniffi_wysiwyg_composer.a
  • Generate the bindings inside given output dir:
cargo uniffi-bindgen \
    --library ../../target/aarch64-apple-ios/release/libuniffi_wysiwyg_composer.a \
    --language swift \
    --config uniffi.toml \
    --out-dir MY_OUTPUT_DIR

cd MY_OUTPUT_DIR
mv *.h         headers/
mv *.modulemap headers/module.modulemap
mv *.swift     Sources/

The used library file is arbitrary the ARM64 one, but any could be used.

Note: The project should always have a single Swift modulemap file, and it should be named module.modulemap otherwise the generated framework will not expose symbols properly to Swift.

  • Generate the .xcframework file:
xcodebuild -create-xcframework \
  -library ../../target/aarch64-apple-ios/debug/libwysiwyg_composer.a" \
  -headers MY_OUTPUT_DIR/headers \
  -library MY_OUTPUT_DIR/libwysiwyg_composer.a" \
  -headers MY_OUTPUT_DIR/headers \
  -output MY_OUTPUT_DIR/ExampleRustBindings.xcframework"

Note: Generating with xcodebuild is not recommended as it might make the resulting library clash with other Rust libraries or even some C/C++ libraries. See this script in the root directory for further details.

Now you can use the framework wherever you see fit, just add the framework (as well as the generated Swift code from MY_OUTPUT_DIR/Sources/) as a dependency inside an existing XCode project, or package them with your preferred dependency manager. See Example Rust Bindings for a full example of how it all fits together.