nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-25 08:13:41 +00:00
Code Issues Packages Projects Releases Wiki Activity

Remove ancient and outdated references to config.mk

Browse Source
This commit is contained in:
Joshua Nelson 2022-12-23 19:03:51 -06:00
parent 1bd1b25be8
commit 70a0e0a277
3 changed files with 4 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -228,9 +228,7 @@ configure script and makefile (the latter of which just invokes `x.py`).
make && sudo make install make && sudo make install
``` ```
When using the configure script, the generated `config.mk` file may override the `configure` generates a `config.toml` which can also be used with normal `x.py` invocations.
`config.toml` file. To go back to the `config.toml` file, delete the generated
`config.mk` file.
## Building Documentation ## Building Documentation

10
src/bootstrap/README.md
View File

@ -80,18 +80,12 @@ The script accepts commands, flags, and arguments to determine what to do:
## Configuring rustbuild ## Configuring rustbuild
There are currently two methods for configuring the rustbuild build system. rustbuild offers a TOML-based configuration system with a `config.toml`
First, rustbuild offers a TOML-based configuration system with a `config.toml`
file. An example of this configuration can be found at `config.toml.example`, file. An example of this configuration can be found at `config.toml.example`,
and the configuration file can also be passed as `--config path/to/config.toml` and the configuration file can also be passed as `--config path/to/config.toml`
if the build system is being invoked manually (via the python script). if the build system is being invoked manually (via the python script).
Next, the `./configure` options serialized in `config.mk` will be You can generate a config.toml using `./configure` options if you want to automate creating the file without having to edit it.
parsed and read. That is, if any `./configure` options are passed, they'll be
handled naturally. `./configure` should almost never be used for local
installations, and is primarily useful for CI. Prefer to customize behavior
using `config.toml`.
Finally, rustbuild makes use of the [cc-rs crate] which has [its own Finally, rustbuild makes use of the [cc-rs crate] which has [its own
method][env-vars] of configuring C compilers and C flags via environment method][env-vars] of configuring C compilers and C flags via environment

5
src/bootstrap/config.rs
View File

@ -46,10 +46,7 @@ pub enum DryRun {
/// Global configuration for the entire build and/or bootstrap. /// Global configuration for the entire build and/or bootstrap.
/// ///
/// This structure is derived from a combination of both `config.toml` and /// This structure is parsed from `config.toml`, and some of the fields are inferred from `git` or build-time parameters.
/// `config.mk`. As of the time of this writing it's unlikely that `config.toml`
/// is used all that much, so this is primarily filled out by `config.mk` which
/// is generated from `./configure`.
/// ///
/// Note that this structure is not decoded directly into, but rather it is /// Note that this structure is not decoded directly into, but rather it is
/// filled out from the decoded forms of the structs below. For documentation /// filled out from the decoded forms of the structs below. For documentation