@@ -18,7 +18,7 @@ git clone https://github.com/rust-lang/rust.git
18
18
cd rust
19
19
```
20
20
21
- ## Create a config.toml
21
+ ## Create a ` config.toml `
22
22
23
23
To start, copy [ ` config.toml.example ` ] to ` config.toml ` :
24
24
@@ -122,9 +122,7 @@ It is, in particular, very useful when you're doing some kind of
122
122
"type-based refactoring", like renaming a method, or changing the
123
123
signature of some function.
124
124
125
- <a name =command ></a >
126
-
127
- Once you've created a config.toml, you are now ready to run
125
+ Once you've created a ` config.toml ` , you are now ready to run
128
126
` x.py ` . There are a lot of options here, but let's start with what is
129
127
probably the best "go to" command for building a local rust:
130
128
@@ -177,7 +175,7 @@ build. The **full** `rustc` build (what you get if you say `./x.py build
177
175
./x.py build library/core
178
176
```
179
177
180
- - Build the core and proc_macro libraries only
178
+ - Build only the core and ` proc_macro ` libraries
181
179
182
180
``` bash
183
181
./x.py build library/core library/proc_macro
@@ -186,7 +184,7 @@ build. The **full** `rustc` build (what you get if you say `./x.py build
186
184
Sometimes you might just want to test if the part you’re working on can
187
185
compile. Using these commands you can test that it compiles before doing
188
186
a bigger build to make sure it works with the compiler. As shown before
189
- you can also pass flags at the end such as --stage.
187
+ you can also pass flags at the end such as ` --stage ` .
190
188
191
189
## Creating a rustup toolchain
192
190
@@ -215,13 +213,13 @@ your local environment:
215
213
216
214
``` bash
217
215
$ rustc +stage1 -vV
218
- rustc 1.25 .0-dev
216
+ rustc 1.48 .0-dev
219
217
binary: rustc
220
218
commit-hash: unknown
221
219
commit-date: unknown
222
220
host: x86_64-unknown-linux-gnu
223
- release: 1.25 .0-dev
224
- LLVM version: 4 .0
221
+ release: 1.48 .0-dev
222
+ LLVM version: 11 .0
225
223
```
226
224
## Other ` x.py ` commands
227
225
@@ -252,4 +250,5 @@ everything up then you only need to run one command!
252
250
./x.py clean
253
251
```
254
252
255
- ` rm -rf build ` works too, but then you have to rebuild LLVM.
253
+ ` rm -rf build ` works too, but then you have to rebuild LLVM, which can take
254
+ a long time (on the order of a half-hour).
0 commit comments