When attempting to compile a crate that has i686-pc-windows-msvc forced as its target, Cargo panics:
thread 'main' panicked at src/cargo\core\resolver\features.rs:323:14:
activated_features for invalid package: features did not find PackageId { name: "windows_i686_msvc", version: "0.52.6", source: "registry `crates-io`" } NormalOrDev
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Steps
Enable the experimental Cargo feature per-package-target inside Cargo.toml.
Specify package.forced-target to be i686-pc-windows-msvc.
Thanks for the bug report. Mind sharing your Cargo.toml, or any minimal reproducible example?
A plain Cargo.toml with the steps you described in cargo 1.84.0-nightly (4a2d8dc63 2024-11-09) doesn't panic.
Problem
When attempting to compile a crate that has
i686-pc-windows-msvc
forced as its target, Cargo panics:Steps
per-package-target
inside Cargo.toml.package.forced-target
to bei686-pc-windows-msvc
.Possible Solution(s)
No response
Notes
No response
Version