-
Notifications
You must be signed in to change notification settings - Fork 2.1k
dist/tools/ci: include rust, node and git commit in print-version #21734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Looks good, I just asked the other maintainers with more Rust experience if anything else should be evaluated too (since I don't know much about that kind of Rust 😅 ) |
While rustup is not technically required, we check through it whether the right cross toolchain is present, for it is the only widespread way to install those. (Debian ships cargo, but no cross toolchains.) |
Added 😄 I think on arch there is also a way to install Rust without rustup so its probably a common mistake people dont really notice (esp. in their first steps with Rust) |
I just noticed on my work pc that riscv32-unknown-elf is not tracked, partly because the riscv toolchain ecosystem is confusing as heck and everyone has their own names. riscv32-unknown-elf is used on Arch though. (btw I use Arch) The output looks like this now:
|
Contribution description
Currently the print-version script used for debugging does not include information about the Rust and Frontend environment. While at it I thought it might also make sense to include information about the exact state the RIOT repository is in, esp. to debug cases where the RIOT repository might simply be outdated.
Before:
After:
Testing procedure
make print-version
Issues/PRs references