Ability to cross-compile build scripts about cargo HOT 2 OPEN

I have wondered if there would be benefits to allowing package.build to be split out into its own target table.

For the field name, I would likely go with [whatever field is used with per-package-targets (currently forced-target).
Do you need only the build script to be forced to a target or would doing it for the entire package work? Granted, not everyone with forced-target might want that but I worry about a package that is meant for any target but the build script only works on one.

As for the request itself, it feels a bit odd to me and I'm hesitant. I'm not sure if its lack of knowledge or familiarity with the use case or what.

from cargo.

The crate itself happens to be built for x86_64-pc-windows-msvc as well, so building the build script and the crate for the same target would work.

I agree that restricting builds to a particular target can be problematic. However, a build script that builds for any target, but then works only on one target because it spawns a target-specific subprocess makes little difference.

from cargo.