-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[experimental] rust: Update versions #17491
Conversation
There are now clones of the relevant crates in https://github.com/RIOT-OS-pkgmirror. By now, this always-experimental PR is not showing how they'd be used (which should be straightforward from swapping around the upstreams), but also to give branches of riot-sys and -wrappers a trial run on the full set of boards rather than the limited set their own CI can do. |
b740d99
to
2d582c5
Compare
e968cf3
to
e079086
Compare
With #18151 merged, this branch can now be generated more easily: Just run for x in examples/rust* tests/rust*; do cd $x; cargo update || break; make BOARD=samd21-xpro CARGO_CHANNEL=nightly || break; cd -; done
git commit */*/Cargo.lock -m "rust: Update versions" (which includes a simple local build check just see issues early). The top description is being updated to reflect how this PR works now. |
This was accidentally marked as merged when the branch happened to be on the same commit as a different PR (that was not experimental/always-open) and the latter was merged. Trying to re-open it... |
[updated description; see below the line for the original version]
This PR is a template for what needs to be done when updating the riot-sys and riot-wrappers Rust crates used in the examples. Usual steps are:
Apart from being useful as a template for other PRs, this PR is also occasionally used to just run these steps (force pushing, without an intention to merge) to get the latest -sys and -wrappers tested by Murdock.
This is a test balloon for how #17488 could turn out.
This is a draft commit because the git repo is not yet one RIOT controls, and anyhow there's no good reason to switch to an unreleased version right now.