-
-
Notifications
You must be signed in to change notification settings - Fork 3k
build-dir legacy layout post stablization cleanup #17182
Copy link
Copy link
Open
Labels
A-layoutArea: target output directory layout, naming, and organizationArea: target output directory layout, naming, and organizationC-cleanupCategory: cleanup within the codebaseCategory: cleanup within the codebaseS-blocked-externalStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fixStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fix
Description
Activity
Metadata
Metadata
Assignees
Labels
A-layoutArea: target output directory layout, naming, and organizationArea: target output directory layout, naming, and organizationC-cleanupCategory: cleanup within the codebaseCategory: cleanup within the codebaseS-blocked-externalStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fixStatus: ❌ blocked on something out of the direct control of the Cargo project, e.g., upstream fix
The new
build-dirlayout tracked in #15010 was stabilized in #16807. However, the stabilization route we decided to go was to keep the legacy layout with a temporary__CARGO_TEMPORARY_BUILD_DIR_NEW_LAYOUT_OPT_OUTenv var to allow them to opt out to ease the transition.This issue issue tracks the removal of the legacy
build-dirlayout, including the opt out, implementation, and legacy tests.In the stabilziation pull request, we called out that the legacy
build-dirlayout would be removed 1 release cycle after the new layout stabilization.Checklist
-Zbuild-dir-new-layoutflag#[derive(Default)]back forCliUnstable- Stabilizebuild-dirlayout v2 #16807 (comment)deps_outputtodylibs_pathReduce library search path length in new build dir layout #17191 (comment)cargo/tests/testsuite/build.rs
Line 6620 in 3efb1f4