capnfabs / crossbuild-spotifyd

How to cross compile a rust project w/ linux system libraries for the raspberry pi

crossbuild-spotifyd

Cross-compile the Rust Application spotifyd for the Raspberry Pi, using cross, multistrap.

This is the example repo for a blog post on capnfabs.net.

Checkout / Build instructions

These instructions assume you've already got Rust and Docker installed.

# Install cross (https://github.com/rust-embedded/cross)
cargo install cross

# Clone repo and spotifyd (pinned to a commit in a submodule)
git clone --recursive https://github.com/capnfabs/crossbuild-spotifyd
cd crossbuild-spotifyd

# Build and tag the docker container
docker build -t crossbuild:local .

# Switch into the spotifyd repo
cd spotifyd

# Tell Cross to use our new Docker container
echo -e '[target.armv7-unknown-linux-gnueabihf]\nimage = "crossbuild:local"' >> Cross.toml

# Build!
cross build --target=armv7-unknown-linux-gnueabihf --features=dbus_mpris

crossbuild-spotifyd's Issues

Very informative!

I try to make cross compile another Rust thing (RedisJSON plugin) but should use specific GLIBC. When compile it in docker I'd receive GLIBC_2.29 on target is libc_2.24.so
Do you have idea how to tell cargo build to use sepcific version of libc ?

PS: Something like that ?
https://capnfabs.net/posts/cross-compiling-rust-apps-linker-shenanigans-multistrap-chroot/#:~:text=Some%20quick%20googling%20reveals%20that%20this%20should%20be%20fixable%20by%20telling%20the%20gcc%20linker%20to%20look%20in%20a%20different%20system%20root.%20We%20can%20tell%20cargo%20to%20tell%20rustc%20to%20tell%20gcc%20to%20tell%20the%20linker%20(%F0%9F%98%85)%20to%20do%20that%20by%20setting%20the%20CARGO_TARGET_%3Ctriple%3E_RUSTFLAGS%20environment%20variable%20in%20the%20Dockerfile%3A