Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
In order to build librustpad, rustspy and rust-poc, you'll need the following configuration after having installed the proper toolchain to your $PATH. The installation of arm-linux-gnueabihf-gcc toolchain is described on the README.md at the repository root. You can then set up your Rust toolchain for cross compilation with: rustup target add armv7-unknown-linux-gnueabihf.
Once that's done, you should add the following to your ~/.cargo/config:
[target.armv7-unknown-linux-gnueabihf]
linker = "arm-linux-gnueabihf-gcc"
After this, you will be able to build these projects with:
➜ rust-poc git:(master) ✗ cargo build --release --target=armv7-unknown-linux-gnueabihf
...
Compiling librustpad v0.1.0 (file:///home/main/Desktop/RemarkableFramebuffer/librustpad)
Compiling rust-poc v0.1.0 (file:///home/main/Desktop/RemarkableFramebuffer/rust-poc)
Finished dev [unoptimized + debuginfo] target(s) in 24.85 secs
Note that the --release argument is important as this enables optimizations and without optimizations you'll be looking at ~70% CPU utilization even when idle. With optimizations, rust-poc runs really light, 0% CPU utilization when idle and 1-2% at peak.