replace config.toml to bootstrap.toml in src:doc:rustc-dev-guide · rust-lang/rustc-dev-guide@e4ddc21 (original) (raw)
`` @@ -159,15 +159,15 @@ similar to the one declared in section What is x.py, but
``
159
159
`` it works as an independent process to execute the x.py rather than calling the
``
160
160
`shell to run the platform related scripts.
`
161
161
``
162
``
`` -
Create a config.toml
``
``
162
`` +
Create a bootstrap.toml
``
163
163
``
164
164
`` To start, run ./x setup and select the compiler defaults. This will do some initialization
``
165
``
`` -
and create a config.toml for you with reasonable defaults. If you use a different default (which
``
``
165
`` +
and create a bootstrap.toml for you with reasonable defaults. If you use a different default (which
``
166
166
`you'll likely want to do if you want to contribute to an area of rust other than the compiler, such
`
167
167
`` as rustdoc), make sure to read information about that default (located in src/bootstrap/defaults)
``
168
168
`as the build process may be different for other defaults.
`
169
169
``
170
``
`` -
Alternatively, you can write config.toml by hand. See config.example.toml for all the available
``
``
170
`` +
Alternatively, you can write bootstrap.toml by hand. See bootstrap.example.toml for all the available
``
171
171
`` settings and explanations of them. See src/bootstrap/defaults for common settings to change.
``
172
172
``
173
173
`` If you have already built rustc and you change settings related to LLVM, then you may have to
``
`@@ -206,7 +206,7 @@ See the chapters on
`
206
206
`Note that building will require a relatively large amount of storage space.
`
207
207
`You may want to have upwards of 10 or 15 gigabytes available to build the compiler.
`
208
208
``
209
``
`` -
Once you've created a config.toml, you are now ready to run
``
``
209
`` +
Once you've created a bootstrap.toml, you are now ready to run
``
210
210
`` x. There are a lot of options here, but let's start with what is
``
211
211
`probably the best "go to" command for building a local compiler:
`
212
212
``
`@@ -326,7 +326,7 @@ involve proc macros or build scripts, you must be sure to explicitly build targe
`
326
326
`` host platform (in this case, x86_64-unknown-linux-gnu).
``
327
327
``
328
328
`` If you want to always build for other targets without needing to pass flags to x build,
``
329
``
`` -
you can configure this in the [build] section of your config.toml like so:
``
``
329
`` +
you can configure this in the [build] section of your bootstrap.toml like so:
``
330
330
``
331
331
```` ```toml
````
332
332
`[build]
`
`@@ -336,8 +336,8 @@ target = ["x86_64-unknown-linux-gnu", "wasm32-wasip1"]
`
336
336
`Note that building for some targets requires having external dependencies installed
`
337
337
`(e.g. building musl targets requires a local copy of musl).
`
338
338
`Any target-specific configuration (e.g. the path to a local copy of musl)
`
339
``
`` -
will need to be provided by your config.toml.
``
340
``
`` -
Please see config.example.toml for information on target-specific configuration keys.
``
``
339
`` +
will need to be provided by your bootstrap.toml.
``
``
340
`` +
Please see bootstrap.example.toml for information on target-specific configuration keys.
``
341
341
``
342
342
`For examples of the complete configuration necessary to build a target, please visit
`
343
343
`