Support for Raspberry Pi OS (at least bookworm) in cross-rs

[azachar]

Checklist

• I've looked through the issues and pull requests for similar request
• This feature could be solved with a custom image (optional)

Describe your request

I'm developing a library that depends on specific features of Raspberry Pi OS. I would like to inquire if there's a recommended base image in cross-rs tailored for Raspberry Pi OS development.

If such an image isn't available, could you provide guidance on creating a custom Docker image compatible with cross-rs? This would greatly assist in streamlining the development and deployment process for projects targeting Raspberry Pi devices.

Thank you for considering this feature request.

Describe why this would be a good inclusion for cross

Integrating support for Raspberry Pi OS into cross would significantly enhance its utility for developers targeting Raspberry Pi devices. Here's why this inclusion would be beneficial:

1. Streamlined Development Process:

   • Simplified Cross-Compilation: Currently, developers often face challenges setting up cross-compilation environments for Raspberry Pi OS, especially when dealing with external libraries and system dependencies. Native support within cross would abstract these complexities, providing a seamless experience.
   • Consistent Build Environment: By offering a standardized Docker image tailored for Raspberry Pi OS, cross would ensure consistent and reproducible builds, reducing issues arising from environment discrepancies.

2. Expanded User Base:

   • Appealing to IoT and Embedded Developers: The Raspberry Pi is a cornerstone in the IoT and embedded systems communities. Enhancing cross to support Raspberry Pi OS would attract developers from these sectors, broadening the tool's adoption.
   • Educational Outreach: Raspberry Pi is widely used in educational settings to teach programming and hardware interaction. Facilitating Rust development on this platform through cross would promote Rust as a language of choice for learners and educators.

3. Community and Ecosystem Growth:

   • Encouraging Contributions: With official support, the community can collaboratively maintain and improve the Raspberry Pi OS build environment, leading to more robust and up-to-date tooling.
   • Fostering Package Development: Simplified cross-compilation can lead to an increase in Rust-based packages optimized for Raspberry Pi, enriching the ecosystem with diverse and efficient libraries and applications.