Single-Target Builds

Build only for a specific target instead of the full matrix

Two flags let you run a subset of the configured target matrix — useful for local iteration, CI escape hatches, and determinism harness sharding.

--single-target

Build only for the host triple. Nothing else changes: UPX, archive, checksum, and all downstream stages run exactly as for a full release, just for one platform.

anodizer release --single-target

Typical use: tight iteration loop where you only need the local binary.

# No config changes needed — --single-target is a runtime flag.
# Your existing targets list is ignored for the build step.
defaults:
  targets:
    - x86_64-unknown-linux-gnu
    - aarch64-unknown-linux-gnu
    - x86_64-apple-darwin
    - aarch64-apple-darwin
    - x86_64-pc-windows-msvc
    - aarch64-pc-windows-msvc
# Builds only x86_64-unknown-linux-gnu on a Linux host.
anodizer release --snapshot --single-target

--targets=<csv>

Build for an explicit comma-separated subset of the configured triples. Useful when you know exactly which platforms you need — for example, the determinism harness shards the matrix across runners and passes --targets= per shard so each runner only cross-compiles the platforms it is responsible for.

anodizer release --targets=x86_64-unknown-linux-gnu,aarch64-unknown-linux-gnu

Config is not required, but the targets you pass must be a subset of the triples declared in your defaults.targets (or the per-crate builds[].targets override); unknown triples are rejected at validation time.

# CI shard config — build step is scoped at runtime with --targets=
defaults:
  targets:
    - x86_64-pc-windows-msvc
    - aarch64-pc-windows-msvc
  cross: auto
# On a Windows runner: build only the x86_64 Windows target.
anodizer release --targets=x86_64-pc-windows-msvc

--host-targets

Build every configured target this host can build, automatically skipping only the ones that need a cross-toolchain the host lacks. In practice the only real blocker is Apple: *-apple-darwin (and any *-apple-*) targets require a macOS SDK that exists only on a real Mac, so they are skipped on a non-macOS host. Linux and Windows targets cross-link from any host via cargo-zigbuild and are always kept.

Unlike --single-target (one platform) and --targets=<csv> (a hand-picked subset), --host-targets is computed from the host: "build the maximal subset this machine can actually produce." The skipped triples are logged loudly so you always know what was dropped:

$ anodizer release --snapshot --host-targets
host-targets: skipping 2 target(s) not buildable on this linux host \
  (apple targets require a macOS host): aarch64-apple-darwin, x86_64-apple-darwin

It is mutually exclusive with --single-target and --targets, and is only valid together with --snapshot or --dry-run — silently dropping configured targets in a real release would ship an incomplete artifact set, so a non-snapshot run with --host-targets hard-errors at startup. If the host can build none of the configured targets (e.g. an apple-darwin-only config on Linux), it hard-errors too, telling you to run on a macOS host.

# `task prepush` uses this for a real host-scoped build of everything,
# minus publish/announce (auto-skipped in snapshot mode).
anodizer release --snapshot --clean --host-targets

--output / -o

Copy the resulting binary to a specific path after the build step. Handy when you want the binary in a well-known location without parsing dist/.

anodizer build -o ./bin/anodizer
# No config equivalent — --output is a runtime-only flag.

The flag copies the binary for the host target (or the sole target when only one is built); it is not defined when building multiple targets simultaneously.