What? Why?

I got my hands on a RG350M - a portable, MIPS32, Linux based handheld portable using the OpenDingux distribution - for the purpouse of low-spec handheld Rust game development without signing a bunch of NDAs.

Quick Start

1. Install rustup on Linux (Windows WSL OK)
2. Install VS Code
3. Open this directory in VS Code
4. Optionally install workspace recommended VS Code extensions
5. Connect the RG350M via USB (see Debugging the USB Connection bellow)
6. Run the default build task (Ctrl+Shift+B).
   May require sudo password (to auto-install dependencies / rust stubs)
7. The build should have auto-deployed. If you couldn't get your USB connection working, however, you can manually copy target/package.opk onto your device's SD card, in the APPS folder.
8. Otherwise, see the apps in the new rust category on your RG350M!
9. Profit!

Debugging the USB Connection

• If you can ping/telnet/ssh into 10.1.1.2 as root, you're good to go!
• Use the USB2/USB/DC port, not USB1/OTG
• The cable that came with your RG350M may not work properly for data. I had to use another cable, even though Windows half-recognized the USB connection.
• Windows 10's preinstalled "Remote NDIS" driver should just work (tm).
• On the device, run settings > Network. scripts/deploy.sh assumes:
  • IP address: 10.1.1.2
  • Username: root
  • Password: none (not actually network connected)

Installed Dependencies

• /opt/gcw0-toolchain from http://www.gcw-zero.com/files/opendingux-gcw0-toolchain.2014-08-20.tar.bz2
• rustup toolchain install nightly-2020-06-15 --component rust-src --profile=minimal
• cargo install xargo --version "^0.3"

License

Licensed under either of

• Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
• MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Takeaways

• egl is unsound as heck and unmaintained
• khronos-egl 's pkg_config isn't cross compilation friendly
• egli for the win?