Rust ESP32 Community Meeting 2021-08-03

[georgik]

Please add topics and links to this discussion.

The meeting is scheduled 3th August 2021 - 4pm CEST/GMT+2 via Google Meet. The meeting invite is automatically sent to attendees of previous meetings. If you'd like to join, please let me know.

[georgik]

Builds of tools

• build of 1.53.0 is available: https://github.com/espressif/rust-esp32-example/blob/main/docs/rust-on-xtensa.md
• build requirements: 20 GB of disk, 6 GB of RAM
• schedule of next Rust version releases
• CI pipeline update
• rustup for custom toolchain

Questions:

• Are we able to use llvm already built by Espressif instead of compiling it during Rust build?
• Are we able to build just dist of rust package? Rest of dist packages are not necessary to build and distribute.

[MabezDev]

Are we able to use llvm already built by Espressif instead of compiling it during Rust build?

You can with the --llvm-root option, however I am unsure how this works with dist. Hopefully it just copies what it needs from the prebuilt llvm toolchain into the rust build.

[ivmarkov]

• libStd and libc PRs submitted upstream
• Xtensa+RiscV+libStd (the same one that I submitted upstream) applied to Rust 1.54. @MabezDev - if you could review and merge to esp-rs/Rust
• Need feedback on this cargo-first build proposal with "native" ESP-IDF tooling (without PlatformIO)

[MabezDev]

• LLVM 12 status of the fork
  • Will fix esp 1.54 breaks Mac M1 builds #62

[georgik]

Distribution of custom Rust build:

• option RUSTUP_DIST_SERVER="https://foo.bar" rustup install $CHANNEL - Remote Custom Toolchains rust-lang/rustup#2696
• "mirror" simple directory structure with .sha256 files - https://github.com/jiegec/rustup-mirror
• rustup does not print many errors when parsing fails - no success with this approach now
• debugging of rustup is problematic, since it's polymorphic binary changing the bahaviour based on the name of binary - any idea how to pass binary name (argv[0]) to cargo run?
• the best current option is to follow manual steps to deploy toolchain

[jessebraham]

• The SVD for the ESP32C3 is "complete" for the time being
  • There are still some changes that should be made, but they will happen at a later date
• esp32c3 PAC has been updated in my fork to use the new SVD
  • https://github.com/jessebraham/esp32c3/tree/new-svd
  • I messaged the repo owner about transferring ownership to esp-rs, awaiting reply
  • Is the current device.x file accurate?
• Do we want to use the existing esp-rs/esp32-hal repo for the C3/SX/etc., or should each chip have its own HAL repo?
  • I imagine there is probably a fair bit of overlap between devices?