bpo-36862: Add VS2019 to env.bat by tonybaloney · Pull Request #13215 · python/cpython
Navigation Menu
{{ message }}
- Notifications You must be signed in to change notification settings
- Fork 34.4k
Closed
tonybaloney wants to merge 2 commits intopython:masterfrom
Closed
bpo-36862: Add VS2019 to env.bat#13215
tonybaloney wants to merge 2 commits intopython:masterfrom
bpo-36862: Add VS2019 to env.bat#13215
tonybaloney wants to merge 2 commits intopython:masterfrom
Conversation
Copy link Copy Markdown
Contributor
tonybaloney
requested a review
from a team
as a code owner
the-knights-who-say-ni
added
the
CLA signed
label
bedevere-bot
added
the
awaiting review
label
Copy link Copy Markdown
Contributor Author
tonybaloney
commented
May 9, 2019
tonybaloney commented
May 9, 2019auvipy approved these changes May 13, 2019
bedevere-bot
added
awaiting core review
and removed
awaiting review
labels
zooba reviewed May 13, 2019
| echo Build environments: x86, amd64, x86_amd64 | ||
| echo. | ||
| set VSTOOLS=%VS140COMNTOOLS% | ||
| if "%VSTOOLS%"=="" set VSTOOLS=%VS160COMNTOOLS% |
Copy link Copy Markdown
Member
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is correct - we'll want some detection more like what's in find_msbuild.bat (using the vswhere.exe app - and if that's not there, then neither VS 2017 or VS 2019 are installed!)
Copy link Copy Markdown
Contributor Author
tonybaloney
commented
Aug 22, 2019
tonybaloney commented
Aug 22, 2019So, I've discovered that the scripts don't work with prerelease versions of Visual Studio. You can use the -prerelease flag for vswhere so that would discover MSBuild, but as VS2019 is now released, this seems like an edge-case
tonybaloney
closed this
This file contains hidden or 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment