Struct BuildScripts 

pub struct BuildScripts {
    pub to_link: Vec<(PackageId, UnitHash)>,
    seen_to_link: HashSet<(PackageId, UnitHash)>,
    pub plugins: BTreeSet<(PackageId, UnitHash)>,
}

Linking information for a Unit.

See build_map for more details.

Fields

to_link: Vec<(PackageId, UnitHash)>

List of build script outputs this Unit needs to include for linking. Each element is an index into BuildScriptOutputs.

Cargo will use this to_link vector to add -L flags to compiles as we propagate them upwards towards the final build. Note, however, that we need to preserve the ordering of to_link to be topologically sorted. This will ensure that build scripts which print their paths properly will correctly pick up the files they generated (if there are duplicates elsewhere).

To preserve this ordering, the (id, metadata) is stored in two places, once in the Vec and once in seen_to_link for a fast lookup. We maintain this as we’re building interactively below to ensure that the memory usage here doesn’t blow up too much.

For more information, see #2354.

seen_to_link: HashSet<(PackageId, UnitHash)>

This is only used while constructing to_link to avoid duplicates.

plugins: BTreeSet<(PackageId, UnitHash)>

Host-only dependencies that have build scripts. Each element is an index into BuildScriptOutputs.

This is the set of transitive dependencies that are host-only (proc-macro, plugin, build-dependency) that contain a build script. Any BuildOutput::library_paths path relative to target will be added to LD_LIBRARY_PATH so that the compiler can find any dynamic libraries a build script may have generated.

Trait Implementations

impl Default for BuildScripts

fn default() -> BuildScripts

Returns the “default value” for a type.

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: 96 bytes