8000
We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
ab0a611
d57c175
3eb568f
4dd19cf
7f91920
c3d656b
3638cda
b8b79ed
d3766d8
c811b8a
904b7ee
991b50f
166187c
5f7ad24
6d7b689
aadfec4
1d7c051
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
It might be convenient to add --clang as a build.bat option, though you'd still need the quoting to get the other variables in.
--clang
Also, FWIW, unless you're explicitly trying to override other settings, you can set these variables as environment variables instead. The MSBuild files can override those if it isn't authored properly, but at least PlatformToolset is correct, and I expect the other two will be too.
PlatformToolset
Sorry, something went wrong.
Actually, I was thinking of using the default clang that comes with VS. The latest VS comes with Clang 19, so it's perfect for this. However, I don't know if the CI runners updated to use the latest VS yet, and I don't want a situation where sometimes we break on older VS and sometimes we don't. So for now, I'll let users manually specify, and maybe in a year or so we can revisit adding a --clang option.