-
Notifications
You must be signed in to change notification settings - Fork 124
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
Windows 2022: couldn't determine visual studio generator #141
Comments
Looks like the error is coming from the |
Thanks, this helped me to fix the same issue by settings |
@aloucks Looks to me like it's not cc but cmake: https://github.com/alexcrichton/cmake-rs/blob/7793895d88acc45d29fac7c711ddaef11c897ea9/src/lib.rs#L610-L621 I assume Vs17 must be added. @nibanks Is your target i686? |
We're just running on a |
Hi, for anyone interested in a temporary solution - just add this patch to your root [patch.crates-io]
cc = { git = "https://github.com/alexcrichton/cc-rs" } |
We use the cmake crate in our CI for building msquic. We just tried updating the Azure Pipeline to use Windows Server 2022 instead of 2019 to build it and the CI failed.
We are getting the following error (from here):
We have no problem with any non-Rust cmake builds, so I suspect this is something specific to the the cmake crate. Do you know of any work around for this? For the time being we can continue to use 2019, but eventually that will be deprecated. Thanks!
The text was updated successfully, but these errors were encountered: