-
Notifications
You must be signed in to change notification settings - Fork 10.5k
utils: use longer paths for build trees #79363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@swift-ci please build toolchain Windows platform |
CC: @hjyamauchi @jeffdav |
37eaa5f
to
72e4505
Compare
@swift-ci please build toolchain Windows platform |
72e4505
to
247266e
Compare
@swift-ci please build toolchain Windows platform |
247266e
to
2bb3db0
Compare
@swift-ci please build toolchain Windows platform |
2bb3db0
to
babd854
Compare
@swift-ci please build toolchain Windows platform |
(It might be extra nice if this can be run against the cross-compiling arm64 CI if it works, even better native arm64 CI) |
babd854
to
e12a5ea
Compare
@swift-ci please build toolchain Windows platform |
e12a5ea
to
a8b768b
Compare
The only currently known constraint on the build path is the compilers build. Use long paths for the builds, co-locating more build products and allowing better re-use of the build content. This makes it easier to adjust the various targets that we are building without having to force clean builds due to changes in the build mapping.
a8b768b
to
f2352a5
Compare
@swift-ci please build toolchain Windows platform |
@swift-ci please smoke test |
@swift-ci please test Windows platform |
@swift-ci please build toolchain Windows arm64 platform |
The only currently known constraint on the build path is the compilers build. Use long paths for the builds, co-locating more build products and allowing better re-use of the build content. This makes it easier to adjust the various targets that we are building without having to force clean builds due to changes in the build mapping.