riotbuild: Install Rust (minimal edition)#152
Conversation
The c2rust program (required in addition to Rust itself) is installed for what is for most intents and purposes a third party container, but happens to have its sources shipped along the other containers.
|
By the way, the container built from this is successfully in use for the riot-examples CI (so successfully that I've started building more in CI than was previously tested, which is why it's red again). |
chrysn
changed the title
|
bors try |
tryBuild succeeded: |
|
Regular builds seem to still work, so lets go. bors merge |
|
👎 Rejected by too few approved reviews |
|
bors merge |
|
Build succeeded: |
|
Unfortunately due to Docker not doing auto builds anymore, this won't be used for Murdock until I move the murdock container builds somewhere else. That's high on my list... |
|
Thanks, working to improve from here now. (Given that the trouble building on native with this comes from mismatched LLVM 7.0 and 7.1 (from c2rust-build), I expect best progress after #104.) Is there anything I can do on the murdock side (being relatively unfamiliar with its inner workings)? |
161: Rust updates r=kaspar030 a=chrysn * Add what is needed to experiment with AVR (not fully supported for Rust-on-RIOT, but way easier to test being in the docker build as I haven't had AVR toolchains installed around for a long time, though they probably still can be installed easily) * Update Rust nightly (that's a semi-regular thing since we decided to pin the version in #141 (comment) which also went into #152) Co-authored-by: chrysn <[email protected]>
2 participants
The c2rust program (required in addition to Rust itself) is installed
for what is for most intents and purposes a third party container, but
happens to have its sources shipped along the other containers.
This is a minimal version competing with #141 -- we can still get c2rust to fully integrate over time, but right now there's a third party (happens to be me) who publishes a suitable base container, which is not much more or less transparently managed than any other base container (especially immunant/c2rust which it itself is based on), and hey by the way even the Dockerfile for that container is shipped here (but more for informational purposes, not because CI would access it).