Struct CargoBuilderConfig 

pub struct CargoBuilderConfig {
    pub targets: Vec<String>,
    pub manifest_path: Option<PathBuf>,
    pub bins: Vec<String>,
    pub parallel: bool,
}

Configuration for CargoBuilder.

Fields

targets: Vec<String>

Cargo target triples to build for (e.g. "x86_64-unknown-linux-musl").

Each entry is passed as --target <triple> in a separate cargo build invocation. When the list is empty, cargo builds for the host target.

manifest_path: Option<PathBuf>

Optional path to the Cargo.toml manifest.

Passed verbatim as --manifest-path. Defaults to the manifest in the current working directory when absent.

bins: Vec<String>

Restrict collected artifacts to these binary (or cdylib) target names.

When empty every artifact produced by a workspace member or local path-dependency is kept. Use this to avoid picking up extra binaries from dev-tools or examples that live in the same workspace.

[[builders]]
type = "cargo"
bins = ["my_binary", "my_cdylib"]

parallel: bool

Run cross-compilation targets in parallel using isolated temporary target directories.

When true (the default), each target triple is given its own --target-dir backed by a tempfile::TempDir, so multiple cargo build processes can compile simultaneously without contending on cargo’s file lock (target/.cargo-lock). Compiled artifacts are copied to the canonical target/<triple>/release/ paths and the temporary directories are then removed automatically.

Set this to false when:

• Disk space is tight. Each temporary build tree can occupy several gigabytes for dependency-heavy crates. Four targets running in parallel means roughly four times the peak disk usage of a single build.
• Incremental compilation matters. Temporary target directories always start cold, discarding Rust’s incremental cache. Disabling parallelism lets all targets share the persistent target/ directory and reuse previously compiled artefacts on subsequent runs.
• The build host is resource-constrained. Parallel cargo build processes each consume significant CPU and RAM. On CI machines with limited memory, running them sequentially avoids thrashing or out-of-memory failures.
• Your cross-compilation toolchain is not concurrency-safe. Some custom linkers or build-script tools assume exclusive access and may produce corrupt output when invoked concurrently.

Trait Implementations

impl Clone for CargoBuilderConfig

fn clone(&self) -> CargoBuilderConfig

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for CargoBuilderConfig

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

Formats the value using the given formatter.

impl Default for CargoBuilderConfig

fn default() -> Self

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for CargoBuilderConfig

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl JsonSchema for CargoBuilderConfig

fn schema_name() -> Cow<'static, str>

The name of the generated JSON Schema.

fn schema_id() -> Cow<'static, str>

Returns a string that uniquely identifies the schema produced by this type.

fn json_schema(generator: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn inline_schema() -> bool

Whether JSON Schemas generated for this type should be included directly in parent schemas, rather than being re-used where possible using the $ref keyword.

impl Serialize for CargoBuilderConfig

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.