user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

remove redundant _toml suffix and other misc changes

Browse source
This commit is contained in:
bit-aloo 2025-08-04 21:36:37 +05:30
parent 7f20ad86ba
commit 962836dfd3
No known key found for this signature in database
4 changed files with 368 additions and 386 deletions
Download patch file Download diff file Expand all files Collapse all files

743
src/bootstrap/src/core/config/config.rs
View file

File diff suppressed because it is too large Load diff

2
src/bootstrap/src/core/config/toml/mod.rs
View file

@ -5,7 +5,7 @@
//! these raw TOML configurations from various sources (the main `bootstrap.toml`,
//! included files, profile defaults, and command-line overrides). This processed
//! TOML data then serves as an intermediate representation, which is further
//! transformed and applied to the final [`Config`] struct.
//! transformed and applied to the final `Config` struct.
use serde::Deserialize;
use serde_derive::Deserialize;

2
src/bootstrap/src/core/config/toml/rust.rs
View file

@ -6,7 +6,7 @@ use serde::{Deserialize, Deserializer};
use crate::core::build_steps::compile::CODEGEN_BACKEND_PREFIX;
use crate::core::config::toml::TomlConfig;
use crate::core::config::{DebuginfoLevel, Merge, ReplaceOpt, StringOrBool};
use crate::{BTreeSet, HashSet, PathBuf, TargetSelection, define_config, exit};
use crate::{BTreeSet, CodegenBackendKind, HashSet, PathBuf, TargetSelection, define_config, exit};
define_config! {
/// TOML representation of how the Rust build is configured.

7
src/bootstrap/src/core/config/toml/target.rs
View file

@ -7,15 +7,12 @@
//! * [`TomlTarget`]: This struct directly mirrors the `[target.<triple>]` sections in your
//! `bootstrap.toml`. It's used for deserializing raw TOML data for a specific target.
//! * [`Target`]: This struct represents the processed and validated configuration for a
//! build target, which is is stored in the main [`Config`] structure.
//! * [`Config::apply_target_config`]: This method processes the `TomlTarget` data and
//! applies it to the global [`Config`], ensuring proper path resolution, validation,
//! and integration with other build settings.
//! build target, which is is stored in the main `Config` structure.
use serde::{Deserialize, Deserializer};
use crate::core::config::{LlvmLibunwind, Merge, ReplaceOpt, SplitDebuginfo, StringOrBool};
use crate::{HashSet, PathBuf, define_config, exit};
use crate::{CodegenBackendKind, HashSet, PathBuf, define_config, exit};
define_config! {
/// TOML representation of how each build target is configured.