You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was attempting to compile with the Microsoft EWDK, but received error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/ while running from the developer prompt. I was quite puzzled by the nonsensical error, as the active developer prompt was, in fact, "Microsoft Visual C++ 14.0 or greater".
Describe the solution you'd like
Detect the already configured compiler, and if it is suitable just use it, without the user having to find out about the existence of DISTUTILS_USE_SDK.
Alternative Solutions
If the envvars look to be configured while printing the earlier error, inform the user about the existence of DISTUTILS_USE_SDK that lets them just use the configured compiler, so that they don't have to go deep in setuptools source code to find out about it.
Code of Conduct
I agree to follow the PSF Code of Conduct
The text was updated successfully, but these errors were encountered:
What's the problem this feature will solve?
I was attempting to compile with the Microsoft EWDK, but received
error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
while running from the developer prompt. I was quite puzzled by the nonsensical error, as the active developer prompt was, in fact, "Microsoft Visual C++ 14.0 or greater".Describe the solution you'd like
Detect the already configured compiler, and if it is suitable just use it, without the user having to find out about the existence of
DISTUTILS_USE_SDK
.Alternative Solutions
If the envvars look to be configured while printing the earlier error, inform the user about the existence of
DISTUTILS_USE_SDK
that lets them just use the configured compiler, so that they don't have to go deep in setuptools source code to find out about it.Code of Conduct
The text was updated successfully, but these errors were encountered: