Tracking Issue: Support project-specific config in manifest

[epage]

Configuration is for the environment a package is being built in. Through experience, we find that some environment concerns are actually package concerns and users run into problems with them being tied into the environment.

This is meant to track configuration that should be supported in manifests. This won't always be a one-to-one mappings.

• alias
  • Use case: commands tied to developing the project
  • See also
    • Make commands in dev-dependencies available to run #2267
    • https://github.com/matklad/cargo-xtask
    • https://aturon.github.io/tech/2018/04/05/workflows/
• RUSTFLAGS
  • See Tracking Issue: Exposing RUSTFLAGS in cargo #12739
• RUSTFLAGS
  • See Tracking Issue for profile-rustflags #10271
• build.target
  • Tracking Issue for per-package-target #9406
  • Target configuration for binaries #9208
  • Allow specifying a set of supported target platforms in Cargo.toml #6179
• registries, see Config-independent way of specifying alternative registry in Cargo.toml #14500

See also

• Cargo does not always search for .cargo/config file in project root #2930
• internals thread