Struct cargo::core::profiles::Profiles

pub struct Profiles {
    incremental: Option<bool>,
    dir_names: HashMap<InternedString, InternedString>,
    by_name: HashMap<InternedString, ProfileMaker>,
    original_profiles: BTreeMap<InternedString, TomlProfile>,
    requested_profile: InternedString,
    rustc_host: InternedString,
}

Collection of all profiles.

To get a specific Profile, you usually create this and call get_profile then.

Fields

incremental: Option<bool>

Incremental compilation can be overridden globally via:

• CARGO_INCREMENTAL environment variable.
• build.incremental config value.

dir_names: HashMap<InternedString, InternedString>

Map of profile name to directory name for that profile.

by_name: HashMap<InternedString, ProfileMaker>

The profile makers. Key is the profile name.

original_profiles: BTreeMap<InternedString, TomlProfile>

The original profiles written by the user in the manifest and config.

This is here to assist with error reporting, as the ProfileMaker values have the inherits chains all merged together.

requested_profile: InternedString

The profile the user requested to use.

rustc_host: InternedString

The host target for rustc being used by this Profiles.

Implementations

impl Profiles

pub fn new( ws: &Workspace<'_>, requested_profile: InternedString ) -> CargoResult<Profiles>

fn predefined_dir_names() -> HashMap<InternedString, InternedString>

Returns the hard-coded directory names for built-in profiles.

fn add_root_profiles( profile_makers: &mut Profiles, profiles: &BTreeMap<InternedString, TomlProfile> )

Initialize by_name with the two “root” profiles, dev, and release given the user’s definition.

fn predefined_profiles() -> Vec<(&'static str, TomlProfile)>

Returns the built-in profiles (not including dev/release, which are “root” profiles).

fn add_maker( &mut self, name: InternedString, profile: &TomlProfile, profiles: &BTreeMap<InternedString, TomlProfile> ) -> CargoResult<()>

Creates a ProfileMaker, and inserts it into self.by_name.

fn process_chain( &mut self, name: InternedString, profile: &TomlProfile, set: &mut HashSet<InternedString>, profiles: &BTreeMap<InternedString, TomlProfile> ) -> CargoResult<ProfileMaker>

Build a ProfileMaker by recursively following the inherits setting.

• name: The name of the profile being processed.
• profile: The TOML profile being processed.
• set: Set of profiles that have been visited, used to detect cycles.
• profiles: Map of all TOML profiles.

Returns a ProfileMaker to be used for the given named profile.

pub fn get_profile( &self, pkg_id: PackageId, is_member: bool, is_local: bool, unit_for: UnitFor, kind: CompileKind ) -> Profile

Retrieves the profile for a target. is_member is whether or not this package is a member of the workspace.

pub fn get_profile_run_custom_build( &self, for_unit_profile: &Profile ) -> Profile

The profile for running a build.rs script is only used for setting a few environment variables. To ensure proper de-duplication of the running Unit, this uses a stripped-down profile (so that unrelated profile flags don’t cause build.rs to needlessly run multiple times).

pub fn base_profile(&self) -> Profile

This returns the base profile. This is currently used for the [Finished] line. It is not entirely accurate, since it doesn’t select for the package that was actually built.

pub fn get_dir_name(&self) -> InternedString

Gets the directory name for a profile, like debug or release.

pub fn validate_packages( &self, profiles: Option<&TomlProfiles>, shell: &mut Shell, resolve: &Resolve ) -> CargoResult<()>

Used to check for overrides for non-existing packages.

fn get_profile_maker(&self, name: InternedString) -> CargoResult<&ProfileMaker>

Returns the profile maker for the given profile name.

Trait Implementations

impl Clone for Profiles

fn clone(&self) -> Profiles

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Profiles

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

Layout

Note: Most layout information is completely unstable and may even differ between compilations. The only exception is types with certain repr(...) attributes. Please see the Rust Reference's “Type Layout” chapter for details on type layout guarantees.

Size: 160 bytes