IssueRaiser

Tracking Issue for per-package-target

**Summary** Feature gate: `per_package_target` Discussion: https://internals.rust-lang.org/t/proposal-move-some-cargo-config-settings-to-cargo-toml/13336 Implementation: https://github.com/rust-lang/cargo/pull/9030 Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#per-package-target Issues: https://github.com/rust-lang/cargo/labels/Z-per-package-target **Unresolved issues** - [ ] Should the new fields be allowed in cargo scripts? - [ ] The interaction with proposals like [RFC 3028](https://github.com/rust-lang/rfcs/pull/3028) does not work well. Selection for targets to build happens at the workspace level instead of at a level where the full compile graph is known. This affects selected packages (target-specific dependencies) and feature resolution as well. There's also some possible confusion, as the per-package-target settings are ignored in dependencies. - [ ] The exact interaction with feature resolution is a bit up in the air. This may not be super well-tested where in theory each target artifact should get an independently resolved feature graph (ish). Related to: https://github.com/rust-lang/cargo/issues/9521 - [ ] [Interaction with `-Zbuild-std`](https://github.com/rust-lang/cargo/issues/9451)

Posted by Ekleog on Apr 24, 2021, 6:39 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments

github (Software)

Tracking Issue for per-package-target

EkleogApr 24, 2021, 6:39 PM

**Summary** Feature gate: `per_package_target` Discussion: https://internals.rust-lang.org/t/proposal-move-some-cargo-config-settings-to-cargo-toml/13336 Implementation: https://github.com/rust-lang/cargo/pull/9030 Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#per-package-target Issues: https://github.com/rust-lang/cargo/labels/Z-per-package-target **Unresolved issues** - [ ] Should the new fields be allowed in cargo scripts? - [ ] The interaction with proposals like [RFC 3028](https://github.com/rust-lang/rfcs/pull/3028) does not work well. Selection for targets to build happens at the workspace level instead of at a level where the full compile graph is known. This affects selected packages (target-specific dependencies) and feature resolution as well. There's also some possible confusion, as the per-package-target settings are ignored in dependencies. - [ ] The exact interaction with feature resolution is a bit up in the air. This may not be super well-tested where in theory each target artifact should get an independently resolved feature graph (ish). Related to: https://github.com/rust-lang/cargo/issues/9521 - [ ] [Interaction with `-Zbuild-std`](https://github.com/rust-lang/cargo/issues/9451)

Comments (0)

No comments yet. Start the discussion.

Comment on this issue