-
Notifications
You must be signed in to change notification settings - Fork 113
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
Building metadata projects outside vscmd results in failure to find cl.exe #1854
Comments
Should be possible to use vswhere to find the exes for us? |
The win32metadata/sources/GeneratorSdk/sdk/sdk.props Lines 48 to 51 in 9d6d88a
Which sets a bunch of properties, some of which we rely upon (e.g. win32metadata/sources/GeneratorSdk/sdk/sdk.targets Lines 124 to 133 in 9d6d88a
But then we also have these properties to contend with: win32metadata/sources/GeneratorSdk/sdk/sdk.props Lines 24 to 31 in 9d6d88a
And... that's as far as I've gotten at the moment. We just need to spend a bit more time following all the wires around, see what we've got, determine what *.SDK.CPP offers, and hopefully clean things up a bit so that we're working with a properly hydrated build environment. |
Just creating an official issue to track fixing a long time annoyance.
dotnet build
in a vanilla Terminal session results in midl.exe/cl.exe failures due to tooling paths not getting wired up correctly.The text was updated successfully, but these errors were encountered: