Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Fix initializing BuildTools when the Platform environment variable is set #24998

Merged
merged 2 commits into from
Jun 6, 2019

Conversation

elinor-fung
Copy link
Member

@elinor-fung elinor-fung commented Jun 6, 2019

  • Clear Platform variable before initializing BuildTools
  • Make build-test.cmd exit if init-tools.cmd fails

Some BuildTools initialization steps fail if Platform is set to a value with which they are not compatible. We were relying on dotnet.cmd to clear the Platform environment variable before init-tools.cmd was called. build-test.cmd was always calling init-tools.cmd in such a way that the Platform variable was not cleared, but generally the tools would previously have been initialized through dotnet.cmd, so they would not be initialized again. With #24841, we stopped initializing BuildTools in dotnet.cmd, so the call in build-test.cmd was actually doing the initialization (and failing depending on how `Platform is set).

Fixes #24943

@elinor-fung elinor-fung requested review from jashook and sbomer June 6, 2019 07:38
@elinor-fung elinor-fung merged commit a0486f5 into dotnet:master Jun 6, 2019
@elinor-fung elinor-fung deleted the fix24943 branch June 6, 2019 21:03
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
… set (dotnet/coreclr#24998)

* Make build-test.cmd exit if init-tools.cmd fails

* Clear Platform variable before initializing BuildTools


Commit migrated from dotnet/coreclr@a0486f5
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CoreCLR failed to build due to error MSB3073 with MSVC on windows
3 participants