rust-raspberrypi-OS-tutorials VS cross

I am very interested in this tutorial for building an OS for the Raspberry Pi in Rust: https://github.com/rust-embedded/rust-raspberrypi-OS-tutoria...

I'd love to try it out when (if ever) I have the time.

I like rust, low level and embedded hacking so I programmed a simple "kernel", based on this: https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials

So every week, I basically followed along these tutorials. I didn't even made an effort to fully understand the code I was copying, as I just didn't want to waste mental energy on it as I wanted that energy and time wasted on my focus at the time (C++ and JS). I did that for like a year, doing 1-3 tutorials/week from that site. Over the course of it, I got to build web apps, several compilers, several games mostly board games/3d shooters/2d multiplayer games, raytracers, peer to peer apps, building a networking stack, bots, blockchain apps, servers, PGP encryption, E2E encryption apps such as for messaging, built a NES emulator, virtual machines, simulators and graphics programming, etc. I'd say the longest one was learning to build a tiny OS on raspberry pi

Hello everyone, I'm not sure if this is possible, but I'll give it a shot. I have a raspberry PI zero and a linux host pc. I am trying to run stuff on the raspberry on bare metal, no OS below it (using this tutorial https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials/). Now in the tutorial 4 there is a step "flash the kernel onto SD card and insert the SD card into the raspberry". Now, given my lack of SD card adapter (I'm also curious) I wanted to ask if it is possible to deliver this kernel onto the raspberry without the SD card using USB.

I believe it already exists: https://github.com/rust-embedded/rust-raspberrypi-OS-tutorials

Is this just an alternative UI for GitHub but without the files? Am I missing something obvious? I'm confused.

Actual github repo for anyone looking for the files: https://github.com/rust-embedded/rust-raspberrypi-OS-tutoria...

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.