-
Notifications
You must be signed in to change notification settings - Fork 459
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add rust-toolchain file instead of always using stable. (#2408)
Cherry-pick from master of 463a663 and 8a02d35, except that the toolchain is set to 1.40.0 instead of stable. --- Add rust-toolchain file instead of always using stable. Currently our release branches always use the stable toolchain, just like master. Unfortunately a new stable has the ability to break the build, since it brings new clippy and rustfmt and we enforce clean clippy and formatting in the builds. With this change, we now let rustup read the toolchain from the rust-toolchain file instead of forcing it to use latest stable. The expectation is that when we create release branches, we'll freeze the toolchain version to the latest Rust release at the time. For the Windows ARM32 builds, since we use a custom toolchain instead of rustup, the toolchain version is part of the download URL. --- Fix handling of toolchain-specific Windows ARM32 compiler. - Ensure that compiler zip and expanded directory are resolved relative to the repo root, not current directory. This is needed because the azureiotedge-diagnostics build script changes the current directory when it switches from building amd64 to arm32. - Ensure that compiler zip and expanded directory contain the toolchain name. Previously the existing expanded directory would be used regardless of which toolchain zip was expanded to create it. This is also needed because the build agent is shared for older branches that do not use the toolchain file, so their zip and expanded directories must not conflict.
- Loading branch information
Showing
18 changed files
with
145 additions
and
237 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.