Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/keith/bazel-rust-mobile-demo
An example repository for using rust on iOS and Android with bazel
https://github.com/keith/bazel-rust-mobile-demo
Last synced: 3 days ago
JSON representation
An example repository for using rust on iOS and Android with bazel
- Host: GitHub
- URL: https://github.com/keith/bazel-rust-mobile-demo
- Owner: keith
- License: mit
- Created: 2022-05-10T18:23:36.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-07-27T18:19:55.000Z (over 1 year ago)
- Last Synced: 2024-10-12T06:08:16.984Z (about 1 month ago)
- Language: Starlark
- Size: 23.4 KB
- Stars: 63
- Watchers: 3
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# bazel-rust-mobile-demo
This is an example repository for how to setup a bazel build that uses
rust on iOS and Android. I also did [a talk](https://www.youtube.com/watch?v=e2ID05dpJzo)
on this at bazelcon.
## Usage
You can explore the code, which has some comments around the issues you
hit. You can also run each entry point to see them working.
For a standard `cc_binary` running on your host machine:
```sh
$ bazel run normal_binary
...
Ferris says hello!
Some value from rust: 42
```
For an `ios_application` (requires running on macOS with Xcode setup):
```sh
$ bazel run ios_app
...
com.example.iosapp: 25008
Ferris says hello!
Some value from rust: 42
```
For an `android_application` (requires the android SDK and an emulator
to be configured):
```sh
$ bazel mobile-install android_app --fat_apk_cpu=arm64-v8a --start_app
# View the result in the emulator, or view logs with 'adb logcat'
```
## Notes
- At the time of writing this setup was tested with bazel 5.1.1
- The key to targeting the right platforms until the iOS and Android
rules natively support bazel platforms is the
[`platform_mappings`](platform_mappings) file, and the `platform`
rules in the [`BUILD`](BUILD) file
([docs](https://bazel.build/concepts/platforms-intro#platform-mappings))
- If you don't want to use a root `platform_mappings` file you can pass
`--platform_mappings=path/to/platform_mappings`
- The `rules_rust` patch, and `android_armeabi` platform definition will
change with bazel 6.x since
https://github.com/bazelbuild/bazel/issues/14982 was fixed
- When testing Android, depending on your emulator or device you can
pass whatever `--fat_apk_cpu` value you need
- When testing with iOS you can pass whatever `--ios_multi_cpus` value
you need
- When using something like this in production you should checkout
[cxx](https://github.com/dtolnay/cxx) which helps bridge between rust
and C++
- This example doesn't include it but using
[cargo-raze](https://github.com/google/cargo-raze) works fine for
rust dependencies from our testing
- When using `cargo-raze` with the arm64 iOS simulator you need [this
patch](https://github.com/google/cargo-raze/pull/484) for some cases,
hopefully it's in a release soon
- When debugging `platform_mappings` issues,
`--toolchain_resolution_debug='.*'` is verbose but very useful
- If you find any other interesting gotchas when setting this up please
submit an issue or PR here so we can document them for the community!