-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Open
Labels
A-build-scriptsArea: build.rs scriptsArea: build.rs scriptsC-tracking-issueCategory: A tracking issue for something unstable.Category: A tracking issue for something unstable.Z-bindepsNightly: binary artifact dependenciesNightly: binary artifact dependenciesZ-metabuildNightly: metabuildNightly: metabuild
Description
This is a tracking issue for the RFC "metabuild: semantic build scripts for Cargo" (rust-lang/rfcs#2196).
Steps:
- Implement the RFC (Metabuild (RFC 2196) #5628)
- Implement Multiple Build Scripts
- Parsing feat(toml): Parse support for multiple build scripts #15630
- Running multiple build scripts feat: Implementation and tests for
multiple-build-scripts
#15704
- Implement Build Script Delegation
- Adjust documentation (see instructions on forge)
- Stabilization PR (see instructions on forge)
Unresolved questions:
OUT_DIR
: how to readOUT_DIR
when there are multiple build scripts was deferred out of feat: Implementation and tests formultiple-build-scripts
#15704- Conflicts between build scripts: if two build scripts write the same env variable, etc, what should happen? As of feat: Implementation and tests for
multiple-build-scripts
#15704, the last one alphabetically wins (except sometimes the first alphabetically wins). We need this consistent and users might need control over this. So long as its build scripts, the user can change names to control order. However, when we get to build script delegation, that won't work.
Techcable and boozook
Metadata
Metadata
Assignees
Labels
A-build-scriptsArea: build.rs scriptsArea: build.rs scriptsC-tracking-issueCategory: A tracking issue for something unstable.Category: A tracking issue for something unstable.Z-bindepsNightly: binary artifact dependenciesNightly: binary artifact dependenciesZ-metabuildNightly: metabuildNightly: metabuild
Type
Projects
Status
No status