@@ -106,26 +106,21 @@ Toolchain {#toolchain}
106
106
107
107
To install the necessary Rust components, it is easiest use [ ** rustup** , installed as described on its website] .
108
108
109
- Using Rust on RIOT needs the latest stable or nightly version of Rust,
110
- depending on the precise example used.
111
- (Currently, it's mainly the CoAP parts that use nightly features, and some native builds;
112
- until stable is universally available, only tests are run on stable by default).
109
+ Using Rust on RIOT needs the latest stable version of Rust.
113
110
114
- Make sure you have both the nightly and stable ** toolchains **
111
+ Make sure you have the stable ** toolchain **
115
112
and the core library for the CPU (** target** ) of your choice available:
116
113
117
114
```
118
- $ rustup toolchain add nightly
119
115
$ rustup toolchain add stable
120
- $ rustup target add thumbv7m-none-eabi --toolchain nightly
121
116
$ rustup target add thumbv7m-none-eabi --toolchain stable
122
117
```
123
118
124
119
Substitute thumbv7m-none-eabi with the value of ` RUST_TARGET `
125
- in the output of ` make info-build ` of an application that has your current board selected,
126
- or just add it later whenever the Rust compiler complains about not finding the core library for a given target).
127
- Installing only nightly will work just as well,
128
- but you may need to remove the ` CARGO_CHANNEL = stable ` line to run tests .
120
+ in the output of ` make info-build ` of an application that has your current board selected
121
+ ( or just add it later whenever the Rust compiler complains about not finding the core library for a given target).
122
+ Using a beta or nightly will work just as well,
123
+ but you may need to set ` CARGO_CHANNEL=nightly ` on your shell or in your Makefiles .
129
124
130
125
131
126
While Rust comes with its own [ cargo] dependency tracker for any Rust code,
0 commit comments