Skip to main content

Module session

Module session 

Source

Re-exportsΒ§

use std::cell::Cell; πŸ”’
use std::collections::BTreeSet; πŸ”’
use std::collections::HashMap; πŸ”’
use std::collections::HashSet; πŸ”’
use std::fmt::Display; πŸ”’
use std::ops::Deref; πŸ”’
use std::path::Path; πŸ”’
use std::path::PathBuf; πŸ”’
use std::time::Instant; πŸ”’
use std::time::SystemTime; πŸ”’
use std::env; πŸ”’
use std::env; πŸ”’
use std::fs; πŸ”’
use std::io; πŸ”’
use std::str; πŸ”’
use build_helper::ci::gha; πŸ”’
use termcolor::ColorChoice; πŸ”’
use termcolor::StandardStream; πŸ”’
use termcolor::WriteColor; πŸ”’
use crate::core::build_steps::format::InternalRustfmt; πŸ”’
use crate::core::build_steps::test::TestTarget; πŸ”’
use crate::core::build_steps::vendor::VENDOR_DIR; πŸ”’
use crate::core::builder::Builder; πŸ”’
use crate::core::builder::Kind; πŸ”’
use crate::core::compiler::Compiler; πŸ”’
use crate::core::config::flags; πŸ”’
use crate::core::config::flags::Subcommand; πŸ”’
use crate::core::config::BootstrapOverrideLld; πŸ”’
use crate::core::config::Config; πŸ”’
use crate::core::config::DryRun; πŸ”’
use crate::core::config::LlvmLibunwind; πŸ”’
use crate::core::config::TargetSelection; πŸ”’
use crate::core::download::DownloadContext; πŸ”’
use crate::core::download::download_beta_toolchain; πŸ”’
use crate::core::metadata::Crate; πŸ”’
use crate::utils::build_stamp::BuildStamp; πŸ”’
use crate::utils::channel::GitInfo; πŸ”’
use crate::utils::exec::BootstrapCommand; πŸ”’
use crate::utils::exec::ExecutionContext; πŸ”’
use crate::utils::exec::command; πŸ”’
use crate::utils::helpers; πŸ”’
use crate::utils::helpers::dir_is_empty; πŸ”’
use crate::utils::helpers::exe; πŸ”’
use crate::utils::helpers::libdir; πŸ”’
use crate::utils::helpers::set_file_times; πŸ”’
use crate::utils::helpers::split_debuginfo; πŸ”’
use crate::utils::helpers::t; πŸ”’
use crate::debug; πŸ”’
use crate::trace; πŸ”’

MacrosΒ§

forward πŸ”’

StructsΒ§

Session πŸ”’
Global configuration for the build system.
TargetAndStage πŸ”’
An alternative way of specifying what target and stage is involved in some bootstrap activity. Ideally using a Compiler directly should be preferred.

EnumsΒ§

CLang πŸ”’
DependencyType πŸ”’
When building Rust various objects are handled differently.
FileType πŸ”’
Mode πŸ”’
The various β€œmodes” of invoking Cargo.
RemapScheme πŸ”’
When rust.rust_remap_debuginfo is requested, the compiler needs to know how to opportunistically unremap compiler vs non-compiler sources. We use two schemes, RemapScheme::Compiler and RemapScheme::NonCompiler.

FunctionsΒ§

chmod πŸ”’