cross VS termux-adb-fastboot

To compile a program with musl on a glibc system you can use cross-rs!

I cross compile to Mac, bsd, windows, etc cross ... Works great for me with either docker or podman.

If docker is available for you, https://github.com/cross-rs/cross is another and reliable way to solve this kind of problem. I do use it regularly.

We are using https://github.com/cross-rs/cross.

There is some built-in support in rustc for cross-compiling, but getting the build to actually work can be tricky due to the need for an appropriate linker. Instead, we’re going to use the Cross crate, which used to be maintained by the Rust Embedded Working Group Tools group.

I have used cross before to cross compile from Linux to other Linux. It has a section on it's wiki about this. Maybe that could be of help.

You can use cross to build your application and copy the artifacts into an alpine armv7 container. It would also build faster due to using cross compilation rather than QEMU.

Looks like cross is the easiest way to get something cross-compiled but its Mac support is blocked behind building your own build image. Even that repo says that it might be broken.

Bonus: if you’re working with Rust and doing a lot of cross platform stuff, check out cross. It runs QEMU in docker so you can run tests on a bunch of different emulated targets easily- literally a one line setup, it’s kind of magical.

It's also not as naturally cross-compilable as Go, though that's partly a side-effect of not accepting being a semi-closed ecosystem to achieve that and cross exists as a stop-gap while things like cargo-zigbuild explore less drastic options.

Using only the device itself (you will need to be connected to wifi for this to work, these instructions are hot garbage): Install Termux from F-Droid. In termux install platform-tools adb/fastboot. Then Enable Wireless ADB, Settings-> System -> Developer Options -> Wireless Debugging, turn the slider to on, then get the port number from the Wireless Debugging sub menu get the port number. (Remember to turn off Wireless Debugging when done!). In Termux run adb connect localhost:PORT then check adb devices you should see an authorization prompt for a debug connection, you'll need the connection challenge code from settings (this authorization only needs to happen once). Then adb shell and run one of the commands below.

Termux for the help install in termux this: https://github.com/rendiix/termux-adb-fastboot pair your localhost:port with termux's adb connect to it and run adb shell wm size [Xres]x[Yres] -d [display number]

Just a heads up for anyone reading that tries this and finds it doesn't work: in the comments /u/-korni- linked to an alternative version of adb and I found that fixed the problem for me and the task works again.

There is a known bug with Samsung devices and the version of android-tools included in the repo. You have to use a different version of ADB to getaround the issue with the server not running right, I personally use https://github.com/rendiix/termux-adb-fastboot on my A32 5G. Not sure if others like termux-ADB work.

This one works; https://github.com/rendiix/termux-adb-fastboot

newest binary